Log file Viewer

[00:16:02] <travis-ci> pypa/pip#18082 (master - fe2075b : Pradyun Gedam): The build passed.

[00:16:02] <travis-ci> Change view : https://github.com/pypa/pip/compare/ccc84a6ab208a6dedf4eec3e297d80e89ceae55f...fe2075b6861cfd4d9a21fcb1328ca8baa89c15f9

[00:16:02] <travis-ci> Build details : https://travis-ci.com/pypa/pip/builds/187505032

[14:11:10] <travis-ci> mijdavis2/pyokta-aws-cli-assume-role#107 (master - c7e22f5 : MJD): The build was broken.

[14:11:10] <travis-ci> Change view : https://github.com/mijdavis2/pyokta-aws-cli-assume-role/compare/f761f159bcc9...c7e22f57f2f7

[14:11:10] <travis-ci> Build details : https://travis-ci.org/mijdavis2/pyokta-aws-cli-assume-role/builds/731947231

[14:19:25] <McSinyx[m]> ^ anyone got any idea why this one is reported here?

[15:13:05] <clarkb> McSinyx[m]: https://github.com/mijdavis2/pyokta-aws-cli-assume-role/blob/master/.travis.yml#L46-L51 I'm guessing that travis' bot will report to any publicly accessible channel if you tell it to

[15:14:19] <McSinyx[m]> that makes sense hmmm

[15:14:38] <McSinyx[m]> why does that repo want to notify to this channel though

[15:21:48] <McSinyx[m]> PR filed: https://github.com/mijdavis2/pyokta-aws-cli-assume-role/pull/13

[15:23:12] <McSinyx[m]> btw is travis status for pip helpful anymore, since we're obligated to view the many other checks on github anyway and that it's always quite sometime after pull?

[15:24:36] <McSinyx[m]> I think I've raised this earlier (among with the proposal to merge this with #pypa for more traffic) but didn't get any affirmative answer

[15:33:26] <fungi> we've recently tried to update our ci system's trusted container images to use python 3.8, and discovered that one of twine's binary dependencies lacks a manylinux1 wheel for 3.8... anybody know what's involved in getting a cp38 manylinux1 x86_64 wheel added for cmarkgfm? there's been an open request for it since january, and also an open pr for roughly a year for adding 3.7 and 3.8 to the metadata

[15:34:21] <fungi> i'm guessing the maintainer for that library has simply taken some well-deserved time off, but i'm happy to try to help if needed

[15:37:13] <McSinyx[m]> building and adding the wheel would not be a technical issue since there are tests for 3.8 already

[15:37:44] <McSinyx[m]> you're best shot would be to ping the maintainer under the issue asking for the wheel

[15:38:15] <fungi> ahh, yeah maybe github will send them a more obvious e-mail notification that way

[15:38:39] <fungi> thanks

[15:40:09] <McSinyx[m]> no problem, although I suppose it can be built from source just fine (since I'm pretty sure that there are peopel including me are using twine for python 3.8)?

[15:40:30] <McSinyx[m]> of course a wheel would be much better

[15:43:22] <fungi> yes, it builds from source with python 3.8, just don't really like the idea of convincing the ci system maintainer team to add a c toolchain and headers to the official docker image for the executor

[15:43:50] <fungi> or of maintaining forked images with gcc et cetera copied in

[15:44:21] <fungi> it's basically a restricted environment to safeguard the pypi credentials

[15:45:29] <McSinyx[m]> thanks for the clarification

[15:45:56] <fungi> we could supply our own wheel of course, but that doesn't help anyone else who's in a similar situation

[15:50:44] <McSinyx[m]> this makes be wonder if the upstream maintainer just disappears (not in this case though)

[15:52:08] <McSinyx[m]> how would one takes up the maintainance of the index or users of the lib would have to manually switch to a new fork dispite the current version could be perfect and all it needs it just builds for newer abi

[15:53:58] <dstufft> cmarkgfm can probably upload an abi3 wheel

[15:54:04] <dstufft> which will solve this problem for 3.9 too

[15:57:04] <fungi> the metadata lists pypa-dev as an author, so it seems like there may have been some intention for team maintenance there

[15:58:19] <fungi> and yeah, i'm really looking forward to seeing abi3 wheels more, that will indeed keep this from being as much of an ongoing issue for libs

[16:01:47] <dstufft> It appears Thea is the maintainer

[17:31:36] <ayharano> Hello there. I would like to contribute to "Changes are coming to pip" video with a subtitle, but I don't know where could I exactly talk about that. Could anyone give me directions about that?

[19:38:59] <ayharano> !logs

[19:38:59] <pmxbot> http://kafka.dcpython.org/channel/pypa-dev

[20:51:49] <graingert> pradyunsg: maybe it's time to release a video showing how to get a free t-shirt by enabling --use-feature=2020-resolver

[21:35:25] <eamanu> Hi, IMO this PR https://github.com/pypa/pip/pull/8910 seems good to be merged.

[21:38:21] <pradyunsg> graingert: ahahaha.

[21:41:30] <pradyunsg> eamanu: thanks for the nudge! ^>^

[21:42:36] <pradyunsg> !logs

[21:42:36] <pmxbot> http://kafka.dcpython.org/channel/pypa-dev

[21:44:50] <graingert> pradyunsg: I'm serious

[21:45:32] <graingert> Why not https://freenode.logbot.info/pypa-dev ?

[21:45:38] <pradyunsg> graingert: who's funding it? DO marketing isn't gonna be happy about my tweets or emails. :)

[21:46:02] <graingert> pradyunsg: funding the t-shirts?

[21:46:15] <pradyunsg> graingert: coz pmxbot is coooool.

[21:46:32] <graingert> Ok

[21:46:37] <pradyunsg> !8

[21:46:37] <pmxbot> As I see it, yes.

[21:46:54] <pradyunsg> ^ seeeee

[21:52:54] <graingert> globbot probably does cool stuff too

[21:53:32] <graingert> pradyunsg "who's funding it" ???

[21:53:38] <graingert> Who's funding what

[21:53:53] <pradyunsg> graingert: yes, the t-shirts.

[21:54:05] <graingert> Azure I presume

[21:56:58] <graingert> pradyunsg: why are DO directing people to their competitors website?

[22:07:33] <graingert> Does anyone have a 32px (CSS px) svg of the platypus?

[22:11:08] <graingert> Looking to contribyte a new https://simpleicons.org/?q=pypi

[22:11:18] <graingert> (for a t-shirt piece)

[22:16:19] <pradyunsg> Might be an idea to ping the discuss.python.org announcement to ask about this -- an SVG format of the logo.

[22:21:34] <graingert> pradyunsg: there's not an svg already?

[22:21:44] <graingert> pradyunsg: it's more like what's the logo?

[22:22:08] <graingert> Is the PyPI logo different from the PyPA logo?

[22:32:05] <pradyunsg> graingert: PyPI has a logo. PyPA -- not so much.

[22:32:44] <graingert> The platypus is the PyPA logo or the pypi logo?

[22:33:12] <pradyunsg> It's the mascot for Python Packaging.

[22:33:19] <graingert> PyPI*

[22:33:27] <pradyunsg> https://discuss.python.org/t/the-packaging-platypus/1939

[22:33:30] <graingert> Oh of course

[22:35:58] <graingert> > use freely to promote Python packaging; ask about using a derivative.

[22:36:15] <graingert> Hmm could do with a machine readable license

[22:37:10] <graingert> pradyunsg: also logos have a purpose exemption to copyright that mascots don't have

[22:49:00] <travis-ci> pypa/pip#18090 (master - d0f80a4 : Pradyun Gedam): The build passed.

[22:49:00] <travis-ci> Change view : https://github.com/pypa/pip/compare/fe2075b6861c...d0f80a44c981

[22:49:00] <travis-ci> Build details : https://travis-ci.com/pypa/pip/builds/187716274

[22:52:22] <cooperlees> I like where Platypus' are from :D