[Python-Dev] [Python-checkins] cpython: Issue #19512: Add PyRun_InteractiveOneObject() function (original) (raw)
Eric Snow ericsnowcurrently at gmail.com
Fri Nov 8 01:15:35 CET 2013
- Previous message: [Python-Dev] [Python-checkins] cpython: Issue #19512: Add PyRun_InteractiveOneObject() function
- Next message: [Python-Dev] [Python-checkins] cpython: Issue #19512: Add PyRun_InteractiveOneObject() function
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Nov 7, 2013 at 4:55 PM, Victor Stinner <victor.stinner at gmail.com> wrote:
About the 72523 functions PyRunxxx(), I don't understand something. The PyRunFileEx() is documented in the Python "very high" C API to use Python. But this function is not part of the stable ABI. So there is no "very high" function in the stable ABI to use Python?
My understanding is that if you are using the PyRun_* API (embedding?), you aren't concerned with maintaining binary compatibility across Python versions. If you are writing an extension module, you probably aren't using PyRun_*.
Another question: it's not documented if a function is part or not part of the stable ABI. So as an user of the API, it is hard to check if a function is part of the stable ABI or not.
The best we have is probably PEP 384. I've been meaning to work on the C-API docs for a while and add a concise reference page that would include a summary of the stable API. Alas, other things have taken precedence.
-eric
- Previous message: [Python-Dev] [Python-checkins] cpython: Issue #19512: Add PyRun_InteractiveOneObject() function
- Next message: [Python-Dev] [Python-checkins] cpython: Issue #19512: Add PyRun_InteractiveOneObject() function
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]