This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author zach.ware
Recipients les.bothwell, loewis, serhiy.storchaka, steve.dower, zach.ware
Date 2014-06-05.15:25:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1401981914.1.0.828407345773.issue21665@psf.upfronthosting.co.za>
In-reply-to
Content
I can confirm this on the current 2.7 branch and, oddly, on a fresh build of v2.7.6.  This looks like it was caused by the way Tcl/Tk was compiled, specifically the 'COMPILERFLAGS=-DWINVER=0x0500' and 'OPTS=noxp' options which are supposed to be for Win2k support.  Removing just 'OPTS=noxp' causes a compilation failure (due to WINVER redefinition), but removing both makes ttk work properly.

Steve: how did you compile Tcl/Tk for the 2.7.7 installer?

Martin: how have you compiled Tcl/Tk for past installers?  In particular, Python 3.2's ttk works perfectly Win2k, but is properly themed on Windows 7, which leads me to believe that you did not use the 'Win2k compatibility' options.
History
Date User Action Args
2014-06-05 15:25:14zach.waresetrecipients: + zach.ware, loewis, serhiy.storchaka, steve.dower, les.bothwell
2014-06-05 15:25:14zach.waresetmessageid: <1401981914.1.0.828407345773.issue21665@psf.upfronthosting.co.za>
2014-06-05 15:25:14zach.warelinkissue21665 messages
2014-06-05 15:25:13zach.warecreate