Steve Dower <steve.do...@python.org> added the comment:
> I have a patch that seems to do the right thing. It required adding > WITH_NEXT_FRAMEWORK to the globals when evaluating getpath.py 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 > getpath.py without using a debugger warn(str(globals())) or some variant at the top of getpath.py 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue46890> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
