Victor Stinner

> Include/Python-ast.h was removed by @vstinner Not removed, read the commit: it was moved to Include/internal/pycore_ast.h. > Include/token.h was removed by @vstinner Same, just renamed to to Include/internal/pycore_token.h. I prefer...

> _PyLong_AsByteArray, _PyLong_FromByteArray, _PyLong_NumBits It was discussed https://github.com/python/cpython/issues/111140 No clear API was proposed.

In pyperf, I tried to give the choice to the user to decide how to display data and to not take decisions for them. That's why it stores all timings,...

If it's a new option, and it doesn't change the default, i'm fine with it. Th problem is just how to explain it in the doc, shortly with simple words...

Would it be possible to add a "Display Python Version" step to display python -VV, and to check if it's a free threading build or not?

The Free Threading CI says: ``` Run python -VV Python 3.13.0b1+ (main, May 17 2024, 08:49:18) [GCC 11.4.0] ``` I'm not convinced that it's the expected binary. We should also...

Good, it now works as expected: ``` Python 3.13.0b1+ (main, May 17 2024, 08:49:18) [GCC 11.4.0] Free threading? Yes ```

Remark: If clearing env vars is a surprising/bad default behavior for end users, we can also just remove it? I did it to make benchmarks easier to reproduce.

In the main process, the function directly returns an object which contains data. Why do you need a filename? Please elaboate your use case.

You can manually change the number of computed warmup values using --warmup command line option. But yeah, it would be interesting to increase the number of warmups when running on...