Embedding Python in Visual C++ 6.0

Mark Hammond mhammond at skippinet.com.au
Thu Apr 13 22:28:25 EDT 2000


It appears that 2 win32ui.pyd files are being loaded.  This is almost
certainly my fault.  It is possible that in the registry you already have
a "Modules" subkey that specifies the location of win32ui.pyd?

Also, FYI, in the CVS version of Pythonwin, this implementation has
changed.  It now doesnt attempt to find registered modules or any of the
other funky stuff that it does now.  The new code is simpler and more
robust - but does insist that win32ui.pyd is either on your PYTHONPATH, or
in the same directory as pythonwin.exe - no a burden IMO!  The new code
also magically works with either 1.5 or 1.6.

Anyway, whatever the reason, the clues are:

...
> Loaded symbols for 'C:
> \Programme\Python\Pythonwin\src\work\Pythonwin\Build\win32ui_d.pyd'

That is fine:
...

> Extension module C:
> \Programme\Python\Pythonwin\src\work\Pythonwin\Build\win32ui_d.pyd
> initialising.

Still looking good!

> LDR: Dll win32ui_d.pyd base 1e400000 relocated due to collision with C:
> \Programme\Python\Pythonwin\src\work\Pythonwin\Build\win32ui_d.pyd
> Preloaded symbols may not match 'C:
> \Programme\Python\Pythonwin\win32ui_d.pyd'.

Did you cut any messages?  This message appears to imply another
win32ui_d.pyd has been loaded, and its symbols have been relocated due to
a clash with another win32ui_d.pyd.

Can you ensure you system has no others win32ui*.pyd.

Also, I highly recommend getting the CVS version of Pythonwin - just for
the new startup code if nothing else.

Mark.






More information about the Python-list mailing list