[12:58:02] <mgedmin> ah, but status.python.org got wind of it :)
[16:53:53] <apollo13> dstufft: wow, the debian pip patching is relatively minimal with 8.x, that is nice
[19:48:56] <natefoo> a new release of wheel is just about ready to roll
[19:49:05] <natefoo> i just want to verify that pip's tests pass first
[19:49:46] <natefoo> if anyone happens to have a windows machine w/ all the various pythons we have tox envs for, i'd appreciate if someone would run wheel's tests on it
[19:50:00] <natefoo> as i don't have a windows machine
[19:52:50] <ronny> natefoo: can you upload it to devpi.net, then i can run a devpi test on one of the pytest infrastructure machines
[22:29:48] <Ryan_Lane> there seems to be some weird issue between versions of pip and entrytools... for some reason in newer versions of pip my script isn't finding a module
[22:30:02] <Ryan_Lane> but in older versions the script can properly find the module
[22:30:35] <Ryan_Lane> was there something that changed, and if so, how do I manage my setup.py in a compatible way?
[23:36:33] <Ivo> Ryan_Lane, that sounds possibly like stuff hasn't been properly uninstalled
[23:36:47] <Ivo> and that there are wrong scripts on your $PATH that haven't been removed
[23:36:48] <Ryan_Lane> it's because I'm using pip editable and subdirectory
[23:37:00] <Ryan_Lane> and it works differently between different versions of pip
[23:37:18] <Ryan_Lane> so, I split my packages into confidant-common, confidant-web and confidant-client
[23:37:29] <Ryan_Lane> where web and client are in subdirs and they depend on common
[23:37:30] <Ivo> pip -e in since pretty much forever, on a basic level just means `setup.py develop`