Bug 2328711

Summary: qtile fails to build with Python 3.14: _pickle.PicklingError: Can't pickle local object <function TestManager.start.<locals>.run_qtile at 0x7f9c5918fed0>
Product: [Fedora] Fedora Reporter: Karolina Surma <ksurma>
Component: qtileAssignee: Jakub Kadlčík <jkadlcik>
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: alex, fti-bugs, jdulaney, jkadlcik, ksurma, mhroncok
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
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, 2339432, 2339435, 2372210    

Description Karolina Surma 2024-11-25 16:36:14 UTC
qtile fails to build with Python 3.14.0a2.

= 489 failed, 430 passed, 68 skipped, 1 deselected, 8 xfailed, 35 warnings, 2642 errors in 151.99s (0:02:31) =

Example failures:
ERROR test/test_manager.py::test_unmap_noscreen[x11-2-ManagerConfig] - AttributeError: 'NoneType' object has no attribute 'terminate'
ERROR test/test_manager.py::test_unmap_noscreen[wayland-2-BareConfig] - _pickle.PicklingError: Can't pickle local object <function TestManager.start.<locals>.run_qtile at 0x7f9c57415430>
when serializing dict item '_target'
when serializing multiprocessing.context.Process state
when serializing multiprocessing.context.Process object
ERROR test/test_manager.py::test_unmap_noscreen[wayland-2-BareConfig] - AttributeError: 'NoneType' object has no attribute 'terminate'
ERROR test/test_manager.py::test_unmap_noscreen[wayland-2-ManagerConfig] - _pickle.PicklingError: Can't pickle local object <function TestManager.start.<locals>.run_qtile at 0x7f9c57624f60>
when serializing dict item '_target'
when serializing multiprocessing.context.Process state
when serializing multiprocessing.context.Process object
ERROR test/test_manager.py::test_unmap_noscreen[wayland-2-ManagerConfig] - AttributeError: 'NoneType' object has no attribute 'terminate'

According to https://docs.python.org/dev/whatsnew/3.14.html#multiprocessing

The default start method (see Contexts and start methods) changed from fork to forkserver on platforms other than macOS & Windows where it was already spawn. If you require the threading incompatible fork start method you must explicitly request it using a context from multiprocessing.get_context() (preferred) or change the default via multiprocessing.set_start_method(). (Contributed by Gregory P. Smith in gh-84559.)


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/08301832-qtile/

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

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 Aoife Moloney 2025-02-26 13:18:11 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle.
Changing version to 42.

Comment 2 Karolina Surma 2025-06-11 16:06:11 UTC
*** Bug 2372209 has been marked as a duplicate of this bug. ***