Bug 2353126

Summary:	python-aws-sam-translator fails to build with Python 3.14: 77 test failures, 4 error
Product:	[Fedora] Fedora	Reporter:	Karolina Surma <ksurma>
Component:	python-aws-sam-translator	Assignee:	Ben Beasley <code>
Status:	ASSIGNED ---	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	code, ksurma, mhroncok
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2322407

Description Karolina Surma 2025-03-18 09:52:35 UTC

python-aws-sam-translator fails to build with Python 3.14.0a6.

======== 77 failed, 3936 passed, 4 errors, 77 rerun in 91.74s (0:01:31) ========

https://docs.python.org/3.14/whatsnew/3.14.html

For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.14/fedora-rawhide-x86_64/08783354-python-aws-sam-translator/

For all our attempts to build python-aws-sam-translator with Python 3.14, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.14/package/python-aws-sam-translator/

Testing and mass rebuild of packages is happening in copr.
You can follow these instructions to test locally in mock if your package builds with Python 3.14:
https://copr.fedorainfracloud.org/coprs/g/python/python3.14/

Let us know here if you have any questions.

Python 3.14 is planned to be included in Fedora 43.
To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.14.
A build failure prevents us from testing all dependent packages (transitive [Build]Requires),
so if this package is required a lot, it's important for us to get it fixed soon.

We'd appreciate help from the people who know this package best,
but if you don't want to work on this now, let us know so we can try to work around it on our side.

Comment 1 Ben Beasley 2025-03-18 10:41:14 UTC

I see that python-pydantic-core finally built once in https://copr.fedorainfracloud.org/coprs/g/python/python3.14/package/python-pydantic-core (then segfaulted in its tests on the next build), and similarly python-pydantic built once for Python 3.14 and then started failing again.

In this package, see a lot of errors like:

>       raise InvalidDocumentException(self.document_errors)
E       samtranslator.model.exceptions.InvalidDocumentException: [InvalidResourceException('SuperCoolAPI', "Property 'Auth' is invalid.")]

samtranslator/translator/translator.py:247: InvalidDocumentException

I suspect that, even though we got a successful build of Pydantic at some point, the validation issues here *may* still be attributable to Pydantic. It’s hard to be sure, especially because it is not yet possible to "pip install pydantic" in a virtualenv, even with PYO3_USE_ABI3_FORWARD_COMPATIBILITY=1.

Since it’s not blindingly obvious to me what is causing the test failures here, I’m planning to wait to report the issue upstream until a Pydantic appears on PyPI with Python 3.14 support. It’s not really practical for upstream to help fix what they can’t reproduce.

Comment 2 Karolina Surma 2025-03-18 10:51:55 UTC

I see. Waiting may be the best course of action. It wasn't immediately obvious to me this can root from Pydantic which I've got in a half-zombie state at the moment in Copr (it let build some dependents successfully though, so I'm keeping it there for now without reporting any issues that stem from it to avoid noise).