This is my mistake - I didn't know that lextab checks ply versions, and seem to have had a stale lextab lying around. Sorry for the bother. Feel free to mark the issue as invalid.
- Pavel Panchekha On Wed, Aug 26, 2009 at 8:58 PM, David Beazley <[email protected]> wrote: > > I've looked at this patch and I'm not sure I understand what's > happening or think that it's a bug now. If PLY is running in > optimize mode, it is always going to read data from a lextab.py > file. If that file already exists and is readable, then the code > never reaches a point where any attempt would be made to overwrite > it. There are only two situations where PLY is going to try and > recreate the lextab.py file on every run: > > 1. PLY can't find the lextab.py file because it's installed in the > wrong location. > 2. The lextab.py file has a version mismatch--being created by an > older version of PLY. > > I think I'm going to need more information from you about your setup > to know why you're seeing this behavior. For example, what version of > Python? What options to lex() and yacc()? Where are files being > placed? > > -Dave > > > > On Aug 26, 2009, at 5:34 PM, Pavel Panchekha wrote: > > > Issue with patch submitted. Hope you understand why I think this is > > a bug. > > > > Cheers! > > - Pavel Panchekha > > > > > > On Wed, Aug 26, 2009 at 5:44 PM, David Beazley <[email protected]> > > wrote: > > > > > > > > > > > What I meant by "not maintained" is the the google-code list of bugs > > > doesn't seem to be doing anything, and I didn't know if filing > > > another would actually lead to anything. Has the project moved from > > > google code? Should I open a bug anyway? > > > > > > > Yes. Please open a bug report. I always go through the Google code > > tracker when making new PLY releases. However, as PLY is primarily a > > side project with new releases only occurring once or twice a year, > > it's not uncommon for bugs to sit the tracker for a little while. > > For what it's worth, I was actually thinking about putting out a > > PLY-3.3 release sometime in the next few weeks so if there are other > > bugs, now would be a really good time to report them (that goes for > > everyone). > > > > Cheers, > > Dave > > > > > > > > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
