Bug 2460595

Summary: python-faker fails to build with Python 3.15: NameError: name 'TestEnUS' is not defined
Product: [Fedora] Fedora Reporter: Karolina Surma <ksurma>
Component: python-fakerAssignee: Juan Orti Alcaine <jorti>
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: jorti, ksurma, mhroncok, mikel
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: 2412434    

Description Karolina Surma 2026-04-22 13:47:32 UTC
python-faker fails to build with Python 3.15.0a8.

==================================== ERRORS ====================================
_________________ ERROR collecting tests/providers/test_geo.py _________________
tests/providers/test_geo.py:10: in <module>
    class TestArDz(TestEnUS):
                   ^^^^^^^^
E   NameError: name 'TestEnUS' is not defined

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

For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.15/fedora-rawhide-x86_64/10344743-python-faker/

For all our attempts to build python-faker with Python 3.15, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.15/package/python-faker/

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.15:
https://copr.fedorainfracloud.org/coprs/g/python/python3.15/

Let us know here if you have any questions.

Python 3.15 is planned to be included in Fedora 45.
To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.15.
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.