[08:49:48] <indistylo> My goal is to build real time notification , Django realtime: : How to solve the NameError:name 'root' is not defined, Read problem details at http://stackoverflow.com/questions/32944158/django-realtime-how-to-solve-the-nameerrorname-root-is-not-defined
[09:31:45] <ronny> indistylo: wrong channel, and you never defined root
[15:14:40] <elarson> if I have a requirements.txt that includes foo >= 1.0 where the latest package foo is 1.5. If I then install foo == 1.3, will 1.3 become the "active" version in the virtualenv?
[15:18:14] <elarson> looks like pip uninstalls the later version and installs the 1.3
[15:19:51] <Ivo> elarson: yep, you basically answered yourself :)
[15:20:55] <Ivo> but if you tell it to install an exact version itll even uninstall a newer one, yes
[15:25:12] <elarson> Ivo: perfect, thanks for confirming!
[15:25:16] <gthank> I'm sure I'm missing something obvious, and will feel like a dolt when you guys answer this, but: how do I put a dependency on a VCS version of a lib in my requirements file? I'm trying `uWSGI==git+https://github.com/unbit/uwsgi.git#egg=uWSGI` with no success
[15:26:14] <gthank> The error is https://gist.github.com/gthank/6f803612c9a26ff863d1
[15:26:43] <gthank> But when I use that same URL to install manually, it works (as far as I can tell, at least)
[15:26:46] <doismellburning> gthank: drop the `uWSGI==`
[15:26:49] <tdsmith> i think you'll want to drop the prefix and just use the URL
[15:27:09] <gthank> …and I was right about the "something obvious"
[15:28:35] <Ivo> gthank: any particular reason you want master and not 2.0.11.1?
[15:28:58] <gthank> Because their compile flags are a little confused
[15:29:06] <gthank> And they haven't cut a new release.
[15:29:18] <gthank> Under El Cap, they use an undefined symbol
[15:29:58] <gthank> Because their feature detection used to only pick up some feature under Linux, but El Cap added the feature, but the symbol exported by socket.h on Cap is named differently
[15:30:13] <gthank> Ah the joys of living in the fast lane :-D
[15:56:28] <dstufft> fwiw I am working with Debian to try and resolve the conflict and figure out a reasonable path forward.
[15:57:17] <ionelmc> dstufft: what's the status on that?
[15:57:18] <Wooble> What, their opinion isn't that pip needs to die and everyone should install everything for the system python using apt? :)
[15:59:39] <dstufft> ionelmc: they're working on a thing called "dirtbike" which will enable them to rebundle pip based on the versions of bundled software that exist in the Debian apt repo
[15:59:59] <dstufft> so pip will still be bundled, they'll just rebundle it at python-pip build time
[16:00:29] <elarson> does that mean the deps still get unvendored?
[16:00:59] <dstufft> Wooble: There are some folks who think that pip needs to die, but some folks (particularly Barry Warsaw, who is awesome) who don't agree and are pushing forward a lot of the work to make pip and Debian play nicely together
[16:01:10] <ionelmc> dstufft: where can i read about this dirtbikeshed thing? :)
[16:01:12] <elarson> or is it like unvendoring, and then revendoring with deb's package code
[16:01:25] <dstufft> elarson: sort of? they'll remove the copies that pip has vendored, but revendor with Debian's copy of requests, cachecontrol, etc
[16:09:55] <dstufft> (I use the # I'm Sorry comment a lot :D)
[16:18:18] <gthank> If I just want pip to download the archives, but not install (because I have to manually bundle some stuff up and then ship it all over a big tarball for use with --find-links), isn't `pip install --download $MY_DIR` the way to do it?