Comments on: .gitignore for Python developers

By: python developers

python developers — Fri, 02 Sep 2011 13:28:11 +0000

luckily i found this article and it helps me a lot to learn from you.helps me a lot thank you.

By: Ned

Ned — Fri, 23 Jul 2010 12:40:33 +0000

If you are using coverage.py to measure code coverage, then you’ll also want to ignore:

.coverage

and probably:

htmlcov

If you are building C extensions, then add:

*.pyd *.so

By: Hanno Schlichting

Hanno Schlichting — Fri, 23 Jul 2010 12:11:08 +0000

I have “dist” in addition, which gets created whenever you make a release. You also could ignore virtualenv things as well: “.Python include lib” and finally I have “local.cfg” in my list.

By: Dan MacKinlay

Dan MacKinlay — Fri, 23 Jul 2010 12:04:45 +0000

I don’t know if it belongs here, but I usually also ignore
*.LCK
*.lck

to avoid fallout from dreamweaver users with whom i may share my source tree. (Yup, web developer here)

By: Maurits van Rees

Maurits van Rees — Fri, 23 Jul 2010 10:26:46 +0000

Oh, and since you are ignoring .bzr and .hg, you will want to ignore their ignore files as well, so:
.bzrignore
.hgignore

By: Maurits van Rees

Maurits van Rees — Fri, 23 Jul 2010 10:23:57 +0000

For emacs users:
*~
And perhaps:
*.bak

By: Peter

Peter — Fri, 23 Jul 2010 09:59:41 +0000

How about Jython class files (*.class, the equivalent of *.pyc)?

And if any of the developers use Mac OS X, ignore the .DS_Store folders.