Re: Python 3.5 EOL; when can require 3.6?

[Eduardo Habkost]

On Wed, Sep 16, 2020 at 02:57:37PM +0100, Daniel P. Berrangé wrote:
> On Wed, Sep 16, 2020 at 02:53:55PM +0100, Alex Bennée wrote:
> > 
> > Thomas Huth <thuth@redhat.com> writes:
> > 
> > > On 16/09/2020 09.53, Philippe Mathieu-Daudé wrote:
> > >> On 9/16/20 9:43 AM, Markus Armbruster wrote:
> > >>> We require Python 3.5.  It will reach its "end of life" at the end of
> > >>> September 2020[*].  Any reason not to require 3.6 for 5.2?  qemu-iotests
> > >>> already does for its Python parts.
> > >>>
> > >>>
> > >>> [*] https://www.python.org/downloads/release/python-3510/
> > >> 
> > >> Not answering your question, but it would help to start a table
> > >> of "oldest package released" versions, with our supported distributions
> > >> as columns and package names as row.
> > >> 
> > >> This way when new distributions are released (and oldest dropped from
> > >> our side) we can add/remove a column and see the oldest version we aim
> > >> to support.
> > >
> > > That's quite a bit of extra work - I think it's enough to look up the
> > > versions on repology instead, e.g.:
> > >
> > > https://repology.org/project/python/versions
> > 
> > Hmm are there any magic runes to limit the list to only the distros we
> > care about?
> 
> No, thats the hard bit. Basically have to search through the list looking
> for the two most recent versions of RHEL, Ubuntu, Debian, Fedora, etc

I'm using the following command to query Repology from the command line:

 $ curl -s 'https://repology.org/api/v1/project/python' |  \
   jq -r 'group_by(.repo) | .[] | "\(.[0].repo): \(map(.version))"' | \
   egrep -i 'fedora|ubuntu|debian|rhel|centos|bsd|suse|sles'

-- 
Eduardo