Author AlexWMF
Recipients AlexWMF, paul.moore, r.david.murray, steve.dower, tim.golden, zach.ware
Date 2016-05-11.13:13:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1462972390.85.0.836623911939.issue26998@psf.upfronthosting.co.za>
In-reply-to
Content
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.

I understand that python should work without set up of sys.path from the registry, but after start of embedded python instance, sys.path don't have any valid path where 'c:\Python27x64\lib' folder resides. sys.path have ['c:\windows\system32\python27.zip', '.\Dlls', '.\Lib\'] and '.\\' expands to current application directory.
But directory is always different, not points to the python home.
When start the application which embeds x86_64 python, it just exits because can't find the 'site' module when tried to perform Py_InitializeEx(0).
History
Date User Action Args
2016-05-11 13:13:10AlexWMFsetrecipients: + AlexWMF, paul.moore, tim.golden, r.david.murray, zach.ware, steve.dower
2016-05-11 13:13:10AlexWMFsetmessageid: <1462972390.85.0.836623911939.issue26998@psf.upfronthosting.co.za>
2016-05-11 13:13:10AlexWMFlinkissue26998 messages
2016-05-11 13:13:10AlexWMFcreate