Barry A. Warsaw <ba...@python.org> added the comment: On Sep 18, 2010, at 12:23 PM, Antoine Pitrou wrote:
>Antoine Pitrou <pit...@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 <rep...@bugs.python.org> <http://bugs.python.org/issue9877> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
