[issue25251] Unknown MS Compiler version 1900

Change by Roundup Robot : -- nosy: +python-dev nosy_count: 14.0 -> 15.0 pull_requests: +25365 pull_request: https://github.com/python/cpython/pull/26780 ___ Python tracker ___

[issue25251] Unknown MS Compiler version 1900

anthony shaw added the comment: Closing as 3rd party feature for setuptools -- nosy: +anthonypjshaw resolution: -> third party stage: -> resolved status: open -> closed ___ Python tracker _

[issue25251] Unknown MS Compiler version 1900

Cheryl Sabella added the comment: Should this issue be closed as third-party or do we want to leave it open as reference? -- nosy: +cheryl.sabella ___ Python tracker ___

[issue25251] Unknown MS Compiler version 1900

Steve Dower added the comment: That sounds like a great feature for setuptools. Core distutils is highly focused on what is needed for the core product, and we are very much trying to avoid bloating it, whereas setuptools is free to add extensions wherever necessary and make them available on

[issue25251] Unknown MS Compiler version 1900

Sam Miller added the comment: Hi disutils. I got this bug when trying to pip install pomegranate to python 3.5. There is now a m2w64-toolchain (https://github.com/ContinuumIO/anaconda-issues/issues/561)that allows installing the notoriously windows-challenged theano, so I thought this error c

[issue25251] Unknown MS Compiler version 1900

Steve Dower added the comment: Please test your extensions thoroughly when building with MinGW, especially if you're planning on distributing wheels on PyPI. CPython assumes an ABI compatible with what MSVC would have built, and mixing ABIs will lead to crashes or data corruption. (I'm not jus

[issue25251] Unknown MS Compiler version 1900

Jonathan Hanba added the comment: I just ran across this bug in Python 3.5.1 while trying to build pycrypto using MinGW. I patched the cygwincompiler.py with the attached patch.diff file, and that got me part of the way there. With the additions made by patch.diff, the MinGW linker then looked

[issue25251] Unknown MS Compiler version 1900

Marcelo Duarte added the comment: I hava a problem with others packages, like cchardet and aiohttp. Aplying the patch changed the error message, then I generate a lib for vcruntime140, and finally, it is installed: #go to python installation dir cd M:\Applications\Python35-32 pexports vcruntime

[issue25251] Unknown MS Compiler version 1900

Tod Haren added the comment: In addition to patching cygwincompiler.py I also had to patch numpy\distutils\misc_util.py and numpy\distutils\mingw32ccompiler.py to handle the new dll name. A pull request has been submitted for the numpy patches. https://github.com/numpy/numpy/pull/6875 --

[issue25251] Unknown MS Compiler version 1900

Ateik Al-Zehla added the comment: forget to tell you that even i deleted the cache, but nothing happened. it use the old code. -- ___ Python tracker ___

[issue25251] Unknown MS Compiler version 1900

Ateik Al-Zehla added the comment: thanks Matt for your replay. But I copied the lines to cygwinccompiler.py and it didn't work. and it pretend as there is no change happened to the file. To see if the execution goes through the code I changed message if raise ValueError to "God Help Me %s " i

[issue25251] Unknown MS Compiler version 1900

Matt Hickford added the comment: Hi Ateik. Find cygwinccompiler.py on your computer and copy the patch to the same folder. Then run the command `patch < patch.diff`. It that doesn't work, just open both files in a text editor and copy and paste the lines to the right place, you'll work it out. I

[issue25251] Unknown MS Compiler version 1900

Ateik Al-Zehla added the comment: how to apply patch file : patch.diff ? plz help -- nosy: +Ateik Al-Zehla ___ Python tracker ___ ___

[issue25251] Unknown MS Compiler version 1900

Steve Dower added the comment: There isn't one. MinGW doesn't support building with the UCRT yet, so you'll need to link to a different version of the library and hope that it works (or test/fix the extension). -- ___ Python tracker

[issue25251] Unknown MS Compiler version 1900

Matt Hickford added the comment: I'm not sure what the correct analogue of msvcr100 is for Visual C++ 14.0. "msvcr140.dll no longer exists" http://blogs.msdn.com/b/vcblog/archive/2014/06/03/visual-studio-14-ctp.aspx elif msc_ver == '1600': # VS2010 / MSVC 10.0

[issue25251] Unknown MS Compiler version 1900

Matt Hickford added the comment: Here's a patch that helped on my computer On 28 September 2015 at 00:29, Zachary Ware wrote: > > Changes by Zachary Ware : > > > -- > components: +Windows > nosy: +paul.moore, steve.dower, tim.golden, zach.ware > type: crash -> behavior > >

[issue25251] Unknown MS Compiler version 1900

Changes by Zachary Ware : -- components: +Windows nosy: +paul.moore, steve.dower, tim.golden, zach.ware type: crash -> behavior ___ Python tracker ___ ___

[issue25251] Unknown MS Compiler version 1900

New submission from Matt Hickford: Hi distutils. I previously used compiler=mingw32 with success. Today I installed Visual Studio 2015. Now compiler=mingw32 gives me an error File "c:\python35\lib\distutils\cygwinccompiler.py", line 86, in get_msvcr raise ValueError("Unknown MS Compiler ver