I'm creating a virtual environment (venv) on a network location (X drive) in order to allow other people to work on my project. The intention is for this project to be worked on by different people at different times (not concurrently) on their own computer. All data and scripts will be stored on the network drive, so I figured it makes sense to have the venv there too.
I can create the venv fine by going to Settings->Project Interpreter->(cog wheel)->Add... I use as my base interperter the python3 installation I have on my C drive (C:\Users\my_name\AppData\Local\Programs\Python\Python37\python.exe). The venv is made and everything works fine on my machine.
However, when I investigate the Interpreter Paths for the interpreter that's in my new venv(my_env\Scripts\python.exe), there are three paths that direct to my C drive. I'm confused as to why they are there, because I thought everything should be pointing to the new virtual environment folder I made on the X drive:
Furthermore, when a colleague of mine opens the project, I get a warning to configure the interpreter. When I configure the project from his machine to use the python.exe file in the new virtual environment I made, I get the following warning:
Which is particularly strange to me considering I set up the virtual environment using Python 3, but for some reason, on his computer, it's being read as Python 2.
Can someone please give me some guidance on the following things:
1) Why are there paths pointing to my C Drive after I make a venv on the X drive?
2) Why can't I get pycharm to use the interpreter on the venv on my colleague's machine?
3) Am I using virtual environments in the way they're intended, or am I naive to think a venv on the X drive should be self-contained (i.e. wouldn't reference anything on a local machine)?
Thanks in advance!