> On 25 May 2021, at 21:57, Guido van Rossum <gu...@python.org> wrote: > > On Tue, May 25, 2021 at 12:34 PM Brett Cannon <br...@python.org > <mailto:br...@python.org>> wrote: > > I personally think it should be a Standards Track PEP. This PEP isn't > documenting some detail like PEP 13 or some release schedule, but is instead > proposing a rather major change to the interpreter which a lot of us will > need to understand in order to support the code (and I do realize the entire > area of "what requires a PEP and what doesn't" is very hazy). > > Now, we've done similar things before (for example, the pattern matching > implementation was a long-living branch), but the difference is that for > pattern matching, the implementation followed the design, whereas for the > changes to the bytecode interpreter that we're undertaking here, much of the > architecture will be designed as the implementation proceeds, based on what > we learn during the implementation.
Good point. We've also done long-living branching during Gilectomy which saved a lot of pain when it turned out not to be worth pursuing after all. Do you think this case is qualitatively different? - Ł
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ 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/PUMUMMZDBXICCZ6VVKU43VQY32DIYQED/ Code of Conduct: http://python.org/psf/codeofconduct/
