On Mon, Nov 12, 2018 at 3:31 PM Mats Wichmann <m...@wichmann.us> wrote: > > Reconstruct the virtualenv you want maybe? Their whole concept is that > they're cheap and easy and can just be thrown away. Of course, you then > have to remember what you did to create it in order to make a new one...
It's been 3 years, I'm clueless as to how I created it. Also I'm a noob when it comes to Linux which makes this even more confusing for me. The 3 years I've been absent from Programming I went back to Windows. > Since you're on a Linux platform, use "which" to see how the names you > are typing are resolving > > which python > which python3 The "command" gives this output: (website) matthew@linux-oq68:~/Documents/mywork/web/website/blogsite> which python /usr/bin/python (website) matthew@linux-oq68:~/Documents/mywork/web/website/blogsite> which python3 /usr/bin/python3 > Usually if the virtualenv has been broken by external factors, it won't > even activate. Are you sure you remembered to try to activate it? > Yep, I double checked to make sure I remembered to try to activate it. _______________________________________________ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: https://mail.python.org/mailman/listinfo/tutor
