python bump

python bump

[Marek Belisko]

Hi,

I'm using poky release thud and would like to bump python3 to 3.8.x. I
took recipe from most recent poky version but I'm hitting issue with
e.g. meson build like:
Log data follows:
| DEBUG: Executing shell function do_configure
| Traceback (most recent call last):
|   File "setup.py", line 25, in <module>
|     from setuptools import setup
| ModuleNotFoundError: No module named 'setuptools'

Are there some other things I need to take care when want to bump python3?

Thanks and BR,

marek

-- 
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com

Re: [yocto] python bump

[Alexander Kanavin]

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

You should rather move to a yocto release that has the needed python,
backporting major pieces like that is difficult to impossible.

Alex

On Tue, 10 Nov 2020 at 19:45, Marek Belisko <marek.belisko@gmail.com> wrote:

> Hi,
>
> I'm using poky release thud and would like to bump python3 to 3.8.x. I
> took recipe from most recent poky version but I'm hitting issue with
> e.g. meson build like:
> Log data follows:
> | DEBUG: Executing shell function do_configure
> | Traceback (most recent call last):
> |   File "setup.py", line 25, in <module>
> |     from setuptools import setup
> | ModuleNotFoundError: No module named 'setuptools'
>
> Are there some other things I need to take care when want to bump python3?
>
> Thanks and BR,
>
> marek
>
> --
> as simple and primitive as possible
> -------------------------------------------------
> Marek Belisko - OPEN-NANDRA
> Freelance Developer
>
> Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
> Tel: +421 915 052 184
> skype: marekwhite
> twitter: #opennandra
> web: http://open-nandra.com
>
> 
>
>

[-- Attachment #2: Type: text/html, Size: 1588 bytes --]

Re: [yocto] python bump

[Mikko Rapeli]

Hi,

On Tue, Nov 10, 2020 at 07:44:39PM +0100, Marek Belisko wrote:
> Hi,
> 
> I'm using poky release thud and would like to bump python3 to 3.8.x. I
> took recipe from most recent poky version but I'm hitting issue with
> e.g. meson build like:
> Log data follows:
> | DEBUG: Executing shell function do_configure
> | Traceback (most recent call last):
> |   File "setup.py", line 25, in <module>
> |     from setuptools import setup
> | ModuleNotFoundError: No module named 'setuptools'
> 
> Are there some other things I need to take care when want to bump python3?

When backporting changes, I find it better to cherry-pick the changes for e.g.
python3 update from master to the old branch that I have to use. In my case I can
not update anything which breaks ABIs on target images but can update all
development tools like python3. Often fixes and/or updates to components which
fail to build are also easy to find from master and cherry-pick, especially if you
don't need to build all recipes from poky but only a certain subset. Over
time this will make your local branch look horrible though, but at least
merges from stable branches will in most cases work, if they are still alive.

But like Alex said, using 3.1 dunfell LTS or 3.2 gatesgarth would be better.

Hope this helps,

-Mikko

Re: [yocto] python bump

[Marek Belisko]

On Wed, Nov 11, 2020 at 8:04 AM <Mikko.Rapeli@bmw.de> wrote:
>
> Hi,
>
> On Tue, Nov 10, 2020 at 07:44:39PM +0100, Marek Belisko wrote:
> > Hi,
> >
> > I'm using poky release thud and would like to bump python3 to 3.8.x. I
> > took recipe from most recent poky version but I'm hitting issue with
> > e.g. meson build like:
> > Log data follows:
> > | DEBUG: Executing shell function do_configure
> > | Traceback (most recent call last):
> > |   File "setup.py", line 25, in <module>
> > |     from setuptools import setup
> > | ModuleNotFoundError: No module named 'setuptools'
> >
> > Are there some other things I need to take care when want to bump python3?
>
> When backporting changes, I find it better to cherry-pick the changes for e.g.
> python3 update from master to the old branch that I have to use. In my case I can
> not update anything which breaks ABIs on target images but can update all
> development tools like python3. Often fixes and/or updates to components which
> fail to build are also easy to find from master and cherry-pick, especially if you
> don't need to build all recipes from poky but only a certain subset. Over
> time this will make your local branch look horrible though, but at least
> merges from stable branches will in most cases work, if they are still alive.
Thanks for sharing. But I'm using official poky release from git so I
cannot cherry pick changes.
Or you have clone of poky repo and add changes on top from newest versions?
>
> But like Alex said, using 3.1 dunfell LTS or 3.2 gatesgarth would be better.
Yes but it's not an option for me to do it now ;).
>
> Hope this helps,
>
> -Mikko

Thanks,

Marek

Re: [yocto] python bump

[Martin Jansa]

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

If you don't really need 3.8 and 3.7.5 from warrior would be good enough
for you, then backporting it to thud was relatively straightforward as
implemented in:
https://github.com/ros/meta-ros/commits/thud/meta-ros-backports-warrior
and as it's in a separate layer it doesn't make your main distro layer more
ugly or difficult to maintain (just drop backports layers when upgrading to
newer release instead of trying to find out all backported bits and pieces
across a whole set of layers).

But even this "small" upgrade from 3.6 to 3.7 introduces ABI change as
shown in:
https://github.com/ros/meta-ros/commit/b8efe1dfcfce63135d846df0106085f83aeaa790
so it's better to upgrade completely to a new release if possible at all.

On Tue, Nov 10, 2020 at 7:45 PM Marek Belisko <marek.belisko@gmail.com>
wrote:

> Hi,
>
> I'm using poky release thud and would like to bump python3 to 3.8.x. I
> took recipe from most recent poky version but I'm hitting issue with
> e.g. meson build like:
> Log data follows:
> | DEBUG: Executing shell function do_configure
> | Traceback (most recent call last):
> |   File "setup.py", line 25, in <module>
> |     from setuptools import setup
> | ModuleNotFoundError: No module named 'setuptools'
>
> Are there some other things I need to take care when want to bump python3?
>
> Thanks and BR,
>
> marek
>
> --
> as simple and primitive as possible
> -------------------------------------------------
> Marek Belisko - OPEN-NANDRA
> Freelance Developer
>
> Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
> Tel: +421 915 052 184
> skype: marekwhite
> twitter: #opennandra
> web: http://open-nandra.com
>
> 
>
>

[-- Attachment #2: Type: text/html, Size: 2418 bytes --]

Re: [yocto] python bump

[Mikko Rapeli]

On Wed, Nov 11, 2020 at 08:39:42AM +0100, Belisko Marek wrote:
> On Wed, Nov 11, 2020 at 8:04 AM <Mikko.Rapeli@bmw.de> wrote:
> >
> > Hi,
> >
> > On Tue, Nov 10, 2020 at 07:44:39PM +0100, Marek Belisko wrote:
> > > Hi,
> > >
> > > I'm using poky release thud and would like to bump python3 to 3.8.x. I
> > > took recipe from most recent poky version but I'm hitting issue with
> > > e.g. meson build like:
> > > Log data follows:
> > > | DEBUG: Executing shell function do_configure
> > > | Traceback (most recent call last):
> > > |   File "setup.py", line 25, in <module>
> > > |     from setuptools import setup
> > > | ModuleNotFoundError: No module named 'setuptools'
> > >
> > > Are there some other things I need to take care when want to bump python3?
> >
> > When backporting changes, I find it better to cherry-pick the changes for e.g.
> > python3 update from master to the old branch that I have to use. In my case I can
> > not update anything which breaks ABIs on target images but can update all
> > development tools like python3. Often fixes and/or updates to components which
> > fail to build are also easy to find from master and cherry-pick, especially if you
> > don't need to build all recipes from poky but only a certain subset. Over
> > time this will make your local branch look horrible though, but at least
> > merges from stable branches will in most cases work, if they are still alive.
> Thanks for sharing. But I'm using official poky release from git so I
> cannot cherry pick changes.
> Or you have clone of poky repo and add changes on top from newest versions?

Locally, as developer you always have a local branch where you can cherry-pick
changes. With git submodules and repo tooling, you should use a local or
project specific clone of poky. Or move all updates and changes to your own
layers, but I find this doesn't scale and instead branching in git works
better.

Cheers,

-Mikko