3 ms·
Pip, Venv, poetry, pipenv, now uv If you are still struggling with this in 2024, you are missing the actual challenges of the world.
by TZubiri 2y ago
Pip, Venv, poetry, pipenv, now uv
If you are still struggling with this in 2024, you are missing the actual challenges of the world.
- simiones 2y agoSo the fact that there are 5 different tools that (attempt to?) fix this problem is a sign that it is not a problem, from your point of view?
- TZubiri 2y agoIt's a sign developers get stuck in a paper bags. Same thing with text editors, orms, frameworks. Imagine 2050, flying cars, talking robots, teleportation, and John Developer is going to be releasing solution 57 to a problem that was solved in the 90s
- dist-epoch 2y agoWhat is the 90's solution to this problem - autoconf, apt, yum, oops, here we go again with multiple standards.
- dikei 2y agoJust like JS has npm, yarn, pnpm, bun... It seems the more users a language has; the more dev tools get written for it.
- TZubiri 2y agoMaybe if you don't import stuff like left-pad and actually write some code, you wouldn't have to write a dissertation on package management.
- dikei 2y agoActually, I prefer spending my time writing right-pad
- TZubiri 2y agoMaybe we could abstract directions away. d-pad(pad_character,direction,string) Of course this would be an internal dependency of both left-pad and right-pad.
- zahlman 2y agoPlease try familiarizing yourself with the actual dependency graphs of major large Python projects - and with what these dependencies actually do - and then see if you still want to maintain this facetious tone.
- globular-toast 2y agoAgreed, but who is struggling with it? Do you think tool development should just stop because it's not an "actual challenge"?
- zo1 2y agoNot OP, but I honestly think that these kinds of devs are just way too opinionated and don't want to accept the 95% valid existing solution. In a healthy ecosystem, people can try and experiment and if something is awesome then people would naturally switch to it over time. Sadly what happens now is that everyone under the sun tries to evangelise and "create content" for these new tools so much that the natural filter mechanisms don't work. Doubly-so because tools like Google effectively created a new fitness function for peoples' behavior that incentivizes just plain old content creation (whatever weird form it may take, including new libraries being created + promoted).
- maleldil 2y agoIMO, there's a direct line of improvement between pipenv, poetry, (briefly) rye and now uv. I think the ecosystem is improving over time and will eventually coalesce around a majority platform. I like uv, but I'm unsure if that will be the final product. Beyond just tool names, it's also important to realise that there has been a significant movement from the Python development team to standardise aspects of tooling. Tools like Poetry and uv weren't possible a few years ago before there was pyproject.toml to unify a bunch of separate things, for example.
- TZubiri 2y agoI don't know I don't care. I just use pip. If I need to virtualize I just do so at che OS or Kernel level. At any rate I take care of all of my python installs by not downloading a gazillion of random packages online, if I ever reach the situation where package 517 depends on package 208 and package 598 depends on a different version of package 208, I'll just pull out the FlemmenWerfer and trash the whole thing before it reproduces.
- the_mitsuhiko 2y agoNot that multiversion support was one of the goals that I had when I built rye. It's also something I want to see if it's possible with uv. Multiversion support is entirely orthogonal with how you are installing packages.