3 ms·
This works for me. But I am crazy. - Install Python through Brew. - Upgrade pip using pip. Install all further libraries using pip. Never install Python packa
by photonios 7y ago
This works for me. But I am crazy.
- Install Python through Brew.
- Upgrade pip using pip. Install all further libraries using pip. Never install Python packages through brew.
- Use a plain virtualenv per project/repo.
A long time ago I wrote some bash that I keep in my `.bashrc` that overrides the `cd` command. When entering a directory, my little bash script iterates upwards in the directories and activated any virtualenv it finds. I also override the `virtualenv` command to automatically activate the env after creating it.
I am aware there are existing tools out there that do this. Pyenv does this right? But I never got used to them and this keeps things simple enough for me. I cannot forget to enter a virtualenv.
As I said, I am probably nuts. I also don't use any form of IDE. Just plain VIM.
- skiman10 7y agoDoing things differently doesn't make you nuts. Do you mind sharing your dotfiles? This is really interesting to me.
- photonios 7y agoSure! I have a Gist here with this little snippet: https://gist.github.com/Photonios/4a17d6c952d85cc23234b4394b9becfc https://gist.github.com/Photonios/4a17d6c952d85cc23234b4394b... Hope it proves useful :)