➜

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 ronaldoussoren
Recipients esc24, ned.deily, ronaldoussoren, samueljohn
Date 2012-12-31.07:29:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1356938945.74.0.240054198961.issue15663@psf.upfronthosting.co.za>
In-reply-to
Content 
The logical location for installing and embedded Tcl/Tk is either in {sys.prefix}/lib (for a unix install of Tk) or in Python.framework/Versions/X.Y/Frameworks (for a Tcl/Tk framework install).

In either case Tcl/Tk would be installed *inside* Python.framework and hence couldn't conflict with other installations of Tcl/Tk (system, activate-state, homebrew, ...).

Note that this would also make it harder for end users to upgrade Tcl/Tk, currently they can use the ActiveState installer to install a better Tk release and that would no longer be necessary.

That would be a small cost relative to the large gain of having a working Tk release.
History
Date User Action Args
2012-12-31 07:29:05ronaldoussorensetrecipients: + ronaldoussoren, ned.deily, samueljohn, esc24
2012-12-31 07:29:05ronaldoussorensetmessageid: <1356938945.74.0.240054198961.issue15663@psf.upfronthosting.co.za>
2012-12-31 07:29:05ronaldoussorenlinkissue15663 messages
2012-12-31 07:29:05ronaldoussorencreate