Papagayo doesn't work on Mac OS X Leopard

[skyvan]

I just installed Mac OS X Leopard and now Papagayo 1.1 doesn't work anymore. Does anyone have any ideas how to fix this?

[heyvern]

Try reinstalling Papagayo. Other than that I don't think there is much to do but hope it gets fixed someday. I really don't think efrontier is spending any time with papagayo since it is open source and free.

-vern

[kevin]

Yeah, I installed Leopard too and now Papagayo won't boot for me either. Reinstalled it but still won't work. I've been using Photoshop 7 for years and that won't work with Leopard either.

[myles]

Replace all Pithon words below with with the comedy team/snake name that's spelled with a 'y' - there's a default security restriction on this forum (to prevent running malicious scripts) that prevents me from posting if I use the p-y-t-h-o-n word, except in URLs and similarly safe contexts.

It appears to be a problem with the Pithon launcher configuration on Leopard rather than a problem with Papagayo, and a similar situation is showing up in a number of Mac/Pithon forums.

Option 1 (different Pithon path on Leopard):
Try doing this in a command line window:
$ export PITHONPATH=/Library/Pithon/2.5/site-packages
Then trying to run Papagayo again
(from http://the.taoofmac.com/space/blog/2007/11/11/1922 )

Option 2 (should also work on pre-Leopard Macs):
Find the Papagayo program folder, open a command line window in that folder, then try
$ pithon papagayo.py
(possibly that might be $ pithon papagayo.pyc ? or even $ pithon papagayo ? I'm not a Mac user, so I'm guessing wildly here)
(from http://www.gossamer-threads.com/lists/p ... hon/599638)
That's assuming the original Pithon source file is included with the Mac distribution of Papagayo.

Option 3:
Try option 1, then option 2 in the same commandline session

Good luck!
That's all the guessing I can do without actually getting within visual range of a Mac.

Regards, Myles.

[mooncaine]

Has this worked for anyone?

[ulrik]

not for me, i tried all 3 examples but with no luck.

[douglsmith]

I also tried the above suggestions with no luck. Here's a dump of the Mac console log when Papagayo tries to start.

Code: Select all

12/20/07 11:25:13 AM [0x0-0x49049].Papagayo[798] Exception in AE event handler function 
12/20/07 11:25:13 AM [0x0-0x49049].Papagayo[798] Traceback (most recent call last): 
12/20/07 11:25:13 AM [0x0-0x49049].Papagayo[798]   File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/plat-mac/argvemulator.py", line 76, in callback_wrapper 
12/20/07 11:25:13 AM [0x0-0x49049].Papagayo[798]     raise 'Cannot happen: AE callback without handler', (_class, _type) 
12/20/07 11:25:13 AM [0x0-0x49049].Papagayo[798] Cannot happen: AE callback without handler 
12/20/07 11:25:13 AM [0x0-0x49049].Papagayo[798] : ('tvea', 'ppao') 
12/20/07 11:25:13 AM [0x0-0x49049].Papagayo[798] Traceback (most recent call last): 
12/20/07 11:25:13 AM [0x0-0x49049].Papagayo[798]   File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/plat-mac/argvemulator.py", line 53, in lowlevelhandler 
12/20/07 11:25:13 AM [0x0-0x49049].Papagayo[798]     AE.AEProcessAppleEvent(event) 
12/20/07 11:25:13 AM [0x0-0x49049].Papagayo[798] Error: (-1, 'queue element not found during deletion') 
12/20/07 11:25:14 AM [0x0-0x49049].Papagayo[798] AE error:  (-1, 'queue element not found during deletion') 
12/20/07 11:25:14 AM [0x0-0x49049].Papagayo[798] in High Level Event: '0x61657674' '0x70706f61' 
12/20/07 11:25:14 AM [0x0-0x49049].Papagayo[798] Traceback (most recent call last): 
12/20/07 11:25:14 AM [0x0-0x49049].Papagayo[798]   File "/Applications/Papagayo/Papagayo.app/Contents/Resources/__argvemulator_papagayo.py", line 4, in ? 
12/20/07 11:25:14 AM [0x0-0x49049].Papagayo[798]     execfile(os.path.join(os.path.split(__file__)[0], "papagayo.py")) 
12/20/07 11:25:14 AM [0x0-0x49049].Papagayo[798]   File "/Applications/Papagayo/Papagayo.app/Contents/Resources/papagayo.py", line 23, in ? 
12/20/07 11:25:14 AM [0x0-0x49049].Papagayo[798]     import wx 
12/20/07 11:25:14 AM [0x0-0x49049].Papagayo[798] ImportError: No module named wx 
12/20/07 11:25:14 AM com.apple.launchd[186] ([0x0-0x49049].Papagayo[798]) Exited with exit code: 1 

[kirkmona]

I wrote lost marble and not to worry. They are working on a new Leopard friendly version as we speak. They still haven't changed their site though and it says the current version works with 10.4 or later which is confusing an inaccurate. It would be pretty easy to put a note up that says 10.5 compatibility is forthcoming.

If you write tech support and ask nicely they may even let you beta test it. I have a copy and rest assured it does work. There are a couple of bugs but nothing is a deal breaker so far. Sit tight and wait for the release or ask to test it. They were going to release it by the end of January but they must be ironing out a few kinks still. I would expect it to be released soon.

~Kirk

[Lost Marble]

We do have a working version for Leopard, but it has a few bugs still. The bugs appear to be display bugs only (redraw glitches and such) - for the most part it works as expected. You can download it here if you're using MacOS X 10.5 (Leopard).

http://www.lostmarble.com/downloads/pap ... eopard.zip

-Mike

[Rasheed]

Now it works again. Thanks a million, Mike!