On Fri, 30 Oct 2020 at 00:19, Fabio Zadrozny <fabi...@gmail.com> wrote: > On Thu, Oct 29, 2020 at 9:45 AM Victor Stinner <vstin...@python.org> wrote: >> >> > If it's non controversial, is a PEP needed or just an issue to track it >> > would be enough to remove those 2 lines? >> >> Incompatible changes should be well documented in What's New in Python >> 3.10. In this case, I don't think that a deprecation period is needed. >> >> Just open an issue. Please post the URL to your issue in reply to your >> email. It's even better if you can write a PR to implement your idea >> ;-)
Removing those calls would require a PEP, as it would break all sorts of tools in cases that currently work correctly. > Ok, I've created https://bugs.python.org/issue42197 to track it. Please also have a look at PEP 558 and its draft reference implementation at https://github.com/python/cpython/pull/3640 The way these trampoline calls currently work isn't just slow, it's actually broken in various ways, and changing them to use a write-through proxy instead of a dict-based snapshot means that the cost of producing those dict-based snapshots simply because tracing is turned on will go away. The PEP itself didn't seem to be particularly controversial (at least in its current form - earlier versions drew more objections), but there's a bunch of preparatory work that needs to be done before it could seriously be submitted for final review (specifically: the write-through proxy isn't actually implementing the full mutable mapping API. In order for it to do that without excessive code duplication, the helper functions already written for ordered dictionaries needed to moved out to a separate linkable module so that the new write-through proxy can reuse them without taking a separate copy of them) Cheers, Nick. P.S. If that sounds like a request for help, that's because it is ;) -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@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/RGP4UJFWUML6LQQPB4RALTBOXEHOEMHE/ Code of Conduct: http://python.org/psf/codeofconduct/
