On 9/23/26 10:53 AM, Stuart Henderson wrote:
On 2026/09/23 10:40, [email protected] wrote:
On 9/23/26 10:27 AM, Landry Breuil wrote:
Le Wed, Sep 23, 2026 at 10:03:58AM +0200, [email protected] a écrit :
Hello,
Here is an update to devel/py-pydantic 2.13.5
It must be updated at the same time as devel/py-pydantic-core
which will follow.
i'll play the devil's advocate, but was this at least tested/checked
with other consumers than net/synapse ? pydantic tends to be fragile
iirc..
Yes, my whole update batch was tested against all consumers (at least the
compile and install part).
typically it's runtime where problems are more likely to be seen with
Python ports.
20260923 0905 [ L] 1905 [update] devel/py-pydantic-core 2.46.5 renaud@ope
20260923 0907 [ L] 1906 [update] devel/py-typing-extensions 4.16 renaud@ope
20260923 0910 [ L] 1907 [update] devel/py-typing-inspection 0.4. renaud@ope
20260923 0903 [ L] 1910 [update] devel/py-pydantic 2.13.5b renaud@ope
I think these could be a can of worms and I'd prefer to wait until
we're done with OPENBSD_8_0_BASE, they're interrelated, and in
particular typing-extensions is quite widely used.
Also they're quite a version jump in some cases, which makes it harder
to identify how disruptive the update is likely to be.
Wouldn't now be a good time to open the can of worms so we can spot
issues and have time to solve them?
