[Python-Dev] [Python-checkins] cpython: Issue #19512: Add PyRun_InteractiveOneObject() function

Nick Coghlan ncoghlan at gmail.com
Fri Nov 8 10:35:05 CET 2013

On 8 Nov 2013 10:15, "Eric Snow" <ericsnowcurrently at gmail.com> wrote:
> On Thu, Nov 7, 2013 at 4:55 PM, Victor Stinner <victor.stinner at gmail.com>
> > About the 72523 functions PyRun_xxx(), I don't understand something.
> > The PyRun_FileEx() 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.

Give it six months or so and I'll likely once again be looking for people
to help out with the "make embedding CPython less painful and arcane"
project that is PEP 432. There's a *lot* we can do in that space, along
with the PEP 451 based extension loading enhancements. Just throwin' it out
there ;)


> -eric
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20131108/b6809632/attachment.html>

More information about the Python-Dev mailing list