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 sbt
Recipients asvetlov, pitrou, sbt, serhiy.storchaka
Date 2012-08-11.19:17:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> In the latest patch, what are "broken" and "priority" for?

They are for a subclass used by multiprocessing.  But it is premature to worry about subclassing, so I will take them out.

> Also, I would question why atexit is false by default. I would find it 
> personally less surprising to be true.


One thing I do worry about is having the loop in the exit function to run any finalizers created during the exit function.  The current implementation will run these extra finalizers at the wrong time.  Fixing this could probably be done by using a dirty flag and disabling gc while running the finalizers.

I wonder if it would be better to not call finalizers created during the exit function.  We cannot guarantee that every finalizer created during shutdown is run, so is a best effort attempt really worth the effort?
Date User Action Args
2012-08-11 19:17:39sbtsetrecipients: + sbt, pitrou, asvetlov, serhiy.storchaka
2012-08-11 19:17:39sbtsetmessageid: <>
2012-08-11 19:17:38sbtlinkissue15528 messages
2012-08-11 19:17:38sbtcreate