From 9b335b3c08d251b6b7cd81795c3cf4f74804efff Mon Sep 17 00:00:00 2001 From: Nikolas Nyby Date: Thu, 2 May 2019 14:58:19 -0400 Subject: [PATCH] rename to commonmark.py in a few places --- CHANGELOG.md | 6 +++--- README.rst | 10 +++++----- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 6aba006..738fed3 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -39,12 +39,12 @@ - Contributions from @funkybob and @hyperknot ## 0.6.3 (2016-01-19) -- CommonMark-py now supports Python 2.6. +- commonmark.py now supports Python 2.6. - The CommonMark spec has been updated to 0.24. ## 0.6.2 (2016-01-08) - Fixed a UnicodeEncodeError when parsing unicode entities on - Python 2. As a result, CommonMark-py now relies on the "future" + Python 2. As a result, commonmark.py now relies on the "future" module in Python 2, as documented in setup.py. This can be found on pypi: https://pypi.python.org/pypi/future @@ -53,7 +53,7 @@ was empty. ## 0.6.0 (2016-01-04) -- CommonMark-py now complies to the 0.23 CommonMark spec +- commonmark.py now complies to the 0.23 CommonMark spec http://spec.commonmark.org/0.23/ - The ExtensionBlock has been removed in this release, since the parser has been rewritten. diff --git a/README.rst b/README.rst index bf1e960..e9f0746 100644 --- a/README.rst +++ b/README.rst @@ -1,7 +1,7 @@ -CommonMark-py +commonmark.py ============= -CommonMark-py is a pure Python port of `jgm `__'s +commonmark.py is a pure Python port of `jgm `__'s `commonmark.js `__, a Markdown parser and renderer for the `CommonMark `__ specification, using only native @@ -9,7 +9,7 @@ modules. Once both this project and the CommonMark specification are stable we will release the first ``1.0`` version and attempt to keep up to date with changes in ``commonmark.js``. -CommonMark-py is tested against the CommonMark spec with Python versions +commonmark.py is tested against the CommonMark spec with Python versions 2.7, 3.4, 3.5, 3.6, and 3.7. **Current version:** 0.9.0 @@ -83,7 +83,7 @@ a pull request adding your test to the existing test suite. Tests ----- -To work on CommonMark-py, you will need to be able to run the test suite to +To work on commonmark.py, you will need to be able to run the test suite to make sure your changes don't break anything. To run the tests, you can do something like this: @@ -106,7 +106,7 @@ tracing. $ ./venv/bin/python commonmark/tests/run_spec_tests.py -h usage: run_spec_tests.py [-h] [-t T] [-p] [-f] [-i] [-d] [-np] [-s] - script to run the CommonMark specification tests against the CommonMark-py + script to run the CommonMark specification tests against the commonmark.py parser. optional arguments: