I rarely comment here on hackernews. I've also seen several flame wars over pipenv. I also believe that python packaging and pinning is nothing but a mess. Recently I started using Pipenv and suddenly I've been having horrific issues with python to the point of me almost giving up on the language itself. I believe the issue is a mix of Pipenv, Pip and Debian. I don't have full scope view of the issue yet but without evidence I believe the issue is how Debian uses Pip at the system level, and in pip 9+ an API used by Debian changed. Pipenv seems to greedly somehow upgrade my pip and thusly hoses everything and I find myself reinstalling everything. All three are making me consider making changes to my entire stack and setup that I've been using daily for the past 5 years on many many systems.In addition when/if I have time I'll further debug and attempt at PRs and issues to help.
depressedpanda|7 years ago
- First of all, never `sudo pip install` anything.
- Second, on a fresh Debian install, run `sudo apt install python3-pip && pip3 install --user --upgrade` to get the latest pip while still allowing Debian to use its old outdated version. I would actually recommend you remove it to prevent you from accidentally using with (with `sudo apt purge python3-pip`), unless you need it available at the system level for some reason.
- Add `~/.local/bin` to your $PATH.
- If you need to deal with py2 packages for some reason, consider managing multiple Python versions with pyenv[1].
I won't go into Pipenv because I dislike the tool.
[1]: https://github.com/pyenv/pyenv
murphy214|7 years ago