[00:48:48] <kwlzn> hoping to get this landed so we can consume in pex
[00:54:10] <kwlzn> (with the end game of supplanting the custom pex resolver in favor of pip's (One Resolver To Rule Them All), which would effectively net support of a dozen or more experienced python developers from the pex/pants projects toward upstream improvements)
[00:56:24] <sigmavirus24> kwlzn: I think dstufft just needs to give it a once over
[00:56:39] <sigmavirus24> He's quite busy with pypa/warehouse though
[01:00:01] <kwlzn> @dstufft - if you happen to have any cycles to review coming up, it'd be most appreciated. would even be willing to horse trade work with you to carve time, if that helps ;)
[08:45:48] <ronny> xafer: no, im still investigating why exactlx it happens, its not easy
[08:56:24] <ronny> it seems to be a interaction issue between the remote side pytest plugin initialization, the qucker tmpdir init by bruno just made it more apparent
[08:59:58] <xafer> Yup race conditions are usually tricky to debug :-/
[09:00:12] <xafer> Let me know if I can be of any help
[09:29:36] <ronny> xafer: i think i#ll start with a fork of pip that uses xdist for testing on a smaller matrix and against the features branch of pytest
[09:31:23] <xafer> Seems like a good plan, I used https://github.com/pypa/pip/pull/3341 at the time
[09:38:14] <raju> I know basics of python3 and a little python2. And I want to contribute to this project. Any body could help me
[09:57:30] <ronny> raju: i think a good idea might be to pick an issue and trying to figure if you can sove it while getting a bit used to the codebase