[issue9877] Expose sysconfig._get_makefile_filename() in public API
Barry A. Warsaw
report at bugs.python.org
Mon Sep 20 14:10:06 CEST 2010
Barry A. Warsaw <barry at python.org> added the comment:
On Sep 18, 2010, at 12:23 PM, Antoine Pitrou wrote:
>Antoine Pitrou <pitrou at free.fr> added the comment:
>
>Barry's request looks reasonable. Any build information will have
>platform specificities to it.
Thanks. I'll take that as approval to land it. :)
>On the other hand, this begs the question of why you want to access
>the Python makefile at all. Is there any information in there that
>isn't currently exposed? I think it would be nice if people could
>completely forget about the existence of that file, and instead have
>nice programmatic APIs to query properties they are interested in.
In principle I agree that the parsing of pyconfig.h and Makefile are
implementation details that shouldn't matter. I'm working on the bug to
pre-parse these at build time and generate a _sysconfig module that sysconfig
would import. However, for introspection purposes, since pyconfig.h's
location is exposed, I wanted symmetry for Makefile.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue9877>
_______________________________________
More information about the Python-bugs-list
mailing list