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.

I think much more important to mention registry key in http://docs.python.org/3/library/importlib.html#importlib.machinery.WindowsRegistryFinder 
``imp`` is private module to access implementation internals but ``importlib`` is public interface to import system

I agree with Andrew.

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?

Both 
http://docs.python.org/3/library/importlib.html#importlib.machinery.WindowsRegistryFinder 
and 
http://docs.python.org/3/library/imp.html#imp.find_module:

are now deprecated. Is this issue still relevant?