So, I wanted to run Python 3.4.x inside a virtualenv virtual environment. I learned that the first step should be to build Python 3.4.x.
I was doing so in /usr/bin/Python3.4.x (a folder I created), where I had extracted Python3.4.x stuff. Then ran
make, and then did
sudo make install. As that command was doing its work, I realized that I might have messed up pretty badly by overwriting core Debian stable Python.
A simple test of running
python in terminal shows that I am still using Python 2.7.x, so it seems that I am okay, but I have no clue. Doing something like
sudo make uninstall is not an option because I don't think Python makefile comes with uninstall rules for make.
Doing something like
sudo apt-get install --reinstall python also doesn't do much, leaving me feeling like I am safe, since reinstall didn't have to overwrite any files?
In any case, I am not sure what I just did, and I am not sure what the consequences are. Could someone help me understand?
I finally understand why the instructions I was following suggest that I configure and make using /opt/some_folder prefix, but its something I omitted...and now...yeah.