Re: [Pyobjc-dev] No module named os - Erm, uh?

[Ronald O. <ron...@ma...>]

On 7 Oct, 2007, at 22:20, Zachery Bir wrote:

> On Oct 2, 2007, at 10:31 AM, Ronald Oussoren wrote:
>
>> On Tuesday, October 02, 2007, at 04:18PM, "Ben Artin"
>> <be...@ar...> wrote:
>>>> I've gotten several bug reports about Thumbscrew dying on startup
>>>> with "No module named os". It's built with Python 2.5, so includes
>>>> its own Python runtime, and os is explicitly imported. In fact, it
>>>> runs quite well for *most* people who've downloaded it.
>>>>
>>>> Can anyone think of what I might ask these certain people about
>>>> their
>>>> environment/setup to see what might be different? Would having an
>>>> explicit PYTHONPATH/PYTHONHOME in their environment (like, through
>>>> a .MacOSX/environment.plist) cause this?
>>>
>>> Yes, anything that causes PYTHONPATH or PYTHONHOME to point to the
>>> wrong place when your app is run will cause this. Assuming the users
>>> are just launching from the Finder, Environment.plist would be my
>>> first guess.
>>
>> PYTHONPATH should get cleared by the py2app stub executable, unless
>> the use_pythonpath option is on in the Info.plist of the application.
>>
>> PYTHONHOME should also be set to the right value by the stub
>> executable.
>>
>> But either way, I consider this to be a bug in py2app: py2app build
>> application bundles should just work.
>
> It seems to be. I've checked the generated Info.plist and
> use_pythonpath is set to No. When I explicitly set a PYTHONHOME in
> my .MacOSX/Environment.plist, I can reproduce the "No module named
> os" error on startup.
>
> The link to the py2app trac seems to point instead to the MacPython
> moin wiki. Where should this bug get filed?

As far as I know there is no py2app bug tracker at the moment. Feel  
free to abuse the pyobjc one.

Ronald