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 | georg.brandl |
|---|---|
| Recipients | asvetlov, chris.jerdonek, georg.brandl, gregory.p.smith, pitrou, r.david.murray |
| Date | 2012年08月19日.10:59:49 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1345374010.49.0.707167118223.issue12623@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> The main question: can be fix applied to 3.3 or it can wait for 3.4? > 3.2 has the same problem BTW. I don't see any fix attached :) If it is a bug, it can be fixed before 3.3rc1, no need for release blocker status. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012年08月19日 11:00:10 | georg.brandl | set | recipients: + georg.brandl, gregory.p.smith, pitrou, r.david.murray, asvetlov, chris.jerdonek |
| 2012年08月19日 11:00:10 | georg.brandl | set | messageid: <1345374010.49.0.707167118223.issue12623@psf.upfronthosting.co.za> |
| 2012年08月19日 10:59:49 | georg.brandl | link | issue12623 messages |
| 2012年08月19日 10:59:49 | georg.brandl | create | |