On Thu, 06 Apr 2006 12:47:25 +0200, Diez B. Roggisch wrote:
> And even if that wasn't the case: I think as long as you don't run into
> memory-troubles, don't do it. Its complex, flaky and thus an unnecessary
> source of failure.
Yeah that sounds fair enough. Actually I ran in to threading proble
> I want to fork a process, but my scope has lots of stuff that the child
> won't need. Is it possible to clean the current environment of cruft so it
> is collected and freed? Basically I want it to go something like this.
> This is my first forking Python app, by the way:
I'm not an expert of th
