pmxbot IRC Log Viewer

[07:39:47] <Ivo> dstufft: do you not think the changes in https://github.com/pypa/pip/pull/1685/files#diff-35 look stupid?

[11:05:48] <dstufft> Ivo: I think those blocks look stupid regardless

[11:06:00] <dstufft> Ivo: and are a sign of poorly factored code

[18:33:00] <Ivo> dstufft: https://github.com/dstufft/pip/blob/190824b9496435cf6c0accfdad5e1fd8fc114a53/pip/download.py#L451-L453

[18:33:01] <jezdez> peterbe at mozilla has built a useful tool: https://prs.paas.allizom.org/pypa/pip

[18:33:25] <dstufft> Ivo: whoops

[18:34:03] <dstufft> jezdez: neat

[18:34:07] <qwcode> jezdez, snazzy

[18:34:35] <dstufft> I wish github showed people without write access if the PR is mergeable or not

[18:34:40] <Ivo> dstufft: I swear I have to reread every sentence I write to include the two words my brain decided it was too lazy to include the first time

[18:36:13] <Ivo> jezdez: is that essentialy just a more compact / focused listing?

[18:36:37] <dstufft> I think it only shows mergeable PRs

[18:36:51] <dstufft> and it shows on the overview if the tests have passed

[18:36:51] <jezdez> Ivo: well, it shows more info, who's assigned, what's the last action

[18:36:52] <jezdez> etc

[18:36:59] <jezdez> yep

[18:37:16] <jezdez> we're experimenting with it in a couple of projects to deal with the PR queue issue

[18:37:54] <Ivo> might have to have a go at closing some of pypa's older issues

[18:38:13] <dstufft> Ivo: I do that every so often

[18:38:35] <dstufft> I mostly close the ones I can tell easily can be though

[18:38:40] <dstufft> i don't investigate too much

[18:38:53] <Ivo> was planning the sameish approach

[18:39:32] <dstufft> it'd be nice sometime to actually go hrough and review the pen issues and prs and figure out which ones are still valid / reproducable

[18:39:43] <dstufft> I suspect a lot of them can be closed just because they've been around so long

[18:40:01] <jezdez> yeah :-/

[18:40:10] <jezdez> do we still have issues from bitbucket?

[18:40:21] <jezdez> I mean those that we migrated?

[18:40:38] <Ivo> 'have less than 100 open issues' might be a nice target...

[18:41:02] <Ivo> dstufft: yeah I saw you doing that, and I got all excited for you, and then you stopped :)

[18:41:43] <Ivo> Everyone only has so much time in the day tho

[18:43:01] <dstufft> yea

[18:43:06] <dstufft> I should probably do it sometime

[18:43:11] <dstufft> since I get work hours to do it :V

[18:43:20] <jezdez> exactly!

[18:43:22] <jezdez> :D

[18:43:34] <Ivo> hangon....

[18:43:56] <Ivo> This means we can legitimately ask dstufft,

[18:44:07] <Ivo> "What are we even paying you for?"

[18:44:25] <dstufft> well Rackspace is paying me not pypa ;P

[18:44:39] <Ivo> on behalf of rackspace.

[18:44:43] <dstufft> ;)

[18:44:46] <Ivo> >_>

[18:45:01] <jezdez> teehee

[18:45:22] <dstufft> jezdez: yes btw, i'm pretty sure there are still migrated issued open

[18:45:30] <jezdez> nooooooo

[18:45:41] <jezdez> sigh, I wish we wouldn't have done that

[18:46:11] <dstufft> a good chunk of the issues are old enough that the code base doesn't look anything like it did back then

[18:46:20] <jezdez> yeah :-/

[18:46:42] <jezdez> pretty sure many are from the time when pip was still one big-ass pip.py file

[18:47:16] <dstufft> hahaha go to http://php.net/ and type "I hate PHP" (no quotes, case matters) and hit enter

[18:47:43] <jezdez> wtf!

[18:47:59] <dstufft> apparently the PHP folks have a sense of humor

[18:49:23] <Ivo> I dun geddit T_T

[18:50:19] <jezdez> there are a couple of other gimmicks hidden neat

[18:51:27] <Ivo> oh you need to type it fast enough

[18:53:04] <qwcode> Ivo, let's just have the open target be whichever ones are valid : )

[18:55:41] <Ivo> heh, php.net has vim bindings

[18:57:01] <Ivo> qwcode: nah, i think 100 is a nice round number

[18:57:20] <dstufft> lets have the target be zero

[18:57:20] <qwcode> ok, you go dude. 100 it is

[18:58:15] <Ivo> dstufft: that would mean noone is actually using pip!

[19:00:40] <qwcode> the key is to be highly caffeinated prior to closing issues. gives you confidence to close more stuff

[19:04:30] <Ivo> epic finale cinematic music probably helps too

[19:06:44] <Ivo> that's pretty cool

[19:06:55] <Ivo> apparently there are some packages around that end in .tar.tar

[19:13:42] <dstufft> qwcode: I think in general we have a problem of not closing things when we should

[19:13:44] <dstufft> myself included

[19:17:45] <qwcode> dstufft, well, is it that we're failing to close, or failing to look at issues enough to make the confident decision to close

[19:18:07] <dstufft> qwcode: little bit of both I think

[19:21:34] <qwcode> a lot of the issues are "ideas". it's hard to say "no way. closing"

[19:26:02] <dstufft> qwcode: yea

[19:26:15] <dstufft> but i think we should close them if we don't intend to implement them?

[19:27:14] <qwcode> maybe we do @pypa -1, to signal or member to pile on to close. make's it more obvious to close when 2 or more -1

[19:27:30] <qwcode> "signal another member"

[19:27:54] <dstufft> does @pypa work?

[19:28:07] <qwcode> good question. I just see people do it

[19:28:39] <qwcode> or maybe just -1. the core people are pretty much watching everything

[19:28:56] <qwcode> I see everything, just only respond to what I can

[19:29:16] <Ivo> I just chucked a @pypa in a comment then

[19:30:28] <qwcode> went thru normal channels for me

[19:30:39] <qwcode> so not so helpful

[19:44:49] <dstufft> two years ago heh

[19:44:57] <dstufft> I think that was my first PR against pip ever

[20:18:48] <qwcode> Ivo, how about let's close that, and open another issue about the `pip freeze -r` enhancement idea

[20:26:59] <qwcode> net gain 0, but it feels good to close a 3 yr old issue I guess

[20:27:23] <Ivo> net gain slight clarification of the actual issue

[20:28:02] <Ivo> pretty low hanging fruit for a patch as well

[20:31:17] <qwcode> Ivo, sure, it was a net gain. I was being sarcastic

[20:31:45] <Ivo> qwcode: then you need to include an /s, geeez

[20:32:28] <Ivo> I agree on the closing 3 yr old issue sentiment :3

[20:32:33] <qwcode> the "unnamed" thing pains me. there's even an issue tag for that

[20:33:24] <dstufft> http://d.stufft.io/image/35103q2X2D14 did I ever mention how awesome Fastly is

[20:33:59] <Ivo> dstufft: is that "public" information?

[20:34:25] <dstufft> Ivo: it's not officially published anywhere or anything, but i've never been shy about telling people

[20:34:53] <Ivo> that discount percentage is rather delicious

[20:35:09] <dstufft> this doesn't count the SSL cost either

[20:35:45] <dstufft> which is an extra $100/month per regular domain and 275 for the wild card we just asked for

[20:35:47] <Ivo> are there still download counts around?

[20:36:07] <dstufft> what do you mean around? they update on PyPI near instantly

[20:39:18] <Ivo> cryptography cost $330 dollars to distribute this month

[20:39:46] <Ivo> :D

[20:40:02] <dstufft> haha

[20:40:13] <dstufft> that's kind of a neat idea

[20:42:55] <Ivo> hopefully that'll drop by more than 10x with 0.3 :)

[21:03:32] <jezdez> dstufft: amazing stats!

[21:03:46] <dstufft> that's python.org now too FWIW

[21:03:53] <jezdez> gotcha

[21:03:55] <dstufft> well techincally www.python.org

[21:04:02] <dstufft> but python.org redirects

[21:04:20] <dstufft> and we have a 5 year commitment from Rackspace for 5k/month worth of free servers

[21:04:34] <dstufft> so 300k over the next 5 years more or less

[21:07:15] <jezdez> excellent

[21:10:11] <jezdez> dstufft: are you happily using pyenv on your dev machine?

[21:10:23] <dstufft> jezdez: I've had zero problems with it

[21:10:28] <jezdez> been annoyed by homebrew breaking my venvs all the time

[21:10:48] <jezdez> ok, I think I'll rebuild everything tomorrow then

[21:10:58] <jezdez> gonna blame you if I get stuck

[21:11:01] <jezdez> just kidding :)

[21:11:29] <jezdez> I totally don't get why this concept hasn't been picked up by more people though

[21:12:36] <dstufft> I got annoyed when homebrew removed Python 2.6 and Python 3.2

[21:12:45] <dstufft> even from the versions repo

[21:12:50] <dstufft> like I need those versions

[21:13:01] <jezdez> yeah

[21:14:08] <dstufft> the "shim" thing is kind of wierd

[21:14:30] <dstufft> if you install a new script into one of your pyenv pythons you have to run ``pyenv rehash``

[21:14:52] <dstufft> becuase it makes shims in `~/.pyenv/bin/`` that'll call the pip in whatever the activated python is

[21:15:12] <dstufft> (you can set which Python is active by default, or with an env var, or a file in the curdir)

[21:15:30] <dstufft> I hardly ever install stuff into global site packages though, so I don't care that much

[21:21:27] <Ivo> jezdez: how is homebrew breaking stuff?

[21:29:50] <jezdez> Ivo: if you install a new version of python 3, e.g. 3.3.3 or whatever

[21:29:57] <jezdez> the venvs break

[21:30:17] <jezdez> also lots of odd behavior with regard to setuptools/pip

[21:30:50] <Ivo> just when I thought homebrew is what I should recommend to mac people...

[21:31:57] <jezdez> well, it *is* pretty good

[21:32:14] <jezdez> my use of python may not be the most common after all :)

[21:32:31] <jezdez> I'd definitely recommend it to anyone

[21:32:45] <jezdez> and I've used both fink and macports for years

[21:33:09] <Ivo> could always go to the dark side and use conda

[21:33:30] <jezdez> you know, I really should check it out in more detail

[21:33:37] <jezdez> I only glanced at it

[21:34:17] <jezdez> anyways.. time for bed

[21:34:19] <jezdez> later all

[21:36:23] <Ivo> something something know your enemy

[22:00:20] <dstufft> heh

[22:00:33] <dstufft> Fastly favorited/retweeted and I noticed this http://d.stufft.io/image/1q3r3S0v0i2E

[22:01:48] <dstufft> jezdez: FWIW if you upgrade and delete on pyenv it'll break virtualenvs too, but afaik if you leave 3.3.3 there and just add 3.3.5 (for example) it won't break them

[23:27:06] <dstufft> sigh

[23:27:19] <dstufft> I really don't feel like explaining why you can't just throw GPG at a problem

[23:28:41] <qwcode> dstufft, months ago you gist posted your own little resolver solution. still have that?

[23:28:56] <dstufft> qwcode: my dep solver?

[23:29:06] <qwcode> yea, you posted something related to that

[23:29:08] <dstufft> I never finished it, I probably still have it though

[23:31:07] <dstufft> hm

[23:31:11] <dstufft> I'm not seeing it in search

[23:31:13] <qwcode> no worries

[23:31:40] <dstufft> I was going to use a SAT Solver though

[23:31:48] <qwcode> yea

[23:31:56] <dstufft> there's also uh

[23:32:10] <dstufft> https://github.com/enthought/depsolver and another one someone linked on one of the issues

[23:32:14] <dstufft> I haven't looked through them yet

[23:32:23] <qwcode> yea, I was looking thru all the related issues

[23:32:26] <dstufft> I was worried depsolver seemed badly abstracted

[23:33:06] <qwcode> ok, gotta run. I did close 6 issues I think today woo hoo!!

[23:33:39] <dstufft> yay :D

Log file Viewer

Help | Karma | Search:

#pypa-dev logs for Thursday the 27th of March, 2014