summaryrefslogtreecommitdiff
path: root/textproc/py-marko/files/setup.py (follow)
Commit message (Collapse)AuthorAgeFilesLines
* textproc/py-marko: Update to 1.2.2Po-Chuan Hsieh2022-10-041-1/+0
| | | | Changes: https://github.com/frostming/marko/blob/master/CHANGELOG.md
* textproc/py-marko: Update to 1.2.1Po-Chuan Hsieh2022-05-141-8/+0
| | | | Changes: https://github.com/frostming/marko/blob/master/CHANGELOG.md
* textproc/py-marko: Update to 1.2.0Po-Chuan Hsieh2022-01-241-4/+3
| | | | Changes: https://github.com/frostming/marko/blob/master/CHANGELOG.md
* textproc/py-marko: Update version in setup.py automaticallyPo-Chuan Hsieh2021-11-011-1/+1
|
* textproc/py-marko: Add py-marko 1.1.0Po-Chuan Hsieh2021-09-281-0/+66
Marko is a markdown parser written in pure Python that complies with CommonMark's spec v0.30. It is designed to be highly extensible. Among all implementations of Python's markdown parser, it is a common issue that user can't easily extend it to add his own features. Furthermore, Python-Markdown and mistune don't comply with CommonMark's spec. It is a good reason for me to develop a new markdown parser. Respecting that Marko complies with CommonMark's spec at the same time, which is a super complicated spec, Marko's performance will be affected. However, using a parser which doesn't comply with the CommonMark spec may give you unexpected rendered results from time to time. A benchmark result shows that Marko is 3 times slower than Python-Markdown, but a bit faster than Commonmark-py, much slower than mistune. If performance is a bigger concern to you than spec compliance, you'd better choose another parser. WWW: https://github.com/frostming/marko