pmxbot IRC Log Viewer

[06:13:25] <lifeless> dstufft: o/ ?

[11:03:51] <wong2> great!

[11:07:40] <wong2> how can I paticipate into warehouse development?

[11:10:26] <StevenK> dstufft: https://github.com/pypa/packaging/pull/49 is ready for another look

[11:13:04] <dstufft> StevenK: \o/

[11:13:15] <dstufft> StevenK: Can you rebase https://github.com/pypa/packaging/pull/50 ?

[11:13:48] <StevenK> dstufft: Yup, but the push for it will have to wait since I'm writing docs for it

[11:13:56] <dstufft> no problem

[11:14:24] <StevenK> Hopefully I'll finish that off tomorrow.

[11:17:00] <dstufft> sounds great

[11:17:04] <dstufft> good job!

[11:18:39] <xafer> hello, https://github.com/pypa/packaging/pull/51 is a smaller (and odder) beast :)

[11:20:10] <dstufft> wong2: Find an issue that looks interesting and make a PR is the easiest thing to do :)

[11:20:20] <dstufft> xafer: yea, it's on my list today :)

[11:20:28] <dstufft> soon as I wake up enough to wrap my head around the padding logic

[11:20:52] <dstufft> going to cut a pip 8.0 today, so clearing out whatever issues I can before that

[11:21:46] <xafer> :)

[11:22:02] <xafer> https://github.com/pypa/pip/pull/3284 could

[11:24:03] <xafer> https://github.com/pypa/pip/pull/3210 also

[11:26:22] <dstufft> I probably won't get to that one (but if you want to you can!) because I don't feel like fucking with SVN :/

[11:26:49] <StevenK> WCPGW!

[11:28:58] <xafer> Maybe even https://github.com/pypa/pip/pull/3173 ^^

[11:31:10] <xafer> dstufft: any idea on the release timing ?

[11:31:49] <dstufft> xafer: in some hours. Not going to cut a release until I wake up fully :) More specific than that nope.

[11:32:45] <xafer> There are a bunch of old PRs that could be interesting

[11:33:13] <xafer> ok perfect

[11:33:34] <xafer> I'll try to make a small list :)

[12:21:56] <dstufft> look at xafer making me look illiterate ;)

[12:23:49] <xafer> :p

[12:25:04] <ronny> dstufft: i guess he could do the same to me - im pretty sure it would be reasonably easy to fill a whole conference venue of good engineers with bad writing

[12:25:40] <StevenK> Easy? I think you mean 'trivial'

[12:26:48] <ronny> StevenK: there is surrounding logistics

[12:27:21] <xafer> It looked more like typos :)

[12:28:13] <ronny> xafer: typos are als omy worst offence, followed by the usual non native gramar errors

[12:29:19] <xafer> same for me :)

[12:29:27] <xafer> any clue on https://github.com/pytest-dev/pytest/issues/1083 ?

[12:30:22] <ronny> didnt find time to look into it again, due to needing to find a appartment ~500 km away

[12:32:37] <xafer> it looks like a valid reason :)

[12:34:05] <ronny> my fiancee is starting her phd soon, so we move

[12:35:19] <dstufft> ronny: I don't even have it being non-native as an excuse :) I just suck at it D:

[15:11:37] <xafer> dstufft: any opinion on https://github.com/pypa/pip/pull/3321 ? It would indeed give a faster feedback

[15:12:00] <dstufft> I don't have any opinion

[15:28:59] <xafer> But no objection ? I usually forget to run pep8 at 80 on my pull requests so a quick feedback allows me to quickly cancel the build and trim the long lines.

[15:29:12] <dstufft> no objection

[15:51:31] <xafer> dstufft: Can https://github.com/pypa/pip/pull/2168 be closed ?

[16:47:58] <xafer> ^^

[16:48:15] <xafer> I was thinking: we didnt test ?!?

[17:00:00] <dstufft> lol

[17:00:01] <dstufft> whoops

[17:51:03] <lifeless> dstufft: morning

[17:51:11] <dstufft> lifeless: heya

[17:51:17] <lifeless> dstufft: time for my daily request for abstract build system review

[17:52:13] <dstufft> working on getting a pip/virtualenv release out ATM so probably not today

[17:53:40] <lifeless> k

[18:06:21] <Ivoz> dstufft, hope didn't give you too much fun rebasing on top of virtualenv.py

[18:07:38] <Ivoz> bork, should've used rebase

[18:09:46] <Ivoz> dstufft, it would be really nice to get a fix in for https://github.com/pypa/virtualenv/issues/837 before releasing virtualenv, 'cus I think atm the story is virtualenv doesn't work for anyone installing 3.5 off python.org in Windows T_T

[18:10:16] <dstufft> I don't have a Windows box handy right now to test it :|

[18:10:33] <Ivoz> I'm finished for the moment

[18:11:08] <Ivoz> if it's not within your power but you really wanna cut a release today its not the end of the world

[18:12:03] <Ivoz> Maybe we can get a 14.1 out after or similar?

[18:12:22] <dstufft> sure

[18:12:30] <dstufft> cutting virtualenv releases is the easiest of the bunch

[18:15:33] <Ivoz> Should be better than virtualenv 12, anyway

[18:16:15] <Ivoz> http://rst.ninjs.org/?n=c14e92ecd8f959998da3ad2cc0ed32a1&theme=basic is what long_description should look like now

[18:17:20] <dstufft> Ivoz: awesome, might even make sense to cut it down to jsut the latest release's change log too

[18:18:14] <Ivoz> I like the idea of seeing "Oh, that was in the last one.. and this is in the new one!"

[18:18:56] <Ivoz> that's why I did 2

[18:19:44] <dstufft> seems fine to me

[18:20:38] <Ivoz> I'm also thinking I want to get some of the changes in virtual_embedded back into Python proper's venv

[18:20:54] <Ivoz> since when I last looked it looked like venv's scripts were just a C+P of virtualenv's

[18:21:07] <Ivoz> at least for the most part

[18:21:46] <Ivoz> not sure what python's those changes get to go into tho... 3.3,3.4 & 3.5? or some subset, or 3.6 only

[18:22:02] <Wooble> almost certainly 3.6-only.

[18:22:42] <Ivoz> some of the changes are certainly bug-fix in nature

[18:22:44] <Wooble> (maybe 3.5 if they count as strict bugfixes, I guess)

[18:25:25] <Ivoz> night, glhf

[18:59:00] <kostco> hey anyone around?

[19:58:31] <lifeless> ish

[21:40:40] <xafer> dstufft: we could change the default wheel dir at an other time, but I think it would be more consistent if pip wheel and pip download had similar defaults

[21:41:16] <dstufft> xafer: I think changing pip wheel to . is a reasonable change, I just don't (personally) feel like figuring out a deprecation path for it atm :)

[21:42:46] <xafer> The deprecation path I had in mind was a nice changelog and give people the possibility to pass `--wheel-dir=wheelhouse` to have the previous behavior

[22:51:56] <xafer> dstufft: does https://github.com/pypa/pip/pull/3381 seem ok to you ?

[22:52:14] <dstufft> sure

[22:59:13] <dstufft> gonna be cutting a release after I get back from picking up food,

[23:02:09] <xafer> Isn't https://github.com/pypa/pip/pull/3287 needed ?

[23:05:15] <xafer> btw, unit tests now pass on windows (except on 3.5 due to our old pytest), it would be nice to add an appveyor hook on pip with an official pypa account

[23:20:00] <agronholm> what would that do?

[23:21:22] <xafer> same as travis

[23:21:41] <xafer> cf https://ci.appveyor.com/project/xavfernandez/pip

[23:24:30] <agronholm> ah right

[23:26:15] <agronholm> xafer: do you happen to know if travis can be used to build/upload OSX binary wheels?

[23:26:38] <agronholm> but only if the build succeeds as a whole

[23:27:38] <xafer> nope, sorry, I know little of travis and even less of OSX :p

[23:28:57] <agronholm> I'm thinking of having travis automatically upload releases when a tagged build completes but I don't know if that's doable

[23:35:56] <xafer> I think I read something about that but no idea where :-/

[23:37:42] <xafer> Just found https://github.com/MacPython/numpy-wheels that seems to do something related

[23:39:13] <xafer> going to bed, looking forward pip8 tomorrow morning ;)

Log file Viewer

Help | Karma | Search:

#pypa-dev logs for Tuesday the 19th of January, 2016