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 | skrah |
|---|---|
| Recipients | benjamin.peterson, meador.inge, petri.lehtinen, skrah |
| Date | 2012年02月16日.22:55:10 |
| SpamBayes Score | 0.007758928 |
| Marked as misclassified | No |
| Message-id | <1329432910.67.0.0892479959445.issue13089@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Yes, that's basically what I did, but using the latest revision I cannot reproduce the parsetok leak either. The atexit leak is an old friend (#11826), so I think we can close this one for now. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012年02月16日 22:55:10 | skrah | set | recipients: + skrah, benjamin.peterson, meador.inge, petri.lehtinen |
| 2012年02月16日 22:55:10 | skrah | set | messageid: <1329432910.67.0.0892479959445.issue13089@psf.upfronthosting.co.za> |
| 2012年02月16日 22:55:10 | skrah | link | issue13089 messages |
| 2012年02月16日 22:55:10 | skrah | create | |