ImportError under python 2.7 on windows 2000

ImportError under python 2.7 on windows 2000

I have a windows 2000 machine on which wxpython will not work under
python 2.7. It runs just fine under python 2.5.

With windows 2000 sp4, python-2.7.1, wxPython2.8-win32-ansi-2.8.11.0-
py27, I get this error:

python

Python 2.7.1 (r271:86832, Nov 27 2010, 18:30:46) [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:\Python27\lib\site-packages\wx-2.8-msw-ansi\wx\__init__.py",
line 45,in <module>
    from wx._core import *
  File "C:\Python27\lib\site-packages\wx-2.8-msw-ansi\wx\_core.py",
line 4, in <module>
    import _core_
ImportError: DLL load failed: The specified procedure could not be
found.

I've searched high and low trying to find a solution and the best I've
been able to find are suggestions to install "Microsoft Visual C++
2008 Redistributable Package (x86)" or to use Dependency walker. I
have installed the Redistributable Package; but that makes no
difference.

I don't really know what I'm doing using Dependency Walker; but I had
it open C:\Python27\Lib\site-packages\wx-2.8-msw-ansi\wx\_core_.pyd.
The only issue that I see is that is says I'm missing apphelp.dll.
However, the help for Dependency Walker says "This is normal ... This
warning can be ignored. You do not need (or want) APPHELP.DLL on
Windows 95/98/ME/2000"

I have not found any other post that has a solution that works and I
have no idea what to try next.

Gary

Hi Gary and All,

ImportError under python 2.7 on windows 2000

I have a windows 2000 machine on which wxpython will not work under
python 2.7. It runs just fine under python 2.5.

With windows 2000 sp4, python-2.7.1, wxPython2.8-win32-ansi-2.8.11.0-
py27, I get this error:

Have you tried the Unicode version of wxPython 2.8? I've used Python
2.7 and wxPython 2.8.x Unicode on Windows 2000 without issues. IIRC,
the ANSI version of wxPython is going to be going away in the 2.9.x
series.

HTH a little. Good luck.

Cheers,
Scott.

···

On Sat, Mar 26, 2011 at 2:40 PM, Gary Seven <g7.s194@gmail.com> wrote:

Hi Gary and All,

> ImportError under python 2.7 on windows 2000

> I have a windows 2000 machine on which wxpython will not work under
> python 2.7. It runs just fine under python 2.5.

> With windows 2000 sp4, python-2.7.1, wxPython2.8-win32-ansi-2.8.11.0-
> py27, I get this error:

Have you tried the Unicode version of wxPython 2.8? I've used Python
2.7 and wxPython 2.8.x Unicode on Windows 2000 without issues. IIRC,
the ANSI version of wxPython is going to be going away in the 2.9.x
series.

The unicode version also fails, but for a different reason:

python

Python 2.7.1 (r271:86832, Nov 27 2010, 18:30:46) [MSC v.1500 32 bit
(Intel)] on
win32
Type "help", "copyright", "credits" or "license" for more information.

import wx

16:47:58: Debug: src/helpers.cpp(140): 'CreateActCtx' failed with
error 0x000000
7f (the specified procedure could not be found.).

Do I need a different version or python? I only see one installer for
32bit windows.

Gary

···

On Mar 26, 2:27 pm, grunculus <gruncu...@gmail.com> wrote:

On Sat, Mar 26, 2011 at 2:40 PM, Gary Seven <g7.s...@gmail.com> wrote:

Hi Gary and All,

I'm sorry I was mistaken. My Win2k machines are still on Python
2.5.x. I have installed Python 2.7.x for some experiments with
wxPython 2.9.x on an XP machine, but haven't pursued that.

Hi Gary and All,

> ImportError under python 2.7 on windows 2000

> I have a windows 2000 machine on which wxpython will not work under
> python 2.7. It runs just fine under python 2.5.

> With windows 2000 sp4, python-2.7.1, wxPython2.8-win32-ansi-2.8.11.0-
> py27, I get this error:

Have you tried the Unicode version of wxPython 2.8? I've used Python
2.7 and wxPython 2.8.x Unicode on Windows 2000 without issues. IIRC,
the ANSI version of wxPython is going to be going away in the 2.9.x
series.

The unicode version also fails, but for a different reason:

python

Python 2.7.1 (r271:86832, Nov 27 2010, 18:30:46) [MSC v.1500 32 bit
(Intel)] on
win32
Type "help", "copyright", "credits" or "license" for more information.

import wx

16:47:58: Debug: src/helpers.cpp(140): 'CreateActCtx' failed with
error 0x000000
7f (the specified procedure could not be found.).

There are several threads that can be found with Google that talk
about differences in compiler used for 2.6 and above and various DLL
issues. That's probably what is biting you. It has bitten many
py2exe users in the past. Unfortunately, I don't know of a quick
pointer to a solution.

But perhaps this page on the Wiki will help -
http://wiki.wxpython.org/py2exe-python26

Do I need a different version or python? I only see one installer for
32bit windows.

I doubt that that's the issue, but see above.

HTH a little, and sorry for the misdirection earlier. Good luck.

Gary

Cheers,
Scott.

···

On Sat, Mar 26, 2011 at 5:54 PM, Gary Seven <g7.s194@gmail.com> wrote:

On Mar 26, 2:27 pm, grunculus <gruncu...@gmail.com> wrote:

On Sat, Mar 26, 2011 at 2:40 PM, Gary Seven <g7.s...@gmail.com> wrote:

IIRC that is only a warning and wxPython should continue to work normally after the message is displayed. Is that not the case?

···

On 3/26/11 2:54 PM, Gary Seven wrote:

On Mar 26, 2:27 pm, grunculus<gruncu...@gmail.com> wrote:

Hi Gary and All,

On Sat, Mar 26, 2011 at 2:40 PM, Gary Seven<g7.s...@gmail.com> wrote:

ImportError under python 2.7 on windows 2000

I have a windows 2000 machine on which wxpython will not work under
python 2.7. It runs just fine under python 2.5.

With windows 2000 sp4, python-2.7.1, wxPython2.8-win32-ansi-2.8.11.0-
py27, I get this error:

Have you tried the Unicode version of wxPython 2.8? I've used Python
2.7 and wxPython 2.8.x Unicode on Windows 2000 without issues. IIRC,
the ANSI version of wxPython is going to be going away in the 2.9.x
series.

The unicode version also fails, but for a different reason:

python

Python 2.7.1 (r271:86832, Nov 27 2010, 18:30:46) [MSC v.1500 32 bit
(Intel)] on
win32
Type "help", "copyright", "credits" or "license" for more information.

import wx

16:47:58: Debug: src/helpers.cpp(140): 'CreateActCtx' failed with
error 0x000000
7f (the specified procedure could not be found.).

--
Robin Dunn
Software Craftsman

Sorry it took me a while to get back to this.

Robin, yes you are right. I did not realize at first but - yes, it is
just a warning, everything seems to work normally except the message
it spits out.

I have ready through tons of posts that discuss this issue with
py2exe. However, I'm not using py2exe. None the less, I'll go through
them again in case I missed something. I just don't remember seeing
anything that was relevant to me.

For now, the important thing is that it does work using the unicode
version.

Thanks for all of your help
Gary

···

On Mar 28, 10:22 am, Robin Dunn <ro...@alldunn.com> wrote:

On 3/26/11 2:54 PM, Gary Seven wrote:

> On Mar 26, 2:27 pm, grunculus<gruncu...@gmail.com> wrote:
>> Hi Gary and All,

>> On Sat, Mar 26, 2011 at 2:40 PM, Gary Seven<g7.s...@gmail.com> wrote:
>>> ImportError under python 2.7 on windows 2000

>>> I have a windows 2000 machine on which wxpython will not work under
>>> python 2.7. It runs just fine under python 2.5.

>>> With windows 2000 sp4, python-2.7.1, wxPython2.8-win32-ansi-2.8.11.0-
>>> py27, I get this error:

>> Have you tried the Unicode version of wxPython 2.8? I've used Python
>> 2.7 and wxPython 2.8.x Unicode on Windows 2000 without issues. IIRC,
>> the ANSI version of wxPython is going to be going away in the 2.9.x
>> series.

> The unicode version also fails, but for a different reason:
>> python
> Python 2.7.1 (r271:86832, Nov 27 2010, 18:30:46) [MSC v.1500 32 bit
> (Intel)] on
> win32
> Type "help", "copyright", "credits" or "license" for more information.
>>>> import wx
> 16:47:58: Debug: src/helpers.cpp(140): 'CreateActCtx' failed with
> error 0x000000
> 7f (the specified procedure could not be found.).

IIRC that is only a warning and wxPython should continue to work
normally after the message is displayed. Is that not the case?

--
Robin Dunn
Software Craftsmanhttp://wxPython.org