Hello Pavel, A quick search resulted in these earlier discussions, which may be of interest to you:
http://groups.google.com/group/ply-hack/browse_frm/thread/a799e10f9c200444/edd49473b4aca366?lnk=gst&q=lex+optimized# http://groups.google.com/group/ply-hack/browse_frm/thread/22685d1b7fb728fe/f09ce65cf3a04e3a?lnk=gst&q=lex+optimized#f09ce65cf3a04e3a http://groups.google.com/group/ply-hack/browse_thread/thread/fe785e81d3d14815# http://groups.google.com/group/ply-hack/browse_frm/thread/925c8062a9d0513d http://groups.google.com/group/ply-hack/msg/12adcdd411a0bff3 These earlier discussions deal among others with disabling table files alltogether. The last one is an earlier post that I once posted. It is about PlyWrapper, a wrapper around Ply that takes care of table files and has functionality for generating them on command, which I use in my project to write tables during installation, at which time the appropriate rights are available. Best, Dennis Pavel Panchekha wrote: > Both the parser and the lexer attempt to write out parse tables each > time they are run, if they have been told to do so. > > If an application that uses ply is installed in an area only root can > write to, this will cause the application to crash. > > I'm currently using the following hacky fix: > > Wrap line 176 in lex.py with > > try: > # line 176 > except IOError: > pass > > Wrap line 2549 in yacc.py with > > try: > # line 2549 > except IOError: > pass > > This removed annoying error messages and program crashes. > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
