Message274059
| Author | nnnnnn |
|---|---|
| Recipients | davin, gvanrossum, nnnnnn, rhettinger |
| Date | 2016-08-31.18:52:10 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1472669531.1.0.806480606206.issue27916@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Thanks for the explanation, understood. However, I don't think it would be terribly difficult to demonstrate that these changes do address actual pains(*) in the situations they're supposed to address them. And the pains in question might in real world occur quite rarely, unexpectedly, and take some time/cost to debug and reproduce, which is why it would be good to be able to preemptively address them. (*) For some values of "pain" -- many of the changes here are just for outputting nice-to-know timing information. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2016-08-31 18:52:11 | nnnnnn | set | recipients: + nnnnnn, gvanrossum, rhettinger, davin |
| 2016-08-31 18:52:11 | nnnnnn | set | messageid: <1472669531.1.0.806480606206.issue27916@psf.upfronthosting.co.za> |
| 2016-08-31 18:52:11 | nnnnnn | link | issue27916 messages |
| 2016-08-31 18:52:11 | nnnnnn | create | |