Log file Viewer

[02:12:58] <kingkong> for python 2.7.3 do you advice me to run get-pip.py or something else to install pip on debian wheezy ?

[02:15:28] <kingkong> pip 7.1.2 from /usr/local/lib/python2.7/dist-packages (python 2.7) thats latest pip version for debian wheezy ?

[13:02:51] <ionelmc> mhils: why wouldn't it work?

[13:03:33] <mhils> ionelmc: from my limited testing, you cannot upgrade setuptools in-flight.

[13:03:48] <ionelmc> mhils: what do you mean "in-flight"?

[13:04:13] <ionelmc> kingkong: are you asking about using pip from debian's repo vs pip from pypi?

[13:04:37] <mhils> so, if I install_requires or setup_requires setuptools >=17.1 in setup.py, but the client has setuptools 17.0 installed, it'll fail with some exception.

[13:05:00] <ionelmc> mhils: seems un-necessary

[13:05:11] <mhils> ionelmc: what seems un-necessary?

[13:05:37] <ionelmc> mhils: if user has too old setuptools then it don't get to that part at all, it will fail to parse the envmarkers

[13:06:15] <mhils> yes, that's what I see for very old versions as well.

[13:06:53] <mhils> so, in other words, shipping wheels with env markers won't work for us as long as we support old clients?

[13:08:00] <ionelmc> mhils: tbh i have a package with fancy env markers and i just tell the users to upgrade their setuptools

[13:08:52] <ionelmc> i suspect you have something like this in mind: ':python_version < "3.4"': ['statistics', 'pathlib']

[13:08:59] <mhils> yes.

[13:09:07] <mhils> we have maaaany mitmproxy users sitting on ubuntu 12 etc. I don't really want to answer all their support requests :(

[13:09:17] <ionelmc> canned response :)

[13:09:28] <mhils> heh.

[13:10:00] <ionelmc> "if you can't upgrade setuptools then please wait for ubuntu to package mitmproxy"

[13:10:04] <ionelmc> easy, blame ubuntu

[13:10:06] <ionelmc> :)

[13:10:21] <mhils> ubuntu 12 ships mitmproxy 0.9, current is 0.15

[13:10:32] <mhils> then I get a whole bunch of other bug reports :D

[13:10:46] <mhils> maybe we should try to build Linux binaries using PyInstaller to mitigate the layer 8 issues.

[13:10:50] <ionelmc> it's not your problem in the first place, don't make it be yours

[13:11:41] <mhils> heh

[13:11:44] <ionelmc> for `':python_version < "3.4"': ['statistics', 'pathlib']` there is a way to fix, by using non-universal wheels

[13:11:49] <ionelmc> but that is too much hassle

[13:12:09] <mhils> yes, exactly.

[13:12:15] <ionelmc> hard to justify

[13:12:21] <ionelmc> users will understand

[13:12:57] <mhils> ok, looks like there's no way around it.

[13:13:04] <mhils> more than happy to remove all that cruft O:-)

[13:13:56] <mhils> let's see how precompiled linux binaries work out for the masses, maybe that gives us the best of both worlds.

[13:14:22] <mhils> ionelmc: thx for your input. will redirect all bug reports to you ;-)

[13:14:23] <ionelmc> eg: https://github.com/ionelmc/pytest-benchmark/issues/42

[17:02:05] <dstufft> mhils: wheels don't care about the setuptools version

[17:02:12] <dstufft> wheels are about the *pip* version

[17:02:45] <mhils> dstufft: so, if I build a wheel with environment markers, ... ?

[17:03:15] <dstufft> pretty sure pip has supported < in wheels env markers since pip has supported wheels

[17:03:46] <mhils> so, that means, if I distribute a wheel with env markers, pip will just process it properly?

[17:03:59] <mhils> even if setuptools is outdated?

[17:06:22] <dstufft> yea I think so (you'd want to verify this)

[17:06:31] <dstufft> pip doesn't need setuptools installed at all to install a wheel

[17:06:36] <mhils> nice, I'll play around with it. Thanks! .-9

[17:06:44] <mhils> :-) *

[19:55:52] <kingkong> ionelmc: i dont know which one i should use ? debian's repo is different than pip from pypi ? i want latest pip. i readed on debian repo 1.1 version has security vulnerability if i remember right

[19:56:34] <kingkong> so, i uninstalled it and used another one

[19:57:18] <ionelmc> kingkong: debian have "deb" packages

[19:57:33] <ionelmc> and they repackaged pip, as "python-pip"

[19:58:07] <ionelmc> if you want the latest then don't use the repackaged one, iow - don't install pip with apt-get

[20:01:18] <kingkong> ionelmc: my pip version is latest now? pip 7.1.2 from /usr/local/lib/python2.7/dist-packages (python 2.7)

[20:01:41] <ionelmc> kingkong: mission accomplished :)

[20:02:32] <kingkong> ionelmc: ok thanks. :)