zlacker

[parent] [thread] 3 comments
1. ilaksh+(OP)[view] [source] 2024-08-21 12:50:31
Ok so for web dev, are most projects using poetry, the, or something else?
replies(1): >>wswope+i31
2. wswope+i31[view] [source] 2024-08-21 20:15:23
>>ilaksh+(OP)
Most projects do just fine with pip + venv, and that’s what they stick to.

The exception is if they have specific dependencies outside the CPython ecosystem - in which case they’ll probably be using conda. Examples of such dependencies include nodejs/cuda/cublas/specific versions of gcc. Webdev generally doesn’t have as many of these dependencies compared to the data world, which is why conda is less popular there.

Speaking in sweeping generalities here: you probably don’t need poetry, uv, or kin - at all. But there’s nothing wrong with choosing to use them if you prefer to do so either.

replies(1): >>ilaksh+qy1
◧◩
3. ilaksh+qy1[view] [source] [discussion] 2024-08-22 01:11:37
>>wswope+i31
ok.. thanks.. but the reaction in this thread seems to slightly contradict that? I didn't see anyone say "we use pip + venv, it works fine".
replies(1): >>wswope+0D1
◧◩◪
4. wswope+0D1[view] [source] [discussion] 2024-08-22 01:59:20
>>ilaksh+qy1
Think of it this way: the release of VS Code didn’t mean people suddenly stopped using or updating Emacs/Vim. VS Code simply offered a more polished, beginner-friendly way of setting up and building software projects than the old TUI editors.

In the same way, none of the “fancy-pip-replacement” projects will outright obsolete pip or conda. They’re just tools that can work a bit more intuitively for new users and provide a bit of polish/UX value - but their niche fills the exact same role as pip/conda: managing the set of binaries on your PATH.

[go to top]