Let me explain an impression I'm getting. It is *just one aspect* of my opinion, one that doesn't make sense to me. Please tell me where it is wrong. In the C API, there's a somewhat controversial refactoring going on, which involves passing around tstate arguments. I'm not saying [the first discussion] was perfect, and there are still issues, but, however flawed the "do-ocracy" process is, it is the best way we found to move forward. No one who can/wants to do the work has a better solution. Later, Mark says there is an even better way – or at least, a less intrusive one! In [the second discussion], he hints at it vaguely (from that limited info I have, it involves switching to C11 and/or using compiler-specific extensions -- not an easy change to do). But frustratingly, Mark doesn't reveal any actual details, and a lot of the complaints are about churn and merge conflicts. And now, there's news -- the better solution won't be revealed unless the PSF pays for it! That's a very bad situation to be in for having discussions: basically, either we disregard Mark and go with the not-ideal solution, or virtually all work on changing the C API and internal structures is blocked. I sense a similar thing happening here: https://github.com/ericsnowcurrently/multi-core-python/issues/69 -- there's a vague proposal to do things very differently, but I find it hard to find anything actionable. I would like to change my plans to align with Mark's fork, or to better explain some of the non-performance reasons for recent/planned changes. But I can't, because details are behind a paywall. [the first discussion]: https://mail.python.org/archives/list/python-dev@python.org/thread/PQBGECVGV... [the second discussion]: https://mail.python.org/archives/list/python-dev@python.org/thread/KGBXVVJQZ... On 10/20/20 2:53 PM, Mark Shannon wrote:
Hi everyone,
CPython is slow. We all know that, yet little is done to fix it.
I'd like to change that. I have a plan to speed up CPython by a factor of five over the next few years. But it needs funding.
I am aware that there have been several promised speed ups in the past that have failed. You might wonder why this is different.
Here are three reasons: 1. I already have working code for the first stage. 2. I'm not promising a silver bullet. I recognize that this is a substantial amount of work and needs funding. 3. I have extensive experience in VM implementation, not to mention a PhD in the subject.
My ideas for possible funding, as well as the actual plan of development, can be found here:
https://github.com/markshannon/faster-cpython
I'd love to hear your thoughts on this.
Cheers, Mark. _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-leave@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/RDXLCH22...
Code of Conduct: http://python.org/psf/codeofconduct/