Log file Viewer

[01:11:43] <lifeless> dstufft: hey spo

[01:11:46] <lifeless> *so*

[16:09:43] <sigmavirus24> dstufft: hopefully I can help you with debugging 3215 but I'm not certain what the most likely cause is going to be

[16:10:01] <sigmavirus24> will probably try to pry enough information out of them to let lukasa do his usual proxy magic

[16:10:26] <dstufft> sigmavirus24: awesome thanks :)

[16:10:43] <dstufft> There's like 5 things going on in distutils-sig, and I'm not sure I can follow all of them while I'm also trying to buy a house :|

[16:11:56] <sigmavirus24> dstufft: make your life easier, move all discussion to some other platform

[16:12:01] <sigmavirus24> or just ignore all the threads

[16:21:42] <xafer> hello sigmavirus24 , thanks for the #3215 but while you're at it, could you maybe triage/check the 8 other proxy-related pip issues ? https://github.com/pypa/pip/labels/proxy :-P

[16:27:52] <sigmavirus24> proxies are the devil

[16:29:06] <xafer> I believe you

[16:32:48] <sigmavirus24> xafer: seriously though, I've added that label to my todo list

[16:32:56] <sigmavirus24> I kind of wish you could subscribe to a label in GitHb

[16:32:58] <sigmavirus24> *GitHub

[16:35:29] <xafer> I can nag you whenever a new proxy issue arrives on pypa/pip if you want ;)

[16:37:14] <sigmavirus24> proxy label notifications as a service?

[16:37:21] <sigmavirus24> xafer: just @-mention me and Lukasa on them

[16:37:26] <sigmavirus24> That should sufficie

[16:37:28] <sigmavirus24> *suffice

[16:37:35] <xafer> noted :)

[16:44:57] <nlh> Hi folks - just a quick update on the PyPI redesign - we're making good progress. You can view a *mobile friendly* preview at whoisnicoleharris.com/warehouse-ui/

[16:45:46] <dstufft> \o/

[16:45:51] <dstufft> nlh: Oh I forgot to respond to your email

[16:46:38] <nlh> dstufft: :o)

[16:47:20] <dstufft> I browsed the preview on my phone and it felt really nice and seemed to work well

[16:47:21] <nlh> probably wont have a lot of time to spend on it within the next week, but I would like to get some idea from you on how long you think it might take to integrate into the repo

[16:47:42] <dstufft> what format is it in now? is it like hand rolled CSS or is it in scss or something?

[16:47:43] <nlh> and publish it with on the preview site...

[16:48:05] <nlh> no - it's using a static site generator

[16:48:14] <nlh> with SCSS using Bourbon and Neat

[16:48:18] <dstufft> okay

[16:48:20] <nlh> but I need to clean up the code a lot

[16:48:44] <nlh> https://github.com/nlhkabu/warehouse-ui

[16:49:02] <dstufft> well I can either wait until you clean it up, or if you want to jsut clean it up in the main repo I can work on integrating it into the main repo this next week if you're not going to have a ton of time to work on it then

[16:49:12] <dstufft> I can work on integrating it in it's current state*

[16:49:25] <nlh> mmmmmmmmmmmm

[16:49:27] <nlh> not sure

[16:49:52] <nlh> Basically, I need to have some idea of when we can get it working with mock data, so I can schedule some user testing...

[16:50:13] <nlh> but Im quite reluctant to put the current codebase into the main repo...

[16:50:43] <nlh> I kind of feel like if I let that happen, then it might spiral out of control before I get the chance to do a clean up

[16:51:04] <nlh> Mainly I need to create a whole lot of mixins, make the SCSS more DRY

[16:51:10] <nlh> and use more relative units

[16:51:33] <nlh> This will make it *a lot* easier moving forward

[16:52:20] <dstufft> I'm pretty much at the "hurry up and wait" portion of buying a house, so my time is going to be less crazy now. I can't imagine it will take super long for me to transfer it into the main repo since I imagine that will mostly be copy+paste the scss into the right folder, and adapt the html to use the templating language and pull data in from the render context instead of being hardcoded

[16:52:37] <dstufft> so most of the work will probably be in html not in scss/css for me?

[16:52:38] <dstufft> I think

[16:53:03] <nlh> Yeah, I would think so

[16:53:12] <nlh> there is also a little JS that I'll need to go through with you

[16:53:14] <nlh> but not much

[16:55:10] <dstufft> nlh: So I'm willing to dedicate time to it whenever you want it moved over. There's four pages you have done right now, so moving the design over is probably not more than a day or two since you've already done all the hard work, copying it over is just adaption of the html really. I'm also willing to "freeze" the html and scss in the main repo to only be touched by you so nobody starts using the stuff until you're ready for them to be used

[16:55:11] <dstufft> if that's helpful at all

[16:55:19] <dstufft> I'm also willing to wait until you clena it up :)

[16:55:51] <nlh> Yeah - that's really helpful.

[16:55:53] <dstufft> In Dec my time is probably going to be crazy again, Dec 4th is settlement on the house so after that I'll be involved in a lot of house crap

[16:56:19] <nlh> I have told the user testers that I want to start testing at the end of november, so we have a little time

[16:56:29] <dstufft> right now I haven't really been bothering to attempt to style stuff at all on the new things I've been adding, just tossing random html in there to make it functional

[16:56:45] <nlh> so, i think at this stage I'd prefer to wait ;)

[16:56:46] <sigmavirus24> nlh: that looks amazing by the way

[16:56:50] <dstufft> nlh: ok!

[16:56:52] <nlh> thanks sigmavirus24

[16:57:03] <dstufft> nlh: Oh, anothe roption I just thought of

[16:58:05] <dstufft> nlh: we could put the design on a branch in warehouse, not merged into master, and i can setup a warehouse-design.python.org that is backed by the real Python database, and that branch can be a no touch zone for anyone but you as well

[16:58:20] <dstufft> and once you're ready to merge it into master, we can just kill warehosue-design.python.org

[16:58:27] <dstufft> I'm happy with any of the options :)

[16:58:46] <nlh> meaning I can run my user tests with the current SCSS but with real data?

[17:00:17] <nlh> If yes, this sounds ideal

[17:00:52] <dstufft> yup, and it can auto deploy from your branch so any changes you make will show up within a few minutes (not factoring in caching, but you can purge that easily, or we can disable caching on warehouse-design). You won't get any feature work added to master branch in the mean time unless you merge it in (or ask me to merge it in) but yea, real data, real code, current scss

[17:02:04] <nlh> great! Got to go now, but let's do this - let me know by email what you need from me :)

[17:02:17] <dstufft> will do!

[17:02:21] <dstufft> see ya

[17:02:25] <nlh> bye :)

[18:09:27] <ErikRose> dstufft: Hey, congrats on the house!

[18:09:37] <dstufft> ErikRose: thanks :)

[18:09:48] <dstufft> the seller is a pain in the ass, but the home is great I think

[21:29:32] <xafer> I've 5 PRs looking for reviewers that I'm tempted to merge as is :-/

[21:33:16] <xafer> #3173, #3187, #3203, #3211 and #3213 if anyone has time, they are all fairly small (less than 100 lines)

[22:28:10] <dstufft> xafer: I'll try to take a look in a bit

[22:28:42] <xafer> dstufft: thanks :)

[23:01:29] <dstufft> lifeless: I have a migraine so it's possible (probable?) that I'm not fully thinking through the sdist -> wheel case wrt dependencies. I'm not opposed to adding a dist-info command to the interface if we also add an assertion to the spec that, assuming no other state on the machine changes between invocation, the resulting wheel created by bdist_wheel has the same information in it.

[23:04:19] <lifeless> dstufft: yes, that assertion wasn't in my PEP, I'll add it

[23:05:40] <lifeless> dstufft: :( at migraine

[23:05:50] <lifeless> -> breakfast