Benjamin Peterson schrieb: > 2009/3/16 Brett Cannon <br...@python.org>: >> At this point importlib is done for its public API for Python 3.1. That >> means it's time to turn my attention to making sure the semantics of import >> are well documented. But where to put all of the details? The language >> reference for import >> (http://docs.python.org/dev/py3k/reference/simple_stmts.html#the-import-statement) >> explains the basics, but is lacking all of the details of PEP 302 and other >> stuff like __path__ that have existed for ages. >> >> My question is if I should flesh out the details in the language reference >> or do it in importlib's intro docs. The main reason I could see not doing it >> in the langauge reference (or at least duplicating it) is it would be >> somewhat easier to reference specific objects in importlib but I am not sure >> if the language reference should try to stay away from stdlib references. > > Thanks so much for doing this! Personally, I think you should put it > in the language reference. (I think it deserves it's own file if it's > as big as I suspect it will be.)
If you asked me, I'd concur with Benjamin. Georg -- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou shalt indent, and the number of thy indenting shall be four. Eight shalt thou not indent, nor either indent thou two, excepting that thou then proceed to four. Tabs are right out. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
