[issue9202] Update platform.win32_ver() to account for change to #8413

2010-07-08 Thread Brian Curtin
Brian Curtin added the comment: Agreed. This started out as a knee-jerk reaction to regrtest not working, but the problem is deeper. Closing this. The structseq stuff is being dealt with elsewhere. -- resolution: -> rejected stage: needs patch -> committed/rejected status: open -> cl

[issue9202] Update platform.win32_ver() to account for change to #8413

2010-07-08 Thread Eric Smith
Eric Smith added the comment: Surely we don't want to find every place that uses structseq and fix them. This will no doubt break user code as well. I think we'll need to fix structseq to somehow have its old behavior. -- nosy: +eric.smith ___ Pyth

[issue9202] Update platform.win32_ver() to account for change to #8413

2010-07-08 Thread Brian Curtin
Brian Curtin added the comment: The following little patch could do the trick. --- platform.py (revision 82643) +++ platform.py (working copy) @@ -606,7 +606,9 @@ # Find out the registry key and some general version infos winver = GetVersionEx() -maj,min,buildno,plat,csd = winv

[issue9202] Update platform.win32_ver() to account for change to #8413

2010-07-08 Thread Brian Curtin
New submission from Brian Curtin : The change to #8413 broke the use of sys.getwindowsversion() in platform.platform() calls on Windows, which subsequently breaks all runs of regrtest (e.g. buildbots) since it outputs platform info at the start. Now that structseq subclasses tuple, every field