Message337189
| Author | harman786 |
|---|---|
| Recipients | harman786 |
| Date | 2019-03-05.14:28:02 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1551796082.49.0.510573730128.issue36195@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
In Python 3.6, the docs for ThreadPoolExecutor mentions the following line: initializer is an optional callable that is called at the start of each worker thread; initargs is a tuple of arguments passed to the initializer. Should initializer raise an exception, all currently pending jobs will raise a BrokenThreadPool, as well any attempt to submit more jobs to the pool. But, from my experiment in Python 3.6 and 3.7, I have observed that `initializer` and `initargs` were introduced in Python 3.7. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-03-05 14:28:02 | harman786 | set | recipients: + harman786 |
| 2019-03-05 14:28:02 | harman786 | set | messageid: <1551796082.49.0.510573730128.issue36195@roundup.psfhosted.org> |
| 2019-03-05 14:28:02 | harman786 | link | issue36195 messages |
| 2019-03-05 14:28:02 | harman786 | create | |