[issue31144] add initializer to concurrent.futures.ProcessPoolExecutor

2017-09-02 Thread Antoine Pitrou
Antoine Pitrou added the comment: Actually, looks like this was already proposed in issue 21423. Closing as duplicate. -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> concurrent.futures.ThreadPoolExecutor/ProcessPoolExecutor should accept an init

[issue31144] add initializer to concurrent.futures.ProcessPoolExecutor

2017-09-02 Thread Antoine Pitrou
Antoine Pitrou added the comment: That would sound like a reasonable addition, yes. -- nosy: +pitrou versions: +Python 3.7 -Python 3.6 ___ Python tracker ___

[issue31144] add initializer to concurrent.futures.ProcessPoolExecutor

2017-08-21 Thread nvdv
nvdv added the comment: I can make a PR if it makes any sense for stdlib maintainer. -- ___ Python tracker ___ ___ Python-bugs-list ma

[issue31144] add initializer to concurrent.futures.ProcessPoolExecutor

2017-08-08 Thread nvdv
New submission from nvdv: Unfortunately concurrent.futures.ProcessPoolExecutor does not provide any means to interact with worker processes (like initializer function in multiprocessing.Pool constructor). This problem has been mentioned at least once: https://mail.python.org/pipermail/python-