Python and the need for speed

[Chris Angelico]

On Wed, Apr 12, 2017 at 5:19 AM, Grant Edwards
<grant.b.edwards at gmail.com> wrote:
> On 2017-04-11, Chris Angelico <rosuav at gmail.com> wrote:
>> On Wed, Apr 12, 2017 at 4:42 AM, Grant Edwards
>><grant.b.edwards at gmail.com> wrote:
>>> On 2017-04-11, Paul Rubin <no.email at nospam.invalid> wrote:
>>>
>>>> You might look at MicroPython too (micropython.org).  A fairly complete
>>>> Python 3 implementation with some ahead-of-time compiling, no fancy
>>>> JIT.  Completely breaks the Python C API though.
>>>
>>> I didn't know there was such a thing as "The Python C API".
>>>
>>> Or do you just mean that the C API is different than that chosen by
>>> the developers of https://github.com/python/cpython?
>>
>> Do you mean this?
>>
>> https://docs.python.org/3/c-api/intro.html
>
> I think so.  That's the C API for one particlar implementation of
> Python "CPython", right?
>
> There is no "Python" C API specified as part of the language
> definition is there?

Oh, I see what you mean.

That is indeed correct - there is no language-level API specification
- but it's linguistically redundant to say "the CPython C API", so
it's often not said that way.

ChrisA