Message194758
| Author | pitrou |
|---|---|
| Recipients | eli.bendersky, flox, jcea, pitrou, python-dev, scoder |
| Date | 2013-08-09.19:34:43 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1376076874.2646.25.camel@fsol> |
| In-reply-to | <1376067145.12.0.789836502463.issue17741@psf.upfronthosting.co.za> |
| Content | |
|---|---|
> Can we agree on discarding the current implementation for now and then > rewriting it based on a tree builder instead of a parser wrapper? Only if it actually brings something (feature-wise, performance-wise, maintenance-wise, whatever) that the current implementation doesn't have. Otherwise, I'd rather check in the simple inheritance-to-composition change. I'm sorry that you noticed this after the alpha. I would have had a lower threshold for changes if you had manifested when I proposed the feature. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2013-08-09 19:34:43 | pitrou | set | recipients: + pitrou, jcea, scoder, eli.bendersky, flox, python-dev |
| 2013-08-09 19:34:43 | pitrou | link | issue17741 messages |
| 2013-08-09 19:34:43 | pitrou | create | |