On 4 Apr, 2011, at 21:04, Russell E. Owen wrote:
> In article ,
> Russell Owen wrote:
>
>>> On 29 Mar, 2011, at 22:02, Russell E. Owen wrote:
>>>
I used easy_install to install py2app 0.6 and tried it out on one of
several applications I distribute. Unfortunately the build failed wi
In article ,
Russell Owen wrote:
> > On 29 Mar, 2011, at 22:02, Russell E. Owen wrote:
> >
> >> I used easy_install to install py2app 0.6 and tried it out on one of
> >> several applications I distribute. Unfortunately the build failed with;
> >
> > The testsuite is obviously not good enough
On 3/30/11 8:25 AM, Russell Owen wrote:
BTW: I'm also not allowing my code to be zipped up because I use __file__ to
locate some non-code resources and the dynamically loaded scripts. I should
convert that code but I'm not sure if there's a standard technique that will
have long-term support.
On Mar 29, 2011, at 10:58 PM, Ronald Oussoren wrote:
>
> On 29 Mar, 2011, at 22:02, Russell E. Owen wrote:
>
>> I used easy_install to install py2app 0.6 and tried it out on one of
>> several applications I distribute. Unfortunately the build failed with;
>
> The testsuite is obviously not go
On 29 Mar, 2011, at 22:02, Russell E. Owen wrote:
> I used easy_install to install py2app 0.6 and tried it out on one of
> several applications I distribute. Unfortunately the build failed with;
The testsuite is obviously not good enough yet to catch all errors. I've done
some changes in how
I used easy_install to install py2app 0.6 and tried it out on one of
several applications I distribute. Unfortunately the build failed with;
*** using recipe: virtualenv ***
*** using recipe: PIL ***
*** using recipe: matplotlib ***
*** using recipe: pydoc ***
*** using recipe: scipy ***
*** usin
