Log file Viewer

[00:03:02] <jessamynsmith> carljm: I have a rough first cut of the ideas we talked about up: https://github.com/jessamynsmith/pipwrap

[00:04:37] <carljm> jessamynsmith: nice! i'll try it out

[00:04:51] <jessamynsmith> It doesn't handle -r yt

[00:04:54] <jessamynsmith> *yet0

[00:04:59] <jessamynsmith> obviously it needs to do that to be truly useful

[00:05:20] <jessamynsmith> I will probably make some prs to requirements-parser

[00:05:37] <jessamynsmith> I'm super happy to see that someone has set up an easily-includable lib for parsing reqs

[00:05:45] <carljm> yes, that is nice

[01:53:39] <lealezal> hi, I got those error messages when I try to use pip. It was working like few hours ago on the same machine, don't know what happened :/ https://dpaste.de/ecOE

[02:35:01] <_habnabit> lealezal, did you install requests?

[02:35:25] <lealezal> _habnabit: hi, what do you mean by requests?

[02:35:35] <_habnabit> lealezal, there's a python library called requests

[02:35:44] <lealezal> gonna check this out

[02:35:47] <lealezal> 2 sec

[02:35:53] <_habnabit> lealezal, also, have you run pip as root?

[02:38:28] <lealezal> yes python-requests 2.4.3-6 is installed

[02:38:34] <lealezal> and yes I run with sudo

[02:39:05] <lealezal> I installed it through Debian repo btw

[02:47:00] <_habnabit> lealezal, ok, yeah, never run pip as root

[07:22:17] <wleslie> is there a list somewhere of things we would like to fix in python packaging, but haven't for lack of time and energy?

[09:16:02] <ztane> wleslie: #pypa-dev?

[10:14:03] <apollo13> ronny: around?

[10:14:42] <apollo13> ronny: remember my enum34 import issues? boils down that this: https://github.com/timothycrosley/pies/issues/41 is the root cause -- it should have never tried installing enum34 on python3.4 in the first place :)

[10:19:40] <apollo13> dstufft: time to move install_requires out of setup.py into a static config file *grml*

[10:22:54] <dstufft> apollo13: they could also just use a conditional requirementfor enum34

[10:23:22] <apollo13> dstufft: oh? I do not know about them, mind commenting on the PR?

[10:32:54] <apollo13> interesting, gotta read the peps :)

[10:37:09] <ronny> apollo13: that package is still a mess, enum34 is broken beyond repair

[10:37:46] <apollo13> ronny: that is besides the point :)

[15:38:41] <Charachka> Hello, since I restart my PC, when using "pip" I got those errors messages in terminal... Don't know what went wrong, but for sure it was working fine earlier on the same machine. Any help? https://paste.debian.net/hidden/8254108d/

[15:53:38] <tos9> Charachka: I don't know much about pip internals, but my wild guess, even though I think pip vendors requests, would be that you ran sudo pip on a thing that upgraded or downgraded requests.

[15:54:46] <tos9> Charachka: Yeah, google's first result somewhat suggests that ubuntu / debian are doing wrong things.

[15:54:49] <tos9> Charachka: E.g. https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1306991

[15:56:29] <Charachka> looks like that's my problem tos9, and I actually use Debian

[16:07:52] <Charachka> brb

[16:08:10] <Charachka> tos9: so I fixed it.

[16:09:16] <Charachka> it seems there was 2 version of requests, one being installed in /usr/local/lib (the old version) and the other in /usr/lib (proper version)

[16:09:52] <Charachka> pip was talking to the older version of requests I don't know why, I removed the requests folder from /usr/local/lib and now it's working fine

[17:21:22] <a-tal> >.< damn you git!

[17:24:26] <a-tal> such a waste of time

[18:26:57] <a-tal> k. finaly. after gh auto-closed the PR on me now it's good

[18:37:06] <jessamynsmith> carljm: less awesome: the author of requirements-parser seems not to be accepting prs

[18:37:58] <carljm> jessamynsmith: like, on principle, or "busy and no longer maintaining"?

[18:38:06] <jessamynsmith> carljm: I don't know

[18:38:18] <jessamynsmith> I just see no action, e.g. https://github.com/davidfischer/requirements-parser/issues/20

[18:38:30] <jessamynsmith> oh,s orry, I read the date wrong

[18:38:33] <jessamynsmith> my bad

[18:38:53] <jessamynsmith> the commit is old but the issue is new

[18:38:58] <carljm> looks like they merged a PR on Feb 25

[18:39:06] <jessamynsmith> yeah

[18:39:13] <jessamynsmith> 2 months is a long time in os land

[18:39:38] <jessamynsmith> they merged it, just didn't release it

[18:48:41] <jessamynsmith> carljm: my dilemma is that without it handling -r, I either have to parse files twice, or not use it, or use a custom fork

[18:51:10] <carljm> jessamynsmith: Probably just hasn't gotten around to releasing - I'd start by opening an issue to ask about issuing a release. (if the fix you need is already in, just not released)

[18:51:23] <jessamynsmith> seems reasonable

[19:05:23] <carljm> Timespans in OSS depend quite a bit on the activity of the project and the free time of the maintainer :-)

[19:05:40] <carljm> I have projects that regularly go a year-plus between releases :-)

[19:56:19] <jessamynsmith> carljm: fair enough

[19:56:25] <jessamynsmith> I'll see if that commit fixes it

[21:05:20] <jessamynsmith> carljm: I made it preserve -r lines

[21:05:24] <jessamynsmith> I think this is working fairly well :)

[21:05:27] <jessamynsmith> now to test vcs lines

[23:08:10] <jessamynsmith> carljm: it's live: https://pypi.python.org/pypi/pipwrap

[23:08:20] <jessamynsmith> nedbat: ^^ you had also talked to me about these ideas

[23:08:24] <jessamynsmith> I think this is a much nicer way

[23:16:37] <carljm> jessamynsmith: sweet