Showing content from http://mail.python.org/pipermail/python-dev/attachments/20120108/e6a25c2b/attachment.html below:
Nick did you mean to say "wrap python code around a reentrant lock to create a non-reentrant lock"? Isn't that what PyRLock is doing?<div><br></div><div>FWIW having now read issues 13697 and 13550, I'm +1 for dropping Python RLock, and all the logging machinery in threading.<br>
<br><div class="gmail_quote">2012/1/8 Nick Coghlan <span dir="ltr"><<a href="mailto:ncoghlan@gmail.com">ncoghlan@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2012/1/7 Charles-François Natali <<a href="mailto:neologix@free.fr">neologix@free.fr</a>>:<br>
> Thanks for those precisions, but I must admit it doesn't help me much...<br>
> Can we drop it? A yes/no answer will do it ;-)<br>
<br>
The yes/no answer is "No, we can't drop it".<br>
<br>
Even though CPython no longer uses the Python version of RLock in<br>
normal operation, it's still the reference implementation for everyone<br>
else that has to perform the same task (i.e. wrap Python code around a<br>
non-reentrant lock to create a reentrant one).<br>
<br>
Cheers,<br>
Nick.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Nick Coghlan  |  <a href="mailto:ncoghlan@gmail.com">ncoghlan@gmail.com</a>  |  Brisbane, Australia<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br>ಠ_ಠ<br>
</div>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4