Bug 2440569 - libpeas fails to build with Python 3.15: ERROR:../tests/libpeas/extension-py.c:54:test_extension_py_instance_refcount: assertion failed (extension->ref_count == 2): (1 == 2)
Summary: libpeas fails to build with Python 3.15: ERROR:../tests/libpeas/extension-py....
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: libpeas
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: PYTHON3.15
TreeView+ depends on / blocked
 
Reported: 2026-02-18 11:45 UTC by Karolina Surma
Modified: 2026-02-18 11:45 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Karolina Surma 2026-02-18 11:45:11 UTC
libpeas fails to build with Python 3.15.0a6.

not ok /extension/python/instance-refcount - ERROR:../tests/libpeas/extension-py.c:54:test_extension_py_instance_refcount: assertion failed (extension->ref_count == 2): (1 == 2)

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/10144364-libpeas/

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

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.


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