On 9 mar, 15:37, I V <[EMAIL PROTECTED]> wrote:
> On Sun, 09 Mar 2008 01:57:38 -0800, Vince wrote:
> > Well, that suits me. The most unnatural thing about Python was adapting
> > to the idea of just letting unreleased resources go jogging off
> > wherever. :)
>
> Yes, that's a bad habit that garba
On Sun, 09 Mar 2008 01:57:38 -0800, Vince wrote:
> Well, that suits me. The most unnatural thing about Python was adapting
> to the idea of just letting unreleased resources go jogging off
> wherever. :)
Yes, that's a bad habit that garbage collection can encourage. GC is good
for managing memory
On Mar 9, 1:51 am, Marc 'BlackJack' Rintsch <[EMAIL PROTECTED]> wrote:
> On Sun, 09 Mar 2008 01:42:01 -0800, vpalexander wrote:
> > I keep seeing destructor calls in wx for ad hoc dialogs and wonder if
> > this is required, and if so, why would normal gc flow not be good?
>
> Because there is no gu
On Sun, 09 Mar 2008 01:42:01 -0800, vpalexander wrote:
> I keep seeing destructor calls in wx for ad hoc dialogs and wonder if
> this is required, and if so, why would normal gc flow not be good?
Because there is no guarantee when `__del__()` is called or if it is
called *at all*.
Ciao,
I keep seeing destructor calls in wx for ad hoc dialogs and wonder if
this is required, and if so, why would normal gc flow not be good?
def GetDir(self,Caption,DefaultDir):
dlg = wx.DirDialog(None,Caption,style = 1,defaultPath =
DefaultDir,pos = (10,10))
res = dlg.ShowModal()
pck =
