From 996d300e17682100129a07d4006f7ae8b4a3b14f Mon Sep 17 00:00:00 2001 From: ptmcg Date: Sat, 10 Sep 2016 15:21:27 +0000 Subject: Cleanup/notes in prep for 2.1.9 release git-svn-id: svn://svn.code.sf.net/p/pyparsing/code/trunk@432 9bf210a0-9d2d-494c-87cf-cfb32e7dff7b --- src/CHANGES | 25 ++++++++++++++++--------- src/pyparsing.py | 4 ++-- src/unitTests.py | 8 ++++++++ 3 files changed, 26 insertions(+), 11 deletions(-) diff --git a/src/CHANGES b/src/CHANGES index 979b5c3..5689d53 100644 --- a/src/CHANGES +++ b/src/CHANGES @@ -2,14 +2,14 @@ Change Log ========== -Version 2.1.9 - ------------------------------- +Version 2.1.9 - September, 2016 +------------------------------- - Added class CloseMatch, a variation on Literal which matches "close" matches, that is, strings with at most 'n' mismatching characters. - Fixed bug in Keyword.setDefaultKeywordChars(), reported by Kobayashi - shinji - nice catch, thanks! + Shinji - nice catch, thanks! - Minor API change in pyparsing_common. Renamed some of the common expressions to PEP8 format (to be consistent with the other @@ -36,9 +36,16 @@ Version 2.1.9 - - Fixed Python3 compatibility bug when using dict keys() and values() in ParseResults.getName(). +- After some prodding, I've reworked the unitTests.py file for + pyparsing over the past few releases. It uses some variations on + unittest to handle my testing style. The test now: + . auto-discovers its test classes (while maintining their order + of definition) + . suppresses voluminous 'print' output for tests that pass -Version 2.1.8 - ------------------------------- + +Version 2.1.8 - August, 2016 +---------------------------- - Fixed issue in the optimization to _trim_arity, when the full stacktrace is retrieved to determine if a TypeError is raised in pyparsing or in the caller's parse action. Code was traversing @@ -57,8 +64,8 @@ Version 2.1.8 - - Improved use of runTests in several example scripts. -Version 2.1.7 - ------------------------------- +Version 2.1.7 - August, 2016 +---------------------------- - Fixed regression reported by Andrea Censi (surfaced in PyContracts tests) when using ParseSyntaxExceptions (raised when using operator '-') with packrat parsing. @@ -69,8 +76,8 @@ Version 2.1.7 - oneOf will accept the list or set or generator directly.) -Version 2.1.6 - ------------------------------- +Version 2.1.6 - August, 2016 +---------------------------- - *Major packrat upgrade*, inspired by patch provided by Tal Einat - many, many, thanks to Tal for working on this! Tal's tests show faster parsing performance (2X in some tests), *and* memory reduction diff --git a/src/pyparsing.py b/src/pyparsing.py index c8b317b..d602a35 100644 --- a/src/pyparsing.py +++ b/src/pyparsing.py @@ -1,6 +1,6 @@ # module pyparsing.py # -# Copyright (c) 2003-2015 Paul T. McGuire +# Copyright (c) 2003-2016 Paul T. McGuire # # Permission is hereby granted, free of charge, to any person obtaining # a copy of this software and associated documentation files (the @@ -61,7 +61,7 @@ The pyparsing module handles some of the problems that are typically vexing when """ __version__ = "2.1.9" -__versionTime__ = "08 Sep 2016 23:33 UTC" +__versionTime__ = "10 Sep 2016 15:10 UTC" __author__ = "Paul McGuire " import string diff --git a/src/unitTests.py b/src/unitTests.py index 33ab939..b21d1aa 100644 --- a/src/unitTests.py +++ b/src/unitTests.py @@ -1,3 +1,11 @@ +# +# unitTests.py +# +# Unit tests for pyparsing module +# +# Copyright 2002-2016, Paul McGuire +# +# # -*- coding: UTF-8 -*- from unittest import TestCase, TestSuite, TextTestRunner import unittest -- cgit v1.2.1