[Python-Dev] Add an optional timeout to lock operations (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Wed Nov 18 11:38:06 CET 2009
- Previous message: [Python-Dev] Add an optional timeout to lock operations
- Next message: [Python-Dev] Add an optional timeout to lock operations
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Antoine Pitrou wrote:
Guido van Rossum <guido python.org> writes:
Will locks be interruptible with ^C? That is an oft-requested feature which also wasn't supported at that time; what's the situation nowadays? They still aren't interruptible. From what I can read it may be possible to make them interruptible in the POSIX semaphore-based implementation, not in the POSIX condition variable-based implementation (which is used as a fallback when POSIX semaphores are not available, but I don't know whether this fallback is still useful).
I'm pretty sure at least some variants of *BSD still don't have OS level semaphores - their lack is the reason multiprocessing doesn't necessarily work everywhere that the threading module works (since mp needs semaphores in order to work its magic).
Jesse would probably know the gory details.
Cheers, Nick.
-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message: [Python-Dev] Add an optional timeout to lock operations
- Next message: [Python-Dev] Add an optional timeout to lock operations
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]