Re:Why not tell people to “simply” use pyenv, poetry or anac...
by rcfox on Tuesday June 13, 2023 @07:31AM
(#36308600)
Worse than Javascript's 5+ different types of mostly incompatible module formats, transpilers for different version targets, megalithic node_modules directories and the community's love of importing new packages for one-line functions that can disappear and take down the internet?
[ Parent
| on HN ]
Re:Why not tell people to “simply” use pyenv, poetry or anac...
by linkdd on Tuesday June 13, 2023 @07:35AM
(#36308656)
How is `node_modules` different from `/path/to/venv/lib/python3.X/site-packages` ?
Are PyPI, cargo, Maven, etc... all immune to supply chain attacks?
Re:Why not tell people to “simply” use pyenv, poetry or anac...
by rcfox on Tuesday June 13, 2023 @07:57AM
(#36308931)
One major difference is a venv doesn't allow nested dependencies. With npm, you might install version 2.3 of a package, only to find that some other package has installed version 1.4 under itself.
Python also has "wheels", which are pre-compiled distributions, rather than full-source distributions. These are often smaller and install faster.
Re:Why not tell people to “simply” use pyenv, poetry or anac...
by heywhatupboys on Tuesday June 13, 2023 @04:59PM
(#36317235)
> One major difference is a venv doesn't allow nested dependencies. With npm, you might install version 2.3 of a package, only to find that some other package has installed version 1.4 under itself.
a feature not a bug. Anyone who ahs built a sufficiently large project and had to abandon some dependencies know this pain
Re:Why not tell people to “simply” use pyenv, poetry or anac...
by jeltz on Tuesday June 13, 2023 @07:44AM
(#36308778)
Yes. Which is quite impressive.
Re:Why not tell people to “simply” use pyenv, poetry or anac...
by whywhywhywhy on Tuesday June 13, 2023 @08:11AM
(#36309076)
As much as we all have criticized the npm ecosystem, after seeing what exists in the python world I actually came round to it and consider it very good.