Log file Viewer

[03:11:07] <cnx> pradyunsg, do you even sleep?

[03:11:46] <cnx> IIRC you're in India and you're sleeping pattern doesn't seem really healthy

[03:12:25] <cnx> please everyone take care of yourselves during this tough time

[03:12:49] <cnx> wish you all the bests

[03:33:40] <prometheanfire> sleep is for the weak

[03:33:47] <prometheanfire> also, sleep for the week

[05:16:14] <ronny> it seems i have persisted wrong pip configuration for only build-isolated environments - does anyone know where i would find that configuration (aka wheel building passes in a devpi as index that i cant even use)

[05:16:30] <ronny> normal pip is not affected, only build isolation, i have no idea where the config is

[06:10:42] <cnx> ronny, I think https://github.com/pypa/pip/pull/8096 might be able to list the configs pip uses

[06:11:11] <cnx> prometheanfire, my palms are sweaty, knees weak, arms are heavy

[06:11:30] <cnx> it's saturday by my university still make me study

[06:11:46] <ronny> At first glance that would not tell me why only isolation is affected

[06:13:23] <cnx> please tell me more, I just happen to remember that PR, I have no idea if there are configurations that may be pep517 specific

[06:19:21] <cnx> ronny, could you share the config files' content

[06:20:02] <cnx> not like I have the expertise to investigate, but I'm curious by nature

[06:28:35] <ronny> I have no idea how, i don't know where the bad value is from, all config I am aware of is emptied

[06:30:44] <cnx> do you think it's time to file an issue for it?

[07:24:47] <PSFSlack1> <deveshkusingh> ronny: If you run `pip config list -v` , it should list the potential config files in the verbose output

[10:10:28] <travis-ci> pypa/twine#1409 (master - 8765d14 : Brian Rutledge): The build passed.

[10:10:28] <travis-ci> Change view : https://github.com/pypa/twine/compare/2c30b1e9c793...8765d14d1ae5

[10:10:28] <travis-ci> Build details : https://travis-ci.org/pypa/twine/builds/679353168

[10:14:11] <ronny> PSFSlack1: thats not helping as again this only applies to build isolation and all other files are gone

[13:54:34] <cjc7373> Hi, all. Pip is now on the beta release. Is it true that all the PRs merged these days will be part of the pip 20.1 release?

[14:10:57] <toad_polo> cjc7373: As opposed to what?

[14:19:35] <cjc7373> toad_polo: Sorry I didn't get you. Can you make it clearer?

[14:40:20] <toad_polo> cjc7373: What other release would they be part of?

[14:46:03] <cjc7373> toad_polo: a later major release, for example, 20.2

[15:29:18] <cnx> cjc7373, I don't think pip has multiple-branch model so the answer to your question is yes, pip 20.1 will be the snapshot of master on release day

[15:30:36] <cnx> however from watching discussions I feel that until the release only bug fixes of beta will be prioritized to be merged, to avoid regression right after the release I think

[15:31:08] <cnx> good weekend everyone

[15:50:19] <cjc7373> thank you @cnx, got you from the log

[15:56:34] <prometheanfire> buffer 19

[16:39:42] <pradyunsg> ronny: You mean only the index interaction as-part-of the isolated build is affected?

[18:02:12] <ronny> pradyunsg: correct, its most puzzling, i havent found any pip.ini that could be responsible, im most puzzled

[20:18:48] <sigmavirus24> o/ prometheanfire

[20:58:29] <prometheanfire> sigmavirus24: ltns, how ya doing?