Tim Peters wrote:
The globals set up for running the script appear not to contain a '__file__'
key, and have a '__name__' key explicitly set to None. If it set either of
these to something useful, or didn't have a '__name__' key explicitly set to
None, warning.warn() would have been able to make
Tim Peters wrote:
it *looks* like you could leave name None, but set '__file__' to something
(non-None) explicitly.
Thanks! This seems to do the trick, and I have a unit test that fails
before and passes after the change.
While creating the test, though, I ran across some disturbing behavior.
Evan Simpson wrote:
Argh. Scripts need a __name__ defined, or various activities choke. It
can't be the Id of the Script, since that can contain '.', which screws
up imports in the Script. It can't be None, since that will cause this
problem.
Are there hidden gotchas lurking around
