tomlkit
flit
tomlkit | flit | |
---|---|---|
3 | 6 | |
635 | 2,112 | |
2.8% | 1.3% | |
7.1 | 6.6 | |
8 days ago | 7 days ago | |
Python | Python | |
MIT License | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
tomlkit
- Configuration file format that supports hex and comments?
-
Confiig file
I like to use TOML files. I find the syntax to be more palatable than YAML, and you can load them quite easily with tomlkit. I believe there's a PEP to add a parser to the standard library too, since they're used for pyproject.toml now.
- Comparison of Python TOML parser libraries
flit
-
Show HN: Code Indexer Loop
Queries on https://github.com/pypa/flit/tree/main/flit_core/flit_core (omitted tests/)
(Pdb) print(indexer.query("def normalize_dist_name(name: str, version: str) -> str:"))
-
Underappreciated Challenges with Python Packaging
If it's pure Python, the only packaging file you need is `pyproject.toml`. You can fill that file with packaging metadata per PEP 518 and PEP 621, including using modern build tooling like flit[1] for the build backend and build[2] for the frontend.
With that, you entire package build (for all distribution types) should be reducible to `python -m build`. Here's an example of a full project doing everything with just `pyproject.toml`[3] (FD: my project).
[1]: https://github.com/pypa/flit
[2]: https://github.com/pypa/build
[3]: https://github.com/pypa/pip-audit
-
Easy Packing and Publishing to PyPi with Flit, pytest, and Circleci
I published a very simple project flit_pytest_circleci_template that uses: * [flit](https://github.com/pypa/flit) to build a package. * pytest to test it * circleci to run the above and publish the package to pypi whenever a source file is committed. This is the hard part IMO as I do not know circleci well (and didn't know it at all when I started this project).
- Python un-updatable, suggestions?
-
Comparison of Python TOML parser libraries
flit
-
How to make a Python package in 2021
I hadn't heard of flit, it does seem like it's not brand new on the scene, however it is primarily a single contributor:
https://github.com/takluyver/flit/graphs/contributors
With a title like this, I'd be expecting to see an article describing the latest tools and recommendations from the PyPA.
What are some alternatives?
tomli - A lil' TOML parser
Poetry - Python packaging and dependency management made easy
pytoml - A TOML-0.4.0 parser/writer for Python.
pip - The Python package installer
rtoml - A fast TOML library for python implemented in rust.
Pipenv - Python Development Workflow for Humans.
toml - Tom's Obvious, Minimal Language
python-lib - Opinionated cookiecutter template for creating a new Python library
mypy - Optional static typing for Python
qtoml - Another Python TOML encoder/decoder
laravel-websockets-example - Quick example of a docker stack for laravel-websockets