Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 1939941 - python-niapy fails to build with Python 3.10: Fatal Python error: Segmentation fault
Summary: python-niapy fails to build with Python 3.10: Fatal Python error: Segmentati...
Alias: None
Product: Fedora
Classification: Fedora
Component: python-niapy
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Iztok Fister Jr.
QA Contact: Fedora Extras Quality Assurance
Depends On: 1939924
Blocks: PYTHON3.10
TreeView+ depends on / blocked
Reported: 2021-03-17 10:33 UTC by Tomáš Hrnčiar
Modified: 2021-04-26 13:21 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-04-26 13:21:14 UTC
Type: Bug

Attachments (Terms of Use)

Description Tomáš Hrnčiar 2021-03-17 10:33:26 UTC
python-niapy fails to build with Python 3.10.0a6.

NiaPy/tests/ .......Fatal Python error: Segmentation fault

Current thread 0x00007fc667a02740 (most recent call first):
<no Python frame>
/var/tmp/rpm-tmp.FwhEN9: line 36:  1101 Segmentation fault      (core dumped) PYTHONPATH=/builddir/build/BUILDROOT/python-niapy-2.0.0-0.1rc13.fc35.x86_64//usr/lib/python3.10/site-packages pytest -ra -k 'not test_Custom_works_fine and not test_griewank_works_fine' -k 'not test_FA_iters_fine and not test_FA_evals_fine'

For the build logs, see:

For all our attempts to build python-niapy with Python 3.10, see:

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.10:

Let us know here if you have any questions.

Python 3.10 will be included in Fedora 35. To make that update smoother, we're building Fedora packages with early pre-releases of Python 3.10.
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.

Note You need to log in before you can comment on or make changes to this bug.