PMXBOT Log file Viewer

Help | Karma | Search:

#pypa-dev logs for Tuesday the 20th of March, 2018

(Back to #pypa-dev overview) (Back to channel listing) (Animate logs)
[16:06:55] <sumanah> *wave* waseem18
[16:07:03] <waseem18> Hi Sumanah
[16:07:22] <waseem18> How are you doing?!
[16:07:48] <sumanah> waseem18: I'm all right! I'm happy Twine 1.11.0 is out. I'm writing a slightly complicated GitHub comment on an old issue - long enough I'm doing it in a text editor and will then paste it in.
[16:07:51] <sumanah> waseem18: you?
[16:08:08] <waseem18> I'm doing good - Started reading PEP 484
[16:08:51] <sumanah> waseem18: cool
[16:10:22] <sumanah> waseem18: if you want to see type annotations on a large Python project, http://github.com/zulip/zulip/ is annotated with mypy-style annotations
[16:11:00] <waseem18> Oh - Thanks. I'll take a look at it
[16:11:43] <sumanah> waseem18: I want to feel more confident making changes to Twine, and I think having automated testing hooked into this static type checking will help me with that. And as Tim Abbott's blog post points out, we can do this kind of type annotation in stages, and get benefits at each stage.
[16:11:59] <sumanah> waseem18: I'd love to hear what's interesting to you about it
[16:13:35] <waseem18> Sure - Haven't yet started on Tim Abbott's article. Possibly I'll put up a blog post from what I learned from PEP 484 and the Tim's article
[16:32:46] <sumanah> comment posted! https://github.com/pypa/warehouse/issues/991#issuecomment-374665356
[16:33:13] <sumanah> waseem18: cool. please ping me if you do publish that blog post.
[16:34:54] <waseem18> Sure :)
[16:36:29] <pf_moore> Lots of "Failed to connect to s3.amazonaws.com port 443: Connection timed out" errors on travis at the moment. Are there known issues? I'm getting a bit fed up of hitting restart, but I'm reluctant to override and merge PRs, even though I know the problems are unrelated :-(
[17:02:42] <sumanah> pf_moore: this is for all the PyPA GitHub projects?
[17:02:47] <sumanah> *wave* pradyunsg
[17:03:05] <pradyunsg> Hi sumanah! :)
[17:07:32] <sumanah> dstufft: hey are you the person who runs the https://twitter.com/ThePyPA Twitter account?
[18:07:38] <pf_moore> sumanah: sorry, popped out. I'm seeing it on pip, wasn't sure about others. Looks like it may have been intermittent, it seems to have stopped.
[18:07:46] <sumanah> good, glad to hear it pf_moore
[18:45:34] <sumanah> Question for di_codes - we said https://github.com/pypa/warehouse/issues/3221 (Set samesite=lax on session cookies) is dependent on an upstream Pyramid bug. Am I right that the upstream bug is https://github.com/Pylons/pyramid/issues/2733 ?
[19:04:16] <di_codes> sumanah: yep
[19:04:38] <sumanah> ok, alex is right, cool
[19:08:51] <di_codes> sumanah: he usually is
[19:09:00] <sumanah> di_codes: :)
[19:41:32] <sumanah> hi alethea
[19:42:34] <alethea> o/
[19:42:48] <alethea> this has been the most fun bug I had to track down today: https://github.com/pypa/readme_renderer/pull/68#issuecomment-374731090
[19:42:54] <sumanah> alethea: if you want a break from the CommonMark/GitHub-Flavored Markdown stuff but still want to do readme_renderer stuff, https://github.com/pypa/readme_renderer/issues/64 would be awesome to have, IMO. People who are using readme_renderer to check whether their setup.py is properly formatted almost certainly assume it's checking for the presence of a long_description
[19:43:31] <sumanah> alethea: I issue you a deerstalker cap in honor of your detective work today :)
[19:43:40] <sumanah> goodness.
[19:45:25] <sumanah> and one more tip alethea in case you didn't already know: you could ask about wheel-building on Windows, or mention your experience with it, on njs's https://mail.python.org/mailman/listinfo/wheel-builders
[19:45:29] <alethea> oo that's a good one
[19:45:38] <alethea> easy to do, but there's no tests for the integration. I'll write those as well.
[19:45:55] <alethea> I got my wheel building woes worked out. :)
[19:45:58] <sumanah> oh good!
[19:46:38] <sumanah> separate meta-note, alethea -- I have been pinging you on stuff & asking for your advice and so on. I actually don't know how much of your Google-paid time you can spend on this stuff and will understand if you say "no, not this week" and so on
[19:50:15] <alethea> Ostensibly 10% of my time.
[19:50:40] <alethea> It's been a bit less than that for a while because I'm in the process of building a new team to own all of our client libraries (across seven languages!)
[19:51:06] <alethea> which is why I haven't been able to do bigger things like re-write the distributing guide.
[19:51:31] <alethea> & I'm pretty good about saying "no". :)
[19:53:05] <sumanah> Oh I wish I'd had a whole team to do what when I was at Wikimedia Foundation. I had a summer intern who audited/inventoried https://www.mediawiki.org/wiki/API:Client_code and improved a few of the key libraries.
[19:55:07] <alethea> Nice.
[19:55:21] <alethea> We have ~30 products in cloud and we support 7 languages, so we have *very* large surface area.
[19:55:26] <sumanah> For sure.
[19:55:51] <dstufft> oh is alethea jon parrot
[19:55:54] <alethea> Hence my tweet. We need to staff up like crazy. At minimum 10 engineers to start.
[19:55:58] <alethea> Yeah. :)
[19:56:27] <alethea> o/ dstufft
[19:56:34] <dstufft> heya :D
[19:57:01] <sumanah> alethea: if you tell me your OS I can recommend an IRC client so you can, like, save logs, set your name, etc
[19:57:23] <alethea> I'm likely gonna grab an IRC Cloud subscription or setup a bouncer on my home cluster.
[19:57:35] <alethea> dealing with webchat for now. :)
[20:14:52] <alethea> sumanah: your wish is granted: https://github.com/pypa/readme_renderer/pull/69
[20:15:35] <alethea> (I'm just really enjoying giving di_codes more stuff to review)
[20:17:14] <di_codes> alethea: it is _always_ appreciated :slightly_smiling_face:
[20:17:43] <alethea> If I ever find an abundance of free time I'll try to find a way to make you regret saying that. :)
[20:18:00] <alethea> lucky for you, the changes of me finding free time are low! :D
[20:18:27] <di_codes> also, i’m willing to bet you googlers don’t use slack but if you did <https://github.com/di/slack-irc-heroku-bridge> might be a good option for an IRC bouncer/bridge (it’s what I use)
[20:18:38] <sumanah> alethea: https://github.com/pypa/python-packaging-user-guide/pull/455 in case you wanna merge
[20:19:20] <alethea> I use slack. Might try that out.
[20:19:32] <alethea> though heroku is frowned upon for obvious reasons.
[20:20:22] <sumanah> (ha)
[20:21:47] <di_codes> probably wouldn’t be hard to get that to run on the GCP free tier as well!
[20:22:23] <alethea> Yeah it's not too hard, though certainly not as easy as Heroku.
[20:22:50] <alethea> We are peanut butter and jealous of Heroku's developer experience, especially their onboarding.
[20:24:27] <di_codes> the amount of setup required for that bridge happily negates all of that :slightly_smiling_face:
[20:24:30] <sumanah> Thank you alethea for your PR!
[20:24:45] <alethea> lol
[20:24:50] <alethea> no problem!
[21:13:47] <alethea> \o/ alright all the hard parts are done for GitHub-flavored Markdown support. Now it's just a series of merges and releases. https://github.com/pypa/packaging-problems/issues/126#issuecomment-374758533
[21:15:34] <sumanah> alethea: yay!
[21:30:49] <di_codes> alethea: nice work! looking forward to reviewing/merging
[23:17:57] <sumanah> Hi dbrecht!
[23:18:16] <sumanah> Sorry, I see you're often in the channel, I just recognized you from the project ratings issue
[23:53:20] <sumanah> MarkMangoba: EWDurbin: di_codes: am working on the weekly report email, FYI