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 bobbyi, gregory.p.smith, neologix, nirai, pitrou, sdaoden, vstinner
Date 2011-05-13.11:15:03
SpamBayes Score 0.026061691
Marked as misclassified No
Message-id <1305285300.3561.14.camel@localhost.localdomain>
In-reply-to <>
> how can we establish correct (cross library) locking order
> during prepare stage?

That sounds like a lost battle, if it requires the libraries'
cooperation. I think resetting locks is the best we can do. It might not
work ok in all cases, but if it can handle simple cases (such as I/O and
logging locks), it is already very good.
Date User Action Args
2011-05-13 11:15:04pitrousetrecipients: + pitrou, gregory.p.smith, vstinner, nirai, bobbyi, neologix, sdaoden
2011-05-13 11:15:03pitroulinkissue6721 messages
2011-05-13 11:15:03pitroucreate