Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #38041 > unrolled thread
| Started by | Rhubarb Sin <rhubarbsin@gmail.com> |
|---|---|
| First post | 2013-02-01 10:04 -0500 |
| Last post | 2013-02-01 10:04 -0500 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
CamelCase vs. all-lowercase package names Rhubarb Sin <rhubarbsin@gmail.com> - 2013-02-01 10:04 -0500
| From | Rhubarb Sin <rhubarbsin@gmail.com> |
|---|---|
| Date | 2013-02-01 10:04 -0500 |
| Subject | CamelCase vs. all-lowercase package names |
| Message-ID | <mailman.1279.1359731070.2939.python-list@python.org> |
PEP-8 calls for "short, all-lowercase names" for packages: http://www.python.org/dev/peps/pep-0008/#package-and-module-names On the other hand, The Hitchhiker's Guide to Packaging 1.0, under "Background," declares "come up with a CamelCase project name": http://guide.python-distribute.org/creation.html On PyPi, of course, there is great variation. At this point is there a more formal recommendation for a package naming convention?
Back to top | Article view | comp.lang.python
csiph-web