That's good to hear. The more I thought about it, the more it seems like
there are other cases where "non-standard" imports are more than a
little useful. I'm actually running into another Cheetah-related problem
when I use py2app (though this one is very clearly in Cheetah land), and
it's also import related. If I spot anything wacky as I look at that
problem, I'll let you know.
Kevin
Bob Ippolito wrote:
I don't think there is typically a gotcha with imports, I've certainly
never seen this happen before, and I have done imports from
applicationDidFinishLaunching: (pygame, in particular) before. I have
no idea if I should be blaming Cheetah, PyObjC or Python 2.3.0
(haven't tested with 2.4 or CVS), but I will try and remember to dig
in later.
-bob
On Jan 14, 2005, at 16:56, Kevin Dangoor wrote:
Wow. That was quick!
I didn't realize that there was a gotcha with the imports. That was
just a premature optimization, so I can easily avoid that :)
Thanks for your help... that's certainly not the kind of thing I
would have just guessed...
Kevin
Bob Ippolito wrote:
(Kevin sent me the test off-list, and I took a look at it).
I'm not sure exactly why your example crashes (somehow a retain
message gets sent to a dead or non-object), however, the problem is
that you are using an import statement from inside the
implementation of the action. Don't do that. Do your imports in
module level code.
-bob
_______________________________________________
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
_______________________________________________
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
