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 terry.reedy
Recipients barry, eric.araujo, ezio.melotti, nadeem.vawda, ncoghlan, pitrou, python-dev, rosslagerwall, tarek, terry.reedy, vstinner
Date 2011-10-12.19:52:06
SpamBayes Score 1.25953e-07
Marked as misclassified No
Message-id <>
Since #9878 proposes an *alternate* solution to *part* of the sysconfig problem, I disagree with 'supersede'. A Python solution would be more useful for other implementations if enough of the sysconfig info is not CPython specific.

A CPython design feature is that it parses and compiles Python code just once per run, and imported modules just once until the code changes (or might have). For functions, everything possible is put into a behind-the-scenes code object. So even inner functions are parsed and compiled just once.

The problem with sysconfig, it appears, is that lacks the equivalent design feature but instead does the equivalent of re-parsing and re-compiling inner functions with each outer function call.
Date User Action Args
2011-10-12 19:52:07terry.reedysetrecipients: + terry.reedy, barry, ncoghlan, pitrou, vstinner, nadeem.vawda, tarek, ezio.melotti, eric.araujo, rosslagerwall, python-dev
2011-10-12 19:52:06terry.reedysetmessageid: <>
2011-10-12 19:52:06terry.reedylinkissue13150 messages
2011-10-12 19:52:06terry.reedycreate