[19:48:24] <tdsmith> Hi #pypa. I'm trying to use setup.py to install Sphinx into a temporary prefix because I want to guarantee that I'm running the sphinx-build generated by the Sphinx sdist that I downloaded. I'd like to do this without touching any Sphinx build already present somewhere else.
[19:48:52] <tdsmith> Passing --prefix to setup.py install doesn't seem to be doing the right thing. If a user already has Sphinx installed, *that* Sphinx installation gets bundled and the right files don't get written into my --prefix!
[19:49:03] <tdsmith> A log demonstrating that condition is here: https://gist.githubusercontent.com/anonymous/598bf0683e3708524b42/raw/eeb1c7cb28dd79d65562b1757cc64353db6a1f96/05.python
[21:04:10] <bobbyr> i have a project that uses celery with redis support
[21:04:33] <bobbyr> to install that version of the celery package, i run pip install celery[redis]
[21:04:55] <bobbyr> when i pip freeze, i see the celery and redis dependencies seperately
[21:05:49] <bobbyr> however, when i install from a requirements file, project wont build properly because celery and redis are actually being installed seperately
[21:06:44] <bobbyr> is there any way that i can command pip to install celery[redis], rather than installing celery and then redis?
[21:08:15] <bobbyr> in other words, pip install celery && pip install redis; pip freeze; == pip install celery[redis]; pip freeze; in terms of the requirements file, but not in terms of the actual build
[22:57:51] <tdsmith> Gosh, there's root, prefix, install-base, and target.
[23:13:05] <tdsmith> Apparently I want --root, for setup.py. https://mail.python.org/pipermail/distutils-sig/2010-November/017099.html