All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-architecture@lists.openembedded.org
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [Openembedded-architecture] OE-Core python minimum version requirement
Date: Thu, 05 Dec 2019 15:08:09 +1300	[thread overview]
Message-ID: <9058755.I6fkynWszP@shodan> (raw)
In-Reply-To: <216e9c7062d44b98a54b6fd572128266383e83ad.camel@linuxfoundation.org>

On Thursday, 5 December 2019 6:45:03 AM NZDT Richard Purdie wrote:
> I just enabled hashequiv's server in local mode by default in poky.
> 
> This causes an unintended side effect of requiring python 3.5 as the
> minimum version.
> 
> We had thought that the servers would be 'rare' and a 3.5 version
> requirement for that was fine. It turns out a local server is also
> extremely useful.
> 
> The code needed the python 3.5 async support and trying to write it any
> other way is a nightmare, we need that performance for the server.
> 
> At this point I think we just give in and require python 3.5 as a
> minimum. Any objections?

Seems reasonable to me. Theoretically this should allow us to complete the  
subprocess cleanups as well (time permitting of course).

FYI I came across repology.org which tells you the version of various packages 
in each distro, though it's not ideal:

  https://repology.org/project/python/versions

That seems to be missing a few distros, here's another entry:

  https://repology.org/project/python3-defaults/versions

For Ubuntu you have to go back to 14.04 to have 3.4; any others other than 
CentOS 7 that are as old we don't really support.

There is also pkgs.org that I could have sworn used to support comparing 
package versions across distros but it doesn't seem to want to do it anymore. 
Distrowatch also tracks this per distro but only allows side-by-side 
comparisons across versions within a distro or only between two distros. I 
think in this instance we have the information we need though.

Cheers,
Paul


-- 

Paul Eggleton
Intel System Software Products




  parent reply	other threads:[~2019-12-05  2:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04 17:45 OE-Core python minimum version requirement Richard Purdie
2019-12-04 19:07 ` Mark Hatle
2019-12-04 21:07 ` Josef Holzmayr
2019-12-04 23:02 ` Tom Rini
2019-12-04 23:23   ` Adrian Bunk
2019-12-04 23:26     ` Tom Rini
2019-12-05  2:08 ` Paul Eggleton [this message]
2019-12-05  3:10   ` [Openembedded-architecture] " Khem Raj
2019-12-05  6:48   ` Nicolas Dechesne
2019-12-05  8:09     ` Paul Eggleton
2019-12-05 14:37       ` Khem Raj
2019-12-05 16:35         ` Nicolas Dechesne

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9058755.I6fkynWszP@shodan \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-architecture@lists.openembedded.org \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.