➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2004-03-19 04:00 by kbk, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| pep008.patch | kbk, 2004-03-19 04:00 | Initial PEP-008 Patch | ||
| Messages (4) | |||
|---|---|---|---|
| msg45602 - (view) | Author: Kurt B. Kaiser (kbk) *  |
Date: 2004-03-19 04:00 | |
Clarify and standardize the format for names of modules, functions, methods, and instance variables. Consistent, I hope, with discussion on python-dev http://mail.python.org/pipermail/python-dev/2004-March/043257.html http://mail.python.org/pipermail/python-dev/2004-March/043259.html |
|||
| msg45603 - (view) | Author: Guido van Rossum (gvanrossum) * |
Date: 2004-03-19 04:54 | |
Logged In: YES user_id=6380 Thanks! Looks good, except that the alternate style for functions and methods is "mixedCase", not "CamelCase". (We may have our definition of CamelCase mixed up, but the point is that the initial letter is lower case.) Go ahead and check it in (if people disagree they can check in an improvement). |
|||
| msg45604 - (view) | Author: Jim Jewett (jimjjewett) | Date: 2004-03-19 17:51 | |
Logged In: YES user_id=764593 Under modules, should there be a parenthetical comment saying either (1) If a module name does include capitals, then it must be named with capitals during import? (2) Many existing module names follow an older CapWords convention, particularly if they export a single class or wrap a C module. |
|||
| msg45605 - (view) | Author: Kurt B. Kaiser (kbk) * |
Date: 2004-03-20 06:53 | |
Logged In: YES user_id=149084 pep-0008.txt 1.21 |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:56:03 | admin | set | github: 40050 |
| 2004-03-19 04:00:41 | kbk | create | |