[issue26108] Calling PyInitialize with 2.7.11 on Windows x64 terminates process

Steve Dower added the comment: That's true, though if you use the embeddable distribution of Python 3.5 you automatically get the equivalent behavior because of a new option (the "applocal" option in pyvenv.cfg, which is enabled in that distro by default). --

[issue26108] Calling PyInitialize with 2.7.11 on Windows x64 terminates process

David Heffernan added the comment: Thanks for following up Steve, and thanks for changing resolution to dupe. As for 3.5 and embedding the docs are much the same as 2.7 in that the example code at https://docs.python.org/3/extending/embedding.html doesn't explicitly set Python home.

[issue26108] Calling PyInitialize with 2.7.11 on Windows x64 terminates process

Changes by Eryk Sun : -- stage: -> resolved ___ Python tracker ___ ___

[issue26108] Calling PyInitialize with 2.7.11 on Windows x64 terminates process

Changes by Eryk Sun : -- resolution: not a bug -> duplicate superseder: -> 32-bit 2.7.11 installer creates registry keys that are incompatible with the installed python27.dll ___ Python tracker

[issue26108] Calling PyInitialize with 2.7.11 on Windows x64 terminates process

David Heffernan added the comment: Why was this closed as "not a bug"? Shouldn't it have been closed as a duplicate? -- ___ Python tracker ___

[issue26108] Calling PyInitialize with 2.7.11 on Windows x64 terminates process

Changes by Steve Dower : -- resolution: -> not a bug status: open -> closed ___ Python tracker ___

[issue26108] Calling PyInitialize with 2.7.11 on Windows x64 terminates process

David Heffernan added the comment: Thanks Eryk, everything you described happens exactly as you describe it. Much appreciated. As it happens, I'm not distributing Python because I want to give my users the flexibility to use whatever version they please, and with whatever third party modules

[issue26108] Calling PyInitialize with 2.7.11 on Windows x64 terminates process

David Heffernan added the comment: Note that I've just listed the Windows versions on which I have tested this. I have not tested on Windows 7 or Vista so do not know whether or not the issue exists there. -- ___ Python tracker

[issue26108] Calling PyInitialize with 2.7.11 on Windows x64 terminates process

New submission from David Heffernan: Environment: - Python 2.7.11 from python.org, x64. - Windows 10 or Windows 8.1 - MSVC 2015 I compiled the most basic embedding example, taken from the Python docs: #include int main(int argc, char *argv[]) { Py_SetProgramName(argv[0]); /* optional

[issue26108] Calling PyInitialize with 2.7.11 on Windows x64 terminates process

Eryk Sun added the comment: Probably this is related to issue 25824. When built as a console application and run from the command prompt, you should see an the error ImportError: No module named site If that's the case, the problem is that even the 64-bit build is incorrectly setting the