Open Stack

Yeah, we had pyenv conversations with qa and infra folks.
OTOH, I don't think it would be that hard to get that PyPI info.
Anyways, I believe we want to follow one u-c approach as multiple add
the burden on user to use the proper one.

-yoctozepto

pt., 31 sty 2020 o 17:46 Matthew Thode <mthode at mthode.org> napisał(a):
>
> On 20-01-31 10:38:58, Jeremy Stanley wrote:
> > On 2020-01-31 11:17:10 +0100 (+0100), Radosław Piliszek wrote:
> > [...]
> > > The script which generates these proposals needs to learn python
> > > version constraints.
> > [...]
> >
> > It might be possible to crawl the PyPI API and try to apply matching
> > environment markers, but I'm starting to think we just need separate
> > constraints lists per interpreter version instead (and then we can
> > generate them by running the current script from each interpreter).
> > --
> > Jeremy Stanley
>
> I think that would require all those pythons being installed.
> Personally I only have access to 2.7(for now) and 3.6-3.9, so no 3.4 or
> 3.5 locally at least.  Not sure what the availability is for all those
> pythons for gate.  Maybe pyenv can help?  https://github.com/pyenv/pyenv
> --
> Matthew Thode