[rpms/python-futurist] noevent: Force use fork rather than forkserver

[rpms/python-futurist] noevent: Force use fork rather than forkserver

[Steve Traylen]

            A new commit has been pushed.

            Repo   : rpms/python-futurist
            Branch : noevent
            Commit : 2c51caf7a291e7cbdedec9ea8d14cd5970343dc4
            Author : Steve Traylen <steve.traylen@cern.ch>
            Date   : 2026-05-18T20:49:42+02:00
            Stats  : +27/-0 in 2 file(s)
            URL    : https://src.fedoraproject.org/rpms/python-futurist/c/2c51caf7a291e7cbdedec9ea8d14cd5970343dc4?branch=noevent

            Log:
            Force use  fork rather than forkserver

- Resolves: rhbz#2466672

This restores the old python method of using fork rather than
forkserver.

On linux fork is not such a bad idea.

Upstream

https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/CIKLAGYX23SQTKOSNAOITEVVR6KTWHNQ/

is working hard to support 3.14 and is aware of the current fork_server
compatabilities.

---
diff --git a/fix-process-pool-executor-fork-context.patch b/fix-process-pool-executor-fork-context.patch
new file mode 100644
index 0000000..b687539
--- /dev/null
+++ b/fix-process-pool-executor-fork-context.patch
@@ -0,0 +1,20 @@
+diff '--color=auto' -uNr futurist-3.3.0.ORIG/futurist/_futures.py futurist-3.3.0/futurist/_futures.py
+--- futurist-3.3.0.ORIG/futurist/_futures.py	2026-05-16 22:40:23.494242008 +0200
++++ futurist-3.3.0/futurist/_futures.py	2026-05-16 22:50:57.594303841 +0200
+@@ -18,6 +18,7 @@
+ import functools
+ import logging
+ import queue
++import multiprocessing
+ import threading
+ import time
+ from typing import Any, ParamSpec, TYPE_CHECKING, TypeVar
+@@ -468,7 +469,7 @@
+             max_workers = _utils.get_optimal_process_count()
+         if max_workers <= 0:
+             raise ValueError("Max workers must be greater than zero")
+-        super().__init__(max_workers=max_workers)
++        super().__init__(max_workers=max_workers, mp_context=multiprocessing.get_context('fork'))
+         self._gatherer = _Gatherer(
+             # Since our submit will use this gatherer we have to reference
+             # the parent submit, bound to this instance (which is what we

diff --git a/python-futurist.spec b/python-futurist.spec
index 06918d3..d5a9714 100644
--- a/python-futurist.spec
+++ b/python-futurist.spec
@@ -13,6 +13,13 @@ Summary:        Useful additions to futures, from the future
 License:        Apache-2.0
 URL:            http://docs.openstack.org/developer/futurist
 Source0:        https://tarballs.openstack.org/%{pypi_name}/%{pypi_name}-%{version}.tar.gz
+
+# Upstream is totally aware that supporting fork_server is important and urgent.
+# Buying time by forcing the use of the old fork makes sense:
+# https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/CIKLAGYX23SQTKOSNAOITEVVR6KTWHNQ/
+# https://bugzilla.redhat.com/show_bug.cgi?id=2466672
+Patch0:         fix-process-pool-executor-fork-context.patch
+
 # Required for tarball sources verification
 %if 0%{?sources_gpg} == 1
 Source101:        https://tarballs.openstack.org/%{pypi_name}/%{pypi_name}-%{version}.tar.gz.asc