Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

build-details.json should be installed to different locations for nondebug/debug builds and have distinct base_interpreter values #131372

Open
Labels
buildThe build process and cross-buildtopic-installationtype-bugAn unexpected behavior, bug, or error
@befeleme

Description

@befeleme

Bug report

Bug description:

In Fedora, we build Python in 4 variants: debug, optimized, freethreading-debug and freethreading. For all of them builds thebase_interpreter value stored in the filebuild-details.json is the same:

  "base_interpreter": "/usr/bin/python3.14",

I suspect it should reflect the build type and contain the applicable suffix(es):d,t,td.
Because of this line, when we run Python's test suite on an installed python3-debug, the test fails, as you can see e.g. here:https://artifacts.dev.testing-farm.io/0ac8ab69-ed5f-4602-9c01-8c13293aa9b6/

test_base_interpreter (test.test_build_details.CPythonBuildDetailsTests.test_base_interpreter) ... FAIL======================================================================FAIL: test_base_interpreter (test.test_build_details.CPythonBuildDetailsTests.test_base_interpreter)----------------------------------------------------------------------Traceback (most recent call last):  File "/usr/lib64/python3.14/test/test_build_details.py", line 124, in test_base_interpreter    self.assertEqual(os.path.realpath(value), os.path.realpath(sys.executable))    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^AssertionError: '/usr/bin/python3.14' != '/usr/bin/python3.14d'- /usr/bin/python3.14+ /usr/bin/python3.14d?                    +

Another issue is that in both cases, the debug and non-debug files are installed to the same location, resulting in a single rewritten file. In case of our sequential build of 4 Pythons, we end up with just two files. Should they be stored in distinct locations for each build instead?

CPython versions tested on:

3.14

Operating systems tested on:

Linux

Linked PRs

Metadata

Metadata

Assignees

No one assigned

    Labels

    buildThe build process and cross-buildtopic-installationtype-bugAn unexpected behavior, bug, or error

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


      [8]ページ先頭

      ©2009-2025 Movatter.jp