I have wxPython3.0-win64-py27 installed on my windows 7 64bit machine.
Adding
import wxversion
wxversion.select(“3.0”)
import wx
to my script, traceback tells me “DLL load failed: %1 is not a valid Win32 application.”
What am doing wrong here?
I install wxpython 3.0.0 and demo, but when I run it, it appears MS debugger and exit.
Program before I can run under wxpython 2.9.5, they all can not run.
My system is Windows XP SP2.
Why?
在 2013年12月30日星期一UTC+8上午12时33分44秒,George McCown写道:
···
I have wxPython3.0-win64-py27 installed on my windows 7 64bit machine.
Adding
import wxversion
wxversion.select(“3.0”)
import wx
to my script, traceback tells me “DLL load failed: %1 is not a valid Win32 application.”
What am doing wrong here?
zc zhang wrote:
I install wxpython 3.0.0 and demo, but when I run it, it appears MS
debugger and exit.
Program before I can run under wxpython 2.9.5, they all can not run.
My system is Windows XP SP2.
Why?
I don't know. I don't have an XP machine to test on. Since you apparently have the MS debugger installed (and so probably the compilers too) why don't you try building wxPython and debugging it to see where/why it is crashing.
···
--
Robin Dunn
Software Craftsman
George McCown wrote:
I have wxPython3.0-win64-py27
<http://downloads.sourceforge.net/wxpython/wxPython3.0-win64-3.0.0.0-py27.exe>
installed on my windows 7 64bit machine.
Addingimport wxversion
wxversion.select("3.0")
import wxto my script, traceback tells me "DLL load failed: %1 is not a valid
Win32 application."
/What am/ /doing wrong here?/
Is the Python you are using 32-bit or 64-bit?
···
--
Robin Dunn
Software Craftsman
Hi, Robin,
I run it and debug with MS debugger, get follow messages:
wxbase30u_vc90.dll!010388e3()
[The following framework may be incorrect and / or missing is not loaded symbol wxbase30u_vc90.dll]
wxbase30u_vc90.dll!0103b518()
wxmsw30u_core_vc90.dll!0177dd8a()
msvcr90.dll!78583db8()
msvcr90.dll!78583ed8()
msvcr90.dll!78548558()
I am newer and not familiar with MS development, but want to use wxpython 3.0.0.
wxpython 2.9.5 is OK.
在 2013年12月30日星期一UTC+8上午11时17分26秒,Robin Dunn写道:
···
zc zhang wrote:
I install wxpython 3.0.0 and demo, but when I run it, it appears MS
debugger and exit.
Program before I can run under wxpython 2.9.5, they all can not run.
My system is Windows XP SP2.
Why?I don’t know. I don’t have an XP machine to test on. Since you
apparently have the MS debugger installed (and so probably the compilers
too) why don’t you try building wxPython and debugging it to see
where/why it is crashing.–
Robin Dunn
Software Craftsman
http://wxPython.org
Hi, Robin,
I run it and debug with MS debugger, get follow messages:
wxbase30u_vc90.dll!010388e3()
[Frames below may be incorrect and/or missing, no symbols loaded for wxbase30u_vc90.dll]
wxbase30u_vc90.dll!0103b518()
wxmsw30u_core_vc90.dll!0177dd8a()
msvcr90.dll!78583db8()
msvcr90.dll!78583ed8()
msvcr90.dll!78548558()
I am newer and not familiar with MS development, but want to use wxpython 3.0.0.
wxpython 2.9.5 is OK.
在 2013年12月30日星期一UTC+8上午11时17分26秒,Robin Dunn写道:
···
zc zhang wrote:
I install wxpython 3.0.0 and demo, but when I run it, it appears MS
debugger and exit.
Program before I can run under wxpython 2.9.5, they all can not run.
My system is Windows XP SP2.
Why?I don’t know. I don’t have an XP machine to test on. Since you
apparently have the MS debugger installed (and so probably the compilers
too) why don’t you try building wxPython and debugging it to see
where/why it is crashing.–
Robin Dunn
Software Craftsman
http://wxPython.org
I am having the same error. Windows XP Pro SP3 32bit
wxPython3.0-win32-docs-demos-3.0.0.0.exe
wxPython3.0-win32-3.0.0.0-py27.exe
Python 2.7.5 MSC v.1500 32 bit
I can do a:
import wx
app = wx.App()
frame = wx.Frame(None)
frame.Show()
app.MainLoop()
but running pysliceshell (found in my PATH) generates the same error
···
On Sun, Dec 29, 2013 at 10:54 PM, zc zhang xm.zzcclp@gmail.com wrote:
Hi, Robin,
I run it and debug with MS debugger, get follow messages:
wxbase30u_vc90.dll!010388e3()
[Frames below may be incorrect and/or missing, no symbols loaded for wxbase30u_vc90.dll]
wxbase30u_vc90.dll!0103b518()
wxmsw30u_core_vc90.dll!0177dd8a()
msvcr90.dll!78583db8()
msvcr90.dll!78583ed8()msvcr90.dll!78548558()
I am newer and not familiar with MS development, but want to use wxpython 3.0.0.
wxpython 2.9.5 is OK.
在 2013年12月30日星期一UTC+8上午11时17分26秒,Robin Dunn写道:
zc zhang wrote:
I install wxpython 3.0.0 and demo, but when I run it, it appears MS
debugger and exit.Program before I can run under wxpython 2.9.5, they all can not run.
My system is Windows XP SP2.
Why?I don’t know. I don’t have an XP machine to test on. Since you
apparently have the MS debugger installed (and so probably the compilerstoo) why don’t you try building wxPython and debugging it to see
where/why it is crashing.–
Robin Dunn
Software Craftsman
http://wxPython.org
–
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.
For more options, visit https://groups.google.com/groups/opt_out.
32-bit. I see where you are going. Change 2.7 to 64 bit?
···
On Sunday, December 29, 2013 9:17:29 PM UTC-6, Robin Dunn wrote:
George McCown wrote:
I have wxPython3.0-win64-py27
<http://downloads.sourceforge.net/wxpython/wxPython3.0-win64-3.0.0.0-py27.exe>
installed on my windows 7 64bit machine.
Adding
import wxversion
wxversion.select(“3.0”)
import wx
to my script, traceback tells me "DLL load failed: %1 is not a valid
Win32 application."
/What am/ /doing wrong here?/
Is the Python you are using 32-bit or 64-bit?
–
Robin DunnSoftware Craftsman
zc zhang wrote:
Hi, Robin,
I run it and debug with MS debugger, get follow messages:
wxbase30u_vc90.dll!010388e3()
[The following framework may be incorrect and / or missing is not
loaded symbol wxbase30u_vc90.dll]
wxbase30u_vc90.dll!0103b518()
wxmsw30u_core_vc90.dll!0177dd8a()
For what it's worth:
msvcr90.dll!78583db8()
That's inside _malloc.
msvcr90.dll!78583ed8()
That's in "operator new", about to raise a "bad_alloc" exception.
msvcr90.dll!78548558()
That's fetching the C run-time per-thread data structure.
I don't know any reason why that all shouldn't work in XP, unless the
new wx is somehow allocating way more Thread Local Storage than previous
versions.
···
--
Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc.
Could this be a run-time dll mismatch?
Is there more than one version of
msvcr90.dll out in the wild?
-Chris
···
On Mon, Dec 30, 2013 at 9:44 AM, Tim Roberts timr@probo.com wrote:
zc zhang wrote:
Hi, Robin,
I run it and debug with MS debugger, get follow messages:
wxbase30u_vc90.dll!010388e3()
[The following framework may be incorrect and / or missing is not
loaded symbol wxbase30u_vc90.dll]
wxbase30u_vc90.dll!0103b518()
wxmsw30u_core_vc90.dll!0177dd8a()
For what it’s worth:
msvcr90.dll!78583db8()
That’s inside _malloc.
msvcr90.dll!78583ed8()
That’s in “operator new”, about to raise a “bad_alloc” exception.
msvcr90.dll!78548558()
That’s fetching the C run-time per-thread data structure.
I don’t know any reason why that all shouldn’t work in XP, unless the
new wx is somehow allocating way more Thread Local Storage than previous
versions.
–
Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc.
–
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.
For more options, visit https://groups.google.com/groups/opt_out.
–
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Yes. In fact, I believe there are 6 public versions, although
generally a mismatch causes a DLL load failure rather than a
run-time incompatibility. Perhaps downloading and installing the
latest “Visual C++ 2008 SP1 Redistributable Package” would help.
···
Chris Barker wrote:
Could this be a run-time dll mismatch?
Is there more than one version of
msvcr90.dll
out in the wild?
-- Tim Roberts, Providenza & Boekelheide, Inc.
George McCown wrote:
George McCown wrote:
> I have wxPython3.0-win64-py27
>
<http://downloads.sourceforge.net/wxpython/wxPython3.0-win64-3.0.0.0-py27.exe
<http://downloads.sourceforge.net/wxpython/wxPython3.0-win64-3.0.0.0-py27.exe>>> installed on my windows 7 64bit machine.
> Adding
>
> import wxversion
> wxversion.select("3.0")
> import wx
>
> to my script, traceback tells me "DLL load failed: %1 is not a valid
> Win32 application."
> /What am/ /doing wrong here?/Is the Python you are using 32-bit or 64-bit?
32-bit. I see where you are going. Change 2.7 to 64 bit?
Or install the 32-bit wxPython. The Win32/Win64 in the wxPython file name should match the bitness for the Python being used, which is not necessarily the same as the platform.
···
On Sunday, December 29, 2013 9:17:29 PM UTC-6, Robin Dunn wrote:
--
Robin Dunn
Software Craftsman
Tim Roberts wrote:
zc zhang wrote:
Hi, Robin,
I run it and debug with MS debugger, get follow messages:
wxbase30u_vc90.dll!010388e3()
[The following framework may be incorrect and / or missing is not
loaded symbol wxbase30u_vc90.dll]
wxbase30u_vc90.dll!0103b518()
wxmsw30u_core_vc90.dll!0177dd8a()For what it's worth:
msvcr90.dll!78583db8()
That's inside _malloc.
msvcr90.dll!78583ed8()
That's in "operator new", about to raise a "bad_alloc" exception.
msvcr90.dll!78548558()
That's fetching the C run-time per-thread data structure.
I don't know any reason why that all shouldn't work in XP, unless the
new wx is somehow allocating way more Thread Local Storage than previous
versions.
If somebody wants to try the latest Phoenix build on XP that may help find the source of the issue. It is based on wx the current 3.0 branch (version pre 3.0.1) so if this is a general problem in wxWidgets they may have solved it already.
···
--
Robin Dunn
Software Craftsman
George McCown wrote:
32-bit. I see where you are going. Change 2.7 to 64 bit?
Either that or download the 32-bit wxPython. The key point is that you
cannot mix 32-bit and 64-bit components in a single process.
···
--
Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc.
I have installed python 2.7 32bit and wxpython 3.0.0 32bit.
Visual C++ 2008 SP1 Redistributable Package x86 installed.
but problem still exists.
Then I find that if I add “wx.Log.SetLogLevel(0)” on the wx.App and remove wx.SearchCtrl component , wxpython 3.0.0 is OK.
Please help!
在 2013年12月31日星期二UTC+8上午4时56分56秒,Tim Roberts写道:
···
George McCown wrote:
32-bit. I see where you are going. Change 2.7 to 64 bit?
Either that or download the 32-bit wxPython. The key point is that you
cannot mix 32-bit and 64-bit components in a single process.–
Tim Roberts, ti...@probo.com
Providenza & Boekelheide, Inc.
Yes I verified the widget issues on XP also in the wx3.0.0 preview thread on wxPython-dev.
Seems like someone upstream needs a fix as it is apparently in the wxWidgets side of things with the compiled stuff.
Maybe in a few days the snapshot build of phoenix will have fixed it if anyone has noticed yet or may be working on it.
Until someone can pinpoint exactly where the problem started at, then you are probably stuck with using 2.9.5 until then.At least on XP.
Also, it just isn’t the searchctrl, there are other widgets also that crash the demos when run individually.
So, until 3.0.1 or whatever…
···
On Monday, December 30, 2013 8:05:07 PM UTC-6, zc zhang wrote:
I have installed python 2.7 32bit and wxpython 3.0.0 32bit.
Visual C++ 2008 SP1 Redistributable Package x86 installed.
but problem still exists.
Then I find that if I add “wx.Log.SetLogLevel(0)” on the wx.App and remove wx.SearchCtrl component , wxpython 3.0.0 is OK.
Please help!