This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | grahamd |
|---|---|
| Recipients | btubbs, grahamd, jcea, pitrou, pje |
| Date | 2012年10月15日.02:40:05 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1350268805.93.0.821815332061.issue16220@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Hmmm. Wonders if finally finding this was prompted in part by recent post about this very issue. :-) http://blog.dscpl.com.au/2012/10/obligations-for-calling-close-on.html Also related is this issue from Django I highlighted long time ago. https://code.djangoproject.com/ticket/16241 I would have to look through Django code again but wondering if the issue there was in fact caused by underlying issue in standard library or whether would have needed to be separately fixed in Django still. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012年10月15日 02:40:06 | grahamd | set | recipients: + grahamd, jcea, pje, pitrou, btubbs |
| 2012年10月15日 02:40:05 | grahamd | set | messageid: <1350268805.93.0.821815332061.issue16220@psf.upfronthosting.co.za> |
| 2012年10月15日 02:40:05 | grahamd | link | issue16220 messages |
| 2012年10月15日 02:40:05 | grahamd | create | |