[Python-Dev] Software Transactional Memory for Python (original) (raw)
Armin Rigo arigo at tunes.org
Mon Aug 29 11:36:27 CEST 2011
- Previous message: [Python-Dev] Software Transactional Memory for Python
- Next message: [Python-Dev] Software Transactional Memory for Python
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Guido,
On Sun, Aug 28, 2011 at 6:43 PM, Guido van Rossum <guido at python.org> wrote:
This sounds like a very interesting idea to pursue, even if it's late, and even if it's experimental, and even if it's possible to cause deadlocks (no news there). I propose that we offer a C API in Python 3.3 as well as an extension module that offers the proposed decorator.
Very good idea. http://bugs.python.org/issue12850
The extension module, called 'stm' for now, is designed as an independent 3rd-party extension module. It should at this point not be included in the stdlib; for one thing, it needs some more testing than my quick one-page hacks, and we need to seriously look at the deadlock issues mentioned here. But the patch to ceval.c above looks rather straightforward to me and could, if no subtle issue is found, be included in the standard CPython.
A bientôt,
Armin.
- Previous message: [Python-Dev] Software Transactional Memory for Python
- Next message: [Python-Dev] Software Transactional Memory for Python
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]