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.

Author ncoghlan
Recipients ncoghlan
Date 2013-07-16.12:14:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1373976870.86.0.835797297745.issue18472@psf.upfronthosting.co.za>
In-reply-to
Content
Attached diff has 5 changes:

* Explicit note that this is a living document that evolves over time
* Adds another explicit reason for not complying with the style guide (i.e. the code is old but still works and there's no other reason to change it)
* Fixed outdated info in the Tabs & Spaces section (Python 3 doesn't allow mixing them at all)
* Added an admonishment to avoid import *
* Added a new "Public and internal interfaces" section, that leans more heavily on documentation and __all__ than any of the proposals posted to python-dev

Some other oddities I noticed:

- given PEP 352, the admonishment to avoid string exceptions seems old and outdated. Can we just drop that?
- given PEP 3151, the suggestion to create a "domain specific base class" for the module also seems ill-advised. Perhaps we should remove that too?
- I've never understood the rationale for favouring absolute imports over explicit relative ones, so I had forgotten that suggestion was even in here. I've raised that one on python-dev, since I recall it being controversial, although I've never been able to fathom why. Explicit relative imports are just *better* in every way whenever they're applicable.
History
Date User Action Args
2013-07-16 12:14:31ncoghlansetrecipients: + ncoghlan
2013-07-16 12:14:30ncoghlansetmessageid: <1373976870.86.0.835797297745.issue18472@psf.upfronthosting.co.za>
2013-07-16 12:14:30ncoghlanlinkissue18472 messages
2013-07-16 12:14:30ncoghlancreate