Log file Viewer
#pypa logs for Wednesday the 13th of August, 2014
[08:57:00] <dpn`> howdy - I'm getting some strange errors about "not a py file" on pypy - https://gist.github.com/dpnova/73d0276e3370365db98f
[16:48:09] <stbatduke> So I have stepped into an interesting situation and need to know if possible how it was setup.... I am the new Engineer for a setup of production applications working within their own virtualenv containers ... The system (Debian 6.0.9) has python 2.6.6 installed in /usr/bin/python (ln to /usr/bin/python2.6) however the virtualenvs have their own python 2.7.4 installed in their /home/username/.virtualenv/<envname>/bin/python2.7 .... so I am looking for the "co
[16:49:38] <stbatduke> I know that I can simply download and compile by hand the python into the .virtualenv/ path, or I could install by hand in the same way the python into /usr/bin/python2.7, however as this is not what was done before, I need to know what other ways there are to do this that would more match the way this was done on our systems in the first place
[18:28:05] <qwcode> stbatduke, using /home/username/.virtualenv/<envname>/bin/python2.7, you can inspect sys.real_prefix to see what python the virtual environments came from
[18:55:24] <stbatduke1> qwcode: I know that the virtual environments are using python installed within the /home/username/.virtualenvs/bin/ location, but I'm not familiar with how to verify this with sys.real_prefix as I am still new to python :)
[18:55:51] <stbatduke1> What I really want to know is how to install a different version of python "inside" an existing virtualenv container