Message329277
| Author | chris.jerdonek |
|---|---|
| Recipients | chris.jerdonek, jleclanche, martin.panter |
| Date | 2018-11-05.03:10:55 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1541387456.08.0.788709270274.issue29183@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
This may or may not be the same as what you're suggesting, Martin. But is another option to make close() a no-op if it is called a second time? Otherwise, it seems we'd need to make sure that no code path can result in close() being called twice (even during exception handling, etc). |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-11-05 03:10:56 | chris.jerdonek | set | recipients: + chris.jerdonek, martin.panter, jleclanche |
| 2018-11-05 03:10:56 | chris.jerdonek | set | messageid: <1541387456.08.0.788709270274.issue29183@psf.upfronthosting.co.za> |
| 2018-11-05 03:10:56 | chris.jerdonek | link | issue29183 messages |
| 2018-11-05 03:10:55 | chris.jerdonek | create | |