Ned Deily added the comment:

Typically, for other sorts of build configuration data, we have relied on 
extracting that from the ./configure-produced Makefile and making it available 
via sysconfig.get_config_var().  I think we should be cautious about bloating 
sys.implementation with platform-specific data unless there is an overriding 
need for it, for example, if it is needed during interpreter initialization 
before sysconfig can be initialized.  If not, I'd look at adding the needed 
values as configuration variables in configure.ac.

----------
nosy: +ned.deily

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue27442>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to