Log file Viewer

[07:56:49] <flupke_> Hi, given a source package file (package.tar.gz), how can I get the corresponding wheel filename without actually building the wheel?

[07:58:40] <flupke_> This is to speed up https://pypi.python.org/pypi/freeze-requirements/0.4.1, to avoid rebuilding wheels that have already been built

[15:24:54] <stbatduke> Anyone know how to install or change a virtualenv to a different version of python, directly to the .virtualenv/bin/ ?

[16:25:46] <stbatduke> Anyone?

[16:26:19] <Alex_Gaynor> stbatduke: to create a virtualenv with a different python you can use the -p flag

[16:26:29] <stbatduke> Right

[16:26:31] <Alex_Gaynor> you don't want to try to change an existing virtualenv, just delete it and make a new one

[16:26:41] <stbatduke> I can't do that in a production environment

[16:27:44] <stbatduke> So the issue is that: Whoever worked in my position before me did it this way somehow: There is only python 2.6.6 installed on the system in /usr/bin/ and somehow there are about 12 or 13 different virtrualenvs that are using python 2.7.4 within the /home/user/.virtualenvs/bin/ ...

[16:28:37] <stbatduke> I need to know how this was done so that I can continue with this server

[16:29:11] <stbatduke> Frustrating thing is that the dev server and test server are using different versions of python, different versions of debian, and different versions of gcc and glibc etc etc

[17:47:01] <agronholm> dstufft: you around? did you happen to see my question earlier?

[17:47:12] <dstufft> which question was that

[17:47:49] <agronholm> dstufft: it was about a rogue distro (APScheduler2)

[17:48:00] <agronholm> whoever put it there didn't leave any contact info

[17:48:10] <agronholm> and he modified the code in an incompatible fashion

[17:48:25] <agronholm> didn't document the change, and all the links still point to my docs and my issue tracker, etc.

[17:48:39] <agronholm> to top it off, it's completely pointless

[17:49:18] <agronholm> I would like to know what I can do about it

[17:49:23] <dstufft> toss an email to donald@python.org and richard@python.org with links and such and we'll take a look, most likely richard will he normally handles that kind of stuff

[17:49:31] <agronholm> ok thanks