---
- branch: MAIN
  date: Wed Dec 30 14:57:02 UTC 2015
  files:
  - new: '1.4'
    old: '1.3'
    path: pkgsrc/devel/py-pyparsing/Makefile
    pathrev: pkgsrc/devel/py-pyparsing/Makefile@1.4
    type: modified
  - new: '1.4'
    old: '1.3'
    path: pkgsrc/devel/py-pyparsing/distinfo
    pathrev: pkgsrc/devel/py-pyparsing/distinfo@1.4
    type: modified
  - new: '1.3'
    old: '1.2'
    path: pkgsrc/devel/py-pyparsing/PLIST
    pathrev: pkgsrc/devel/py-pyparsing/PLIST@1.3
    type: modified
  id: 20151230T145702Z.fa1bba136ad47bc9bf9724a4a54c6619ea47a5a2
  log: "Update devel/py-pyparsing to 2.0.6.\n\npkgsrc changes:\n- convert to egg.mk
    (no functional changes intended)\n- use MASTER_SITE_PYPI\n- update HOMEPAGE (sf.net
    project page seems not available ATM while the\n  distfiles are fetchable from
    sf.net)\n- minor cosmetic fixes\n\nChanges:\nVersion 2.0.6 -\n---------------------------\n-
    Fixed a bug in Each when multiple Optional elements are present.\n  Thanks for
    reporting this, whereswalden on SO.\n- Fixed another bug in Each, when Optional
    elements have results names\n  or parse actions, reported by Max Rothman - thank
    you, Max!\n- Added optional parseAll argument to runTests, whether tests should\n
    \ require the entire input string to be parsed or not (similar to\n  parseAll
    argument to parseString). Plus a little neaten-up of the\n  output on Python 2
    (no stray ()'s).\n- Modified exception messages from MatchFirst and Or expressions.
    These\n  were formerly misleading as they would only give the first or longest\n
    \ exception mismatch error message. Now the error message includes all\n  the
    alternatives that were possible matches. Originally proposed by\n  a pyparsing
    user, but I've lost the email thread - finally figured out\n  a fairly clean way
    to do this.\n- Fixed a bug in Or, when a parse action on an alternative raises
    an\n  exception, other potentially matching alternatives were not always tried.\n
    \ Reported by TheVeryOmni on the pyparsing wiki, thanks!\n- Fixed a bug to dump()
    introduced in 2.0.4, where list values were shown\n  in duplicate.\n\nVersion
    2.0.5 -\n---------------------------\n- (&$(@#&$(@!!!!  Some \"print\" statements
    snuck into pyparsing v2.0.4,\n  breaking Python 3 compatibility! Fixed. Reported
    by jenshn, thanks!\n\nVersion 2.0.4 -\n---------------------------\n- Added ParserElement.addCondition,
    to simplify adding parse actions\n  that act primarily as filters. If the given
    condition evaluates False,\n  pyparsing will raise a ParseException. The condition
    should be a method\n  with the same method signature as a parse action, but should
    return a\n  boolean. Suggested by Victor Porton, nice idea Victor, thanks!\n-
    Slight mod to srange to accept unicode literals for the input string,\n  such
    as \"[а-Ñ\x8FÐ\x90-Я]\" instead of \"[\\u0430-\\u044f\\u0410-\\u042f]\". Thanks\n
    \ to Alexandr Suchkov for the patch!\n- Enhanced implementation of replaceWith.\n-
    Fixed enhanced ParseResults.dump() method when the results consists\n  only of
    an unnamed array of sub-structure results. Reported by Robin\n  Siebler, thanks
    for your patience and persistence, Robin!\n- Fixed bug in fourFn.py example code,
    where pi and e were defined using\n  CaselessLiteral instead of CaselessKeyword.
    This was not a problem until\n  adding a new function 'exp', and the leading 'e'
    of 'exp' was accidentally\n  parsed as the mathematical constant 'e'. Nice catch,
    Tom Grydeland - thanks!\n- Adopt new-fangled Python features, like decorators
    and ternary expressions,\n  per suggestions from Williamzjc - thanks William!
    (Oh yeah, I'm not\n  supporting Python 2.3 with this code any more...) Plus, some
    additional\n  code fixes/cleanup - thanks again!\n- Added ParserElement.runTests,
    a little test bench for quickly running\n  an expression against a list of sample
    input strings. Basically, I got\n  tired of writing the same test code over and
    over, and finally added it\n  as a test point method on ParserElement.\n- Added
    withClass helper method, a simplified version of withAttribute for\n  the common
    but annoying case when defining a filter on a div's class -\n  made difficult
    because 'class' is a Python reserved word.\n\nVersion 2.0.3 -\n---------------------------\n-
    Fixed escaping behavior in QuotedString. Formerly, only quotation\n  marks (or
    characters designated as quotation marks in the QuotedString\n  constructor) would
    be escaped. Now all escaped characters will be\n  escaped, and the escaping backslashes
    will be removed.\n- Fixed regression in ParseResults.pop() - pop() was pretty
    much\n  broken after I added *improvements* in 2.0.2. Reported by Iain\n  Shelvington,
    thanks Iain!\n- Fixed bug in And class when initializing using a generator.\n-
    Enhanced ParseResults.dump() method to list out nested ParseResults that\n  are
    unnamed arrays of sub-structures.\n- Fixed UnboundLocalError under Python 3.4
    in oneOf method, reported\n  on Sourceforge by aldanor, thanks!\n- Fixed bug in
    ParseResults __init__ method, when returning non-ParseResults\n  types from parse
    actions that implement __eq__. Raised during discussion\n  on the pyparsing wiki
    with cyrfer.\n"
  module: pkgsrc
  subject: 'CVS commit: pkgsrc/devel/py-pyparsing'
  unixtime: '1451487422'
  user: leot