Kevin Phillips added the comment:
This change has the adverse side effect of requiring users of Python 3.5 to use
the Visual Studio 2015 runtime library. Further, as is documented on
Microsoft's website, the minimum system requirements for installing and running
this runtime is Windows 7 SP1
Steve Dower added the comment:
The check is already added and will be in 3.5.1.
Changes to the python.org website should be suggested on
https://github.com/python/pythondotorg (but I agree it could be more clear on
the main site - the rule that we only support the same versions of Windows
Steve Dower added the comment:
Closing again, as Victor's issue was resolved (VS 2010 SP1 is needed, and I'm
updating the devguide to specify that on #23257).
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
Steve Dower added the comment:
I do have Windows 7 SP1.
I expected so, but didn't want to assume.
I have VS 2010 *Express* and I'm now able to open the project after
installing the Service Pack 1 of VS 2010.
Glad to hear it. You made me a little nervous there :) (I don't feel like
STINNER Victor added the comment:
You will need Windows 7 *SP1*
I do have Windows 7 SP1.
There is also a service pack for VS 2010 that may enable opening the newer
solution - it certainly worked for me.
Oh, I also worked for me. I have VS 2010 *Express* and I'm now able to open the
Zachary Ware added the comment:
STINNER Victor added the comment:
Note: The binary (in debug mode) moved from PCbuild\python_d.exe to
PCbuild\win32\python_d.exe
There ought to be a 'python.bat' in the root of the source tree that
will always point to the last-built python[_d].exe, which may
STINNER Victor added the comment:
Visual Studio 2013 Professional works fine under Windows 7 SP1 here.
Ok, good to know. But is it correct that the free version of VS 2013
(community) requires Windows 8.1 or newer? It's not cool to require to upgrade
Windows to being able to freely compile
Mark Lawrence added the comment:
@Victor I don't know what version you need for Windows 7 or earlier but I can
tell you that VS 2013 Community edition is *NOT* free, I fell into that trap
myself, you need the Express edition.
--
___
Python tracker
Antoine Pitrou added the comment:
Visual Studio 2013 Professional works fine under Windows 7 SP1 here.
--
nosy: +pitrou
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22919
___
Steve Dower added the comment:
You will need Windows 7 *SP1*, as I don't think VS will run without the
updates. There is also a service pack for VS 2010 that may enable opening the
newer solution - it certainly worked for me.
We decided not to keep the old project files as they weren't being
STINNER Victor added the comment:
Hi, I'm no more able to compile Python 3.5 on Windows. I have Visual Studio
2008 Express, Visual Studio 2010 Express. VS 2010 is unable to open
PCbuild/pcbuild.sln: it says that the file was created on a more recent Visual
Studio version and it is unable to
STINNER Victor added the comment:
Oh by the way, 2 Windows buildbot slaves are no more able to compile Python. I
don't know if it's related to this issue or not.
Builder AMD64 Windows7 SP1 3.x, owned by Jeremy Kloth:
http://buildbot.python.org/all/builders/AMD64%20Windows7%20SP1%203.x
2LINK
Steve Dower added the comment:
Just emailed Jeremy about the buildbot. It looks like the last time tests were
run something didn't clean up properly and left the build output locked.
There's nothing wrong with the project files.
--
___
Python
Changes by Trent Nelson tr...@snakebite.org:
--
nosy: +trent
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22919
___
___
Python-bugs-list mailing
Roundup Robot added the comment:
New changeset 5754f069b123 by Steve Dower in branch 'default':
Issue #22919: Windows build updated to support VC 14.0 (Visual Studio 2015),
which will be used for the official 3.5 release.
https://hg.python.org/cpython/rev/5754f069b123
--
nosy:
Steve Dower added the comment:
I'll be closely tracking any issues that arise out of this throughout the next
couple of days, but it should be fairly smooth (especially for people who don't
upgrade VS immediately). There are certainly a few things that are broken, but
I'll make separate
Steve Dower added the comment:
Rebased and updated NEWS, so here's a complete patch (and it's all in the
latest change in https://hg.python.org/sandbox/steve.dower#Projects)
--
Added file: http://bugs.python.org/file37405/round7complete.diff
___
Steve Dower added the comment:
Small incremental patch from Zach's feedback and a few sysconfig changes I
missed.
--
Added file: http://bugs.python.org/file37392/round6incremental.patch
___
Python tracker rep...@bugs.python.org
Zachary Ware added the comment:
Sorry Steve, I haven't been on Windows since my last review to give it
another try. And, of course, somewhere in the 5 seconds between shutting
down from Gentoo and turning back on for Windows last night, my laptop
decided that POSTing was just too much effort,
Steve Dower added the comment:
Rebased everything onto default and pushed it to my sandbox.
--
hgrepos: +283
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22919
___
Changes by Steve Dower steve.do...@microsoft.com:
--
hgrepos: -283
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22919
___
___
Python-bugs-list
Steve Dower added the comment:
Having trouble getting the patch uploaded... next attempt.
--
Added file: http://bugs.python.org/file37374/round5complete.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22919
Steve Dower added the comment:
Does anyone else want to provide any feedback? Or should I go ahead and get it
in (after rebasing/retesting/etc.)? The feedback so far has been really helpful.
--
___
Python tracker rep...@bugs.python.org
Steve Dower added the comment:
After a debug build with VS2015, my biggest concern is this:
..\PC\bdist_wininst\install.rc(19): fatal error RC1015: cannot open
include file 'afxres.h'. [P:\ath\to\cpython\PCbuild\bdist_wininst.vcxproj]
I thought I had a workaround for this, but I'll have
Zachary Ware added the comment:
Another round of review posted on Rietveld. I'll try to get the VS2015 preview
downloaded today and give some more feedback after using it.
Just one inconsequential note on python3.diff: the 'lib' command in
python3dll.vcxproj could use a '/nologo' flag.
Zachary Ware added the comment:
After a debug build with VS2015, my biggest concern is this:
..\PC\bdist_wininst\install.rc(19): fatal error RC1015: cannot open include
file 'afxres.h'. [P:\ath\to\cpython\PCbuild\bdist_wininst.vcxproj]
There's also a slew of new warnings, mostly C4456 and
Steve Dower added the comment:
After a debug build with VS2015, my biggest concern is this:
..\PC\bdist_wininst\install.rc(19): fatal error RC1015: cannot open
include file 'afxres.h'. [P:\ath\to\cpython\PCbuild\bdist_wininst.vcxproj]
I thought I had a workaround for this, but I'll have
Steve Dower added the comment:
Added changes from Zach's last review.
Highlight: I deleted the make_versioninfo project and build step :)
--
Added file: http://bugs.python.org/file37270/round4.diff
___
Python tracker rep...@bugs.python.org
Changes by Jeremy Kloth jeremy.kloth+python-trac...@gmail.com:
--
nosy: +jkloth
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22919
___
___
Steve Dower added the comment:
Added some fixes to the python3.dll build (and xxlimited test project) which I
noticed thanks to Antoine's feedback.
--
Added file: http://bugs.python.org/file37265/python3.diff
___
Python tracker
New submission from Steve Dower:
I've basically finished the core of the work to refresh the PCBuild project
files and support building with VS 2015, and I believe it's ready to merge in.
Though the title says VS 2015, builds will work fine with VS 2010 and VS 2013
(and probably VS 2012, but
Changes by Steve Dower steve.do...@microsoft.com:
Added file: http://bugs.python.org/file37247/projects_full.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22919
___
Steve Dower added the comment:
Oh, one other thing I just thought of: the current release of nmake (in VS
2015) has a regression that will make TCL and TK fail to build, but I have a
workaround for their makefile. OpenSSL also had a problem with VC14 but their
fix isn't in the build we've got
Changes by Mark Lawrence breamore...@yahoo.co.uk:
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22919
___
___
Changes by Martin Dengler mar...@martindengler.com:
--
nosy: +mdengler
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22919
___
___
Steve Dower added the comment:
Fixed and pushed a minor issue with debug builds - I wasn't setting the 'g'
suffix on the tcltk libs correctly.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22919
Steve Dower added the comment:
Pushed some changes based on Zach's feedback and added a new complete patch
(minus the deletion of the PC/VS9.0 and PC/VS10.0 folders).
--
Added file: http://bugs.python.org/file37251/cpython_93607_to_93616.diff
___
37 matches
Mail list logo
