Re: Compiling new Pythons on old Windows compilers
On 03/12/2017 09:26 PM, Michael Torrie wrote: > On 03/12/2017 02:45 PM, eryk sun wrote: >> On Sun, Mar 12, 2017 at 5:02 PM, Eric Frederich >> wrote: >>> Any idea why compatibility was dropped recently? There used to be a PC >>> directory with different VS directories in the source tree, now it isn't >>> there any more. >> >> CPython 3.5+ uses the Universal CRT on Windows, which is a system >> component in Vista and later (a recommended update for Windows >> versions prior to 10). See this blog post: >> >> http://stevedower.id.au/blog/building-for-python-3-5 Did I read that right that you can link python statically so you can use the new universal runtime-based python to extend an app with another runtime (but requiring administrator access somehow?)? -- https://mail.python.org/mailman/listinfo/python-list
Re: Compiling new Pythons on old Windows compilers
On 03/12/2017 02:45 PM, eryk sun wrote: > On Sun, Mar 12, 2017 at 5:02 PM, Eric Frederich > wrote: >> Any idea why compatibility was dropped recently? There used to be a PC >> directory with different VS directories in the source tree, now it isn't >> there any more. > > CPython 3.5+ uses the Universal CRT on Windows, which is a system > component in Vista and later (a recommended update for Windows > versions prior to 10). See this blog post: > > http://stevedower.id.au/blog/building-for-python-3-5 Hmm, this is going to be a huge problem for Python users that work with proprietary software that is fixed to specific versions of MSCVRT. The idea that everyone should just update their builds to the latest universal runtime is a good one, but it's just not going to happen across the entire software industry anytime soon. Especially for existing releases. Looks like Python 3 is a no go for Eric. The runtime mixing issue has always been a problem for Windows developers. Not sure the universal runtime really solves it! -- https://mail.python.org/mailman/listinfo/python-list
Re: Compiling new Pythons on old Windows compilers
On Sun, Mar 12, 2017 at 5:02 PM, Eric Frederich wrote: > Any idea why compatibility was dropped recently? There used to be a PC > directory with different VS directories in the source tree, now it isn't > there any more. CPython 3.5+ uses the Universal CRT on Windows, which is a system component in Vista and later (a recommended update for Windows versions prior to 10). See this blog post: http://stevedower.id.au/blog/building-for-python-3-5 -- https://mail.python.org/mailman/listinfo/python-list
Compiling new Pythons on old Windows compilers
There is a commercial application which allows customizations through a C API. There are 3 different releases of this application each compiled with different versions of Visual Studio, 2008, 2010, and 2012. I'd like to release a customization which embeds a Python interpreter, but I'd like to use the same Python release across all 3 application versions. There may be versions of Python like 2.7 or something which compile on all 3 of those Visual Studio releases, but I'd really prefer to use Python 3. Any idea why compatibility was dropped recently? There used to be a PC directory with different VS directories in the source tree, now it isn't there any more. Thanks, ~Eric -- https://mail.python.org/mailman/listinfo/python-list
