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 steve.dower
Recipients eric.snow, ned.deily, pablogsal, ronaldoussoren, steve.dower, vinay.sajip
Date 2022-03-07.17:02:09
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.

I haven't had a chance to go through all your changes, and I'm only very vaguely familiar with this space anyway, but isn't WITH_NEXT_FRAMEWORK a compile-time option? I'm sure that's how it was used in the old getpath.

> Is there a way to find the values that get put into the globals dict for without using a debugger

warn(str(globals())) or some variant at the top of should do it. There's also an "#if 0" section in getpath.c that will print it out (unless I deleted it before merging). There's nothing permanently built in to do this, as I suspect the security concerns (information leakage) would come up more often than the debugging concerns.
Date User Action Args
2022-03-07 17:02:09steve.dowersetrecipients: + steve.dower, vinay.sajip, ronaldoussoren, ned.deily, eric.snow, pablogsal
2022-03-07 17:02:09steve.dowersetmessageid: <>
2022-03-07 17:02:09steve.dowerlinkissue46890 messages
2022-03-07 17:02:09steve.dowercreate