[issue25759] Python 2.7.11rc1 not building with Visual Studio 2015

Steve Dower added the comment: Checked PCBuild/readme.txt and it's pretty clear that you can only use VS 2010+ with the SDK and the old compiler. So I'm closing this as wontfix as we will not be merging support to build Python 2 with VC10 or later. -- resolution: -> wont fix stage: ne

[issue25759] Python 2.7.11rc1 not building with Visual Studio 2015

Kovid Goyal added the comment: No worries, as I said, I understand, I would probably do the same, were I in your shoes. I have found that being a maintainer of a complex software project tends to naturally increase conservatism :) -- ___ Python trac

[issue25759] Python 2.7.11rc1 not building with Visual Studio 2015

R. David Murray added the comment: Unfortunately it is unlikely we'll merge it, since because of the compiled extension issue we have a negative motivation for supporting anything other than the release compiler currently used. -- ___ Python tracker

[issue25759] Python 2.7.11rc1 not building with Visual Studio 2015

Kovid Goyal added the comment: I take it back, my methodology in reproducing the function calls used by the gzip module was flawed. It does look like a bug in the CRT, but I have not been able to isolate a simple way of reproducing it. I have however, found a workaround for it, that has an a

[issue25759] Python 2.7.11rc1 not building with Visual Studio 2015

Kovid Goyal added the comment: Doesn't seem like a bug in the CRT, I cannot reproduce in a plain CRT program, so now I get to try to figure out what is broken in fileobject.c by VS 2015. That's a relief :) -- ___ Python tracker

[issue25759] Python 2.7.11rc1 not building with Visual Studio 2015

Kovid Goyal added the comment: To answer part of my question, the reason the fseek()+fread() bug does not affect python 3.5.0 appears to be because it implements its own buffering and does not use fseek()/fread() at all. Sigh, I really hope the answer does not end up being that I have to re-

[issue25759] Python 2.7.11rc1 not building with Visual Studio 2015

Kovid Goyal added the comment: Yes, I am aware. I embed python in my application, which includes large C++ libraries. Those libraries are going to start requiring to be compiled with a modern compiler soon, which means I need python to also be compiled with a modern compiler. I already manuall

[issue25759] Python 2.7.11rc1 not building with Visual Studio 2015

R. David Murray added the comment: You are aware that you can't use existing pre-compiled extension modules with your 2015 build, right? It would be great if you could open a separate issue for the double close problem. This should be a doc issue for fixing the docs. -- assignee: ->

[issue25759] Python 2.7.11rc1 not building with Visual Studio 2015

Kovid Goyal added the comment: I missed a few places in my initial patch, updated patch: https://github.com/kovidgoyal/cpython/commit/a9ec814d466d3c0139d10b69666f88eed10e4940 Also fixed the code not clearing errno before calling CRT functions, while I was there. Regardless of whether you want t

[issue25759] Python 2.7.11rc1 not building with Visual Studio 2015

Kovid Goyal added the comment: I have it building with just two simple patches: https://github.com/kovidgoyal/cpython/commit/fd1ceca4f21135f12ceb72f37d4ac5ea1576594d https://github.com/kovidgoyal/cpython/commit/edb740218c04b38aa0f385188103100a972d608c However, in developing the patches, I disc

[issue25759] Python 2.7.11rc1 not building with Visual Studio 2015

Steve Dower added the comment: Not off the top of my head, but you only really need to look at my commits, and looking for issues assigned to me is an easy way to find those. Most of the issues are obvious once you start trying to build. -- ___ Pyth

[issue25759] Python 2.7.11rc1 not building with Visual Studio 2015

Kovid Goyal added the comment: OK, I had hoped to avoid having to maintain my own fork of python 2 for a while longer, but, I guess not. Could you at least tell me if there are any other issues I should be aware of, to avoid me having to search through the python 3 sourcecode/commit history.

[issue25759] Python 2.7.11rc1 not building with Visual Studio 2015

Steve Dower added the comment: The proper fix is to remove any hint in the readme file that this will work. Building 2.7 with VS 2015 will not work unless someone forks CPython and makes the updates themselves. -- ___ Python tracker

[issue25759] Python 2.7.11rc1 not building with Visual Studio 2015

Changes by SilentGhost : -- components: +Build, Windows nosy: +paul.moore, steve.dower, tim.golden, zach.ware ___ Python tracker ___ _

[issue25759] Python 2.7.11rc1 not building with Visual Studio 2015

New submission from Kovid Goyal: The Pcbuild/readme.txt file implies that it is possible to build python 2.7.11rc1 with Visual Studio 2015 (although it is not officially supported). However, there are at least a couple of problems, that I have encountered so far: 1) timemodule.c uses timezone