On 31 Jul, 2010, at 23:02, Nathan Lemoine wrote:
> Running the testing application in the command line did confirm that the
> pyglet module isn't being found:
>
> File "/Users/Nate/dist/tester.app/Contents/Resources/__boot__.py", line 160,
> in _run
>execfile(path, globals(), globals())
>
Running the testing application in the command line did confirm that
the pyglet module isn't being found:
File "/Users/Nate/dist/tester.app/Contents/Resources/__boot__.py",
line 160, in _run
execfile(path, globals(), globals())
File "/Users/Nate/Desktop/tester.py", line 1, in
im
On Sat, Jul 31, 2010 at 10:26 AM, Ronald Oussoren
wrote:
>
> On 31 Jul, 2010, at 3:09, Greg Ewing wrote:
>
>> Virgil Dupras wrote:
>>> Is it possible that py2app is a little too complex for what
>>> it does?
>>
>> I think a lot of the complexity of py2app and py2exe come
>> from trying to automati
On 31 Jul, 2010, at 3:09, Greg Ewing wrote:
> Virgil Dupras wrote:
>> Is it possible that py2app is a little too complex for what
>> it does?
>
> I think a lot of the complexity of py2app and py2exe come
> from trying to automatically figure out what modules and
> libraries need to be included.
On 30 Jul, 2010, at 18:24, Russell Owen wrote:
> Fixing py2app would be great, but perhaps it would suffice to document the
> problem and let the user of py2app to fix the bizarre install left by pip.
As pip is a fairly popular tools fixing the the issue in py2app would be
better.
>
> I'll
