flit VS Pipenv

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:"))

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

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).

flit

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.

pipenv solves this by having both kinds of requirement files: Pipfile lists package names and known constraints on which versions can be used, while Pipfile.lock gives specific package versions with hashes. Theoretically the Pipfile (and its lockfile) format were supposed to be a standard that many different tools could use, but I haven't seen it get adopted much outside of pipenv itself, so I'm not sure if it's really going to catch on.

* Tons of longstanding bugs that fail to be resolved in any sort of timely manner like this one: https://github.com/pypa/pipenv/issues/2413

I am sick and tired of the python packaging space pushing this godawful tool for Python. Please just use pip-tools or poetry instead.

ℹ️ You may use a different virtual environment manager like Pipenv or poetry.

Hey lua would you mind looking at this question for me? https://github.com/pypa/pipenv/discussions/5411

Alternatively, you can look into Pipenv, which has a lot more tools to develop secure applications with.

https://github.com/pypa/pipenv/releases https://bodhi.fedoraproject.org/updates/?search=pipenv (pipenv-2021.5.29-7.fc35 for the current Fedora release)