[2/4] python3-build: upgrade 1.5.1 -> 1.6.0

Features:
    - Add --report=PATH to write a machine-readable JSON report of built artifacts; --metadata
      now also accepts .whl files - by @gaborbernat (#198)
    - The srcdir argument now accepts .tar.gz source distributions, extracting and building from
      them - by @gaborbernat (#311)
    - The “Unmet dependencies” error from --no-isolation builds now shows the wanted version,
      found version, and interpreter - by @gaborbernat (#504)
    - Add --sdist-extract-dir to extract the intermediate sdist into a persistent directory,
      enabling compiler cache reuse across rebuilds - by @gaborbernat (#614)
    - Add --env-dir to place the isolated build environment at a fixed path, enabling compiler
      cache reuse across builds - by @gaborbernat (#655)
    - Print a summary of resolved dependency versions (name==version) after installing them in
       isolated builds - by @gaborbernat (#959)
    - On build failure, print a tip pointing to --env-dir and --sdist-extract-dir for debugging and
      link to the “Debug a failed build” how-to - reported by @dimpase, implemented by @gaborbernat (#966)

Bugfixes:
    - Drain verbose subprocess output inline instead of using a ThreadPoolExecutor, which silently
      swallowed logging errors - by @henryiii (#1098)
    - Reject a file passed as --env-dir with a clear error instead of a raw FileExistsError - by @henryiii (#1100)
    - Emit CLI warnings to stderr instead of stdout, so they no longer corrupt --metadata
      JSON output on stdout - by @ymyzk (#1111)
    - Fix the Windows symlink support probe always returning False due to a stale object
      interpolated into the destination path - by @henryiii (#1118)
    - Fix metadata_path’s build-backend fallback returning a nonexistent dist-info path for wheels
      with a build tag - by @henryiii (#1119)
    - Write pip/uv requirements and constraints files with \n instead of os.linesep, avoiding doubled
      \r\r\n line endings on Windows - by @henryiii (#1120)
    - Batch of small robustness fixes: correct macOS release parsing for the minimum pip version, avoid
      sharing the mutable default build-system table between builders, keep the original error when
      isolated-environment setup fails early, and raise BuildException for an invalid wheel - by @henryiii (#1121)
    - Decide color support independently for stdout and stderr instead of only checking stdout.isatty(),
      so redirecting one stream no longer disables or leaks ANSI colors on the other - by @henryiii (#1123)
    - Pass --dependency-constraints-txt files through to the installer unmodified instead of re-parsing them
      into a deduplicated set of lines, fixing a case where a hashed requirement (e.g. from pip-compile
      --generate-hashes) could have its --hash continuation line separated from its requirement line and
      silently dropped, depending on the interpreter’s hash seed - by @manfred-kaiser (#1140)

Removals:
    - Remove exc_info parameter and attribute from BuildBackendException. - by @layday (#1161)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
 .../python3-build/check-valid-dist.patch       | 18 ++++++++++++------
 ...3-build_1.5.1.bb => python3-build_1.6.0.bb} |  2 +-
 2 files changed, 13 insertions(+), 7 deletions(-)
 rename meta/recipes-devtools/python/{python3-build_1.5.1.bb => python3-build_1.6.0.bb} (87%)

Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:

---
Testing patch /home/patchtest/share/mboxes/2-4-python3-build-upgrade-1.5.1---1.6.0.patch

FAIL: test commit message user tags: Mbox includes one or more GitHub-style username tags. Ensure that any "@" symbols are stripped out of usernames (test_mbox.TestMbox.test_commit_message_user_tags)

PASS: pretest src uri left files (test_metadata.TestMetadata.pretest_src_uri_left_files)
PASS: test CVE check ignore (test_metadata.TestMetadata.test_cve_check_ignore)
PASS: test Signed-off-by presence (test_mbox.TestMbox.test_signed_off_by_presence)
PASS: test auh changelog truncation notice (test_mbox.TestMbox.test_auh_changelog_truncation_notice)
PASS: test author valid (test_mbox.TestMbox.test_author_valid)
PASS: test commit message presence (test_mbox.TestMbox.test_commit_message_presence)
PASS: test lic files chksum modified not mentioned (test_metadata.TestMetadata.test_lic_files_chksum_modified_not_mentioned)
PASS: test max line length (test_metadata.TestMetadata.test_max_line_length)
PASS: test mbox format (test_mbox.TestMbox.test_mbox_format)
PASS: test non-AUH upgrade (test_mbox.TestMbox.test_non_auh_upgrade)
PASS: test shortlog format (test_mbox.TestMbox.test_shortlog_format)
PASS: test shortlog length (test_mbox.TestMbox.test_shortlog_length)
PASS: test src uri left files (test_metadata.TestMetadata.test_src_uri_left_files)
PASS: test target mailing list (test_mbox.TestMbox.test_target_mailing_list)

SKIP: pretest pylint: No python related patches, skipping test (test_python_pylint.PyLint.pretest_pylint)
SKIP: test CVE tag format: No new source patches introduced (test_patch.TestPatch.test_cve_tag_format)
SKIP: test Signed-off-by presence: No new source patches introduced (test_patch.TestPatch.test_signed_off_by_presence)
SKIP: test Upstream-Status presence: No new source patches introduced (test_patch.TestPatch.test_upstream_status_presence_format)
SKIP: test bugzilla entry format: No bug ID found (test_mbox.TestMbox.test_bugzilla_entry_format)
SKIP: test lic files chksum presence: No added recipes, skipping test (test_metadata.TestMetadata.test_lic_files_chksum_presence)
SKIP: test license presence: No added recipes, skipping test (test_metadata.TestMetadata.test_license_presence)
SKIP: test pylint: No python related patches, skipping test (test_python_pylint.PyLint.test_pylint)
SKIP: test series merge on head: Merge test is disabled for now (test_mbox.TestMbox.test_series_merge_on_head)
SKIP: test summary presence: No added recipes, skipping test (test_metadata.TestMetadata.test_summary_presence)

---

Please address the issues identified and
submit a new revision of the patch, or alternatively, reply to this
email with an explanation of why the patch should be accepted. If you
believe these results are due to an error in patchtest, please submit a
bug at https://bugzilla.yoctoproject.org/ (use the 'Patchtest' category
under 'Yocto Project Subprojects'). For more information on specific
failures, see: https://wiki.yoctoproject.org/wiki/Patchtest. Thank
you!