I have python embeded intro my application. I wanted to upgrade to python 2.7.12 i use also a static library. Not DLL.  I have defined "Py_NO_ENABLE_SHARE"
Ok, all work fine with 2.7.6

I want to say this error happen just when i run it under windows xp.
Under windows 10 it works , my application start.. Pythoncore and application is build with v140_xp toolset i user visual studio 2015. I can make a video with error if is necessary. Thanks.

Traceback (most recent call last):
  File "Lib/site.py", line 548, in <module>
  File "Lib/site.py", line 537, in main
  File "Lib/site.py", line 465, in aliasmbcs
  File "Lib/locale.py", line 13, in <module>
ImportError: No module named encodings


I made more test and i come with a reply.

I tested again. And the answer is this: Problem is stati library.

I tested:
- 2.7.6
- 2.7.7
- 2.7.8
- 2.7.9
- 2.7.10
- 2.7.11
- 2.7.12

This issue happen just when pythoncore is compiled as static library. With DLL it works.

Is the stati library a third-party project?

You're compiling Python in a completely unsupported way right now, so I'm afraid you'll need to submit a patch to get it fixed.

Python 2.7 is only officially supported with VC 9.0 (not VC 14.0), and I don't believe the other volunteers test the static library build either, so I'm afraid you're somewhat on your own.

That said, if you do find a fix and submit a patch, it may be merged in. However, to even be able to build with VC 14.0 you've probably made a great number of changes that certainly won't be accepted at this stage.

It's ok for me to use  vc .9 but when i try to link it says  "  This library was created with an older visual stuido toolset " And it trow in a error.



And about v140 compatibility i don't maded so much changes. It was 3 minutes of work.

Maybe someone take a look, i'm new in c++ development and python too. I don't think i'm able to find a fix.

Maybe some ideea about how to make vs2015 to link with a library from vc 9.0 ?

Unfortunately, you can't do that either. Projects including static libraries all need to use the same compiler.

So either build python27.dll separately and dynamically link to it (or just use the one that we build and release, and be careful not to mix up memory or file management functions as they will be incompatible), build everything with VS 9.0, or you'll need help to find a fix.

Most - possibly all - of our volunteers are not going to be willing to go deep on custom Python 2.7 build issues. You're probably going to have to find someone who can offer paid support.

Thanks, i don't think is a big issue.  Because on windows 7, 8 , 8.1 , 10 it works.

Just with windows xp i have this issue.

It's ok paid. No problem, soo if someone want to fix for me this :  Sure paid contact me please.

And someone want to do it free contact me too and we will submit a patch to help all users. 

Even paid i will share the fix.  

Regards.

Still searching for someone who can do it.

As 2.7 has now reached end-of-life and with it the last version to support Windows XP, I'm closing the issue.