Richard Oudkerk 59d5404bc7 Issue #14753: Make multiprocessing treat negative timeouts as it did in 3.2 ... In Python 3.2 and earlier, Process.join() and Connection.poll() treated negative timeouts as zero timeouts. Earlier versions from the 3.3 line of development treat them as infinite timeouts. The patch reverts to the old behaviour.		2012-05-10 16:11:12 +01:00
..
dummy	Remove unused or redundant imports in concurrent.futures and multiprocessing.	2011-11-11 20:05:50 +01:00
__init__.py	Mark multiprocessing files with "Licensed to PSF under a Contributor Agreement"	2012-04-30 12:13:55 +01:00
connection.py	Issue #14753: Make multiprocessing treat negative timeouts as it did in 3.2	2012-05-10 16:11:12 +01:00
forking.py	Issue #14753: Make multiprocessing treat negative timeouts as it did in 3.2	2012-05-10 16:11:12 +01:00
heap.py	Mark multiprocessing files with "Licensed to PSF under a Contributor Agreement"	2012-04-30 12:13:55 +01:00
managers.py	Make AcquirerProxy.acquire() support timeout argument	2012-05-06 16:45:02 +01:00
pool.py	Mark multiprocessing files with "Licensed to PSF under a Contributor Agreement"	2012-04-30 12:13:55 +01:00
process.py	Mark multiprocessing files with "Licensed to PSF under a Contributor Agreement"	2012-04-30 12:13:55 +01:00
queues.py	Mark multiprocessing files with "Licensed to PSF under a Contributor Agreement"	2012-04-30 12:13:55 +01:00
reduction.py	Mark multiprocessing files with "Licensed to PSF under a Contributor Agreement"	2012-04-30 12:13:55 +01:00
sharedctypes.py	Mark multiprocessing files with "Licensed to PSF under a Contributor Agreement"	2012-04-30 12:13:55 +01:00
synchronize.py	Mark multiprocessing files with "Licensed to PSF under a Contributor Agreement"	2012-04-30 12:13:55 +01:00
util.py	Issue #14753: Make multiprocessing treat negative timeouts as it did in 3.2	2012-05-10 16:11:12 +01:00