has <[EMAIL PROTECTED]> wrote:
> >> Are you using background threads? PyObjC automatically creates an
> >> autorelease pool for the main thread only; you need to provide
> >> autorelease pools for other threads yourself.
> >
> > Yes, I am using background threads. I have some functions triggered
>
Ah, thanks.
Bill
has <[EMAIL PROTECTED]> wrote:
> On 3 Nov 2008, at 16:00, Bill Janssen wrote:
>
> > So, how does the automatic GC in ObjC-2.0 play into this?
>
>
> PyObjC doesn't work with ObjC 2.0's garbage collector.
>
> HTH
>
> has
> --
> Control AppleScriptable applications from Pytho
On 3 Nov 2008, at 16:00, Bill Janssen wrote:
So, how does the automatic GC in ObjC-2.0 play into this?
PyObjC doesn't work with ObjC 2.0's garbage collector.
HTH
has
--
Control AppleScriptable applications from Python, Ruby and ObjC:
http://appscript.sourceforge.net
___
On 2 Nov 2008, at 23:02, Bill Janssen wrote:
Are you using background threads? PyObjC automatically creates an
autorelease pool for the main thread only; you need to provide
autorelease pools for other threads yourself.
Yes, I am using background threads. I have some functions triggered
by
Python Nutter wrote:
Go to the virtualenv website and post a bug report, its the only way
to get the issues notified to the developers.
Well, the question is: is this a virtualenv bug or a py2app bug? I think
it's more likely that it's a py2app issue, but I suppose it might be
solved form eit
Sarah Ring wrote:
I have Python version 2.5.1 (r251:54863, Apr 15 2008, 22:57:26) and
Py2app version 0.3
You may want to upgrade:
$easy_install -U py2app
should do it.
I'm not using any packages for this test, but I plan to use pyqt4 in the
future.
I tried py2applet --make-setup hello.py
So, how does the automatic GC in ObjC-2.0 play into this?
Bill
Jack Jansen <[EMAIL PROTECTED]> wrote:
>
> On 3 nov 2008, at 00:02, Bill Janssen wrote:
>
> > has <[EMAIL PROTECTED]> wrote:
> >
> >> You're leaking memory, which isn't a good thing.
> >>
> >> Are you using background threads? PyObj
On 3 nov 2008, at 00:02, Bill Janssen wrote:
has <[EMAIL PROTECTED]> wrote:
You're leaking memory, which isn't a good thing.
Are you using background threads? PyObjC automatically creates an
autorelease pool for the main thread only; you need to provide
autorelease pools for other threads yo
