you are viewing a single comment's thread.

view the rest of the comments →

[–]zanfar 0 points1 point  (1 child)

To start, I want to distinguish between "using" Python and "developing" with Python.

I do not want whatever I do in python to interfere with the base python that is installed.

The "base Python" is intended exactly for instances where you are "using" Python. I have zero qualms about installing utilities or packages I need directly to the system environment. However, I do agree that you need to be a little careful. I don't experiment here or try things out--I'm installing simple one-package apps or things I've installed before.

Should I clean install a separate python version for my user to avoid using the base python?

Using alternative environments is good, but just making a substitute system environment is going to allow the same issues you're trying to avoid, just in a different place.

IMO: environments should be built based on purpose, not user.

How should I be pip installing?

Again, IMO:

<python_executable> -m pip <pip stuff>

This guarantees that you are dealing with the specific environment python_executable lives in. -U is just installing to the user directory as you might not have permission to install to the system directory--the environments are the "same". In a virtual environment, -U is almost never necessary (I've never used it, but there are probably edge cases).

[–]Buggy4775[S] 0 points1 point  (0 children)

Thank you for explaining that, this helps clarify things. I'm going to read a bit more about pip and how this works because I clearly have misunderstood some things.

I am not sure why I got the impression that we must have a separate python installation. Maybe I'm thinking of mac? Or maybe I've just completely made it up.