flit VS virtualenv

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.

For more information visit: virtualenv documentation.

Python's venv module is officially recommended for creating virtual environments since Python 3.5 comes packaged with your Python installation. While there still are additional older tools available, such as conda and virtualenv, if you are new to virtual environments, it is best to use venv now.

Despite these attractive attributes, many developers I've come across don't prefer Fish shell, primarily due to integration gaps with tools like Python's virtualenv. So, in this article, I'm offering a simple solution for automatic virtualenv activation for Fish shell, steering clear of resource-intensive frameworks like oh-my-fish that often slow down the shell.

`virtualenv` still exists and is still actively developed. It's true that Python 3 ships with `venv` but I think `virtualenv` offers some additional features.

https://github.com/pypa/virtualenv

virtualenv is a tool that creates an isolated Python environment for each of your projects.

Python is the chosen language for this tutorial and as you can guess some precautions should be done to make sure that the environment is setup correctly and the main OS I'll use is Ubuntu(a Linux distro) virtual environment is a tool that helps you to isolate your code from the rest of the system. It is a good idea to create a virtual environment for your project.

$ curl -O https://github.com/pypa/virtualenv/raw/master/virtualenv.py$ python virtualenv.py my_new_env$ . my_new_env/bin/activate(my_new_env)$ pip install ... Or something entirely different?

I've been using Fish for years and spend my entire day working with Python. Python's virtualenv has an `activate.fish` command, I've never had any problems with it. Additionally, we have a ton of internal tooling built in a fabfile, so I've written a couple of snippets of fish that automatically activate that .venv (Poetry managed) whenever I cd into a directory that has one, and also expands a bunch of env vars into the shell session. I've also got this feature request in on the virtualenv repo in the hope that one day we can have activate.fish emit an event - https://github.com/pypa/virtualenv/issues/1456

We of cause, like all good developers do, put the error message online and look for clues, we quickly found a GitHub issue and boi, we are not the only souls that got crushed by a "timely" release of virtualenv just a few hours before us. Since the lastest version of virtualenv got installed every time we create the CI build job on Travis, it fails even we have done nothing. Of cause we didn't point fingers at other maintainers, they are just as hardworking as us and it's human to make mistakes. We are faced with 2 options, roll back to the previous release or wait for the patch of virtualenv to get released. As the devs of virtualenv did a lighting fast patch, we have chosen option 2.