Le mer. 14 nov. 2018 à 03:24, Nathaniel Smith <n...@pobox.com> a écrit : > So I think what you're saying is that your goal is to get a > new/better/shinier VM, and the plan to accomplish that is: > > 1. Define a new C API. > 2. Migrate projects to the new C API. > 3. Build a new VM that gets benefits from only supporting the new API. > > This sounds exactly backwards to me? > > If you define the new API before you build the VM, then no-one is > going to migrate, because why should they bother? You'd be asking > overworked third-party maintainers to do a bunch of work with no > benefit, except that maybe someday later something good might happen.
Oh, I should stop to promote my "CPython fork" idea. There is already an existing VM which is way faster than CPython but its performances are limited by the current C API. The VM is called... PyPy! The bet is that migrating to a new C API would make your C extension faster. Victor _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
