Doc changes are now checked in. Someone who has not been starting at import
for over two years should probably go in and clean it up as it is probably
not clear to a newbie (but then again newbies should not be reading the
language ref; more worried about the docs in sys).
On Mon, Mar 16, 2009 at
2009/3/20 Brett Cannon br...@python.org:
Doc changes are now checked in. Someone who has not been starting at import
for over two years should probably go in and clean it up as it is probably
not clear to a newbie (but then again newbies should not be reading the
language ref; more worried
On Fri, Mar 20, 2009 at 20:18, Benjamin Peterson benja...@python.orgwrote:
2009/3/20 Brett Cannon br...@python.org:
Doc changes are now checked in. Someone who has not been starting at
import
for over two years should probably go in and clean it up as it is
probably
not clear to a newbie
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
Steve Holden wrote:
Why not just put a section in both places that says can't be bothered
to spell this out right now and put a URL in referring to this thread
on Google ... that appears to have been the traditional approach to
import semantics :)
Well, first we point to Guido's original
On Tue, Mar 17, 2009 at 06:55, Nick Coghlan ncogh...@gmail.com wrote:
Steve Holden wrote:
Why not just put a section in both places that says can't be bothered
to spell this out right now and put a URL in referring to this thread
on Google ... that appears to have been the traditional
Brett Cannon wrote:
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
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
On Mon, Mar 16, 2009, Michael Foord wrote:
Personally I would rather see the import semantics themselves in the
language reference.
Either way is fine with me, but it needs to be cross-referenced.
--
Aahz (a...@pythoncraft.com) * http://www.pythoncraft.com/
Adopt A
Brett Cannon wrote:
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
10 matches
Mail list logo
