Your message dated Sun, 12 Oct 2025 14:21:40 +0100
with message-id <[email protected]>
and subject line Re: Bug#1117895: mypy FTBFS with Python 3.14: error:
‘_PyLong_New’ is deprecated
has caused the Debian Bug report #1117895,
regarding mypy FTBFS with Python 3.14: error: ‘_PyLong_New’ is deprecated
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1117895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1117895
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: mypy
Version: 1.18.2-1
Severity: normal
Tags: ftbfs upstream
User: [email protected]
Usertags: python3.14
Python 3.14 is upon us, and we would like to enable it as a supported version
in Debian.
m2crypto fails to build with Python 3.14 as an available version. Graham
Inggs did a test rebuild in Ubuntu and found this build failure. These can be
reproduced in Debian by installing python3-all from experimental (but you may
need to rebuild some dependencies by hand, first).
I think it has been fixed in a new upstream version, but that needs to
be checked. 1.17 claims to support Python 3.14 RC1, and the later
releases have expanded on this.
https://github.com/python/mypy/blob/master/CHANGELOG.md
Build log:
https://launchpadlibrarian.net/823715613/buildlog_ubuntu-questing-amd64.mypy_1.15.0-5build1_BUILDING.txt.gz
Errors:
x86_64-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration
-fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -flto=auto -ffat-lto-objects
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -fcf-protection
-fdebug-prefix-map=/<<PKGBUILDDIR>>=/usr/src/mypy-1.15.0-5build1
-Wno-misleading-indentation -Wdate-time -D_FORTIFY_SOURCE=3 -fPIC
-I/usr/include/python3.14 -c build/mypy/build.c -o
build/temp.linux-x86_64-cpython-314/build/mypy/build.o -O3 -g2 -Werror
-Wno-unused-function -Wno-unused-label -Wno-unreachable-code
-Wno-unused-variable -Wno-unused-command-line-argument
-Wno-unknown-warning-option -Wno-unused-but-set-variable
-Wno-ignored-optimization-argument -Wno-cpp
In file included from build/__native_3204bda914b7f2c6f497.c:4:
/<<PKGBUILDDIR>>/mypyc/lib-rt/int_ops.c: In function ‘CPyTagged_BitwiseLongOp_’:
/<<PKGBUILDDIR>>/mypyc/lib-rt/int_ops.c:320:5: error: ‘_PyLong_New’ is
deprecated [-Werror=deprecated-declarations]
320 | r = _PyLong_New(op == '&' ? asize : bsize);
| ^
In file included from /usr/include/python3.14/Python.h:84,
from /<<PKGBUILDDIR>>/mypyc/lib-rt/init.c:1,
from build/__native_3204bda914b7f2c6f497.c:1:
/usr/include/python3.14/cpython/longintrepr.h:103:47: note: declared here
103 | Py_DEPRECATED(3.14) PyAPI_FUNC(PyLongObject*) _PyLong_New(Py_ssize_t);
| ^~~~~~~~~~~
In file included from /usr/include/python3.14/internal/pycore_backoff.h:12,
from /usr/include/python3.14/internal/pycore_code.h:11,
from /usr/include/python3.14/internal/pycore_call.h:11,
from /<<PKGBUILDDIR>>/mypyc/lib-rt/pythonsupport.h:20,
from /<<PKGBUILDDIR>>/mypyc/lib-rt/CPy.h:12,
from /<<PKGBUILDDIR>>/mypyc/lib-rt/init.c:2:
/<<PKGBUILDDIR>>/mypyc/lib-rt/str_ops.c: In function ‘CPyStr_Build’:
/<<PKGBUILDDIR>>/mypyc/lib-rt/str_ops.c:132:12: error: implicit declaration of
function ‘_PyUnicode_CheckConsistency’; did you mean
‘_PyThreadState_CheckConsistency’? [-Wimplicit-function-declaration]
132 | assert(_PyUnicode_CheckConsistency(res, 1));
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
--- End Message ---
--- Begin Message ---
Source: mypy
Source-Version: 1.18.2-1
Control: found -1 1.15.0-5
Control: notfound -1 1.18.2-1
On Sun, Oct 12, 2025 at 10:51:14AM +0200, Stefano Rivera wrote:
Source: mypy
Version: 1.18.2-1
Severity: normal
Tags: ftbfs upstream
User: [email protected]
Usertags: python3.14
Python 3.14 is upon us, and we would like to enable it as a supported version
in Debian.
m2crypto fails to build with Python 3.14 as an available version. Graham
Inggs did a test rebuild in Ubuntu and found this build failure. These can be
reproduced in Debian by installing python3-all from experimental (but you may
need to rebuild some dependencies by hand, first).
I think it has been fixed in a new upstream version, but that needs to
be checked. 1.17 claims to support Python 3.14 RC1, and the later
releases have expanded on this.
https://github.com/python/mypy/blob/master/CHANGELOG.md
Build log:
https://launchpadlibrarian.net/823715613/buildlog_ubuntu-questing-amd64.mypy_1.15.0-5build1_BUILDING.txt.gz
Ubuntu is a bit behind; the failure was with 1.15.0-5, not 1.18.2-1. I
test-built 1.18.2-1 with Python 3.14 (after first building lxml) and
it's fine.
--
Colin Watson (he/him) [[email protected]]
--- End Message ---
