Provide Tcl/Tk linkage information for extension module builds

[ned-deily]

BPO	19558
Nosy	@ned-deily

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = None
created_at = <Date 2013-11-12.08:25:18.534>
labels = ['type-feature', 'build']
title = 'Provide Tcl/Tk linkage information for extension module builds'
updated_at = <Date 2019-04-26.18:13:17.679>
user = 'https://github.com/ned-deily'

bugs.python.org fields:

activity = <Date 2019-04-26.18:13:17.679>
actor = 'BreamoreBoy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Build']
creation = <Date 2013-11-12.08:25:18.534>
creator = 'ned.deily'
dependencies = []
files = []
hgrepos = []
issue_num = 19558
keywords = []
message_count = 2.0
messages = ['202678', '228282']
nosy_count = 2.0
nosy_names = ['ned.deily', 'pietvo']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue19558'
versions = ['Python 3.5']

[ned-deily]

In bpo-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."

[BreamoreBoy]

@ned just a reminder as I see you've been talking tcl/tk on c.l.py earlier today.