I have been distributing a mac application built with py2app. For
months I have received reports of users who were not able to use the
application because of the error "ImportError: No module named os". I
was not able to reproduce the error and was unable to help them,
except to suggest th
Hi david,
I was wondering if you found a work around for the $make problem as I
have encountered the same thing.
Any help would be appreciated.
Thanks,
-Brian
Brian Hunter
brianhunterstudio.com
___
Pythonmac-SIG maillist - Pythonmac-SIG@python
You could use a DMG instead of a zip file. That's more standard anyway.
Also, have you tried unzipping the file with BOMarchive helper (the
built-in unzipping tool that works with Finder)? If that works without
corrupting your file, then you could just recommend that folks use that
instead of
Ronald Oussoren mac.com> writes:
>
>
> On 19 Apr, 2007, at 17:11, Will Henney wrote:
>
> > My initial try was to use "utf-8" as the output codec, but that
> > wrote garbage
> > characters when I ran it in Terminal.app - any idea why?
>
> That's strange, I'd expect UTF-8 to work just fine (
On 24 Apr, 2007, at 5:45, Brian Christensen wrote:
Following up on this lead we found that there is a problem with
StuffIt 10. My application was distributed as a zip file so the user
used StuffIt to unzip the file. It turns out that StuffIt was
unzipping and deleting the site-packages.zip ins
