PMXBOT Log file Viewer

Help | Karma | Search:

#pypa logs for Saturday the 5th of May, 2018

(Back to #pypa overview) (Back to channel listing) (Animate logs)
[02:57:47] <Callek> Is there a way to do basically `pip search` or some similar functionality with checking against a different python version than I'm running, and/or displaying what python versions are available for which package versions
[02:57:57] <Callek> e.g. a way to inspect with `python_requires`
[03:06:06] <njs> Callek: I think the way to do that would be to go to pypi.org's search page, and then somehow filter by required python version.... or possibly by filing an issue on the pypa/warehouse repo asking them to add that as a filter option if it's not there yet :-)
[03:07:50] <Callek> njs: in my case, it looks like using website I see "3.5" and "3.6" as options, but I have in my deployment 3.5.2 and some packages depend on 3.5.3+ so being able to prevent package updates that use 3.5.3+ until I update my deployment would be great
[03:08:27] <Callek> (I also have 3.5.2 locally, but I try to dev/work with 3.6.x locally in my 90% of cases, relying on tox to use 3.5.2 when needed)
[03:10:05] <njs> huh, who depends on 3.5.3+? that's very unusual
[03:12:08] <Callek> njs: aiohttp for example
[03:12:11] <Callek> yarl for another
[03:12:20] <njs> huh, odd
[03:12:39] <njs> sorry, that's not helpful, I'm just intrigued
[03:12:41] <Callek> yarl needs at least 3.5.2 but since they use aiohttp they set setup_requires to 3.5.3+
[03:12:45] <Callek> understood
[03:13:17] <Callek> yarls case was because of https://github.com/aio-libs/yarl/issues/189 (I was curious too)
[03:14:22] <njs> ahh
[03:14:48] <njs> the main one I've run into is the change in __aiter__ semantics, but that would only explain async libraries insisting on 3.5.2+
[03:16:09] <Callek> >=3.5.3 specifically
[03:16:11] <Callek> but yea
[03:16:26] <Callek> anyway, off for the night thanks for the attempted help
[03:17:51] <njs> no problem :-)
[03:18:15] <njs> you might file a bug asking for more granular python versions in the search -- it's possible that they, like me, didn't realize that pakcages actually cared about micro versions like that