A few notes:

1.  The cpp.py file requires the use of generators and generator 
      expressions which were not supported in Python 2.3.4. Since
      this file is still experimental, I'll probably remove it from
      the main release.

2. The cryptic warning about sys.maxint is due to a change in
     calculating signatures.     PLY-3.0 is simply calculating a
     CRC32 checksum instead of using an MD5 hash.    I don't
     actually see that warning message on my machine, but I'm
     not using Python 2.3 either.   I'm open to ideas on whether
     or not PLY should go back to using MD5 hashes.

3. I will look at the nowarn argument to lex again and see if I
    want to add it back.    As a general rule, I'm trying to shift
    output from PLY away from magic flag settings and towards
    the use of the logging module.

4.  I'll check on the debug flag behavior for yacc.  That's probably
     something that should be restored.

Cheers,
Dave


Hello,

> I would appreciate feedback from current PLY users

I can get it to work. However, I do have a few issues:

- I use Python 2.3.4 and get the following during installation:

        byte-compiling XXX/.local/lib/python2.3/site-packages/ply/cpp.py to 
cpp.pyc
        File "XXX/.local/lib/python2.3/site-packages/ply/cpp.py", line 742
            filename = "".join(x.value for x in tokens[1:i])
                                        ^
        SyntaxError: invalid syntax

  and:

        byte-compiling XXX/.local/lib/python2.3/site-packages/ply/yacc.py to 
yacc.pyc
        XXX/.local/lib/python2.3/site-packages/ply/yacc.py:2720: FutureWarning: 
hex/oct constants > sys.maxint will return positive values in Python 2.4 
and up
        return sig & 0xffffffff

- I use the 'nowarn' parameter for lex.lex(...) and now I get:

        TypeError: lex() got an unexpected keyword argument 'nowarn'

  since that argument was removed. I tried to supply errorlog=lex.NullLogger()
  instead, which seems to work.
  
- I had to supply errorlog=yacc.NullLogger() to yacc.yacc(...) to make
  sure "Generating LALR tables" was not printed. It did not get printed
  in Ply 2.5 (for debug=0). I think this is what Andrew (apwaters) already
  replied. I don't think the message indicates an error, so I don't think
  it should be printed if debug=0.

Dennis





--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to