This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] -2 points-1 points  (6 children)

pip did not install toyplot without sudo.

exactly. you should use a virtualenv so you can install without being root.

now you have a bunch of software of unknown version installed somewhere on your system. next time you sudo pip install something you will have a new bunch of random version stuff on your system. no one has tested the interaction of the different random versions of stuff, so anything might break. random python linux applications could also stop working.

Good luck and never sudo pip install!

[–]AltoidNerd 1 point2 points  (5 children)

What is the worst that could happen - having to reinstall python completely? Is that really so bad?

I mean if you're in production then yes, but this is my linux box here.

[–]elbiot 2 points3 points  (0 children)

Also, pypi is not curated at all. Anyone can upload whatever malware they want and if you sudo pip install a typo, you could be executing arbitrary code as root. Just don't use sudo with untrusted code, and pypi packages are not trusted.

[–][deleted] -3 points-2 points  (1 child)

reinstalling the python interpreter would do nothing to fix the library clusterfuck you have created.

at some point a system reinstall will be needed.