python-template
flit
python-template | flit | |
---|---|---|
2 | 6 | |
0 | 2,094 | |
- | 0.4% | |
0.0 | 6.4 | |
about 3 years ago | about 2 months ago | |
Shell | 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.
python-template
-
How to make a Python package in 2021
Somewhat related: I have an example repository which I've been using to keep track of the tools I use, aimed at people in a research lab who are relatively new to Python. I made it because the existing example/template repositories I found don't gel nicely with the way I like to set up and think about things. Here it is -- hope you find it useful:
https://github.com/alknemeyer/python-template/
-
Ask HN: Who wants to be hired? (April 2021)
- good software engineering practice: https://github.com/alknemeyer/python-template
I enjoy working on many types of problems and look forward to hearing from you!
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?
betfair-exchange-hi-lo-odds - This repository contains code to efficiently compute exact odds for Betfair's Exchange Hi Lo card game in polynomial time and space relative to the number of cards in the deck. See README.md
Poetry - Python packaging and dependency management made easy
sampleproject - A sample project that exists for PyPUG's "Tutorial on Packaging and Distributing Projects"
pip - The Python package installer
vscode-python - Python extension for Visual Studio Code
Pipenv - Python Development Workflow for Humans.
virtualenv - Virtual Python Environment builder
python-lib - Opinionated cookiecutter template for creating a new Python library
resume - My resume, in LaTeX
tomli - A lil' TOML parser
laravel-websockets-example - Quick example of a docker stack for laravel-websockets