Re: [Pyobjc-dev] PyObjC Standalone applications socket problem
Brought to you by:
ronaldoussoren
|
From: Bob I. <bo...@re...> - 2004-04-14 14:07:20
|
On Apr 14, 2004, at 9:46 AM, David Giffin wrote: > I have been using PyObjC for a few weeks now and as a rule, I love it. > I have hit a snag though. When I bundle an application using the > --standalone option it builds, but the program fails when it goes to > use a socket. This problem doesn't occur when I build with the > --sem-standalone option, only when using the --standalone. The program > actually continues to run, no crash or anything, but it does not do > it's socket communications. The actual error that I find in the > console is: > > no codec search functions registered: can't find encoding > > Any help with this would be appreciated. I am running on Panther with > all the latest updates. The whole reason I need the --standalone > option is because I have been getting requests for programs I have > written from users on Jaguar, and the programs won't run on Jaguar as > --semi-shared. It has nothing to do with sockets really, you probably just need to include the encodings package, the _codecs extension, and the codecs module. These are all imported implicitly by Python internals as-needed, so BundleBuilder isn't necessarily going to pick it up on its own. -bob |