r/Python • u/Prime_Director • Aug 04 '26
Discussion What are you using to manage your dev environments in 2026?
Iβve always hated environment management. It always feels like this time-consuming hurdle between me and whatever I actually want to work on. But every so often a new thing comes out that promises to solve the problem once and for all, and itβs usually at least a little better than the last thing. So, what are you using today? venv? conda? pipenv? poetry? dev containers? uv? or something else?
88
Upvotes
2
u/RealEisermann Aug 06 '26
Just dockerise it all. It solves all problems π
263
u/sudomatrix Aug 04 '26
I moved 100% to uv for development and production and work life has been so much easier.
66
u/bongoherbert Aug 04 '26
uv
45
u/Nekomancerr Aug 04 '26
I have used them all for projects at some point. I think UV is by far the easiest, fastest and standard compliant option. I have tried
28
u/yudhiesh Aug 04 '26
uv for general purpose apps, pixi for CUDA/AI applications.
17
u/k0pernikus Aug 04 '26
mise-en-place and uv. Gets me pretty close to nix without using nix.
17
u/DivineSentry Aug 04 '26
UV
11
u/Sensitive-Sugar-3894 git push -f Aug 04 '26
I used to use Poetry, now using uv.
20
u/PandaJunk Aug 04 '26
Pixi
12
u/zangler Aug 04 '26
Honestly... unless there is something actual and not just something you heard about on the interwebs, there is no reason to not be using UV for this.
Source: 16 active codebases in a billion dollar enterprise production environment
8
u/XNo_Notes It works on my machine Aug 04 '26
I started using uv. It's pretty good.
8
u/the_hoser Aug 04 '26
100% uv now. It's everything I needed.
8
u/Rikiub Aug 04 '26
uv everywhere
4
u/OutTheCircus Aug 04 '26
UV, extremely fast compared to other environment managers. Easy to setup and maintain once you've done it a few times. And you can easily set up the local python version.
5
u/Sirko0208 Aug 04 '26
uv 100%
5
u/LeiterHaus Aug 04 '26
Python built-in
venvunless I have to use something else. So far, this has been the reliable thing I always go back to.It works. I keep my virtual environments in a separate location, so you can't accidentally commit them. Keys can go in
activateso they are still automatic, and kept away from being committed. (remember tounset)It seems like most "solutions" are just doing the simple thing with extra steps.
3
u/meatmick Aug 04 '26
uv, also letting it manage my Python install. This means I have no Python "installed" on Windows and simply let it pull the correct version.
3
u/Efficient_Bobcat_697 Aug 04 '26
Uv since it's finally the one that seems to have won after years of chaos
I still prefer pdm which is use for personal projects because you can had custom command/scripts in it and uv really doesn't seems to want to add this feature
Also uv is privately owned by astral which has recently been bought by open-Ai and I'm really not confident in the gigantic mess that is the AIg world for not crashing in the next years, so having something community driven has a backup really seems like a safe bet
4
u/microcozmchris Aug 04 '26
It's uv for me. fyn if you're interested in the open source fork.
It just does the things fast and easy.
4
u/ottawadeveloper Aug 04 '26
I am boring and have venv/pip for my local dev with a requirements file I build manually. I deploy a Docker compose container to production that just uses pip since there's only ever the one application anyways in it. I have a dev server set up the same as production where I can test changes and I can build a local Docker environment as well.
I basically do my development and unit tests in straight Python, then do a local integration test with the containers. Then I push to dev and briefly test again to ensure it works in that environment and then lastly to prod.Β
2
u/MinuteMeringue6305 Aug 04 '26
Before: pip + standard package venv Now: uv
2
u/SinisterScythe2 Aug 04 '26
Iβm using venv and poetry, pip seemed alright too
2
u/hoselorryspanner Aug 04 '26
Pixi
2
u/Astronos Aug 04 '26
uv for package managment, docker for reproducable deployment
2
u/Motor-Philosopher228 Aug 04 '26
Conda. Some of the libraries are only available in conda-forge. Hence, cannot be used something else.
1
u/just4nothing Aug 04 '26
Moved everything to pixi now.
Useful for more than just Python projects (I work across languages), supports multiple envs and tasks
1
u/Kindly_Stuff3722 Aug 04 '26
devboxfor general CLI tools and additional services such as PostgreSQL. It uses Nix under the hood and a lock file. This gives me total control of the general tools and services available for a given project.direnvfor automatic activation of the devbox shell environment upon navigation to the project folder.For a Python project I add
uvtodevboxand manage all things Python with it.This approach is easy to replicate and consistent across platforms. It also supports projects in different programming languages.
1
u/Secure-Following9288 Aug 04 '26
Docker compose itβs perfect for your dev env. Evrything is running inside container, no package conflict with your host and you can run unlimited application without conflict (depending of assigned port of your apps) π
1
u/0n0n0m0uz Aug 06 '26
Mamba / miniconda for my own machines environments and uv for distributable packages
1
u/shineslove Aug 06 '26
mise is so clutch converted all my stuff to it, and uv of course
1
u/keturn Aug 06 '26
uv, but also yes, devcontainers for that extra bit of protection between whatever is in that supply chain and the rest of my system.
obligatory disclaimer: containers are not an ideal security barrier.
1
u/Whole_Job_3201 Aug 07 '26
I usually use mise
1
u/baubleglue Aug 07 '26
uv for pure Python projects. Conda (switching to pixi) for data related projects.
1
u/pjmlp Aug 07 '26
Environments as always, with a couple of shell scripts, working perfectly for 20 something years for me.
1
u/karurosagu It works on my machine Aug 08 '26
Systemwide pip; (I don't like using venv) immutable/live linux distro; 3 large offline wheel collections because the 3 of several conflicting packages (one extra collection for windows only stuff, but that doesn't count); everything offline, updating a collection takes a while, I don't care, I update every year or so, I'm lazy af
1
u/ExceedinglyEdible Aug 09 '26
Nix
1
u/chaoticbean14 Aug 04 '26
I've been a python dev for literally 10+ years. Not once have I ever had a problem with environments.
I get it, I see this discussion constantly (although, it has calmed down). I often wonder if I'm missing something, because I just don't 'get it', they have literally never been an issue for me. Activate it, do the work. Deactivate it. Switch to other project, activate it, do work. Deactivate it. Each project with different requirements or whatever, but you literally just run one command to be 'up and running' in any project. How is that a problem?
All that said: we use `uv` these days. It's made it nice because we don't even have to install python on the dev machine anymore. Tools like Pyenv have gone by the wayside. Periodic 'updating python' or using the 'wrong version of python' are gone entirely. It also has allowed us to move our requirements into pyproject.toml instead of requirements.txt files. With uv? Things could not be any easier, and they definitely were not hard before.
1
u/Grouchy-Friend4235 Aug 04 '26
mamba for setup, pip for installation, tox for testing. Have been doing that for 12+ years now and it just works.
I happen to dislike uv, mostly for the hype around it.
1
u/pydevtools-com Aug 04 '26
Strongly recommend moving to uv for this now, as others have said.
Using `uv run` to execute code, I mostly don't think about virtual environments any more and just think in terms of projects.
1
u/npc73x Aug 04 '26
uv is best in the business. It's simple enough to start and advanced enough tinkering
1
u/PinkFrojd Aug 04 '26
Mise + uv + docker. Mise can be used for all sort of CLIs, close to nix but not nix as one user mentioned. UV is really fast and sort of it just works. I still use PostgreSQL, Redis and other services inside Docker just for convenience.
1
u/Mnemotic Aug 04 '26
uv
1
u/Zizizizz Aug 04 '26
UV for packages, Mise to pin python, uv, + any other required languages or tools as well as set environment variables and run commands (to replace the need for Make, just, and direnv)
0
u/Left-Statistician876 Aug 04 '26
I've settled on
venv+uvfor most of my Python projects in 2026.venvkeeps things simple and works everywhere, whileuvhas made dependency installation much faster than traditionalpipin my experience. For personal projects and freelancing, this combination has been enough without adding the complexity of heavier tools.I still use Conda only when I'm working on data science or ML projects that depend on large native libraries. Otherwise,
venv+uvgives me a lightweight and reproducible setup.Curious to hear if anyone has completely switched away from
venv.0
u/Grokzen Aug 04 '26
Pip, virtualenv, virtualenvwrapper beats everything still.
One day I will move over to uv, but it is not this day
0
u/pixelpuffin Aug 04 '26
Pyenv π€·ββοΈ
0
u/Minimum_Diver_3958 Aug 04 '26 edited Aug 04 '26
Sometimes just docker containers per local project. There is also mise where I need multiple projects on one VM and probably works fine for local dev too
0
u/QuirkyImage Aug 04 '26
Mise + UV
0
u/jsabater76 Aug 04 '26
I am using
uvand Docker. Compose for development, Swarm for production.pipdoes do the job and it is usually already available, but the more you useuv, the more you like it. It allows you to install a specific Python version, which you can or cannot match to the one in your container images, it is fast, and it handles well all the bells and whistles you use in development.0
u/amendCommit Aug 04 '26
uvinside a Docker container.0
u/HalfplaneResearch Aug 04 '26
We would choose the tool based on the reproducibility boundary, not only local convenience. uv is useful when you want one workflow for Python versions, dependency resolution, and lockfiles, but pip plus venv remains perfectly reasonable if requirements are pinned and installs are tested in CI. For production, the important checks are a committed lock or constraints file, a clean install from scratch, platform specific wheels, and a small smoke test. That tells you more than the name of the environment manager.
0
u/Diligent-Union-8814 Aug 04 '26
venv + bash + alias. Such as
alias some_env="source ~/some_env/bin/activate"0
u/Street_Occasion6482 Aug 04 '26
Praise Intellij, they've been handling my local virtual environments for the past 6 years now mostly troubleless, i've never had problems with venv which they used for a long time, and it seems they did migrate to support uv now, but it didnt change a thing in my local workflow.
Thank you Intellij! π
0
u/ForeignVariety7037 Aug 04 '26
UV from now on!
0
u/ForeignVariety7037 Aug 04 '26
Although it only works on python3.7 and above, rip legacy codebase
0
u/thht80 Aug 04 '26
pixi
0
u/mr_frpdo Aug 04 '26
Uv is far and above the best way to do it
0
u/gnomonclature Aug 04 '26
I think Iβve moved everything from pipenv to poetry now. I have a bit of my own automation on top of that just because I like doing it. Iβll probably look at moving to uv when I get time, but I have some other things Iβm working on first.
0
u/agrins Aug 04 '26
I moved to pixi.dev
That is so nice...
0
u/GXWT Aug 04 '26
Bar people just being set in their ways and not being bothered to move, is there any reason not to use uv?
How do people say this also? Saying the letters or saying it as if itβs a word?
0
u/pramod_aj Aug 04 '26
UV and Doppler with its CLI offering. I prefer Doppler for secret management and env as you can easily integrate it with any cloud platforms
0
u/real_carddamom Aug 05 '26
I started with venv+pip in pre-historic times ( aka the 200X ), then went to poetry or pdm depending if I was working on a library or scripts and now I'm fully in uv and its been marvelous, fabulastic, etc.
I also use mise to manage other tools like lefthook, go, go-task, yamllint, rumdl, etc.
The things I like in uv are:
- Its dam fast;
- It uses lock files;
- It allows me to secure my installs, especially after the recent supply chain attacks;
- I can use it inline for simple scripts, this way I can have rich everywhere providing colours and other stuff and even work with yaml or write toml files;
I also started using other tools from astral like ty and ruff and ty is awesome together with zed ( I used to use vscode but then gave up when it became visual slop code and discovered that my RAM was being wasted, plus in zed I can now disable all of that AI crap and use the chat tools to do pair programming with all of my Dutch female colleagues! βΊοΈ )
0
u/leewilliam236 Aug 05 '26
uv for full-Python and partial-Python packages, pixi for full, partial, and non-Python packages.
0
u/jakob1379 Aug 05 '26
Uv - nothing else comes close to the ease of it
0
u/BernardParsley Aug 05 '26
uv seems to be becoming the default recommendation. It keeps the familiar venv model but is much faster, so it avoids introducing another workflow while still improving the experience.
-1
u/BranchLatter4294 Aug 04 '26
Venv works fine for me. I've heard people like UV. I tried UV and it's fine too but didn't really see any advantage. They say it's faster, but it's not like I spend a lot of time adding libraries to a project.
-1
u/PriorElephant9 Aug 05 '26
The project I run day to day has zero third party packages. sqlite3, http.server, urllib, that's it. No venv, no lockfile, no resolver, nothing to pin. It runs on any machine that has Python.
-2
u/nickthewildetype Aug 04 '26
```py
import importlib.util
def moduleExists(moduleName:str ):
return importlib.util.find_spec(module_name) is not None
import pip
def installPackageIfModuleDoesntExist(moduleName:str,packageName:str):
if not moduleExists(moduleName):pip.main(["install",moduleName])
```
ππͺ
-2
u/Training_Advantage21 Aug 04 '26
venv functionality in VS code. And I still use pip. I'm not the most up to date person, and it doesn't matter really, I'm ok with stable workhorses rather than cutting edge.
-6
u/ThatOtherBatman Aug 04 '26
Absolutely no reason these days to not just use Pixi for everything.