Trent Mick wrote:
Given that my suggestion is no panacea, perhaps it is better to just leave it
at status quo and tell the user about the requirement to update their PATH.
Thoughts?
Trent
I have come across this issue, and am equally unsatisfied with the
solutions I've come up with so far. all of them require the user to know
too much about what's going on, and does not make the import "just work".
what if we added a python wrapper module (.py) around the native (.pyd)
modules? it would contain something like the following:
import pywintypes
import pythoncom
from _win32ui import *
this would allow us to ensure pywintypes is loaded before the native
code runs, and the python module would just pass all of the imported
stuff from the binary module through to the caller. (some extra work to
set __all__ properly is probably in order here too).
_______________________________________________
python-win32 mailing list
python-win32@python.org
http://mail.python.org/mailman/listinfo/python-win32
