OE-Core python minimum version requirement

OE-Core python minimum version requirement

[Richard Purdie]

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?

Cheers,

Richard

Re: OE-Core python minimum version requirement

[Mark Hatle]

Seems reasonable to me as well..

--Mark

> On Dec 4, 2019, at 11:45 AM, Richard Purdie <richard.purdie@linuxfoundation.org> 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?
> 
> Cheers,
> 
> Richard
> 
> -- 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: OE-Core python minimum version requirement

[Josef Holzmayr]

On Wed, Dec 04, 2019 at 05:45:03PM +0000, 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?

A quick check on packages.ubuntu.com says 16.04 is on python 3.5.1,
18.04 is on 3.6.something.

Hence, looks good to me.

Greetz

> 
> Cheers,
> 
> Richard
> 
> -- 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core

-- 
———————————————
Josef Holzmayr
Software Developer Embedded Systems

Tel: +49 8444 9204-48
Fax: +49 8444 9204-50

R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
———————————————
Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
Ust-IdNr: DE 128592548 

_____________________________________________________________
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548

Re: OE-Core python minimum version requirement

[Tom Rini]

[-- Attachment #1: Type: text/plain, Size: 843 bytes --]

On Wed, Dec 04, 2019 at 05:45:03PM +0000, 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?

In having to pick a minimum Python 3 for U-Boot, it was noted that
Debian/Stretch is 3.4 and gets end of long term support in 2022.  3.5
was otherwise fine I believe in the end.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]

Re: OE-Core python minimum version requirement

[Adrian Bunk]

On Wed, Dec 04, 2019 at 06:02:37PM -0500, Tom Rini wrote:
> On Wed, Dec 04, 2019 at 05:45:03PM +0000, 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?
> 
> In having to pick a minimum Python 3 for U-Boot, it was noted that
> Debian/Stretch is 3.4 and gets end of long term support in 2022.  3.5
> was otherwise fine I believe in the end.

Debian 9 (stretch) has 3.5
Debian 8 (jessie) has 3.4

> Tom

cu
Adrian

Re: OE-Core python minimum version requirement

[Tom Rini]

[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]

On Thu, Dec 05, 2019 at 01:23:24AM +0200, Adrian Bunk wrote:
> On Wed, Dec 04, 2019 at 06:02:37PM -0500, Tom Rini wrote:
> > On Wed, Dec 04, 2019 at 05:45:03PM +0000, 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?
> > 
> > In having to pick a minimum Python 3 for U-Boot, it was noted that
> > Debian/Stretch is 3.4 and gets end of long term support in 2022.  3.5
> > was otherwise fine I believe in the end.
> 
> Debian 9 (stretch) has 3.5
> Debian 8 (jessie) has 3.4

Ah, ok, thanks.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]

Re: [Openembedded-architecture] OE-Core python minimum version requirement

[Paul Eggleton]

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

Re: [Openembedded-architecture] OE-Core python minimum version requirement

[Khem Raj]

On Wed, Dec 4, 2019 at 6:08 PM Paul Eggleton
<paul.eggleton@linux.intel.com> wrote:
>
> 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.
>

yeah and we bandaid centos7 anyway. So probably all is fine.

> 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
>
>
> _______________________________________________
> Openembedded-architecture mailing list
> Openembedded-architecture@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-architecture

Re: [Openembedded-architecture] OE-Core python minimum version requirement

[Nicolas Dechesne]

On Thu, Dec 5, 2019 at 3:08 AM Paul Eggleton
<paul.eggleton@linux.intel.com> wrote:
>
> 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

Nice! How do we get OE plugged into that? Have you looked at that?

>
> 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
>
>
> _______________________________________________
> Openembedded-architecture mailing list
> Openembedded-architecture@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-architecture

Re: [Openembedded-architecture] OE-Core python minimum version requirement

[Paul Eggleton]

On Thursday, 5 December 2019 7:48:11 PM NZDT Nicolas Dechesne wrote:
> On Thu, Dec 5, 2019 at 3:08 AM Paul Eggleton
> <paul.eggleton@linux.intel.com> wrote:
> > 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
> 
> Nice! How do we get OE plugged into that? Have you looked at that?

No, I haven't - only discovered it today. I agree we should look into it 
though.

Cheers
Paul

-- 

Paul Eggleton
Intel System Software Products

Re: [Openembedded-architecture] OE-Core python minimum version requirement

[Khem Raj]

On Thu, Dec 5, 2019 at 2:19 AM Paul Eggleton
<paul.eggleton@linux.intel.com> wrote:
>
> On Thursday, 5 December 2019 7:48:11 PM NZDT Nicolas Dechesne wrote:
> > On Thu, Dec 5, 2019 at 3:08 AM Paul Eggleton
> > <paul.eggleton@linux.intel.com> wrote:
> > > 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
> >
> > Nice! How do we get OE plugged into that? Have you looked at that?
>
> No, I haven't - only discovered it today. I agree we should look into it
> though.
>


you need to have binary feeds somewhere.

> Cheers
> Paul
>
> --
>
> Paul Eggleton
> Intel System Software Products
>
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [Openembedded-architecture] OE-Core python minimum version requirement

[Nicolas Dechesne]

On Thu, Dec 5, 2019 at 3:38 PM Khem Raj <raj.khem@gmail.com> wrote:
>
> On Thu, Dec 5, 2019 at 2:19 AM Paul Eggleton
> <paul.eggleton@linux.intel.com> wrote:
> >
> > On Thursday, 5 December 2019 7:48:11 PM NZDT Nicolas Dechesne wrote:
> > > On Thu, Dec 5, 2019 at 3:08 AM Paul Eggleton
> > > <paul.eggleton@linux.intel.com> wrote:
> > > > 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
> > >
> > > Nice! How do we get OE plugged into that? Have you looked at that?
> >
> > No, I haven't - only discovered it today. I agree we should look into it
> > though.
> >
>
>
> you need to have binary feeds somewhere.

I don't think so. I believe it could work straight from the layerindex
JSON API. in fact the 'source' could be:
http://layers.openembedded.org/layerindex/api/recipes/?filter=layerbranch__branch__name:master

and then we need a simple JSON parser that converts 'our' data into
'their' format, such as:
https://github.com/repology/repology-updater/blob/master/repology/parsers/parsers/ravenports.py

If you check their debian config for example, they use debian 'source'
packages for input:
https://github.com/repology/repology-updater/blob/master/repos.d/deb/debian.yaml

>
> > Cheers
> > Paul
> >
> > --
> >
> > Paul Eggleton
> > Intel System Software Products
> >
> >
> > --
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core