I'm afraid I've missed most of the context here: > 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 *
In what cases is it necessary to explicitly import pywintypes before win32ui? Mark _______________________________________________ python-win32 mailing list python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
