From: "Mark Hammond"
Thanks for the note - can someone with build 213 for Python 3.0 installed check if they have the same problem or not (ie, if it is a regression or just the first report of a problem existing for a few months)?
I just tried 213 for 3.0.1 and it works OK, so it looks like a 214/3.1 regression.
Ideally an issue should be opened at sourceforge too - I'm busy at the moment, so may end up forgetting about then when I next find pywin32 time...
Done: http://sourceforge.net/tracker/?func=detail&aid=2818443&group_id=78018&atid=551954
_______________________________________________ python-win32 mailing list python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
