[marcosdumay]

> For personal projects venv + requirements.txt has never caused problems for me.

That means you don't use Windows.

What is great. Keep not using it. But most people will have a different experience.

[kristianp]

Wait, are most of the people having problems in this thread using windows? It's been mentioned a couple of times, but not by most.

[disgruntledphd2]

There's a bunch of people who tend to have problems with Python dep management: - Windows users

- DS/compiled libs users (mostly Fortran/Cuda/C++)

- Anyone with dependencies on native/non python libraries.

Conda definitely helps with 2 and 3 above, and uv is at least a nice, fast API over pip (which is better since it started doing dependency checking and binary wheels).

More generally, lots of the issues come from the nature of python as a glue language over compiled libraries, which is a relatively harder problem in general.

[Kwpolska]

There are no Windows-specific issues in venv + pip. Windows can be more painful if you need to compile C extensions, but you usually don't, since most commonly used packages have had binary wheels for Windows on PyPI for many years.

[marcosdumay]

Installing anything in Windows is a system-specific problem.

If a pypi package has binary dependencies, it's a pip problem on Windows, if it depends on APIs that aren't installed by default, it's a pip problem on windows, if it depends on specific versions of something that isn't in python, it's a pip problem on Windows. If it depends on some API that the implementation is provided for free, but not freely, and is full of constrains on how you can install, it's a pip problem on Windows.

Most other package managers have the exact same problems. But some of the python alternatives that people often don't understand the point were created exactly to solve those problems.