RetroSearch Browse

Tue Feb 2 15:27:36 EST 2016 · https://mail.python.org/pipermail/python-dev/2016-February/143062.html

On 02.02.2016 20:41, Yury Selivanov wrote:
> Hi Victor,
>
> On 2016-02-02 4:33 AM, Victor Stinner wrote:
>> Hi,
>>
>> Maybe it's worth to write a PEP to summarize all your changes to
>> optimize CPython? It would avoid to have to follow different threads
>> on the mailing lists, different issues on the bug tracker, with
>> external links to GitHub gists, etc. Your code changes critical parts
>> of Python: code object structure and Python/ceval.c.
>
> Not sure about that... PEPs take a LOT of time :(

True.

> Besides, all my changes are CPython specific and
> can be considered as an implementation detail.
>
>>
>> At least, it would help to document Python internals ;-)
>
> I can write a ceval.txt file explaining what's going on
> in ceval loop, with details on the opcode cache and other
> things.  I think it's even better than a PEP, to be honest.

I would love to see that. :)

Best,
Sven

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2016-February/143062.html below:

[Python-Dev] Opcode cache in ceval loop