Debian Package Tracker
Register | Log in
Subscribe

python3.14

Interactive high-level object-oriented language (version 3.14)

Choose email to subscribe with

general
  • source: python3.14 (main)
  • version: 3.14.3-5
  • maintainer: Matthias Klose (DMD)
  • uploaders: Stefano Rivera [DMD]
  • arch: all any
  • std-ver: 4.7.3
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • testing: 3.14.3-3
  • unstable: 3.14.3-5
versioned links
  • 3.14.3-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 3.14.3-5: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • idle-python3.14
  • libpython3.14
  • libpython3.14-dbg
  • libpython3.14-dev
  • libpython3.14-minimal
  • libpython3.14-stdlib
  • libpython3.14-testsuite
  • python3.14 (1 bugs: 0, 0, 1, 0)
  • python3.14-dbg
  • python3.14-dev
  • python3.14-doc
  • python3.14-examples
  • python3.14-full
  • python3.14-gdbm
  • python3.14-minimal
  • python3.14-nopie
  • python3.14-tk
  • python3.14-venv
action needed
Debci reports failed tests high
  • unstable: fail (log)
    The tests ran in 1:29:51
    Last run: 2026-03-29T10:17:07.000Z
    Previous status: unknown

  • testing: pass (log)
    The tests ran in 0:58:48
    Last run: 2026-04-04T03:15:08.000Z
    Previous status: unknown

Created: 2026-03-29 Last update: 2026-04-08 03:32
lintian reports 8 errors and 30 warnings high
Lintian reports 8 errors and 30 warnings about this package. You should make the package lintian clean getting rid of them.
Created: 2026-03-28 Last update: 2026-03-28 21:30
5 security issues in sid high

There are 5 open security issues in sid.

5 important issues:
  • CVE-2026-3479: pkgutil.get_data() did not validate the resource argument as documented, allowing path traversals.
  • CVE-2026-4519: The webbrowser.open() API would accept leading dashes in the URL which could be handled as command line options for certain web browsers. New behavior rejects leading dashes. Users are recommended to sanitize URLs prior to passing to webbrowser.open().
  • CVE-2025-12781: When passing data to the b64decode(), standard_b64decode(), and urlsafe_b64decode() functions in the "base64" module the characters "+/" will always be accepted, regardless of the value of "altchars" parameter, typically used to establish an "alternative base64 alphabet" such as the URL safe alphabet. This behavior matches what is recommended in earlier base64 RFCs, but newer RFCs now recommend either dropping characters outside the specified base64 alphabet or raising an error. The old behavior has the possibility of causing data integrity issues. This behavior can only be insecure if your application uses an alternate base64 alphabet (without "+/"). If your application does not use the "altchars" parameter or the urlsafe_b64decode() function, then your application does not use an alternative base64 alphabet. The attached patches DOES NOT make the base64-decode behavior raise an error, as this would be a change in behavior and break existing programs. Instead, the patch deprecates the behavior which will be replaced with the newly recommended behavior in a future version of Python. Users are recommended to mitigate by verifying user-controlled inputs match the base64 alphabet they are expecting or verify that their application would not be affected if the b64decode() functions accepted "+" or "/" outside of altchars.
  • CVE-2025-15366: The imaplib module, when passed a user-controlled command, can have additional commands injected using newlines. Mitigation rejects commands containing control characters.
  • CVE-2025-15367: The poplib module, when passed a user-controlled command, can have additional commands injected using newlines. Mitigation rejects commands containing control characters.
Created: 2026-01-21 Last update: 2026-03-28 11:30
9 security issues in forky high

There are 9 open security issues in forky.

9 important issues:
  • CVE-2026-2297: The import hook in CPython that handles legacy *.pyc files (SourcelessFileLoader) is incorrectly handled in FileLoader (a base class) and so does not use io.open_code() to read the .pyc files. sys.audit handlers for this audit event therefore do not fire.
  • CVE-2026-3479: pkgutil.get_data() did not validate the resource argument as documented, allowing path traversals.
  • CVE-2026-3644: The fix for CVE-2026-0672, which rejected control characters in http.cookies.Morsel, was incomplete. The Morsel.update(), |= operator, and unpickling paths were not patched, allowing control characters to bypass input validation. Additionally, BaseCookie.js_output() lacked the output validation applied to BaseCookie.output().
  • CVE-2026-4224: When an Expat parser with a registered ElementDeclHandler parses an inline document type definition containing a deeply nested content model a C stack overflow occurs.
  • CVE-2026-4519: The webbrowser.open() API would accept leading dashes in the URL which could be handled as command line options for certain web browsers. New behavior rejects leading dashes. Users are recommended to sanitize URLs prior to passing to webbrowser.open().
  • CVE-2025-12781: When passing data to the b64decode(), standard_b64decode(), and urlsafe_b64decode() functions in the "base64" module the characters "+/" will always be accepted, regardless of the value of "altchars" parameter, typically used to establish an "alternative base64 alphabet" such as the URL safe alphabet. This behavior matches what is recommended in earlier base64 RFCs, but newer RFCs now recommend either dropping characters outside the specified base64 alphabet or raising an error. The old behavior has the possibility of causing data integrity issues. This behavior can only be insecure if your application uses an alternate base64 alphabet (without "+/"). If your application does not use the "altchars" parameter or the urlsafe_b64decode() function, then your application does not use an alternative base64 alphabet. The attached patches DOES NOT make the base64-decode behavior raise an error, as this would be a change in behavior and break existing programs. Instead, the patch deprecates the behavior which will be replaced with the newly recommended behavior in a future version of Python. Users are recommended to mitigate by verifying user-controlled inputs match the base64 alphabet they are expecting or verify that their application would not be affected if the b64decode() functions accepted "+" or "/" outside of altchars.
  • CVE-2025-13462: The "tarfile" module would still apply normalization of AREGTYPE (\x00) blocks to DIRTYPE, even while processing a multi-block member such as GNUTYPE_LONGNAME or GNUTYPE_LONGLINK. This could result in a crafted tar archive being misinterpreted by the tarfile module compared to other implementations.
  • CVE-2025-15366: The imaplib module, when passed a user-controlled command, can have additional commands injected using newlines. Mitigation rejects commands containing control characters.
  • CVE-2025-15367: The poplib module, when passed a user-controlled command, can have additional commands injected using newlines. Mitigation rejects commands containing control characters.
Created: 2026-01-21 Last update: 2026-03-28 11:30
AppStream hints: 1 error and 1 warning for idle-python3.14 high
AppStream found metadata issues for packages:
  • idle-python3.14: 1 error and 1 warning
You should get rid of them to provide more metadata about this software.
Created: 2025-09-19 Last update: 2025-09-19 09:30
The package has not entered testing even though the delay is over normal
The package has not entered testing even though the 5-day delay is over. Check why.
Created: 2026-04-02 Last update: 2026-04-08 04:02
Does not build reproducibly during testing normal
A package building reproducibly enables third parties to verify that the source matches the distributed binaries. It has been identified that this source package produced different results, failed to build or had other issues in a test environment. Please read about how to improve the situation!
Created: 2025-09-25 Last update: 2026-04-08 03:31
Depends on packages which need a new maintainer normal
The packages that python3.14 depends on which need a new maintainer are:
  • db5.3 (#1055356)
    • Depends: libdb5.3t64 libdb5.3t64
  • systemtap (#1114760)
    • Build-Depends: systemtap-sdt-dev
  • db-defaults (#1055344)
    • Build-Depends: libdb-dev
Created: 2025-09-19 Last update: 2026-04-08 01:30
version in VCS is newer than in repository, is it time to upload? normal
vcswatch reports that this package seems to have a new changelog entry (version 3.14.3-6ubuntu1, distribution UNRELEASED) and new commits in its VCS. You should consider whether it's time to make an upload.

Here are the relevant commit messages:
commit cab91c134c67909b201d5cac0887800ef8ca5bf1
Author: Matthias Klose <doko@ubuntu.com>
Date:   Tue Apr 7 05:33:35 2026 +0200

      * Explicitly build-depend on uuid-dev. LP: #2147343.

commit 97c55a4ee2df3c35d39d32b577710ad16e7dce6d
Author: Matthias Klose <doko@ubuntu.com>
Date:   Wed Apr 1 12:38:57 2026 +0200

      * Fix the base_interpreter path in the build-details_*.json files.
      * Don't ship the build-details_*.json file for the debug interpreter,
        because it is installed under the same name as the one for the normal
        build. Still has different contents. PEP 739 deficiency ...

commit 77c5bd7b4fea1ccdfcc75ff9da748065caa7ffda
Author: Matthias Klose <doko@ubuntu.com>
Date:   Wed Apr 1 10:32:17 2026 +0200

      * Also post-process the _sysconfig_vars_*.json files, like done for the
        _sysconfigdata_*.py files.

commit 2f7f34f0b5640d598059093ed444fb51b71ff5e4
Author: Matthias Klose <doko@ubuntu.com>
Date:   Wed Apr 1 09:11:52 2026 +0200

    .gitignore: add one more toplevel dir
Created: 2026-04-01 Last update: 2026-04-07 04:30
10 open merge requests in Salsa normal
There are 10 open merge requests for this package on Salsa. You should consider reviewing and/or merging these merge requests.
Created: 2025-09-18 Last update: 2025-11-22 13:32
Multiarch hinter reports 1 issue(s) low
There are issues with the multiarch metadata for this package.
  • python3.14-examples could be marked Multi-Arch: foreign
Created: 2025-09-19 Last update: 2026-04-07 23:00
debian/patches: 13 patches to forward upstream low

Among the 35 debian patches available in version 3.14.3-5 of the package, we noticed the following issues:

  • 13 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.
Created: 2025-09-19 Last update: 2026-03-28 12:31
Standards version of the package is outdated. wishlist
The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.4 instead of 4.7.3).
Created: 2026-03-31 Last update: 2026-03-31 15:01
testing migrations
  • This package will soon be part of the auto-openssl transition. You might want to ensure that your package is ready for it. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug.
  • excuses:
    • Migration status for python3.14 (3.14.3-3 to 3.14.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
    • Issues preventing migration:
    • ∙ ∙ Autopkgtest for calibre/9.6.0+ds+~0.10.5-5: amd64: Pass ♻ (reference ♻), arm64: Pass ♻ (reference ♻), i386: Pass ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
    • ∙ ∙ Autopkgtest for python3.14/3.14.3-5: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • ∙ ∙ Missing build on riscv64
    • ∙ ∙ Autopkgtest deferred on riscv64: missing arch:riscv64 build
    • ∙ ∙ Lintian check waiting for test results on riscv64 - info
    • Additional info (not blocking):
    • ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python3.14.html
    • ∙ ∙ Not reproduced on amd64 (not a regression): libpython3.14-dev, libpython3.14-minimal, libpython3.14-stdlib, python3.14-dbg, python3.14-dev, python3.14-doc, python3.14-minimal, python3.14-nopie
    • ∙ ∙ Reproducibility check waiting for results on arm64
    • ∙ ∙ Not reproduced on armhf (not a regression): libpython3.14-dev, libpython3.14-minimal, libpython3.14-stdlib, python3.14-dbg, python3.14-dev, python3.14-doc, python3.14-minimal, python3.14-nopie
    • ∙ ∙ Not reproduced on i386 (not a regression): libpython3.14-dev, libpython3.14-minimal, libpython3.14-stdlib, python3.14-dbg, python3.14-dev, python3.14-doc, python3.14-minimal, python3.14-nopie
    • ∙ ∙ Not reproduced on ppc64el (not a regression): libpython3.14-dev, libpython3.14-minimal, libpython3.14-stdlib, python3.14-dbg, python3.14-dev, python3.14-doc, python3.14-minimal, python3.14-nopie
    • ∙ ∙ 11 days old (needed 5 days)
    • Not considered
news
[rss feed]
  • [2026-04-08] Accepted python3.14 3.14.4-1 (source) into unstable (Matthias Klose)
  • [2026-03-28] Accepted python3.14 3.14.3-5 (source) into unstable (Matthias Klose)
  • [2026-03-27] Accepted python3.14 3.14.3-4 (source) into unstable (Matthias Klose)
  • [2026-03-26] python3.14 3.14.3-3 MIGRATED to testing (Debian testing watch)
  • [2026-03-21] Accepted python3.14 3.14.3-3 (source) into unstable (Matthias Klose)
  • [2026-03-17] python3.14 3.14.3-2 MIGRATED to testing (Debian testing watch)
  • [2026-03-11] Accepted python3.14 3.14.3-2 (source) into unstable (Matthias Klose)
  • [2026-02-11] python3.14 3.14.3-1 MIGRATED to testing (Debian testing watch)
  • [2026-02-04] Accepted python3.14 3.14.3-1 (source) into unstable (Stefano Rivera)
  • [2025-12-12] python3.14 3.14.2-1 MIGRATED to testing (Debian testing watch)
  • [2025-12-06] Accepted python3.14 3.14.2-1 (source) into unstable (Stefano Rivera)
  • [2025-12-06] python3.14 3.14.0-5 MIGRATED to testing (Debian testing watch)
  • [2025-12-01] Accepted python3.14 3.14.0-5 (source) into unstable (Matthias Klose)
  • [2025-10-28] python3.14 3.14.0-4 MIGRATED to testing (Debian testing watch)
  • [2025-10-21] Accepted python3.14 3.14.0-4 (source) into unstable (Stefano Rivera)
  • [2025-10-20] Accepted python3.14 3.14.0-3 (source) into unstable (Stefano Rivera)
  • [2025-10-15] python3.14 3.14.0-2 MIGRATED to testing (Debian testing watch)
  • [2025-10-09] Accepted python3.14 3.14.0-2 (source) into unstable (Matthias Klose)
  • [2025-10-07] Accepted python3.14 3.14.0-1 (source) into unstable (Stefano Rivera)
  • [2025-09-25] python3.14 3.14.0~rc3-1 MIGRATED to testing (Debian testing watch)
  • [2025-09-18] Accepted python3.14 3.14.0~rc3-1 (source) into unstable (Stefano Rivera)
  • [2025-08-21] Accepted python3.14 3.14.0~rc2-1 (source) into experimental (Stefano Rivera)
  • [2025-07-24] Accepted python3.14 3.14.0~rc1-1 (source) into experimental (Stefano Rivera)
  • [2025-07-09] Accepted python3.14 3.14.0~b4-1 (source) into experimental (Stefano Rivera)
  • [2025-06-18] Accepted python3.14 3.14.0~b3-1 (source) into experimental (Stefano Rivera)
  • [2025-05-28] Accepted python3.14 3.14.0~b2-1 (source) into experimental (Stefano Rivera)
  • [2025-05-09] Accepted python3.14 3.14.0~b1-1 (source) into experimental (Stefano Rivera)
  • [2025-05-03] Accepted python3.14 3.14.0~a7-1 (source all amd64) into experimental (Debian FTP Masters) (signed by: Matthias Klose)
bugs [bug history graph]
  • all: 3
  • RC: 0
  • I&N: 2
  • M&W: 1
  • F&P: 0
  • patch: 0
links
  • lintian (8, 30)
  • buildd: logs, reproducibility, cross
  • popcon
  • browse source code
  • edit tags
  • other distros
  • security tracker
  • debian patches
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 3.14.3-5

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing