This is marked RFC for exactly that reason :) the purpose is to allow
pre-testing with other layers, and avoid duplication of effort.

Alex

On Sat 17. Sep 2022 at 15.04, Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:

> On Wed, 2022-09-14 at 14:04 +0200, Alexander Kanavin wrote:
> > The semaphore fix has landed and is available from 3.11 onwards:
> >
> https://github.com/python/cpython/commit/1ee0f94d16f150356a4b9b0a39d44ba1d2d5b9fc
> >
> > 3.11 release schedule: https://peps.python.org/pep-0664/
> >
> > Drop 0001-Mitigate-the-race-condition-in-testSockName.patch
> > as it is merged upstream.
> >
> > Signed-off-by: Alexander Kanavin <alex@linutronix.de>
> > ---
> >  meta/classes-recipe/python3-dir.bbclass       |  2 +-
> >  ...ib-termcap-to-linker-flags-to-avoid-.patch |  8 ++--
> >  ...-search-system-for-headers-libraries.patch |  6 +--
> >  ...-use-prefix-value-from-build-configu.patch | 14 +++---
> >  ...e-the-race-condition-in-testSockName.patch | 47 -------------------
> >  ...sts-due-to-load-variability-on-YP-AB.patch | 18 +++----
> >  ...FLAG_REF-always-for-interned-strings.patch | 33 -------------
> >  ...-detection-of-mips-architecture-for-.patch | 33 ++++++++++---
> >  ...fig-append-STAGING_LIBDIR-python-sys.patch |  6 +--
> >  ...asename-to-replace-CC-for-checking-c.patch | 44 ++++++++---------
> >  ...tutils-prefix-is-inside-staging-area.patch | 10 ++--
> >  .../python3/avoid_warning_about_tkinter.patch | 21 ++++-----
> >  .../python/python3/crosspythonpath.patch      | 22 ++++-----
> >  .../python/python3/makerace.patch             | 10 ++--
> >  ...python3_3.10.6.bb => python3_3.11.0rc2.bb} | 13 ++---
> >  15 files changed, 112 insertions(+), 175 deletions(-)
> >  delete mode 100644
> meta/recipes-devtools/python/python3/0001-Mitigate-the-race-condition-in-testSockName.patch
> >  delete mode 100644
> meta/recipes-devtools/python/python3/0001-Use-FLAG_REF-always-for-interned-strings.patch
> >  rename meta/recipes-devtools/python/{python3_3.10.6.bb =>
> python3_3.11.0rc2.bb} (97%)
>
> It is good to have this ready but given the timing of the final release
> compared to ours, and the knock on implications of a python version
> change on other layers, I'm likely to hold this until the next release
> unless there is a pressing reason we need it.
>
> Cheers,
>
> Richard
>