Crash when using wxPython under Python 3.5

Hi everybody,

I just upgraded to Python 3.5.1 and download the latest Phoenix build from here: http://wxpython.org/Phoenix/snapshot-builds/ The one I downloaded is wxPython_Phoenix-3.0.3.dev1949+eedda34-cp35-cp35m-win_amd64.whl .

I started one of my wxPython apps, and when right-clicking its tray icon, it crashed with the two messages pasted below. Seems it’s related to SIP. Any idea what to do?

Thanks,

Ram.

Problem signature:

Problem Event Name: APPCRASH

Application Name: pythonw.exe

Application Version: 3.5.1150.1013

Application Timestamp: 56639599

Fault Module Name: siplib.cp35-win_amd64.pyd

Fault Module Version: 0.0.0.0

Fault Module Timestamp: 56d6b870

Exception Code: c0000005

Exception Offset: 000000000000580a

OS Version: 6.1.7601.2.1.0.256.1

Locale ID: 1033

Additional Information 1: fa1e

Additional Information 2: fa1e7b451be54090160a68432b9fc6d3

Additional Information 3: 6bba

Additional Information 4: 6bba5ed9a6e1027631b89616cab227c2

Problem signature:

Problem Event Name: APPCRASH

Application Name: pythonw.exe

Application Version: 3.5.1150.1013

Application Timestamp: 56639599

Fault Module Name: siplib.cp35-win_amd64.pyd

Fault Module Version: 0.0.0.0

Fault Module Timestamp: 56d6b870

Exception Code: c000041d

Exception Offset: 000000000000580a

OS Version: 6.1.7601.2.1.0.256.1

Locale ID: 1033

Additional Information 1: dd80

Additional Information 2: dd80cb740bd8235d3ee8aa218056b159

Additional Information 3: 4b7b

Additional Information 4: 4b7bf533957191bbceacffaaabae95e9

Hi,
I also encountered errors with wx Phoenix with python 3.5.1 (32bit) (on win7);
after installing via pip from
http://wxpython.org/Phoenix/snapshot-builds/wxPython_Phoenix-3.0.3.dev1956+aab2833-cp35-cp35m-win32.whl

I am getting an error on importing wx; the test file only contains
this import statement; the [edited] error traceback is:

Traceback (most recent call last):
  File "[_my_test_file_path_]\test_wx_py_3_5.py", line 4, in <module>
    import wx
  File "C:\Python35\lib\site-packages\wx\__init__.py", line 17, in <module>
    from wx.core import *
  File "C:\Python35\lib\site-packages\wx\core.py", line 6, in <module>
    from ._core import *
ImportError: DLL load failed: [The respective module not found.
(message translated form the original localised version)]

It seems, that there are some changes of filenames in this version; e.g.
C:\Python35\Lib\site-packages\wx\_core.cp35-win32.pyd
as opposed to
C:\Python34\Lib\site-packages\wx\_core.pyd
however, the file
C:\Python35\Lib\site-packages\wx\core.py
doesn't seem to reflect this (comparing to 3.4)

However, I am not sure, I am not missing something or making some
mistake while installing wx, as such elementary failure is likely to
be found immediately.

Can somebody confirm this bug or, on the other hand, does wx phoenix
(from a snapshot whl file) work for somebody using python 3.5 on
windows?
I'd like to stress, that I really appreciate the efforts to update wx
for the current python version.

Thanks and regards,
  vbr

···

2016-03-05 12:15 GMT+01:00 Ram Rachum <ram.rachum@gmail.com>:

Hi everybody,

I just upgraded to Python 3.5.1 and download the latest Phoenix build from
here: Index of /Phoenix/snapshot-builds The one I downloaded is
wxPython_Phoenix-3.0.3.dev1949+eedda34-cp35-cp35m-win_amd64.whl .

I started one of my wxPython apps, and when right-clicking its tray icon, it
crashed with the two messages pasted below. Seems it's related to SIP. Any
idea what to do?

Thanks,
Ram.

Problem signature:
[...]

Hi everybody,

I just upgraded to Python 3.5.1 and download the latest Phoenix build
from here: Index of /Phoenix/snapshot-builds The one I
downloaded is
wxPython_Phoenix-3.0.3.dev1949+eedda34-cp35-cp35m-win_amd64.whl .

The first question is which PYTHON build type you are using - 32 or 64
bit? That wheel is specifically for python 3.5 64-Bit.

···

On 05/03/2016 11:15, Ram Rachum wrote:

I started one of my wxPython apps, and when right-clicking its tray
icon, it crashed with the two messages pasted below. Seems it's related
to SIP. Any idea what to do?

Thanks,
Ram.

Problem signature:
  Problem Event Name:APPCRASH
  Application Name:pythonw.exe
  Application Version:3.5.1150.1013
  Application Timestamp:56639599
  Fault Module Name:siplib.cp35-win_amd64.pyd
  Fault Module Version:0.0.0.0
  Fault Module Timestamp:56d6b870
  Exception Code:c0000005
  Exception Offset:000000000000580a
  OS Version:6.1.7601.2.1.0.256.1
  Locale ID:1033
  Additional Information 1:fa1e
  Additional Information 2:fa1e7b451be54090160a68432b9fc6d3
  Additional Information 3:6bba
  Additional Information 4:6bba5ed9a6e1027631b89616cab227c2

Problem signature:
  Problem Event Name:APPCRASH
  Application Name:pythonw.exe
  Application Version:3.5.1150.1013
  Application Timestamp:56639599
  Fault Module Name:siplib.cp35-win_amd64.pyd
  Fault Module Version:0.0.0.0
  Fault Module Timestamp:56d6b870
  Exception Code:c000041d
  Exception Offset:000000000000580a
  OS Version:6.1.7601.2.1.0.256.1
  Locale ID:1033
  Additional Information 1:dd80
  Additional Information 2:dd80cb740bd8235d3ee8aa218056b159
  Additional Information 3:4b7b
  Additional Information 4:4b7bf533957191bbceacffaaabae95e9

--
You received this message because you are subscribed to the Google
Groups "wxPython-users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to wxpython-users+unsubscribe@googlegroups.com
<mailto:wxpython-users+unsubscribe@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.

--
Steve (Gadget) Barnes
Any opinions in this message are my personal opinions and do not reflect
those of my employer.

I have 64bit Python:

···

On Sun, Mar 6, 2016 at 4:35 AM, Steve (Gadget) Barnes gadgetsteve@live.co.uk wrote:

On 05/03/2016 11:15, Ram Rachum wrote:

Hi everybody,

I just upgraded to Python 3.5.1 and download the latest Phoenix build

from here: http://wxpython.org/Phoenix/snapshot-builds/ The one I

downloaded is

wxPython_Phoenix-3.0.3.dev1949+eedda34-cp35-cp35m-win_amd64.whl .

The first question is which PYTHON build type you are using - 32 or 64

bit? That wheel is specifically for python 3.5 64-Bit.

I started one of my wxPython apps, and when right-clicking its tray

icon, it crashed with the two messages pasted below. Seems it’s related

to SIP. Any idea what to do?

Thanks,

Ram.

Problem signature:

Problem Event Name:APPCRASH

Application Name:pythonw.exe

Application Version:3.5.1150.1013

Application Timestamp:56639599

Fault Module Name:siplib.cp35-win_amd64.pyd

Fault Module Version:0.0.0.0

Fault Module Timestamp:56d6b870

Exception Code:c0000005

Exception Offset:000000000000580a

OS Version:6.1.7601.2.1.0.256.1

Locale ID:1033

Additional Information 1:fa1e

Additional Information 2:fa1e7b451be54090160a68432b9fc6d3

Additional Information 3:6bba

Additional Information 4:6bba5ed9a6e1027631b89616cab227c2

Problem signature:

Problem Event Name:APPCRASH

Application Name:pythonw.exe

Application Version:3.5.1150.1013

Application Timestamp:56639599

Fault Module Name:siplib.cp35-win_amd64.pyd

Fault Module Version:0.0.0.0

Fault Module Timestamp:56d6b870

Exception Code:c000041d

Exception Offset:000000000000580a

OS Version:6.1.7601.2.1.0.256.1

Locale ID:1033

Additional Information 1:dd80

Additional Information 2:dd80cb740bd8235d3ee8aa218056b159

Additional Information 3:4b7b

Additional Information 4:4b7bf533957191bbceacffaaabae95e9

You received this message because you are subscribed to the Google

Groups “wxPython-users” group.

To unsubscribe from this group and stop receiving emails from it, send

an email to wxpython-users+unsubscribe@googlegroups.com

mailto:wxpython-users+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Steve (Gadget) Barnes

Any opinions in this message are my personal opinions and do not reflect

those of my employer.

You received this message because you are subscribed to a topic in the Google Groups “wxPython-users” group.

To unsubscribe from this topic, visit https://groups.google.com/d/topic/wxpython-users/XQyUng_-KP8/unsubscribe.

To unsubscribe from this group and all its topics, send an email to wxpython-users+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

ImportError: DLL load failed: [The respective module not found.
(message translated form the original localised version)]

This indicates that a DLL is not found.
Do you have DLLs like this in your wx directory?
  wxmsw30u_core_vc140.dll
If not, something with the .whl download went wrong...

It seems, that there are some changes of filenames in this version; e.g.
C:\Python35\Lib\site-packages\wx\_core.cp35-win32.pyd
as opposed to
C:\Python34\Lib\site-packages\wx\_core.pyd
however, the file
C:\Python35\Lib\site-packages\wx\core.py
doesn't seem to reflect this (comparing to 3.4)

That should be OK. Python takes care. If this was the problem, you would get a
   ImportError: No module named 'wx._core'

However, I am not sure, I am not missing something or making some
mistake while installing wx, as such elementary failure is likely to
be found immediately.

Can somebody confirm this bug or, on the other hand, does wx phoenix
(from a snapshot whl file) work for somebody using python 3.5 on
windows?

I just tried the .whl file and have all the DLLs.
(I just unzipped, instead of calling pip.)

Regards,

Dietmar

···

On 06.03.2016 02:31, Vlastimil Brom wrote:

Hi,
many thanks for the detailed answer.
I can confirm, that there is the mentioned dll file in the wx folder
wxmsw30u_core_vc140.dll
(and others for some individual parts/submodules of wx; i guess the
installation using pip with that whl file seems to work as expected
then)
Are there maybe some other options to diagnose this problem?

Thanks and regards,
   vbr

···

2016-03-08 22:35 GMT+01:00 Dietmar Schwertberger <maillist@schwertberger.de>:

On 06.03.2016 02:31, Vlastimil Brom wrote:

ImportError: DLL load failed: [The respective module not found.
(message translated form the original localised version)]

This indicates that a DLL is not found.
Do you have DLLs like this in your wx directory?
wxmsw30u_core_vc140.dll
If not, something with the .whl download went wrong...

It seems, that there are some changes of filenames in this version; e.g.
C:\Python35\Lib\site-packages\wx\_core.cp35-win32.pyd
as opposed to
C:\Python34\Lib\site-packages\wx\_core.pyd
however, the file
C:\Python35\Lib\site-packages\wx\core.py
doesn't seem to reflect this (comparing to 3.4)

That should be OK. Python takes care. If this was the problem, you would get
a
  ImportError: No module named 'wx._core'

However, I am not sure, I am not missing something or making some
mistake while installing wx, as such elementary failure is likely to
be found immediately.

Can somebody confirm this bug or, on the other hand, does wx phoenix
(from a snapshot whl file) work for somebody using python 3.5 on
windows?

I just tried the .whl file and have all the DLLs.
(I just unzipped, instead of calling pip.)

Regards,

Dietmar

Maybe you could run the Dependency Walker on _core.cp35-win32.pyd.
http://www.dependencywalker.com/

I will send you a screenshot with my scan result via PM.

Regards,

Dietmar

···

On 08.03.2016 22:51, Vlastimil Brom wrote:

I can confirm, that there is the mentioned dll file in the wx folder
wxmsw30u_core_vc140.dll
(and others for some individual parts/submodules of wx; i guess the
installation using pip with that whl file seems to work as expected
then)
Are there maybe some other options to diagnose this problem?

I was getting errors with WxPhoenix on Python 3.5.1 windows10 until I installed visual studio 2015 community edition, pip removed and then pip installed WxPhoenix again, after that it worked ok.

···

On Saturday, 5 March 2016 11:15:14 UTC, Ram Rachum wrote:

Hi everybody,

I just upgraded to Python 3.5.1 and download the latest Phoenix build from here: http://wxpython.org/Phoenix/snapshot-builds/ The one I downloaded is wxPython_Phoenix-3.0.3.dev1949+eedda34-cp35-cp35m-win_amd64.whl .

I started one of my wxPython apps, and when right-clicking its tray icon, it crashed with the two messages pasted below. Seems it’s related to SIP. Any idea what to do?

Thanks,

Ram.

Problem signature:

Problem Event Name: APPCRASH

Application Name: pythonw.exe

Application Version: 3.5.1150.1013

Application Timestamp: 56639599

Fault Module Name: siplib.cp35-win_amd64.pyd

Fault Module Version: 0.0.0.0

Fault Module Timestamp: 56d6b870

Exception Code: c0000005

Exception Offset: 000000000000580a

OS Version: 6.1.7601.2.1.0.256.1

Locale ID: 1033

Additional Information 1: fa1e

Additional Information 2: fa1e7b451be54090160a68432b9fc6d3

Additional Information 3: 6bba

Additional Information 4: 6bba5ed9a6e1027631b89616cab227c2

Problem signature:

Problem Event Name: APPCRASH

Application Name: pythonw.exe

Application Version: 3.5.1150.1013

Application Timestamp: 56639599

Fault Module Name: siplib.cp35-win_amd64.pyd

Fault Module Version: 0.0.0.0

Fault Module Timestamp: 56d6b870

Exception Code: c000041d

Exception Offset: 000000000000580a

OS Version: 6.1.7601.2.1.0.256.1

Locale ID: 1033

Additional Information 1: dd80

Additional Information 2: dd80cb740bd8235d3ee8aa218056b159

Additional Information 3: 4b7b

Additional Information 4: 4b7bf533957191bbceacffaaabae95e9

Looks like this thread has been mixing two separate problems… Can someone please help with my problem quoted below?

···

On Sat, Mar 5, 2016 at 1:15 PM, Ram Rachum ram.rachum@gmail.com wrote:

Hi everybody,

I just upgraded to Python 3.5.1 and download the latest Phoenix build from here: http://wxpython.org/Phoenix/snapshot-builds/ The one I downloaded is wxPython_Phoenix-3.0.3.dev1949+eedda34-cp35-cp35m-win_amd64.whl .

I started one of my wxPython apps, and when right-clicking its tray icon, it crashed with the two messages pasted below. Seems it’s related to SIP. Any idea what to do?

Thanks,

Ram.

Problem signature:

Problem Event Name: APPCRASH

Application Name: pythonw.exe

Application Version: 3.5.1150.1013

Application Timestamp: 56639599

Fault Module Name: siplib.cp35-win_amd64.pyd

Fault Module Version: 0.0.0.0

Fault Module Timestamp: 56d6b870

Exception Code: c0000005

Exception Offset: 000000000000580a

OS Version: 6.1.7601.2.1.0.256.1

Locale ID: 1033

Additional Information 1: fa1e

Additional Information 2: fa1e7b451be54090160a68432b9fc6d3

Additional Information 3: 6bba

Additional Information 4: 6bba5ed9a6e1027631b89616cab227c2

Problem signature:

Problem Event Name: APPCRASH

Application Name: pythonw.exe

Application Version: 3.5.1150.1013

Application Timestamp: 56639599

Fault Module Name: siplib.cp35-win_amd64.pyd

Fault Module Version: 0.0.0.0

Fault Module Timestamp: 56d6b870

Exception Code: c000041d

Exception Offset: 000000000000580a

OS Version: 6.1.7601.2.1.0.256.1

Locale ID: 1033

Additional Information 1: dd80

Additional Information 2: dd80cb740bd8235d3ee8aa218056b159

Additional Information 3: 4b7b

Additional Information 4: 4b7bf533957191bbceacffaaabae95e9

You received this message because you are subscribed to a topic in the Google Groups “wxPython-users” group.

To unsubscribe from this topic, visit https://groups.google.com/d/topic/wxpython-users/XQyUng_-KP8/unsubscribe.

To unsubscribe from this group and all its topics, send an email to wxpython-users+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Hi,
I am sorry, if my follow up post turns out to be independent of your
case; it appeared to me, that there may be similar cause (problems
with core pyd files in the recent development build ...)
In any case, the suggestion to look for missing dependencies of the
offending file using dependencywalker was very helpful - after adding
the missing file (MSVCP140.DLL in my case) the problem is fixed.
Maybe you'd be able to track the problem source in a similar way too,
or someone more knowledgable may suggest other possibilities..
regards,
    vbr

···

2016-03-09 10:51 GMT+01:00 Ram Rachum <ram.rachum@gmail.com>:

Looks like this thread has been mixing two separate problems... Can someone
please help with my problem quoted below?

On Sat, Mar 5, 2016 at 1:15 PM, Ram Rachum <ram.rachum@gmail.com> wrote:

Hi everybody,

I just upgraded to Python 3.5.1 and download the latest Phoenix build from
here: Index of /Phoenix/snapshot-builds The one I downloaded is
wxPython_Phoenix-3.0.3.dev1949+eedda34-cp35-cp35m-win_amd64.whl .

I started one of my wxPython apps, and when right-clicking its tray icon,
it crashed with the two messages pasted below. Seems it's related to SIP.
Any idea what to do?

Thanks,
Ram.

Problem signature:
  Problem Event Name: APPCRASH
  Application Name: pythonw.exe
  Application Version: 3.5.1150.1013
  Application Timestamp: 56639599
  Fault Module Name: siplib.cp35-win_amd64.pyd
  Fault Module Version: 0.0.0.0
  Fault Module Timestamp: 56d6b870
  Exception Code: c0000005
  Exception Offset: 000000000000580a
  OS Version: 6.1.7601.2.1.0.256.1
  Locale ID: 1033
  Additional Information 1: fa1e
  Additional Information 2: fa1e7b451be54090160a68432b9fc6d3
  Additional Information 3: 6bba
  Additional Information 4: 6bba5ed9a6e1027631b89616cab227c2

Problem signature:
  Problem Event Name: APPCRASH
  Application Name: pythonw.exe
  Application Version: 3.5.1150.1013
  Application Timestamp: 56639599
  Fault Module Name: siplib.cp35-win_amd64.pyd
  Fault Module Version: 0.0.0.0
  Fault Module Timestamp: 56d6b870
  Exception Code: c000041d
  Exception Offset: 000000000000580a
  OS Version: 6.1.7601.2.1.0.256.1
  Locale ID: 1033
  Additional Information 1: dd80
  Additional Information 2: dd80cb740bd8235d3ee8aa218056b159
  Additional Information 3: 4b7b
  Additional Information 4: 4b7bf533957191bbceacffaaabae95e9

--

That could be due to the missing runtime DLL of Visual Studio. Once VS 2015 or the runtime distributable is installed, you should have MSVCP140.DLL in your system32 directory.

Regards,

Dietmar

···

On 09.03.2016 01:49, 'Yoriz' via wxPython-users wrote:

I was getting errors with WxPhoenix on Python 3.5.1 windows10 until I installed visual studio 2015 community edition, pip removed and then pip installed WxPhoenix again, after that it worked ok.

I've just tried
  - wxPython_Phoenix-3.0.3.dev1956+aab2833-cp35-cp35m-win_amd64.whl
  - with Python 3.5.1 and
  - the wxPython demo.
With the demo I did not see a crash when clicking on the Taskbar icon.
Maybe you should prepare and post a minimum sample to reproduce the problem.

Regards,

Dietmar

···

On 09.03.2016 10:51, Ram Rachum wrote:

Looks like this thread has been mixing two separate problems... Can someone please help with my problem quoted below?

Thanks for checking. I tried it again now and saw I was imprecise before; what causes the crash is not right-clicking, but double-clicking. Not sure why I double-clicked, as it doesn’t even work in that app. I tried it on a computer with Python 3.4 though and it didn’t crash there, so it is a bug, but now it’s on a lower priority for me, so I’m forgetting about it.

Thanks for making the effort Dietmar and sorry I wasn’t precise with my report.

Thanks,

Ram.

···

On Wed, Mar 9, 2016 at 7:44 PM, Dietmar Schwertberger maillist@schwertberger.de wrote:

Looks like this thread has been mixing two separate problems… Can someone please help with my problem quoted below?
On 09.03.2016 10:51, Ram Rachum wrote:

I’ve just tried

  • wxPython_Phoenix-3.0.3.dev1956+aab2833-cp35-cp35m-win_amd64.whl

  • with Python 3.5.1 and

  • the wxPython demo.

With the demo I did not see a crash when clicking on the Taskbar icon.

Maybe you should prepare and post a minimum sample to reproduce the problem.

Regards,

Dietmar

You received this message because you are subscribed to a topic in the Google Groups “wxPython-users” group.

To unsubscribe from this topic, visit https://groups.google.com/d/topic/wxpython-users/XQyUng_-KP8/unsubscribe.

To unsubscribe from this group and all its topics, send an email to wxpython-users+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

No problem. Please test with the next versions. If the problem persists, please try to prepare a sample.
With the demo, a double-click did not cause problems, but it does not have a handler for it...

Regards,

Dietmar

···

On 09.03.2016 21:13, Ram Rachum wrote:

Thanks for making the effort Dietmar and sorry I wasn't precise with my report.