Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #38062 > unrolled thread
| Started by | dieter <dieter@handshake.de> |
|---|---|
| First post | 2013-02-02 09:03 +0100 |
| Last post | 2013-02-02 09:03 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: CamelCase vs. all-lowercase package names dieter <dieter@handshake.de> - 2013-02-02 09:03 +0100
| From | dieter <dieter@handshake.de> |
|---|---|
| Date | 2013-02-02 09:03 +0100 |
| Subject | Re: CamelCase vs. all-lowercase package names |
| Message-ID | <mailman.1287.1359792233.2939.python-list@python.org> |
Rhubarb Sin <rhubarbsin@gmail.com> writes: > PEP-8 calls for "short, all-lowercase names" for packages: > > http://www.python.org/dev/peps/pep-0008/#package-and-module-names This is mainly to support case insensitive file systems (and file systems with quite limited path length). With mixed case, some packages/modules may not conflict on a case sensitive file system but happen to conflict on a case insensitive file system.
Back to top | Article view | comp.lang.python
csiph-web