On Feb 11, 3:44 am, [EMAIL PROTECTED] wrote:
Maybe you can use the in instead of ==, meaning that a certain
string conforms to a certain pattern, that defines an implicit class
of possibilities, so with the in you look if the string is present
in that class of acceptable patterns, instead of
Paul McGuire:
- Added '==' short-cut to see if a given string matches a
pyparsing expression. For instance, you can now write:
integer = Word(nums)
if 123 == integer:
# do something
print [ x for x in 123 234 asld.split() if x==integer ]
# prints ['123', '234']
I have just uploaded version 1.4.11 of pyparsing to SourceForge. It
has been a pretty full 2 months since the last release, with
contributions from new users, old users, and also some help from the
Google Highly-Open Participation contest. I think there are some
very
interesting new features in
I have just uploaded version 1.4.11 of pyparsing to SourceForge. It
has been a pretty full 2 months since the last release, with
contributions from new users, old users, and also some help from the
Google Highly-Open Participation contest. I think there are some very
interesting new features in
