public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Benjamin A. Beasley <code@musicinmybrain.net>
To: git-commits@fedoraproject.org
Subject: [rpms/python-pydantic-core] f45: Allow jiter 0.18
Date: Mon, 26 Oct 2026 10:20:40 GMT [thread overview]
Message-ID: <179301004010.1.10174697323133244945.rpms-python-pydantic-core-fa895a43d826@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/python-pydantic-core
Branch : f45
Commit : fa895a43d826ebf52455ec088c8ae1fb41256990
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date : 2026-10-26T09:39:56+00:00
Stats : +6/-5 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/python-pydantic-core/c/fa895a43d826ebf52455ec088c8ae1fb41256990?branch=f45
Log:
Allow jiter 0.18
---
diff --git a/pydantic-core-fix-metadata.diff b/pydantic-core-fix-metadata.diff
index af8021c..f6570a6 100644
--- a/pydantic-core-fix-metadata.diff
+++ b/pydantic-core-fix-metadata.diff
@@ -6,7 +6,7 @@ diff -Naur ./pydantic_core-2.46.4-original/Cargo.toml pydantic_core-2.46.4/Cargo
num-traits = "0.2.19"
uuid = "1.23.0"
-jiter = { version = "0.14.0", features = ["python"] }
-+jiter = { version = ">=0.14.0, <0.18.0", features = ["python"] }
++jiter = { version = ">=0.14.0, <0.19.0", features = ["python"] }
hex = "0.4.3"
percent-encoding = "2.3.2"
hashbrown = { version = "0.16", default-features = false, features = ["inline-more"] }
diff --git a/python-pydantic-core.spec b/python-pydantic-core.spec
index 10098bc..8cdad3d 100644
--- a/python-pydantic-core.spec
+++ b/python-pydantic-core.spec
@@ -19,11 +19,12 @@ URL: https://github.com/pydantic/pydantic-core
Source: %{pypi_source pydantic_core}
# Manually created patch for downstream crate metadata changes
-# * Allow jiter 0.15 through 0.17. API changes from 0.14 to 0.17 are purely
+# * Allow jiter 0.15 through 0.18. API changes from 0.14 to 0.17 are purely
# additive, plus switching to PyO3 0.29, which we are also doing here, so
-# this is compatible. Downstream-only because jiter is developed by the
-# Pydantic people, and we can reasonably assume that they will update in due
-# course without prompting from us.
+# this is compatible. 0.18 switches to PyO3 0.30, but we patched it to
+# maintain 0.29 support for now. Downstream-only because jiter is developed
+# by the Pydantic people, and we can reasonably assume that they will update
+# in due course without prompting from us.
Patch: pydantic-core-fix-metadata.diff
# Upstream thinks it's a good idea to rely on exact formatting of error messages in other projects. Meh.
# See the commit message in the patch for more info.
reply other threads:[~2026-10-26 10:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=179301004010.1.10174697323133244945.rpms-python-pydantic-core-fa895a43d826@fedoraproject.org \
--to=code@musicinmybrain.net \
--cc=git-commits@fedoraproject.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