From: Leon Anavi <leon.anavi@konsulko.com>
To: Paul Eggleton <bluelightning@bluelightning.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCHv3] python3-manifest.json: Fix re in core
Date: Thu, 20 Apr 2023 13:00:16 +0300 [thread overview]
Message-ID: <8a4872eb-076d-2807-add3-fe7b68de03a8@konsulko.com> (raw)
In-Reply-To: <2427094.jE0xQCEvom@linc>
Hi Paul,
On 20.04.23 г. 7:59 ч., Paul Eggleton wrote:
> Hi Leon
>
> On Friday, 4 November 2022 01:27:55 NZST Leon Anavi wrote:
>> Following the update from 3.10.6 to 3.11.0, the source code of
>> module re for regular expression operations has been moved to
>> Lib/re/. File python3-manifest.json has been modified according
>> to the new path.
>>
>> According to the instructions the new python3-manifest.json
>> version was created by running bitbake python3 -c create_manifest.
>> Because of this it also updated other files and rdepends in it.
> Maybe you're already aware, but just in case not, this patch appears to have
> effectively undone the change you made earlier ("Move urllib to netclient"):
>
> https://git.openembedded.org/openembedded-core/commit/?id=e74ab2c144042b0a9f788b1b15f11b2800e2c7a1
Thank you for pointing this out. Sorry, I have been quite busy for
several months and I didn't have the time to follow up with the upstream
of meta-python recently. I vaguely remember these patches so I am not
sure about the current state of urllib to netclient. I think it still
makes sense to have urllib in netclient.
Best regards, Leon
> Cheers
> Paul
>
>
--
Leon Anavi
Software Engineer
konsulko.com
prev parent reply other threads:[~2023-04-20 10:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 12:27 [PATCHv3] python3-manifest.json: Fix re in core Leon Anavi
2023-04-20 4:59 ` [OE-core] " Paul Eggleton
2023-04-20 10:00 ` Leon Anavi [this message]
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=8a4872eb-076d-2807-add3-fe7b68de03a8@konsulko.com \
--to=leon.anavi@konsulko.com \
--cc=bluelightning@bluelightning.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox