Yes, I saw that. I definitely agree that this is a (subtle) bug that should be fixed in the next release.
Cheers, Dave On Oct 13, 2010, at 4:04 PM, Eugene Voytitsky wrote: > Hi David, > thanks for the PLY! > > please take a look at my issue + workaround here: > http://code.google.com/p/ply/issues/detail?id=26 > > If you interested in including the workaround into main lex code we may > continue discussion in the issue or just here. > > Thanks. > > On 13.10.10 16:45, David Beazley wrote: >> It's been a little while since there was a new release of PLY, but a number >> of minor bug reports have surfaced. So, I'm thinking about making a >> PLY-3.4 release sometime before the end of October. If anyone has any >> issues and/or feature requests, please post them here or submit to the ply >> bug tracker. >> >> On a slightly different note, I'm thinking about dropping support for older >> Python versions (only supporting Python 2.6 or newer). I probably won't do >> this in the PLY-3.4 release, but I might introduce a PLY-4.0 release that >> requires a modern version. The main reason for this is that I want to >> take advantage of newer Python features such as generators, generator >> expressions, etc. I also want to use syntax that more seamlessly makes PLY >> work with Python 2/3 (the "as" form of exceptions, print function, etc.). >> If anyone has any thoughts about this, they should let me know. >> >> Cheers, >> Dave > > > -- > Best regards, > Eugene Voytitsky -- You received this message because you are subscribed to the Google Groups "ply-hack" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/ply-hack?hl=en.
