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 terry.reedy
Recipients serhiy.storchaka, terry.reedy
Date 2014-02-08.17:58:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1391882299.78.0.167304660008.issue20560@psf.upfronthosting.co.za>
In-reply-to
Content
As I may have mentioned before, I *now* use the 'standard' one for Windows for each version of Python, as fetched by Tools/buildbots/external.bat. For 2.7 this is 8.5.2.  The reason I just noticed about a month ago is that I previously ran all repository builds with one version of tcl/tk, the latest -- and had no problems. When 3.4 switched to 8.6.0, I wanted to use that for the repository build also, but my impression is that 2.7 and 3.3 cannot run with 8.6. So I put each Python branch clone in a separate directory instead of side-by-side in one directory as recommended in the developer guide. (This is a nuisance.) I do not really understand why Windows users of 2.7 as saddled with such an old release of tcl/tk.

If there is nothing to be done about this, we can close it.
History
Date User Action Args
2014-02-08 17:58:19terry.reedysetrecipients: + terry.reedy, serhiy.storchaka
2014-02-08 17:58:19terry.reedysetmessageid: <1391882299.78.0.167304660008.issue20560@psf.upfronthosting.co.za>
2014-02-08 17:58:19terry.reedylinkissue20560 messages
2014-02-08 17:58:19terry.reedycreate