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 ned.deily
Recipients ned.deily, pietvo
Date 2013-11-12.08:25:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1384244718.62.0.601132485199.issue19558@psf.upfronthosting.co.za>
In-reply-to
Content
In Issue 19490, Piet van Oostrum suggested:
"I think future versions of Python should add the relevant information about how they are linked to Tcl/Tk in sysconfig. This would include the path of the include files, the shared libraries and the tcl files. Or a framework location on OS X if this is used. The setup.py for extensions that need to link to Tcl/Tk can then interrogate this information, and fall back to the current way, if it is not available."

Ned Deily replied:
"Piet, yes, I've been thinking of how to do that.  Unfortunately, it can only be a hint since, in the case of an "installer" Python, there is no guarantee that the header files on the build machine are available on the installed machine in the same location or even at all."
History
Date User Action Args
2013-11-12 08:25:18ned.deilysetrecipients: + ned.deily, pietvo
2013-11-12 08:25:18ned.deilysetmessageid: <1384244718.62.0.601132485199.issue19558@psf.upfronthosting.co.za>
2013-11-12 08:25:18ned.deilylinkissue19558 messages
2013-11-12 08:25:17ned.deilycreate