Mistune The fastest markdown parser in pure Python with renderer features, inspired by marked.
Latest version- Create, Upload and ShareThis list documents the Python libraries available on the Big Data Cluster and their most recent versions. Name Version Summary / License Note alabaster 0.7.9 Configurable.
- A Python documentation website. Mistune Converts Documents¶. Convert, conversion, document, file. The mistune module is a markdown parser that turns markdown file into HTML. Run this script to see the html result in the terminal.
Released:
Python-Markdown Code Hilite port for Mistune
Project description
Python-Markdown Code Hilite port for Mistune.
Usage
License
MIT
Release historyRelease notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
| Filename, size | File type | Python version | Upload date | Hashes |
|---|---|---|---|---|
| Filename, size mistune-hilite-0.1.0.tar.gz (2.7 kB) | File type Source | Python version None | Upload date | Hashes |
Hashes for mistune-hilite-0.1.0.tar.gz
Python Mistune Example
| Algorithm | Hash digest |
|---|---|
| SHA256 | 69bc967ae10090f83dab85279e26f22cec2b56cd2b5cc6dfbb3dd80d32d87dda |
| MD5 | d9f9095b2a6c5f22afc423c581430aa8 |
| BLAKE2-256 | 1d8ec3d8c3048a7fc2f8cedd59f85e327e018f082cf4a3aeb00f021e95e7ad03 |
Deploying Python Packages to PyPI using Flit
The traditional way of package deployment in Python is using a setup.py script located in the root of your project and then running python setup.py sdist upload to release a new version.
It works by using distutils, setuptools or distribute and there is also twine which is a command line application to manage uploads.
History
distutils is the standard way of Python package distribution included in standard library since Python 2.x then setuptools was created to overcome distutils limitations and also introduces a command line application called easy_install (currently we use its sucessor called pip) and also setuptools introduced a very handy feature called pkg_resources. One of the characteristics of setuptools is that it uses Monkey Patching over the standard distutils to fix existing problems.
Other forks of setuptools has been created to fix that issues and add common developers preferences so well known forks like distribute and distutils2 and distlib has been merged back to the original setuptools
Lots of other packaging tools has been created to try to fix the distribution problems, some maintained by PyPA (Python Package Authority) and some maintained by community.
How it works in standard way
using one of the above you should create a file called setup.py in the root of your project, e.g:
As you can see it is very confusing to decide which of the distribute tools to addopt and how the setup.py should be writen because there are different examples over the github most famous Python repositories.
Making things easier with Flit
NOTE: Forget all about all that history and setup.py you read above and consider using only Flit.
Flit is a simple way to Package and deploy Python projects on PyPI, Flit makes it easier by using a simple flit.ini file and assumes common defaults to save your time and typing.
I knew about Flit when I was taking a look at Mariatta Wijaya game called Tic Tac Taco Pizza and noticed that she used flit to deploy the game, so we also asked her the reason for using this on the podcast we recorded so I decided to try porting my projects to Flit.
How it works?
Instead of a complex setup.py you put a simple flit.ini in the root of your project and it looks like:
Now you only need to have flit installed in your local machine pip3 install flit (unsing pip3 as flit works only in Python3+) and optionally is recommended to have pandoc and pypandoc installed because Flit can convert your README.md into the .rst, the format still used by PyPI (note that Markdown support is coming to PyPi.org soon).
The advantages are:
- No more complicated
setup.py - If you omit some fields it will assume common used defaults
- It is easier to read and write
- Will convert your README.md
- Will take the
__version__included in yourprogram/__init__.py - Can deploy to TestPyPI
- Avoids over engineering on
setup.py
Development installation
To install your package during development use
the --python is optional, by default will take the current which python
Registering and deploying
It is easy and will register the new project for you if doesn't exist on PyPI
Flit packages a single importable module or package at a time, using the import name as the name on PyPI. All subpackages and data files within a package are included automatically.
Important!
- Flit will use the data from
~/.pypircto authenticate and to find the server deployment addresses - You can also set
FLIT_USERNAMEandFLIT_PASSWORDandFLIT_INDEX_URLas environment variables which makes flit good for CI deployment (e.g: TravisCI)
What is missing?
NOTE: Flit is open-source, so some of this things are already under consideration and there are PRs opened.
- Flit will not bump your project version automatically, you can still use tools like bumpversion but this feature would be better if builtin
- Flit will not parse a
requirements.txtfile and would be nice to have it as tools likepyup.iocan track those files but notflit.iniyet - Flit does not create a
.lockfrozen file with the version used on specific release and it is interesting just likepipenvdoes
Conclusion
Flit is the easier way to deploy packaged to PyPI following 3 simple steps.
Python 3 Mistune
- Install flit
- Describe your flit.ini
- Run
flit publish
then your library is released to PyPI.
However
Python Markdown Vs Mistune
Python still needs better standards because you still need separated tools to make common tasks and using a single tool to that tasks (pack, install, deploy, create) would be better (just like what cargo does for Rust), instead in Python you have:
- Flit to deploy packages to PyPI for distribution
- bumpversion to bump your semver number
- pip to install and update packages from PyPI (or pipenv/WIP to do the same with more powers)
- Cookiecutter to create a new Python Package (from strucured templates)
- safety to check dependencies security
- flake or pylint to static and styling checks
- venv, pyenv or virtualenvwrapper to manage isolated environments
- pytest to run tests
- pyup.io to watch for depdendency updates
- tox for testing on multiple environments
- sphinx to create documentation
- lots of other options
Having so many tools brings a lot of confusion and makes it hard to choose, why not having a single tool, based on different plugins sharing the same API?
Just an idea
All above configurable via config file or env vars and each of that endpoints would be provided by many plugins sharing the same API, so you could choose between flit or twine as your publish manager etc..
So maybe I can implement that features in manage
Please share in comments if you know some other Python management tool