[Python-Dev] Backporting the 3.5+ Windows build project files to 2.7
Nick Coghlan
ncoghlan at gmail.com
Tue Jun 23 05:37:43 CEST 2015
More information about the Python-Dev mailing list
Tue Jun 23 05:37:43 CEST 2015
- Previous message (by thread): [Python-Dev] Backporting the 3.5+ Windows build project files to 2.7
- Next message (by thread): [Python-Dev] Backporting the 3.5+ Windows build project files to 2.7
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 23 June 2015 at 11:45, Zachary Ware <zachary.ware+pydev at gmail.com> wrote: > On Mon, Jun 22, 2015 at 6:29 PM, Chris Barker - NOAA Federal > <chris.barker at noaa.gov> wrote: >>> I'd like to backport those new project files to 2.7, >> >> Would this change anything about how extensions are built? >> >> There is now the "ms compiler for 2.7" would that work? Or only in >> concert with VS2010 express? > > It should have absolutely no impact on building extensions. If it > does, that's a bug to be fixed. Regular users of Python on Windows > (those who don't build their own) should have no idea that anything > has changed at all. I'd suggest explicitly reaching out to the Stackless folks to get their feedback. As I believe the switched to a newer compiler and VC runtime for Windows a while back, I suspect it will make their lives easier rather than harder, but it's still worth asking for their input. Regards, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message (by thread): [Python-Dev] Backporting the 3.5+ Windows build project files to 2.7
- Next message (by thread): [Python-Dev] Backporting the 3.5+ Windows build project files to 2.7
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list