[issue8370] change module builtins to __builtin__ in __import__ documentation

2010-04-14 Thread Nick Coghlan
Changes by Nick Coghlan ncogh...@gmail.com: -- nosy: +ncoghlan ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8370 ___ ___ Python-bugs-list mailing

[issue8370] change module builtins to __builtin__ in __import__ documentation

2010-04-14 Thread Georg Brandl
Georg Brandl ge...@python.org added the comment: Thanks, fixed in r80082. The builtins rename happened in 3.0; there are no version added or version changed marks for 3.0 in the docs, since we regard it as a clean start. -- resolution: - fixed status: open - closed

[issue8370] change module builtins to __builtin__ in __import__ documentation

2010-04-13 Thread Daniel Diniz
Changes by Daniel Diniz aja...@gmail.com: -- priority: - normal stage: - patch review ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8370 ___ ___

[issue8370] change module builtins to __builtin__ in __import__ documentation

2010-04-11 Thread Chris Jerdonek
New submission from Chris Jerdonek chris.jerdo...@gmail.com: The builtins module referenced in the Python 2.6 __import__ documentation does not seem to exist in Python 2.6: http://docs.python.org/library/functions.html#__import__ These should probably be changed to __builtin__:

[issue8370] change module builtins to __builtin__ in __import__ documentation

2010-04-11 Thread Chris Jerdonek
Changes by Chris Jerdonek chris.jerdo...@gmail.com: -- assignee: - georg.brandl components: +Documentation nosy: +georg.brandl ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8370 ___

[issue8370] change module builtins to __builtin__ in __import__ documentation

2010-04-11 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: You’re right. This module name has been fixed in the 3.x branch (it used a magic name without reason); when importlib was backported from 3.1 to 2.6, this change must have been overlooked. Are you willing to produce a patch? Regards

[issue8370] change module builtins to __builtin__ in __import__ documentation

2010-04-11 Thread Chris Jerdonek
Chris Jerdonek chris.jerdo...@gmail.com added the comment: Replaced builtins with __builtin__. Also inserted a missing the. -- keywords: +patch Added file: http://bugs.python.org/file16870/_issue-8370-1.diff ___ Python tracker rep...@bugs.python.org

[issue8370] change module builtins to __builtin__ in __import__ documentation

2010-04-11 Thread Chris Jerdonek
Chris Jerdonek chris.jerdo...@gmail.com added the comment: Thanks for the info and quick response. Then this should probably also be applied to trunk (Python 2.7). -- versions: +Python 2.7 ___ Python tracker rep...@bugs.python.org

[issue8370] change module builtins to __builtin__ in __import__ documentation

2010-04-11 Thread Chris Jerdonek
Chris Jerdonek chris.jerdo...@gmail.com added the comment: Would it make sense to put a New in version 3.1 at the top of this page: http://docs.python.org/py3k/library/builtins.html (perhaps also with a note explaining that the module replaces __builtin__). I actually wasn't able to confirm

[issue8370] change module builtins to __builtin__ in __import__ documentation

2010-04-11 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: (perhaps also with a note explaining that the module replaces __builtin__) People used to 2.x will know about the name change; people new to Python with 3.x (the happy ones!) will not this this information, except perhaps to understand outdated

[issue8370] change module builtins to __builtin__ in __import__ documentation

2010-04-11 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: Your first patch seems good to me; wait for a core developer’s answer before taking time to add notes about renamed modules everywhere. Cheers -- ___ Python tracker rep...@bugs.python.org