On Wed, Jun 28, 2006 at 05:47:34PM -0700, Bob Ippolito wrote:
> You have some kind of haxie-like-thing (an InputManager maybe)
> installed. That haxie is broken and causing those messages.
> > #6 0x059be320 in DFPatch::Initialize ()
> > No symbol table info available.
Looks like SCPatch/Defaul
You have some kind of haxie-like-thing (an InputManager maybe)
installed. That haxie is broken and causing those messages.
Nothing to see here, not a bug in appscript or Python.
-bob
On Jun 28, 2006, at 5:42 PM, Jordan Breeding wrote:
> Okay, so this is going to be a bit long, I didn't know i
Okay, so this is going to be a bit long, I didn't know if you would
want the short stack trace or the full stack trace so I will just put
the full one. To reproduce the problem I ran my script with a
certain track list, the program completed and never triggered the
breakpoint. Then I clea
I don't see anything in this script that could directly cause those
warnings. It's got to be something in appscript calls into...
If you run it under GDB with a breakpoint on _NSAutoreleaseNoPool you
might be able to track it down. If you could reproduce the issue in
such a way that it was e
Okay, I am attaching a copy of the current script. Usernames, passwords, and
email addresses have been replaced with "". This code might be a little
rough, probably looks like c++ instead of pure python, etc. But it does work
except for that I get those errors from time to time. I seem t
pythonw is and always has been a stub that launches a regular python
interpreter. There is nothing special about it except for the path
the regular interpreter is located at. The only thing it can do is
enable WindowServer access; it shouldn't ever cause any issues
(especially of this sort)
Hello,
Do you think that the Python 2.4.3 Universal build could be having this effect
with python and pythonw now combined? I don't see these messages all of the
time but when I do it is a block of about 10 or so of them, and I usually only
get the messages once per run of a script even when t
