Log file Viewer

[20:53:49] <dstufft> jaraco: ping

[21:29:32] <buck11> this is pip's profile when installing 172 packages from a wheelhouse, with --no-index http://imgh.us/pipinstall-noindex.svg

[21:29:49] <buck11> you can see it spends 2/3 of the time mucking with strings, and 1/3 actually installing

[21:30:33] <buck11> total time is 90s. would be nice if it were 30s instead

[21:33:03] <xafer> nice :)

[21:33:43] <buck11> i'd file a ticket, but i dont have a concrete suggestion :(

[21:33:53] <buck11> also it's impossible to regression test this kind of thing

[21:34:02] <buck11> afaik

[21:34:24] <buck11> self.assert_not_slow_like_before()

[21:34:44] <dstufft> eh

[21:34:55] <dstufft> you can do performance testing

[21:35:06] <buck11> me ?

[21:35:15] <buck11> dstufft: i haven't seen anyone do it

[21:35:25] <dstufft> I think pypy does it

[21:35:26] <buck11> have you?

[21:35:48] <buck11> ah sure they invented a whole data aggregation site for it

[21:36:06] <buck11> i think that's what you need really, but seems out of scope

[21:36:26] <buck11> you being the rhetorical person writing performance assertions

[21:37:19] <buck11> dstufft: do you or anyone else know an obvious way to reduce the calls to sort_path or _link_package_versions?

[21:37:20] <buck11> http://imgh.us/pipinstall-noindex.svg

[21:37:47] <dstufft> not off the top of my head

[21:38:07] <buck11> dstufft: is it worth ticketting?

[21:39:22] <dstufft> buck11: wouldn't hurt I guess, I'm not sure it'll get much traction right now, but it won't hurt

[21:40:54] <buck11> seems like more than a couple bugs boil down to untangling the hairball that is find_requirements

[21:41:02] <dstufft> yes

[21:41:07] <dstufft> that's on my list :/

[21:41:13] <dstufft> a big refactor of that

[21:41:15] <buck11> yay

[21:42:17] <buck11> dstufft: is your thinking still the same on that? a bunch of little single-purpose finders, and a meta-finder?

[21:42:26] <dstufft> yea

[21:42:43] <dstufft> each finder implementing a certain protocol

[21:43:00] <dstufft> a find links finder, a simple API finder, in the future a warehouse api finder once I get around to do that

[21:58:06] <dstufft> jaraco: fwiw whenever you're around, I'm wondering what I need to do to work on the PEP 440 stuff for setuptools more, I know you merged the PR but were keeping it on another branch or something?

[21:59:06] <jaraco> dstufft: it's in the same (git) branch. "use-packaging" maybe? It hasn't been merged with master, so you can continue to make pull requests against that branch.

[21:59:17] <jaraco> You can merge master into that branch if you like.

[21:59:27] <dstufft> ah

[21:59:36] <dstufft> I missed the fact it was on github too

[21:59:41] <dstufft> I was looking at bitbucket and getting confused

[21:59:50] <dstufft> awesome

[21:59:55] <jaraco> Bitbucket/mercurial represent those branches as bookmrks.

[22:00:05] <dstufft> oh right

[22:00:17] <dstufft> and I think bitbucket doesn't expose that as normal brnaches or something

[22:00:47] <dstufft> jaraco: I'm getting ready to merge in the packaging PR that'll fix legacy specifiers

[22:00:53] <dstufft> I finally ifnished writing tests

[22:01:53] <jaraco> Excellent.