From: Efraim Flashner <efraim@flashner.co.il>
To: Sharlatan Hellseher <sharlatanus@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Question on python-pydantic update, rust and maturin build tool
Date: Thu, 28 Dec 2023 13:56:45 +0200 [thread overview]
Message-ID: <ZY1ifRuMkEEDUhA9@3900XT> (raw)
In-Reply-To: <CAO+9K5qrg-P3v=NE7DMKPRND36bBwVONhN59HhPK0utVYMvoMA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]
On Tue, Dec 26, 2023 at 12:27:38AM +0000, Sharlatan Hellseher wrote:
> Hi Guix!
>
>
> It might be addressed to rust/python teams.
> https://github.com/pydantic/pydantic-core
>
> During update of some packages from (gnu packages astronomy) I've faced
> with requirement for the fresh version of pydantic which depends on
> pydantic-core built with rust and maturin.
>
> This thread is just conversation opener for the potential strategy to deal
> with similar cases where python projects start using rust with rare but new
> build tool.
We have maturin packaged at 1.1.0 and I believe it is even used to build
a couple of packages. python-rpds-py, which just landed in the repo
today, is probably the best short example of how to use a combination of
cargo and any other build system to build a project that doesn't really
need any phases overridden, just added/replaced.
Is there a specific version of pydantic that you need? I might be able
to put together something either using the crates in the master branch
or a newer version on the rust-team branch.
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-12-28 11:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-26 0:27 Question on python-pydantic update, rust and maturin build tool Sharlatan Hellseher
2023-12-28 11:56 ` Efraim Flashner [this message]
2023-12-28 19:20 ` Sharlatan Hellseher
2023-12-28 20:46 ` Ricardo Wurmus
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=ZY1ifRuMkEEDUhA9@3900XT \
--to=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=sharlatanus@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.