Sounds reasonable, but if what you say is true, I am surprised that not
all Python 2.3.2 releases are not equal.
How good is your information? Is it authorative?
===
I need to be in cygin because I have an extensive integrated environment
which includes many cygwin packages, and several python 3rd party packages.
I could hack it with a true win32 python, but my gut says this is not
the way to go.
Miki Tebeka wrote:
Hello John,
>>> from _winreg import *
Traceback (most recent call last):
File "<stdin>", line 1, in ?
ImportError: No module named _winreg >>>
There is no _winreg on cygwin, only on "true" win32 python.
If you must use cygwin you can either patch _winreg to work for you or
use cygwin's regtool (try regtool --help)
HTH.
Miki