Message 143274 - Python tracker
Message143274
| Author | nirai |
|---|---|
| Recipients | Giovanni.Bajo, avian, bobbyi, gregory.p.smith, neologix, nirai, pitrou, sbt, sdaoden, vstinner |
| Date | 2011-08-31.18:25:42 |
| SpamBayes Score | 1.3776298e-05 |
| Marked as misclassified | No |
| Message-id | <1314815143.08.0.52611461825.issue6721@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
For the record, turns out there was a bit of misunderstanding. I used the term deprecate above to mean "warn users (through documentation) that they should not use (a feature)" and not in its Python-dev sense of "remove (a feature) after a period of warning". I do not think the possibility to mix threading and multiprocessing together should be somehow forcibly disabled. Anyway, since my view does not seem to resonate with core developers I I'll give it a rest for now. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011-08-31 18:25:43 | nirai | set | recipients: + nirai, gregory.p.smith, pitrou, vstinner, bobbyi, neologix, Giovanni.Bajo, sdaoden, sbt, avian |
| 2011-08-31 18:25:43 | nirai | set | messageid: <1314815143.08.0.52611461825.issue6721@psf.upfronthosting.co.za> |
| 2011-08-31 18:25:42 | nirai | link | issue6721 messages |
| 2011-08-31 18:25:42 | nirai | create | |