[06:35:33] <pradyunsg> @deveshkusingh: if you’re looking for something to pick up in pip, here’s a PR that could use updating / revisiting: https://github.com/pypa/pip/pull/7869 :)
[06:39:14] <pradyunsg> gutsytechster: I mean, I hear you, but I’d prefer that we continue pinning to the Python minor version, and stick to newer versions wherever possible. Is there some reason you can’t install Python 3.8?
[06:40:11] <pradyunsg> gutsytechster (and devesh) — if one of you would like to pick up https://github.com/pypa/pip/pull/7869, that’d be great! ^>^
[06:40:27] <pradyunsg> (let’s just ignore how broken my IRC client is at times)
[06:42:00] <gutsytechster> pradyunsg: No specific reason. Just that I think, I should be able to do that irrespective of the specific version,
[06:42:22] <gutsytechster> pradyunsg: it happens with IRC> XD
[07:07:40] <gutsytechster> pradyunsg: I would definitely would like to work on https://github.com/pypa/pip/pull/7869, but how do I keep the changes present in that PR? Will it be like I fetch the PR's branch and checkout from it and then create another PR after resolving conflicts?
[07:20:00] <pradyunsg> gutsytechster: yea, you can do `git fetch origin refs/pull/7869/head && git checkout -b <any-new-branch-name>` to get those changes.
[07:20:13] <pradyunsg> (assuming the remote name for pypa/pip is origin)
[07:22:08] <pradyunsg> It'd probably make sense to break that PR up, to keep it smaller. A PR just adding the helpers would be a good place to start. :)
[07:22:55] <pradyunsg> We can likely updating various call sites (i.e. update the tests) in separate PRs.
[07:48:13] <PSFSlack> <deveshkusingh> There is a also a larger PR https://github.com/pypa/pip/pull/7860 to which #7689 contributes too, which also needs to be resurrected
[07:48:26] <PSFSlack> <deveshkusingh> I can perhaps take a stab at it. cc: pradyunsg
[07:56:10] <PSFSlack> <deveshkusingh> gutsytechster: w.r.t overriding basepython in a lower python virtualenv, I think you can also file an issue with https://github.com/tox-dev/tox/issues to either add that option
[07:56:22] <PSFSlack> <deveshkusingh> Or point you on how to do it in the docs
[07:58:07] <PSFSlack> <deveshkusingh> btw, since I am using the IRC-Slack bridge to conect here, you can use @deveshkusingh to refer to me.
[08:10:27] <pradyunsg> @deveshkusingh: IIUC, you're thinking of picking up https://github.com/pypa/pip/issues/6050? If so, that sounds awesome!
[08:16:23] <pradyunsg> @deveshkusingh: Another thing, that I believe is on your radar: getting rid of the `# type: (*Any, **Any) -> None` style comments from pip's Command subclasses. :)
[08:47:05] <PSFSlack> <deveshkusingh> pradyunsg: Yes getting rid of `# type: (*Any, **Any) -> None` is on my radar, I was aiming to get rid of all mypy commments from commands folder before doing that
[08:47:59] <PSFSlack> <deveshkusingh> I already have an issue filed for getting rid of those, and yes I can tackle https://github.com/pypa/pip/issues/6050 as well.
[10:54:08] <gutsytechster> @deveshkusingh: I guess that'd be really helpful. I'll file an issue there. Thanks
[10:55:23] <PSFSlack> <deveshkusingh> And you can always start using python3.8 for development if this doesn't work out for you
[11:00:42] <gutsytechster> @deveshkusingh: I have, after facing that problem. I updated my python version to 3.8.2. I thought it's better now than later. :)