Author Mark.Shannon
Recipients Mark.Shannon, brett.cannon, dino.viehland, eric.snow, fabioz, vstinner
Date 2019-11-04.10:03:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1572861790.81.0.912775204512.issue38500@roundup.psfhosted.org>
In-reply-to
Content
I'm strongly opposed to this change.

PEP 523 does not specify what the semantics of changing the interpreter frame evaluator actually is:
Is the VM obliged to call the new interpreter?
What happens if the custom evaluator leaves the VM in a inconsistent state?
Does the VM have to roll back any speculative optimisations it has made? What happens if it the evaluator is changed multiple times by different modules?
What if the evaluator is changed when a coroutine or generator is suspended, or in another thread?
I could go on...

IMO this punches a big hole in the Python execution model, but provides no benefit.
History
Date User Action Args
2019-11-04 10:03:10Mark.Shannonsetrecipients: + Mark.Shannon, brett.cannon, vstinner, fabioz, dino.viehland, eric.snow
2019-11-04 10:03:10Mark.Shannonsetmessageid: <1572861790.81.0.912775204512.issue38500@roundup.psfhosted.org>
2019-11-04 10:03:10Mark.Shannonlinkissue38500 messages
2019-11-04 10:03:10Mark.Shannoncreate