Marc-Andre Lemburg added the comment: On 16.11.2013 14:25, Nick Coghlan wrote: > > Nick Coghlan added the comment: > > Another big one: the encodings module API is not documented in the prose > docs, and nor is the interface between the default search function and the > individual encoding definitions. There's some decent info in help(encoding) > though. > > The interaction with the import system could also be documented better - you > can actually blacklist codecs by manipulating sys.modules and the encodings > namespace, and you can search additional locations for codec modules by > manipulating encodings.__path__ (even without it being declared as a > namespace package)
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. ---------- nosy: +lemburg _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue19548> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
