Mailing List Archive

Can't run Win32 Debugger outside PythonWin
I just upgraded my NT4 SP3 Workstation to Python 1.5.2 and
win32all build 124. Unluckily I can't start the debugger any
longer from outside PythonWin.
That is, typing

pywin.debugger.fail

works fine, but running fail.py from the shell gives

D:\Programme\Python\Pythonwin\pywin\debugger>fail.py
Traceback (innermost last):
File "D:\Programme\Python\Pythonwin\pywin\debugger\fail.py", line 50, in ?
a()
File "D:\Programme\Python\Pythonwin\pywin\debugger\fail.py", line 18, in a
pywin.debugger.post_mortem(sys.exc_info()[2])
File "D:\Programme\Python\Pythonwin\pywin\debugger\__init__.py", line 75, in p
ost_mortem
p = _GetCurrentDebugger()
File "D:\Programme\Python\Pythonwin\pywin\debugger\__init__.py", line 28, in _
GetCurrentDebugger
currentDebugger = debugger.Debugger()
AttributeError: Debugger

It seems the Scintilla.DLL can't be found (even the latest update from the
author's hompage). However, sys.path is OK:

D:\Programme\Python\Pythonwin\pywin\debugger>python
Python 1.5.2 (#0, Apr 13 1999, 10:51:12) [MSC 32 bit (Intel)] on win32
Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam
>>> import debugger
Traceback (innermost last):
File "<stdin>", line 1, in ?
File "D:\Programme\Python\Pythonwin\pywin\debugger\debugger.py", line 24, in ?

from pywin.framework import app, interact, editor
File "D:\Programme\Python\Pythonwin\pywin\framework\editor\__init__.py", line
90, in ?
LoadDefaultEditor()
File "D:\Programme\Python\Pythonwin\pywin\framework\editor\__init__.py", line
39, in LoadDefaultEditor
mod = __import__(prefModule)
File "D:\Programme\Python\Pythonwin\pywin\framework\editor\color\coloreditor.p
y", line 39, in ?
dllid = win32api.LoadLibrary("Scintilla.DLL")
pywintypes.api_error: (126, 'LoadLibrary', 'Das angegebene Modul wurde nicht gef
unden.')

[The German error msg says "module not found"]

>>> import sys
>>> for x in sys.path: print x
D:\Programme\Python
D:\Programme\Pythonwin
D:\Programme\Python\Pythonwin
D:\Programme\Python\win32
D:\Programme\Python\win32\lib
D:\Programme\Python
D:\Programme\Python\Lib\plat-win
D:\Programme\Python\Lib
D:\Programme\Python\DLLs
D:\Programme\Python\Lib\lib-tk
D:\Programme\Python\DLLs
D:\Programme\Python\lib
D:\Programme\Python\lib\plat-win
D:\Programme\Python\lib\lib-tk
D:\Programme\Python


Stefan
Can't run Win32 Debugger outside PythonWin [ In reply to ]
Stefan Franke wrote:

> I just upgraded my NT4 SP3 Workstation to Python 1.5.2 and
> win32all build 124. Unluckily I can't start the debugger any
> longer from outside PythonWin.
> That is, typing
>
> It seems the Scintilla.DLL can't be found (even the latest update from the
> author's hompage). However, sys.path is OK:
>
> D:\Programme\Python\Pythonwin\pywin\debugger>python
> Python 1.5.2 (#0, Apr 13 1999, 10:51:12) [MSC 32 bit (Intel)] on win32
> Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam
> >>> import debugger
> ...
> dllid = win32api.LoadLibrary("Scintilla.DLL")
> pywintypes.api_error: (126, 'LoadLibrary', 'Das angegebene Modul wurde nicht gef
> unden.')
>
> [The German error msg says "module not found"]

Sorry, I don't see this error myself. As a temporary workaround you
could try copying Scintilla.DLL into the windows or windows system
directory (often called \winnt\system32). I hope Mark has some more
insight into this as I don't understand how Python manipulates the path.

Neil Hodgson
Can't run Win32 Debugger outside PythonWin [ In reply to ]
Neil Hodgson wrote in message <371555BD.70107860@fast.fujitsu.com.au>...
>Stefan Franke wrote:
>
>> I just upgraded my NT4 SP3 Workstation to Python 1.5.2 and
>> win32all build 124. Unluckily I can't start the debugger any
>> longer from outside PythonWin.
>> That is, typing
>>
>> It seems the Scintilla.DLL can't be found (even the latest update from
the
>> author's hompage). However, sys.path is OK:

sob. Ive seen this, and thought my update solved it. Ill check into it
more...

> Sorry, I don't see this error myself. As a temporary workaround you
>could try copying Scintilla.DLL into the windows or windows system
>directory (often called \winnt\system32).

That is the best idea for now. However, you will need to remember to delete
it when a new pythonwin build comes out (fairly soon)

Mark.