This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ronaldoussoren
Recipients eric.snow, ned.deily, pablogsal, ronaldoussoren, steve.dower, vinay.sajip
Date 2022-03-07.11:52:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I have a patch that seems to do the right thing. It required adding WITH_NEXT_FRAMEWORK to the globals when evaluating to detect this scenario.

There probably should be more tests, in particular a test for a virtual environment using a framework install as I had to adjust my patch after manually testing a virtual environment.

I'm not entirely happy with the patch yet, the change to is basically the minimal change I could get away with without grokking the entire file.

There's no PR yet as I've broken my fork of cpython, fixing that is next up on the list.

BTW. Is there a way to find the values that get put into the globals dict for without using a debugger (either a real one or the printf variant)?
Date User Action Args
2022-03-07 11:52:51ronaldoussorensetrecipients: + ronaldoussoren, vinay.sajip, ned.deily, eric.snow, steve.dower, pablogsal
2022-03-07 11:52:51ronaldoussorensetmessageid: <>
2022-03-07 11:52:51ronaldoussorenlinkissue46890 messages
2022-03-07 11:52:51ronaldoussorencreate