From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Asaf Kahlon <asafka7@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/3] package/python-pydantic-core: new package
Date: Sun, 26 Nov 2023 12:27:25 +0100 [thread overview]
Message-ID: <20231126112725.GS3177259@scaer> (raw)
In-Reply-To: <CADvTj4oC_mtb0EymNkFQ969rPRoaw8L8QVvAV2n--knCYB9=iQ@mail.gmail.com>
James, All,
On 2023-11-25 17:11 -0700, James Hilliard spake thusly:
> On Sat, Nov 25, 2023 at 8:36 AM Yann E. MORIN <yann.morin.1998@free.fr> wrote:
[--SNIP--]
> > So what happens if I apply this patch, which adds pydantic-core, but I
> > do not apply the next one, which bumps pydantic, so we end up in a
> > situation with an old pydantic, with the new core also installed?
> >
> > Do the two conflict, or is it an OK situation (obviously the
> > pydantic-core would be of little use)?
> >
> > If there is a conflict, then we will want to introduce the new package
> > at the same time we do the bump, and that should be explained int he
> > commit log.
> >
> > If there is no conflict, then just say, we can ammend the commit log
> > accordignly.
>
> There's no conflict since pydantic-core is a new package with no reverse
> dependencies.
It is not just about reverse dependencies. Assuming we just apply the
pydantic-core new package, and keep the old pydantic (e.g we have to
revert the bump later for various reasons), what happens at build time
or at runtime, if the user enables pydantic-core and pydantic (the old)?
If that makes pydantic-old fail to build or run, that is what we care
about.
[--SNIP--]
> > Could you please extend the manual to descrbe the additional setup types
> > that are currently supported by Buildroot, please?
> Yeah, so we're pretty close right now to having all our python infrastructure
> migrated to pep517 so I was thinking once we have that then a lot of things
> including the documentation can be significantly simplified as maturin and
> setuptools-rust infrastructure will be pep517 based and we can drop all the
> legacy docs like distutils and the docs related to legacy non-pep517 setuptools.
But none of that is on master, for the release to come, so we would stil
need the manual to be up-to-date for master.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-11-26 11:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 8:10 [Buildroot] [PATCH 1/3] package/python-annotated-types: new package James Hilliard
2023-11-25 8:10 ` [Buildroot] [PATCH 2/3] package/python-pydantic-core: " James Hilliard
2023-11-25 15:36 ` Yann E. MORIN
2023-11-26 0:11 ` James Hilliard
2023-11-26 11:27 ` Yann E. MORIN [this message]
2023-11-26 16:19 ` James Hilliard
2023-11-26 16:39 ` Yann E. MORIN
2023-11-26 16:46 ` James Hilliard
2023-11-26 17:12 ` Yann E. MORIN
2023-11-25 8:10 ` [Buildroot] [PATCH 3/3] package/python-pydantic: bump to version 2.5.2 James Hilliard
2023-11-26 17:12 ` Yann E. MORIN
2023-11-26 17:11 ` [Buildroot] [PATCH 1/3] package/python-annotated-types: new package Yann E. MORIN
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=20231126112725.GS3177259@scaer \
--to=yann.morin.1998@free.fr \
--cc=asafka7@gmail.com \
--cc=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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