Message200343
| Author | larry |
|---|---|
| Recipients | Arfrever, abn, barry, benjamin.peterson, christian.heimes, dstufft, georg.brandl, larry, python-dev, sYnfo, vstinner |
| Date | 2013-10-19.01:17:53 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1382145473.89.0.000543135142494.issue18709@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
So, this is fixed, but there's some suspicion of a memory leak? If that's true, maybe we could mark this as closed then open a new bug for the leak? This shows up as a big scary "release blocker" against 3.4, and I'm like making releases and stuff. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2013-10-19 01:17:54 | larry | set | recipients: + larry, barry, georg.brandl, vstinner, christian.heimes, benjamin.peterson, Arfrever, python-dev, dstufft, abn, sYnfo |
| 2013-10-19 01:17:53 | larry | set | messageid: <1382145473.89.0.000543135142494.issue18709@psf.upfronthosting.co.za> |
| 2013-10-19 01:17:53 | larry | link | issue18709 messages |
| 2013-10-19 01:17:53 | larry | create | |