| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
This reverts the core of #100618 while leaving relevant documentation
improvements and minor refactorings in place.
|
|
|
|
|
|
|
|
| |
This starts the process. Users who don't specify their own start method
and use the default on platforms where it is 'fork' will see a
DeprecationWarning upon multiprocessing.Pool() construction or upon
multiprocessing.Process.start() or concurrent.futures.ProcessPool use.
See the related issue and documentation within this change for details.
|
|
|
|
|
|
| |
(#30617)
Co-authored-by: XD Trol <milestonejxd@gmail.com>
Co-authored-by: Antoine Pitrou <pitrou@free.fr>
|
| |
|
|
|
|
| |
On macOS, the multiprocessing module now uses the "spawn" start
method by default.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
* Replaced list(<generator expression>) with list comprehension
* Replaced dict(<generator expression>) with dict comprehension
* Replaced set(<list literal>) with set literal
* Replaced builtin func(<list comprehension>) with func(<generator
expression>) when supported (e.g. any(), all(), tuple(), min(), &
max())
|
|
|
| |
This hides unwanted implementation details from tracebacks.
|
|\
| |
| |
| | |
forkserver process if a preloaded module instantiated some multiprocessing objects such as locks.
|
| |
| |
| |
| | |
forkserver process if a preloaded module instantiated some multiprocessing objects such as locks.
|
|/ |
|
|
This allows different parts of a program to use different methods for
starting processes without interfering with each other.
|