Bug 2245811 - python-pivy fails to build with Python 3.13: error: ‘PyEval_CallObject’ was not declared in this scope; did you mean ‘PyObject_CallObject’?
Summary: python-pivy fails to build with Python 3.13: error: ‘PyEval_CallObject’ was n...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: python-pivy
Version: 40
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Shaw
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 2291841 (view as bug list)
Depends On:
Blocks: PYTHON3.13 F41FTBFS F41FailsToInstall
TreeView+ depends on / blocked
 
Reported: 2023-10-24 08:09 UTC by Karolina Surma
Modified: 2024-06-14 12:49 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-06-14 12:49:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github coin3d pivy issues 107 0 None open Pivy failes to build with Python 3.13 2023-10-25 12:01:35 UTC

Description Karolina Surma 2023-10-24 08:09:39 UTC
python-pivy fails to build with Python 3.13.0a1.

/builddir/build/BUILD/pivy-0.6.8/redhat-linux-build/pivy/gui/soqtPYTHON_wrap.cxx:4964:23: error: ‘PyEval_CallObject’ was not declared in this scope; did you mean ‘PyObject_CallObject’?
 4964 |           if (!(qev = PyEval_CallObject(shiboken_wrapinst_func, arglist))) {
      |                       ^~~~~~~~~~~~~~~~~
      |                       PyObject_CallObject

According to https://docs.python.org/3.13/whatsnew/3.13.html:
Remove PyEval_CallObject(), PyEval_CallObjectWithKeywords(): use PyObject_CallNoArgs() or PyObject_Call() instead.
Warning: PyObject_Call() positional arguments must be a tuple and must not be NULL,
keyword arguments must be a dict or NULL, whereas removed functions checked arguments type and accepted NULL positional and keyword arguments.
To replace PyEval_CallObjectWithKeywords(func, NULL, kwargs) with PyObject_Call(),
pass an empty tuple as positional arguments using PyTuple_New(0).

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

For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.13/fedora-rawhide-x86_64/06546818-python-pivy/

For all our attempts to build python-pivy with Python 3.13, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.13/package/python-pivy/

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

Let us know here if you have any questions.

Python 3.13 is planned to be included in Fedora 41.
To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.13.
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 Richard Shaw 2023-10-25 12:01:36 UTC
Upstream issue submitted but it really doesn't have a true upstream, just someone active with FreeCAD trying to keep it going.

Since FreeCAD was retired from Fedora I'm tempted to let this go as well. I don't think there are any other consumers of Pivy.

Comment 2 Aoife Moloney 2024-02-15 23:01:02 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 40 development cycle.
Changing version to 40.

Comment 3 Karolina Surma 2024-06-12 15:05:36 UTC
*** Bug 2291841 has been marked as a duplicate of this bug. ***


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