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 BreamoreBoy, docs@python, lemburg, ncoghlan, zuo
Date 2013-11-16.14:55:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CADiSq7ftH0v0pDBn4AjawRxv78pyDAo0-Jd8N4TMXYPSDYb3=g@mail.gmail.com>
In-reply-to <52877416.9070908@egenix.com>
Content
On 16 November 2013 23:33, Marc-Andre Lemburg <report@bugs.python.org> wrote:
> On 16.11.2013 14:25, Nick Coghlan wrote:
> Those were not documented on purpose, since they are an implementation
> detail of the encodings package search function.
>
> If you document them now, you'll set the implementation in stone,
> making future changes to the logic difficult. I'd advise against
> this to stay flexible, unless you want to open up the encodings
> package as namespace package - then you'd have to add documentation
> for the import interface.

Yes, that was what got me thinking along those lines, but to make that
possible, the contents of encodings/__init__.py would need to be moved
somewhere else. So this probably isn't on the table for 3.4.
History
Date User Action Args
2013-11-16 14:55:12ncoghlansetrecipients: + ncoghlan, lemburg, zuo, docs@python, BreamoreBoy
2013-11-16 14:55:12ncoghlanlinkissue19548 messages
2013-11-16 14:55:12ncoghlancreate