[08:50:08] <prologic> I *thought* as much but actually hadn't tested it yet
[08:50:16] <prologic> it should use whatever it finds I suppose?
[08:51:01] <prologic> and if it's both pip's cache and wheel's wheeldir and --no-index and no other --find-links should pick up both .egg and .whl from that dir?
[09:02:18] <xafer> speaking of them, I was wondering why the wheel package wasnt vendored in pip ?
[09:04:23] <dstufft> xafer: for similar reasons the setuptools packages wasn't, we're OK with optional dependencies in certain situations, but the core package manager should work
[09:06:57] <xafer> but since pip is expected to install package via building wheels, the wheel package will ultimately be vendored right ?
[09:09:01] <dstufft> we'll have to see how it plays out
[09:09:15] <prologic> in any case it's trivial to just pip install wheel
[09:09:21] <prologic> and even do it as a post hook in virtualenv
[09:09:30] <dstufft> one option, which is likely the real future, but may not in the short term, is to have it dynamically install wheel/setuptools as part of the build process
[10:36:33] <dstufft> what xafer was talking about is that in the future pip is going to build a wheel if one isn't available
[10:36:55] <dstufft> instead of running setup.py install we'll run setup.py bdist_wheel and then install the wheel
[11:48:11] <ronny> dstufft: when will that be supported by default, it would ease some deployment setups of mine, where we start with creating cached wheel, then install those wheels
[11:57:39] <pf_moore> ronny: basically waiting on someone with the time to implement it