Copied upcaseTokens and downcaseTokens to pyparsing_common; renamed pyparsing_common's signedInteger and sciReal to signed_integer and sci_real

git-svn-id: svn://svn.code.sf.net/p/pyparsing/code/trunk@428 9bf210a0-9d2d-494c-87cf-cfb32e7dff7b

1 files changed, 22 insertions, 0 deletions

diff --git a/src/CHANGES b/src/CHANGES
index 40c08ff..e32cc21 100644
--- a/src/CHANGES
+++ b/src/CHANGES
@@ -8,6 +8,28 @@ Version 2.1.9 -
   "close" matches, that is, strings with at most 'n' mismatching

   characters.

 

+- Minor API change in pyparsing_common. Renamed some of the common

+  expressions to PEP8 format (to be consistent with the other 

+  pyparsing_common expressions):

+  . signedInteger -> signed_integer

+  . sciReal -> sci_real

+  

+  Also, in trying to stem the API bloat of pyparsing, I've copied

+  some of the global expressions and helper parse actions into 

+  pyparsing_common, with the originals to be deprecated and removed

+  in a future release:

+  . commaSeparatedList -> pyparsing_common.comma_separated_list

+  . upcaseTokens -> pyparsing_common.upcaseTokens

+  . downcaseTokens -> pyparsing_common.downcaseTokens

+

+  (I don't expect any other expressions, like the comment expressions,

+  quotedString, or the Word-helping strings like alphas, nums, etc.

+  to migrate to pyparsing_common - they are just too pervasive. As for

+  the PEP8 vs camelCase naming, all the expressions are PEP8, while

+  the parse actions in pyparsing_common are still camelCase. It's a 

+  small step - when pyparsing 3.0 comes around, everything will change

+  to PEP8 snake case.)

+

 

 Version 2.1.8 - 

 ------------------------------