Message200789
> - now that FDs are non-inheritable by default, fork locks around
> subprocess and multiprocessing shouldn't be necessary anymore? What
> other use cases does the fork-lock have?
CLOEXEC fds will still be inherited by forked children.
> - the current implementation keeps hard-references to the functions
> passed: so if one isn't careful, you can end up easily with a lot of
> objects kept alive just because of those references, which can be a
> problem
True, but you could make the same complaint about atexit.register().
One can fairly easily create something like weakref.finalize which uses atfork but is smart about not creating hard refs. |
|
Date |
User |
Action |
Args |
2013-10-21 14:41:44 | sbt | set | recipients:
+ sbt, lemburg, twouters, georg.brandl, gregory.p.smith, jcea, amaury.forgeotdarc, pitrou, vstinner, christian.heimes, grahamd, Arfrever, asvetlov, neologix, aliles, DLitz |
2013-10-21 14:41:44 | sbt | set | messageid: <1382366504.66.0.993376755414.issue16500@psf.upfronthosting.co.za> |
2013-10-21 14:41:44 | sbt | link | issue16500 messages |
2013-10-21 14:41:44 | sbt | create | |
|