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 markroseman
Recipients benjamin.peterson, esc24, georg.brandl, kbk, markroseman, ned.deily, python-dev, rhettinger, ronaldoussoren, samueljohn, terry.reedy
Date 2015-08-05.21:49:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1438811365.96.0.483133559588.issue15663@psf.upfronthosting.co.za>
In-reply-to
Content
I'd like to revisit this, particularly in the context of some of the discussions regarding future improvements of IDLE.

Assume we have a barebones Tcl/Tk framework build of e.g. 8.6.4 as part of the installer (core Tcl/Tk, not like e.g. ActiveTcl).

Would something like this work?

1. if just system Tcl/Tk already installed (/System/Library/Frameworks), install new /Library/Frameworks/Tcl.framework and /Library/Frameworks/Tk.framework

2. if /Library/Frameworks/Tcl.framework is installed, but doesn't have 8.6.x (e.g. may have Versions/8.4), add the new version into the existing framework, so we'd then have a 8.4.x and a 8.6.4 installed

3. if there's already /Library/Frameworks/Tcl.framework/Versions/8.6 and it's a lower version (e.g. 8.6.1) we could simply nag them in the installer to consider upgrading on their own (the theory being that if they've installed it once somehow they can most likely do it again with a newer version of whatever they have)

This way if there's any existing Tcl/Tk there that other things are linking against, it shouldn't get disturbed. Possible, or just wishful thinking?
History
Date User Action Args
2015-08-05 21:49:26markrosemansetrecipients: + markroseman, georg.brandl, rhettinger, terry.reedy, kbk, ronaldoussoren, benjamin.peterson, ned.deily, samueljohn, python-dev, esc24
2015-08-05 21:49:25markrosemansetmessageid: <1438811365.96.0.483133559588.issue15663@psf.upfronthosting.co.za>
2015-08-05 21:49:25markrosemanlinkissue15663 messages
2015-08-05 21:49:24markrosemancreate