I just installed python-2.6.2.msi from Python.org
and wxPython2.8-win32-ansi-2.8.10.1-py26.exe and now can’t import wx. (I
had py2.4, but uninstalled)
This reminds me of a basic question I had before: what are the compilers
used for the Win32 binaries? Is this a compiler compatibility issue? a wx
build bug? MS?
From brand new install:
C:\projects>python
Python 2.6.2 (r262:71605, Apr 14 2009, 22:40:02) [MSC v.1500 32 bit
(Intel)] on
win32
Type “help”, “copyright”, “credits” or
“license” for more information.
import wx
Traceback (most recent call last):
File “”, line 1, in
File
“C:\Python26\lib\site-packages\wx-2.8-msw-ansi\wx_init_.py”,
line 45,
in
from wx._core import *
File
“C:\Python26\lib\site-packages\wx-2.8-msw-ansi\wx_core.py”,
line 4, in <
import _core_
ImportError: DLL load failed: The specified procedure could not be
found.
I just installed python-2.6.2.msi from Python.org
and wxPython2.8-win32-ansi-2.8.10.1-py26.exe and now can’t import wx. (I
had py2.4, but uninstalled)
This reminds me of a basic question I had before: what are the compilers
used for the Win32 binaries? Is this a compiler compatibility issue? a wx
build bug? MS?
From brand new install:
C:\projects>python
Python 2.6.2 (r262:71605, Apr 14 2009, 22:40:02) [MSC v.1500 32 bit
(Intel)] on
win32
Type “help”, “copyright”, “credits” or
“license” for more information.
import wx
Traceback (most recent call last):
File “”, line 1, in
File
“C:\Python26\lib\site-packages\wx-2.8-msw-ansi\wx_init_.py”,
line 45,
in
from wx._core import *
File
“C:\Python26\lib\site-packages\wx-2.8-msw-ansi\wx_core.py”,
line 4, in <
import _core_
ImportError: DLL load failed: The specified procedure could not be
found.
The long answer has to do with the new way Python is compiled.
Starting with 2.6 and 3.0, Python is compiled with MS Visual Studio
2008 for Windows. This adds SxS assemblies to the mix which has been
causing major issues with wx and other 3rd party packages.
The newest version of wx was supposed to help alleviate this issue.
Anyway, that wiki entry explains what dlls you'll probably need. If it
still won't run with all that (and the manifests), then you'll
probably want to download Dependency Walker and use that to check your
executable.
- Mike
···
On Aug 13, 12:06 pm, RJ <r...@blue-cove.com> wrote:
I just installed python-2.6.2.msi from Python.org and
wxPython2.8-win32-ansi-2.8.10.1-py26.exe and now can't import wx. (I
had py2.4, but uninstalled)
This reminds me of a basic question I had before: what are the
compilers used for the Win32 binaries? Is this a compiler
compatibility issue? a wx build bug? MS?
From brand new install:
C:\projects>python
Python 2.6.2 (r262:71605, Apr 14 2009, 22:40:02) [MSC v.1500 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
"C:\Python26\lib\site-packages\wx-2.8-msw-ansi\wx\__init__.py", line 45,
in <module>
from wx._core import *
File "C:\Python26\lib\site-packages\wx-2.8-msw-ansi\wx\_core.py",
line 4, in <
>
import _core_
ImportError: DLL load failed: The specified procedure could not be found.
>>>
I just installed python-2.6.2.msi from Python.org and wxPython2.8-win32-ansi-2.8.10.1-py26.exe and now can't import wx. (I had py2.4, but uninstalled)
This reminds me of a basic question I had before: what are the compilers used for the Win32 binaries? Is this a compiler compatibility issue? a wx build bug? MS?
Both Py 2.6 and wxPython for py2.6 use the same MS compiler - at least as far as I know.
While 2.6 is still a bit "bleeding" edge this should work.
Only difference on my py26 test system is that I use wxPython Unicode build. Any reason why you are using the ansi build? IIRC there will soon be no more ansi builds.
I would reinstall wxPython and ensure that you don't have any errors in the installation.
The error pointed out by Jair is not your problem, as it relates to a py2exe'd application, see the Deployment page on the wxPython wiki on how to resolve that issue.
RJ wrote:
> I just installed python-2.6.2.msi from Python.org and
> wxPython2.8-win32-ansi-2.8.10.1-py26.exe and now can't import wx. (I
> had py2.4, but uninstalled)
> This reminds me of a basic question I had before: what are the
> compilers used for the Win32 binaries? Is this a compiler
> compatibility issue? a wx build bug? MS?
Both Py 2.6 and wxPython for py2.6 use the same MS compiler - at least
as far as I know.
While 2.6 is still a bit "bleeding" edge this should work.
Only difference on my py26 test system is that I use wxPython Unicode
build. Any reason why you are using the ansi build? IIRC there will
soon be no more ansi builds.
I would reinstall wxPython and ensure that you don't have any errors in
the installation.
Thanks Werner,
I just uninstalled ansi and installed unicode, now there is only a non fatal message:
C:\projects>python
Python 2.6.2 (r262:71605, Apr 14 2009, 22:40:02) [MSC v.1500 32 bit (Intel)] on
win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import wx
11:48:06: Debug: src/helpers.cpp(140): 'CreateActCtx' failed with error 0x000000
7f (the specified procedure could not be found.).
>>> wx.__version__
'2.8.10.1'
>>>
I want a nice well behaved toolbar that remains stationary at the top of my AUI frame. I’ve done an AddPane for the toolbar as in the wxPython demo, but I don’t want it to be removable (achieved) and also don’t want the knurled gripper there.
The toolbar added with that doesn’t move, so the gripper is superfluous now, and I’d like a cleaner look without it.
I find it’s hard to find out what options there for AddPane from the documentation (maybe there’s are other doc’s somewhere I haven’t discovered with Google).
On Thu, Aug 20, 2009 at 9:17 AM, Ross<rossgk@gmail.com> wrote:
I want a nice well behaved toolbar that remains stationary at the top of my
AUI frame. I've done an AddPane for the toolbar as in the wxPython demo,
but I don't want it to be removable (achieved) and also don't want the
knurled gripper there.
self._mgr.AddPane(self.tb2, wx.aui.AuiPaneInfo().
Name("tb2").Caption("Toolbar 2").ToolbarPane().
Top().Row(1).MinSize(wx.Size(-1,50)).Dockable(False))
The toolbar added with that doesn't move, so the gripper is superfluous now,
and I'd like a cleaner look without it.
I find it's hard to find out what options there for AddPane from the
documentation (maybe there's are other doc's somewhere I haven't discovered
with Google).
Any suggestions? Thx in advance...
If you don' t want it to be movable why not just use the regular
wx.ToolBar instead of the AuiToolbar?
Perhaps there's a newer source of docs, but that's what I use.
Rob
···
On Thu, Aug 20, 2009 at 7:17 AM, Ross<rossgk@gmail.com> wrote:
I want a nice well behaved toolbar that remains stationary at the top of my
AUI frame. I've done an AddPane for the toolbar as in the wxPython demo,
but I don't want it to be removable (achieved) and also don't want the
knurled gripper there.
self._mgr.AddPane(self.tb2, wx.aui.AuiPaneInfo().
Name("tb2").Caption("Toolbar 2").ToolbarPane().
Top().Row(1).MinSize(wx.Size(-1,50)).Dockable(False))
The toolbar added with that doesn't move, so the gripper is superfluous now,
and I'd like a cleaner look without it.
Hi,
does ....Gripper(False).... in the AuiPaneInfo() of the
self._mgr.AddPane call not do what you need, or am I maybe missing
something?
vbr
···
2009/8/20 Ross <rossgk@gmail.com>:
I want a nice well behaved toolbar that remains stationary at the top of my
AUI frame. I've done an AddPane for the toolbar as in the wxPython demo,
but I don't want it to be removable (achieved) and also don't want the
knurled gripper there.
self._mgr.AddPane(self.tb2, wx.aui.AuiPaneInfo().
Name("tb2").Caption("Toolbar 2").ToolbarPane().
Top().Row(1).MinSize(wx.Size(-1,50)).Dockable(False))
The toolbar added with that doesn't move, so the gripper is superfluous now,
and I'd like a cleaner look without it.
I find it's hard to find out what options there for AddPane from the
documentation (maybe there's are other doc's somewhere I haven't discovered
with Google).
Any suggestions? Thx in advance...
Ross. @ottaross
I was having trouble finding a full list of valid methods for the
AddPane call, so didn't know about the Gripper(False) option. I'd
seen GripperTop() but trying to find methods by reading examples is
an inefficient way to learn an interface.
I see now the methods are in the AUIPaneInfo reference area, hence my
inability to find them under the AddPane documentation.
Still learning - thanks for the help
R.
···
On 20-Aug-09, at 11:37 AM, Rob McMullen wrote:
Looks like adding .Gripper(False) to the end of the chain works, at
least on linux and 2.8.9.2 (and probably later).
Thx for the suggestion, will