Re: [Openembedded-architecture] OE-Core python minimum version requirement
On Thursday, 5 December 2019 7:48:11 PM NZDT Nicolas Dechesne wrote: > On Thu, Dec 5, 2019 at 3:08 AM Paul Eggleton > 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 ___ 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
On Wed, Dec 4, 2019 at 6:08 PM Paul Eggleton 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 ___ 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
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 ___ 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
On 04/12/2019 17:45, 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? None here. For reference, 3.5.0 was released in September 2015 and is in security-fixes only mode. Ross ___ Openembedded-architecture mailing list Openembedded-architecture@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-architecture
[Openembedded-architecture] OE-Core python minimum version requirement
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-architecture mailing list Openembedded-architecture@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-architecture
