3 ms·
Much similar work is required for ruby, but gem/bundler is less fraught with fragmentation than pip/poetry/venv.
by e12e 5y ago
Much similar work is required for ruby, but gem/bundler is less fraught with fragmentation than pip/poetry/venv.
- wink 5y agoI think a big part of the problem is that bundler has been around for ages whereas half of the tools mentioned here didn't even exist just 5-6 years ago. Which can be seen by this hilarious sentence: > By default, Python packages are installed with pip install. In reality nobody uses it this way. It installs all your dependencies into one version of Python interpreter which messes up dependencies. Why hilarious? Because everyone I know uses `pip install` if they're not using poetry. And because poetry is kinda new, that's a lot of people.
- dmurray 5y agoThe quote isn't clear, but I think the author means people don't generally run pip with their system python. I.e. they don't run /usr/bin/pip or whatever, but use some virtual environment solution.
- e12e 5y agoWhich is the same for "gem install" - you don't want to go "sudo gem install".
- dmurray 5y agogem catches this by default and warns you. Pip doesn't, but it would probably be good if it did and the pip guys explicitly took the position that "installing stuff on your system python is not a normal use of it".