Re: Phoenix with Python 3.6.0 32 bit ImportError on Windows 7 64 bit

woss <[email protected]>
Newsgroups gmane.comp.python.wxpython.devel
Message-ID <[email protected]>
2017. február 9., csütörtök 4:15:04 UTC+1 időpontban Robin Dunn a 
következőt írta:
>
> woss wrote:
>
> Hi
>
> Python 3.6.0 32 bit
> wxPython_Phoenix-3.0.3.dev2808+717fdf9-cp36-cp36m-win32.whl
>
> I received this message on Windows 7/64 bit:
>
> *R:\python>python*
> *Python 3.6.0 (v3.6.0:41df79263a11, Dec 23 2016, 07:18:10) [MSC v.1900 32 
> bit (Intel)] on win32*
> *Type "help", "copyright", "credits" or "license" for more information.*
> *>>> import wx*
> *Traceback (most recent call last):*
> *  File "<stdin>", line 1, in <module>*
> *  File "R:\python\lib\site-packages\wx\__init__.py", line 17, in <module>*
> *    from wx.core import **
> *  File "R:\python\lib\site-packages\wx\core.py", line 12, in <module>*
> *    from ._core import **
> *ImportError: DLL load failed: %1 is not a valid Win32 application*
> *>>>*
>
> On Windows 7/32 bit has not problem.
>
>
> Any suggestions ?
>
>
> One of the possible reasons for that error is if it's trying to use a 
> 64bit DLL in a 32bit context, however it's working for me here with 32-bit 
> Python on 64-bit Windows 10.
>
>  >  pip install -U --pre \
> ...         -f https://wxpython.org/Phoenix/snapshot-builds/ \
> ...         wxPython_Phoenix
> Collecting wxPython_Phoenix
>   Downloading 
> https://wxpython.org/Phoenix/snapshot-builds/wxPython_Phoenix-3.0.3.dev2808+717fdf9-cp36-cp36m-win32.whl 
> (12.2MB)
>     100% |████████████████████████████████| 12.2MB 79kB/s
> Collecting six (from wxPython_Phoenix)
>   Using cached six-1.10.0-py2.py3-none-any.whl
> Installing collected packages: six, wxPython-Phoenix
> Successfully installed six-1.10.0 wxPython-Phoenix-3.0.3.dev2808+717fdf9
>
>  >  python
> Python 3.6.0 (v3.6.0:41df79263a11, Dec 23 2016, 07:18:10) [MSC v.1900 32 
> bit (Intel)] on win32
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import wx
> >>>
>
> Do you have anything set in the environment or registry that may be 
> affecting the sys.path and causing the wrong set of wx or wxPython binaries 
> to be loaded? Have you tried completely clearing all traces of wxPython and 
> installing the wheel again? In the example above I created a new virtual 
> environment to use for the test, you may want to try that too if the other 
> hints don't help. Another thing that may help would be to use the 
> DependencyWalker tool to see exactly which DLLs are being loaded, or 
> attempting to load.
>
> -- 
> Robin Dunn
> Software Craftsman 
> http://wxPython.org
>

Thx, Robin !

This is really a Python / Win7 problem.
Now don't run the Python 3.6 installer neither. (The Python 3.5 works fine.)

I'm looking for the solution .. 

-- 
You received this message because you are subscribed to the Google Groups "wxPython-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.