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, python-dev, serhiy.storchaka, steve.dower, zach.ware
Date 2014-06-06.01:58:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1402019915.67.0.386806209197.issue21665@psf.upfronthosting.co.za>
In-reply-to
Content
Are you sure you didn't swap that; OPTS=noxp for Tk and no OPTS for the other two?  OPTS=noxp would do nothing for Tcl and Tix (and might cause errors, I'm not sure), and not giving OPTS=noxp along with WINVER=0x0500 would definitely have caused an error building Tk, cutting compilation short before most of ttk could be compiled (if I remember my test from this morning correctly).

(For the record, my testing this morning included completely fresh builds of the tip of 2.7 with Tcl/Tk 8.5.15, tip of 2.7 with Tcl/Tk 8.5.2, v2.7.6 (which had Tcl/Tk 8.5.2), and default with Tcl/Tk 8.6.1, all built using the buildbot scripts, and all showed Les's issue.  I removed the noxp option in each case, and ttk worked correctly in each. To me, that says that our buildbot scripts have been wrong for a long time, but fortunately Martin has been using better options when he has built installers in the past, though I'd still like confirmation on that before I make any changes to 2.7's buildbot scripts.  Since there's no concern about keeping Win2k compatibility on 3.4 and default, I went ahead and fixed those this morning.)
History
Date User Action Args
2014-06-06 01:58:35zach.waresetrecipients: + zach.ware, loewis, python-dev, serhiy.storchaka, steve.dower, les.bothwell
2014-06-06 01:58:35zach.waresetmessageid: <1402019915.67.0.386806209197.issue21665@psf.upfronthosting.co.za>
2014-06-06 01:58:35zach.warelinkissue21665 messages
2014-06-06 01:58:34zach.warecreate