This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients Rhamphoryncus, amaury.forgeotdarc, gregory.p.smith, jnoller, mikemccand, pitrou, tzot
Date 2008-07-15.18:33:50
SpamBayes Score 0.0650395
Marked as misclassified No
Message-id <>
> I still don't like the _after_fork() implementation.  Its O(n) where n
> == number of threads the parent process had.

It may be O(n) but the inner loop looks very cheap. Even with n == 1000
I'm not sure it would make a difference.

However, are you sure the system thread identifier stays the same after
a fork? I see that in _after_fork() you reuse the old ident for
new_active instead of getting it from get_ident().
Date User Action Args
2008-07-15 18:33:52pitrousetspambayes_score: 0.0650395 -> 0.0650395
recipients: + pitrou, gregory.p.smith, mikemccand, tzot, amaury.forgeotdarc, Rhamphoryncus, jnoller
2008-07-15 18:33:52pitrousetspambayes_score: 0.0650395 -> 0.0650395
messageid: <>
2008-07-15 18:33:51pitroulinkissue874900 messages
2008-07-15 18:33:50pitroucreate