[Python-ideas] Copy-on-write when forking a python process

[Antoine Pitrou]

On Wed, 13 Apr 2011 16:17:03 +1000
Nick Coghlan <ncoghlan at gmail.com> wrote:
> On Wed, Apr 13, 2011 at 7:42 AM, jac <john.theman.connor-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org> wrote:
> > Has anyone else looked into the COW problem?  Are there workarounds
> > and/or other plans to fix it?  Does the solution I am proposing sound
> > reasonable, or does it seem like overkill?  Does anyone see any
> > (technical) problems with it?
> 
> There's a clear workaround for the COW problem these days: use PyPy
> instead of CPython :)

Doesn't PyPy use a copying collector? Wouldn't that mean that the first
garbage collector pass after the fork() would un-share the memory pages
anyway?

Regards

Antoine.