| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
recommended)
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Add diagram documentation, add more diagram tests, allow more
customization of diagrams
* Remove accidental edit of unrelated documentation
* Add diagram package
* Add jinja file to manifest
* Add to bdist also
* package_data
* Railroad improvements
* Partial rewrite
* Update
* Use partials everywhere so we can edit the tree before it's constructed
* Rewrite the diagram generator to not duplicate any content; use
monospaced font for titles
* Small documentation change
* Revert back to Python 3.5 type hints, fix a small bug
|
| |
|
|
| |
those who do 'python setup.py install' directly instead of going thru pip
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
* Basic framework
* Initial effort
* Clean up and document code
* jinja newline
* Pre-commit, and add extras to tox
* We can't use the class type-annotations syntax in Python 3.5
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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
|
| | |
|
| |
|
|
|
|
|
| |
The tests are run through either tox or Travis CI. In both cases, the
setup.py "test_suite" entrypoint is not used.
Further, the use of "test_suite" is discouraged as it installs using
eggs rather than pip.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
- pyparsing supports Python 3.8
- pyparsing is Python 3 only
- pyparsing supports PyPy in addition to CPython
The trove classifiers display on PyPI and provide quick, at-a-glance
information for library users to know if it is suitable for inclusion in
a project.
For a complete list of trove classifiers, see:
https://pypi.org/classifiers/
|
| |
|
| |
As pyparsing is a dependency used by setuptools this allows packagers to use distutils as a fallback when bootstraping setuptools without much fuss.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
setuptools includes a vendored version of pyparsing (and other
dependencies). They are not install through traditional tools.
Therefore, distutils is not required as fallback to facilitate
setuptools.
https://github.com/pypa/setuptools/blob/v40.6.3/setuptools/_vendor/pyparsing.py
The Python documentation recommends against using distutils:
https://docs.python.org/3/library/distutils.html
> Most Python users will not want to use this module directly, but
> instead use the cross-version tools maintained by the Python Packaging
> Authority. In particular, setuptools is an enhanced alternative to
> distutils that provides ...
Also remove the unused imports.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
