𝓜𝓪𝓻𝓴𝓸
A markdown parser with high extensibility.
Marko is a markdown parser written in pure Python that complies with CommonMark's spec v0.30. It is designed to be highly extensible, see Extensions for details.
Marko requires Python 3.6 or higher.
Why Marko
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.
Use Marko
The installation is very simple:
$ pip install marko
And to use it:
import marko
print(marko.convert(text))
Marko also provides a simple CLI, for example, to render a document and output to a html file:
$ cat my_article.md | marko > my_article.html
Extensions
It is super easy to use an extension:
from marko import Markdown
from marko.ext.footnote import Footnote
# Add footnote extension
markdown = Markdown(extensions=[Footnote])
# Or you can just:
markdown = Markdown(extensions=['footnote'])
# Alternatively you can register an extension later
markdown.use(Footnote)
An example of using an extension with the command-line version of Marko:
$ cat this_has_footnote.txt | marko -e footnote > hi_world.html
Marko is shipped with 4 extensions: 'footnote', 'toc' 'pangu', 'codehilite'.
They are not included in CommonMark's spec but are common in other markdown parsers.
Marko also provides a Github flavored markdown parser which can be found at marko.ext.gfm.gfm.
Please refer to Extend Marko about how to write your own extension.
License
Marko is released under MIT License
Change Log
1 maintainer
Metadata
1 maintainer
Release files for marko 1.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| marko-1.2.1.tar.gz | 139.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| marko-1.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 177.7 kB
Release files / marko-1.2.1.tar.gz
| Download URL | marko-1.2.1.tar.gz |
|---|---|
| Size | 139.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
80d7807605b5e103f544df93c21e6f66a0d42dbe953c0dcd5b80d35b704bf170
|
|
BLAKE2b-256 checksum How to use checksums |
9bb7c58e9b9f7c3da08731faab65453ef54bcc6b5b4a5a81ca1b6ae0b490644a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.8.12
|
Release files / marko-1.2.1-py3-none-any.whl
| Download URL | marko-1.2.1-py3-none-any.whl |
|---|---|
| Size | 38.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
553cba6b972228d875e5b7728b93fa2d5dd1e93b5c62bdc4bfbdac3802fd8812
|
|
BLAKE2b-256 checksum How to use checksums |
e9fac7f8bdb80a82e9ca649528f9f18e6b647ed587f0ee336e7e5974b6646551
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.8.12
|
Security for marko 1.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
