On 11/03/2015 21:59, polyver...@gmail.com wrote:
On Sunday, March 8, 2015 at 7:51:17 PM UTC+1, Mark Lawrence wrote:
On 08/03/2015 17:57, polyver...@gmail.com wrote:
On Saturday, March 7, 2015 at 5:36:07 PM UTC+1, Mark Lawrence wrote:
On 07/03/2015 15:55, polyver...@gmail.com wrote:
Out of curiosity, is there any plan to use a more recent version of Visual
Studio (i.e.: 2013) to compile the official Python3 distribution for Windows?
Is it in discussion? Maybe waiting for the 2015 version?
I'm working on a C++ software that embeds Python3, currently compiled with
MSVC2010 and would like to upgrade to MSVC2013, but it appears that, while
being feasible, Python3 won't compile out of the box with that configuration. I
would like to avoid that hassle if possible...
Cheers,
I'm building Python 3.5 every day with 2013 no problems at all, thanks
mainly to the work on the build system by Zach Ware and Steve Dower. If
2015 is stable that will be used for 3.5 else we'll stick with 2013.
--
My fellow Pythonistas, ask not what our language can do for you, ask
what you can do for our language.
Mark Lawrence
For the record, I successfully compiled v3.5.0a1 (the latest 3.5 candidate as of today)
with a fresh install of msvc2013. I ran the PCbuild/get_externals.bat script manually
then opened the pcbuild.sln to launch a "Release/x64" build.
Note that I had to launch the global build twice since the first one failed due to
<tcl.h> header not found during _tkinter build. Re-launching the global build
without modifying any setting/property just did the job flawlessly.
http://bugs.python.org/issue23452
As a quick test, I copied the built binaries (python.exe, .dll and .pyd files)
in a new directory, as well as the content of the Lib folder. Then I started an
interpreter session and typed some random imports. It all worked like a charm.
Thank you for your answers.
No problem :)
--
My fellow Pythonistas, ask not what our language can do for you, ask
what you can do for our language.
Mark Lawrence
It seems I encountered issue #17797:
http://bugs.python.org/issue17797
Should I update the bug with my config? (i.e.: native x64 GUI application
embedding version 3.5a2, built with MSVC2013 SP4)
Don't even know if I can as a guest...
Just create yourself a login, doesn't take five minutes, ask the
occasional spammer who gets in :)
It is unclear to me whether or not a workaround will be implemented in 3.5
branch for pre-MSVC2015 compilers.
I would think not but please don't quote me on that, it's all down to
the Windows core developers.
--
My fellow Pythonistas, ask not what our language can do for you, ask
what you can do for our language.
Mark Lawrence
--
https://mail.python.org/mailman/listinfo/python-list
