Message100868
| Author | scoder |
|---|---|
| Recipients | effbot, flox, georg.brandl, pitrou, r.david.murray, scoder |
| Date | 2010-03-11.15:49:01 |
| SpamBayes Score | 0.0036723162 |
| Marked as misclassified | No |
| Message-id | <1268322543.87.0.574751943423.issue8047@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Sorry, Antoine, but you can't possibly mean what you say here. The culprit in question is clearly one of the best hidden features of the new Py3 ET API. The only existing reference to it that I can find is the SVN commit comment when it was applied. How is that supposed to be any reason for keeping up "backwards compatibility" within the Py3 series? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2010-03-11 15:49:03 | scoder | set | recipients: + scoder, effbot, georg.brandl, pitrou, r.david.murray, flox |
| 2010-03-11 15:49:03 | scoder | set | messageid: <1268322543.87.0.574751943423.issue8047@psf.upfronthosting.co.za> |
| 2010-03-11 15:49:02 | scoder | link | issue8047 messages |
| 2010-03-11 15:49:01 | scoder | create | |