AlexWMF added the comment:
I found the following PEP https://www.python.org/dev/peps/pep-0514/
According to this PEP, starting from python 2.7.11 the backward compatibility
was broken, because .dll can't read from the following registry keys anymore:
HKEY_LOCAL_MACHINE\Software\P
AlexWMF added the comment:
The output of both x86 and x86_64 python interpreters is attached
--
Added file: http://bugs.python.org/file42814/Clipboard29.png
___
Python tracker
<http://bugs.python.org/issue26
AlexWMF added the comment:
Could you provide link to that PEP?
As I posted in the previous message, both x86 and x86_64 python27.dll have
version string "2.7-32" (shown in sys.winver). Is this right? Any of installers
(x86 nor x86_64) don't create "2.7-32" subkey.
AlexWMF added the comment:
I've checked the x86_64 version of python27.dll.
It contains "2.7-32" as well as x86 python dll. So strange, seems like "-32" is
always there, independently of target bitness.
--
___
Python tracker
New submission from AlexWMF:
Unable to import "site" error occurs in an embedded application.
I have made small research and found why this module isn't visible for python
core.
I have run the python 2.7.11 x86 (for all users) at my win 7x64.
The installer writes the registry
