---------- Forwarded message ----------
From: Guido van Rossum
Hi!
In today's bug day, an Argentinian colleague called my attention over the issue 1746071.
This issue is about mutex:
"""The mutex module defines a class that allows mutual-exclusion via acquiring and releasing locks. It does not require (or imply) threading or multi-tasking, though it could be useful for those purposes."""
The problem here is that mutex is NOT thread safe! Even when it says in the docs that it could be useful for threading!
"Ok, let's make this mutex to be thread-safe", I thought, and my colleague reviewed the proposed patch, even finding and submitting a correction to it.
But two points prevented me for further work here:
- It has not test cases at all
- It does something that could be easily done (today) using parts from the threading module.
There're some comments in that issue that points towards a deprecation of this module.
So, I'm asking here. Is it still working in 3k? What are the plans here? What do you think about this module? Is somebody using it?
Thank you all! Regards,
[1] http://bugs.python.org/issue1746071 [2] http://docs.python.org/dev/library/mutex.html
-- . Facundo
Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org/ar/ _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/guido%40python.org
-- --Guido van Rossum (home page: http://www.python.org/~guido/) -- --Guido van Rossum (home page: http://www.python.org/~guido/)
2008/2/23, Guido van Rossum
According to the docstring it's only meant to be used with sched.py. Please don't try to make it work with threads! Maybe this needs to be moved into a "simulations" package in 3.0?
Ok, I'll close the issue with this, and forward this mail to the stdlib reorg for proper handling. Thank you! -- . Facundo Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org/ar/
2008/2/23, Facundo Batista
Ok, I'll close the issue with this, and forward this mail to the stdlib reorg for proper handling.
1. Done 2. It was already taken care of in the stdlib reorg sheet (it will be removed, or at least its api hidden, in 3.0) Thank you! -- . Facundo Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org/ar/
participants (2)
-
Facundo Batista
-
Guido van Rossum