| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
| |
save/restore to reset_pyparsing_context()
|
|
|
|
| |
manager, suppressing raised exceptions
|
| |
|
| |
|
|
|
|
| |
vendor pyparsing
|
|
|
|
|
|
|
| |
* Tidy docstring formatting for lists and example codeblock
* Add class references and formatting to docstrings
* Experimental docstring formatting changes
|
|
|
|
|
|
|
|
|
| |
This import is currently unused in the file.
I'm looking at optimising start-up times of a project I work on, and
importing pyparsing currently takes about 82ms, which is quite a lot for
my domain. Just not importing `unittest` shaves 14ms off of that import
time.
|
|
|
|
| |
unit test; change TestParseResultsAsserts to mixin instead of subclass; rollforward 2.4.6 CHANGES blurb from 2.4.6 branch
|
|
* Break up pyparsing.py monolith into sub-modules in a pyparsing package
* Convert relative imports to absolutes
* Reference submodule pyparsing in setup.py modules
* Remove recursive import of pyparsing from setup.py
* Black updates
* setup.py updates - packages vs. modules. use .dev1 for the version
|