brend@BJS_DELL_17 MINGW64 ~
$ pip3.6 install -U wxPython
Collecting wxPython
Using cached https://files.pythonhosted.org/packages/a4/4a/d35b19f8c21b414ece2b3dc02dcf8cb0d45d6fe5aacf56f7ca0b7c66ac58/wxPython-4.0.1.tar.gz
Requirement not upgraded as not directly required: six in c:/msys64/mingw64/lib/python3.6/site-packages (from wxPython) (1.11.0)
Installing collected packages: wxPython
Running setup.py install for wxPython ... error
Complete output from command C:/msys64/mingw64/bin/python3.exe -u -c "import setuptools, tokenize;__file__='C:/Users/brend/AppData/Local/Temp/pip-install-8le1c189/wxPython/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record C:/Users/brend/AppData/Local/Temp/pip-record-p71raf86/install-record.txt --single-version-externally-managed --compile:
running install
running build
WARNING: Building this way assumes that all generated files have been
generated already. If that is not the case then use build.py directly
to generate the source and perform the build stage. You can use
--skip-build with the bdist_* or install commands to avoid this
message and the wxWidgets and Phoenix build steps in the future.
"C:/msys64/mingw64/bin/python3.exe" -u build.py build
Will build using: "C:/msys64/mingw64/bin/python3.exe"
3.6.5 (default, Apr 16 2018, 10:17:38) [GCC 7.3.0 64 bit (AMD64)]
Python's architecture is 64bit
cfg.VERSION: 4.0.1
Running command: build
Running command: build_wx
Command '"C:/msys64/mingw64/bin/python3.exe" -c "import distutils.msvc9compiler as msvc; mc = msvc.MSVCCompiler(); mc.initialize(); print(mc.cc)"' failed with exit code 1.
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "C:/msys64/mingw64/lib/python3.6\distutils\msvc9compiler.py", line 297, in <module>
raise DistutilsPlatformError("VC %0.1f is not supported by this module" % VERSION)
distutils.errors.DistutilsPlatformError: VC 6.0 is not supported by this module
Finished command: build_wx (0.124s)
Finished command: build (0.124s)
Command '"C:/msys64/mingw64/bin/python3.exe" -u build.py build' failed with exit code 1.
----------------------------------------
Command "C:/msys64/mingw64/bin/python3.exe -u -c "import setuptools, tokenize;__file__='C:/Users/brend/AppData/Local/Temp/pip-install-8le1c189/wxPython/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record C:/Users/brend/AppData/Local/Temp/pip-record-p71raf86/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in C:/Users/brend/AppData/Local/Temp/pip-install-8le1c189/wxPython/
Is this an msys2/mingw issue or a python issue? How do I go about getting this to work?
Do you need msys2? Then you
probably need to patch the detection to return the correct
version and maybe submit a bug report to the msys2 people.
If you don't need msys2:
Usually, you need cygwin for the build process as build.py
calls a bash shell script, but the build command itself can
run outside.
E.g.:
D:/Python/Python36/python.exe build.py dox etg --nodoc sip
build
Regards,
Dietmar
> nepix32 <nep...@gmail.com>: May 15 07:37AM -0700
>
> Is it even possible under Windows for a Python 3.6 to use
another compiler
> than VC++ 2015? I remember that the last Python I was able
to compile C
> extensions with mingw32 was Python 3.4.
Not sure. MSYS2 has the following python3
packages, and they seemed be compiled with GCC.
$ pacman -Ss python3 | grep 3.6
mingw32/mingw-w64-i686-python3 3.6.5-1 [installed]
mingw64/mingw-w64-x86_64-python3 3.6.5-1 [installed]
msys/python 3.6.2-1 [installed]
$ /mingw32/bin/python3
Python 3.6.5 (default, Apr 16 2018, 10:30:41) [GCC 7.3.0 32 bit] on win32
Type "help", "copyright", "credits" or "license" for more information.
$ /usr/bin/python3
Python 3.6.2 (default, Sep 7 2017, 13:16:50)
[GCC 6.3.0] on msys
Type "help", "copyright", "credits" or "license" for more information.
Anyway I came to the conclusion that using prebuilt libraries wont work unless using the exact same compiler, which means I can't use the wxPython as that uses VC++ (I think).
The only way to use it with MSYS2/MINGW, would be to build it from sources with MSYS2/MINGW tools.
Thanks, Brendan.
> nepix32 <nep...@gmail.com>: May 15 07:37AM -0700
>
> Is it even possible under Windows for a Python 3.6 to use another compiler
> than VC++ 2015? I remember that the last Python I was able to compile C
> extensions with mingw32 was Python 3.4.
Not sure. MSYS2 has the following python3 packages, and they seemed be compiled with GCC.
$ pacman -Ss python3 | grep 3.6
mingw32/mingw-w64-i686-python3 3.6.5-1 [installed]
mingw64/mingw-w64-x86_64-python3 3.6.5-1 [installed]
msys/python 3.6.2-1 [installed]
$ /mingw32/bin/python3
Python 3.6.5 (default, Apr 16 2018, 10:30:41) [GCC 7.3.0 32 bit] on win32
Type "help", "copyright", "credits" or "license" for more information.
$ /usr/bin/python3
Python 3.6.2 (default, Sep 7 2017, 13:16:50)
[GCC 6.3.0] on msys
Type "help", "copyright", "credits" or "license" for more information.
Anyway I came to the conclusion that using prebuilt libraries wont work unless using the exact same compiler, which means I can't use the wxPython as that uses VC++ (I think).
The only way to use it with MSYS2/MINGW, would be to build it from sources with MSYS2/MINGW tools.