Changes by Brett Cannon br...@python.org:
--
resolution: - invalid
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12648
___
kota nospam.kotarou.d...@gmail.com added the comment:
Ok. Time to get those people over at glib to fix up their python script then :)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12648
kota nospam.kotarou.d...@gmail.com added the comment:
Yea, it runs the parser.py that time. And I didn't understand the page you
linked me to. Would you mind explaining it a bit?
--
___
Python tracker rep...@bugs.python.org
Nick Coghlan ncogh...@gmail.com added the comment:
The Windows build actually uses the registry to locate the standard library
rather than sys.path. This is by design, but isn't really documented properly.
It means that code on sys.path (even in the current directory) won't shadow
standard
kota nospam.kotarou.d...@gmail.com added the comment:
So there isn't any way to load parser.py via import parser on Windows?
--
components: +None -Documentation
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12648
Nick Coghlan ncogh...@gmail.com added the comment:
As far as I know, not as a top-level module in an installed version of Python
(at least, not without mucking about in the registry).
Shadowing standard library modules is generally a bad idea, and this is one of
the reasons.
--
Nick Coghlan ncogh...@gmail.com added the comment:
It's actually the documentation that's slightly wrong in this case. On Windows,
there is an additional import mechanism based on the Windows registry that is
checked before the ordinary sys.path mechanism. (See
Changes by Éric Araujo mer...@netwok.org:
--
nosy: +brett.cannon, ncoghlan
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12648
___
___
New submission from kota nospam.kotarou.d...@gmail.com:
There seems to be a wrong import module search order
(http://docs.python.org/tutorial/modules.html#the-module-search-path) on
Windows. Python seems to be loading the built-in module instead of the python
code with the same name as the
