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 benjamin.peterson, esc24, georg.brandl, ned.deily, python-dev, rhettinger, ronaldoussoren, samueljohn
Date 2013-11-05.11:47:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1383652049.67.0.583800212219.issue15663@psf.upfronthosting.co.za>
In-reply-to
Content
I don't think you can provide a solution that's compatible with existing 3th-party extensions that use Tk and includes a private copy of Tcl/Tk. 

IMHO the best solution would be to provide the Tcl/Tk headers in the Python framework as well, to make it possible to link 3th party extension with the Tk that's provided with the Python installer.  

That should be an acceptable solution for 3.4 because that's a new feature release. 

A possible pain-point are 3th-party extensions that use the limited ABI, link with Tk and are used with Tkinter.
History
Date User Action Args
2013-11-05 11:47:29ronaldoussorensetrecipients: + ronaldoussoren, georg.brandl, rhettinger, benjamin.peterson, ned.deily, samueljohn, python-dev, esc24
2013-11-05 11:47:29ronaldoussorensetmessageid: <1383652049.67.0.583800212219.issue15663@psf.upfronthosting.co.za>
2013-11-05 11:47:29ronaldoussorenlinkissue15663 messages
2013-11-05 11:47:29ronaldoussorencreate