News for hackers. Stuff that matters.
Re:My Python Development Environment, 2020 Edition by Rotareti on Monday November 11, 2019 @09:42PM (#21511080)
Since you are familiar with nodejs:

poetry == npm

pyenv == nvm

pipx == npx

No big difference, IMO.

Re:My Python Development Environment, 2020 Edition by _AzMoo on Monday November 11, 2019 @10:17PM (#21511248)
Right? It's literally the same set of issues.

Package Management - npm? bower? yarn? Which should I use this week?

Interpreter Versions - Revisiting a project I last touched 2 years ago on node 8 has a load of locked dependencies that only work on that node version. OK, let's bring in nvm so I can get a dev environment going.

Executable Packages - oh no I've got two different projects with different and incompatible versions of apollo, what do I do? Oh right, sure npx for executable isolation so we don't pollute the global namespace.

Every ecosystem has these problems, and if they don't it's probably because they're still relatively esoteric.

Re:My Python Development Environment, 2020 Edition by Rotareti on Tuesday November 12, 2019 @07:01AM (#21513413)
> Every ecosystem has these problems, and if they don't it's probably because they're still relatively esoteric.

Exactly! I'm not aware of any non-compiled language where (all) these issues are solved much better. I can be very productive with the tools I mentioned above and I'm glad that they work almost identical for both my main drivers (Python and JS/TS).