pyparsing v0.0.b1 Release Notes
Release Date: 2020-11-03 // over 3 years ago-
API CHANGE
๐ Diagnostic flags have been moved to an enum,pyparsing.Diagnostics
, and they are enabled through module-level methods:pyparsing.enable_diag()
pyparsing.disable_diag()
-
pyparsing.enable_all_warnings()
API CHANGE
โ Most previousSyntaxWarnings
that were warned when using pyparsing classes incorrectly have been converted toTypeError
andValueError
exceptions, consistent with Python calling conventions. All warnings warned by diagnostic flags have been converted fromSyntaxWarnings
toUserWarnings
.๐ To support parsers that are intended to generate native Python collection types such as lists and dicts, the
Group
andDict
classes now accept an additional boolean keyword argumentaslist
andasdict
respectively. See thejsonParser.py
example in thepyparsing/examples
source directory for how to return types asParseResults
and as Python collection types, and the distinctions in working with the different types.0๏ธโฃ In addition parse actions that must return a value of list type (which would normally be converted internally to a ParseResults) can override this default behavior by returning their list wrapped in the new
ParseResults.List
class:# this parse action tries to return a list, but pyparsing # will convert to a ParseResults def return_as_list_but_still_get_parse_results(tokens): return tokens.asList() # this parse action returns the tokens as a list, and pyparsing will # maintain its list type in the final parsing results def return_as_list(tokens): return ParseResults.List(tokens.asList())
This is the mechanism used internally by the
Group
class when defined usingaslist=True
.A new
IndentedBlock
class is introduced, to eventually replace the currentindentedBlock
helper method. The interface is largely the same, however, the new class manages its own internal indentation stack, so it is no longer necessary to maintain an externalindentStack
variable.API CHANGE
๐ Addedcache_hit
keyword argument to debug actions. Previously, if packrat parsing was enabled, the debug methods were not called in the event of cache hits. Now these methods will be called, with an added argumentcache_hit=True
.๐ If you are using packrat parsing and enable debug on expressions using a custom debug method, you can add the
cache_hit=False
keyword argument,
and your method will be called on packrat cache hits. If you choose not to add this keyword argument, the debug methods will fail silently, behaving as they did previously.๐ When using
setDebug
with packrat parsing enabled, packrat cache hits will now be included in the output, shown with a leading '*'. (Previously, cache hits and responses were not included in debug output.) For those using custom debug actions, see the previous item regarding an optional API change for those methods.๐
setDebug
output will also show more details about what expression is about to be parsed (the current line of text being parsed, and the current parse position):Match integer at loc 0(1,1) 1 2 3 ^ Matched integer -> ['1']
๐ The current debug location will also be indicated after whitespace has been skipped (was previously inconsistent, reported in Issue #244, by Frank Goyens, thanks!).
๐ Modified the repr() output for
ParseResults
to include the class name as part of the output. This is to clarify for new pyparsing users who misread the repr output as a tuple of a list and a dict. pyparsing results will now read like:ParseResults(['abc', 'def'], {'qty': 100}]
instead of just:
(['abc', 'def'], {'qty': 100}]
๐ Fixed bugs in Each when passed OneOrMore or ZeroOrMore expressions:
. first expression match could be enclosed in an extra nesting level
. out-of-order expressions now handled correctly if mixed with required expressions
. results names are maintained correctly for these expressionsโช Fixed traceback trimming, and added
ParserElement.verbose_traceback
save/restore toreset_pyparsing_context()
.0๏ธโฃ Default string for
Word
expressions now also include indications ofmin
andmax
length specification, if applicable, similar to regex length specifications:Word(alphas) -> "W:(A-Za-z)" Word(nums) -> "W:(0-9)" Word(nums, exact=3) -> "W:(0-9){3}" Word(nums, min=2) -> "W:(0-9){2,...}" Word(nums, max=3) -> "W:(0-9){1,3}" Word(nums, min=2, max=3) -> "W:(0-9){2,3}"
For expressions of the
Char
class (similar toWord(..., exact=1)
, the expression is simply the character range in parentheses:Char(nums) -> "(0-9)" Char(alphas) -> "(A-Za-z)"
โ Removed
copy()
override inKeyword
class which did not preserve definition of ident chars from the original expression. PR #233 submitted by jgrey4296, thanks!๐ In addition to
pyparsing. __version__
, there is now also apyparsing. __version_info__
, following the same structure and field names as insys.version_info
.