[issue16386] imp.find_module does not specify registry key it searches on windows
New submission from Jan Duzinkiewicz:
quote from http://docs.python.org/3/library/imp.html#imp.find_module:
"...on some systems some other places are looked in as well (on Windows, it looks in the registry which may point to a specific file)."
I actually didn't know the registry key is listed in "using Python on Window" guide until I grepped for PythonCore (which kind of requires to know the key already) - so I'm submitting a patch that cross references find_module docs and using Python on Windows guide.
---------- assignee: docs@python components: Documentation files: import_nt_reg.patch keywords: patch messages: 174508 nosy: dhgmgn, docs@python priority: normal severity: normal status: open title: imp.find_module does not specify registry key it searches on windows versions: Python 2.7, Python 3.3 Added file: http://bugs.python.org/file27843/import_nt_reg.patch
_______________________________________ Python tracker report@bugs.python.org http://bugs.python.org/issue16386 _______________________________________
Changes by Eric Snow ericsnowcurrently@gmail.com:
---------- nosy: +eric.snow
_______________________________________ Python tracker report@bugs.python.org http://bugs.python.org/issue16386 _______________________________________
Andrew Svetlov added the comment:
I think much more important to mention registry key in http://docs.python.org/3/library/importlib.html#importlib.machinery.WindowsR... ``imp`` is private module to access implementation internals but ``importlib`` is public interface to import system
---------- nosy: +asvetlov
_______________________________________ Python tracker report@bugs.python.org http://bugs.python.org/issue16386 _______________________________________
Eric Snow added the comment:
I agree with Andrew.
----------
_______________________________________ Python tracker report@bugs.python.org http://bugs.python.org/issue16386 _______________________________________
Jan Duzinkiewicz added the comment:
Ok, didn't knew much about importlib, I can work on a patch but have a few questions/suggestions:
1. For importlib, simply referencing the "Using on Windows" guide imo won't be ok - the importlib sources show that the key being used is "Software\\Python\\PythonCore\\{sys_version}\\Modules\\{fullname}", while guide refers to \\PythonPath. Am I missing something here? 2. Considering that importlib code is Python, easy to retrieve without having C sources (which is common case on Windows) - do you think this should go into 3.3 docs? 3. Do you think the current version of the patch is applicable to Python 2.7?
----------
_______________________________________ Python tracker report@bugs.python.org http://bugs.python.org/issue16386 _______________________________________
Irit Katriel iritkatriel@yahoo.com added the comment:
Both http://docs.python.org/3/library/importlib.html#importlib.machinery.WindowsR... and http://docs.python.org/3/library/imp.html#imp.find_module:
are now deprecated. Is this issue still relevant?
---------- nosy: +iritkatriel resolution: -> out of date status: open -> pending
_______________________________________ Python tracker report@bugs.python.org https://bugs.python.org/issue16386 _______________________________________
participants (4)
-
Andrew Svetlov -
Eric Snow
-
Irit Katriel
-
Jan Duzinkiewicz