python v3.13.7

[regro-cf-autotick-bot]

It is very likely that the current package version for this feedstock is out of date.

Checklist before merging this PR:

• Dependencies have been updated if changed: see upstream
• Tests have passed
• Updated license if changed and license_file is packaged

Information about this PR:

1. Feel free to push to the bot's branch to update this PR if needed.
2. The bot will almost always only open one PR per version.
3. The bot will stop issuing PRs if more than 3 version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.
4. If you want these PRs to be merged automatically, make an issue with @conda-forge-admin,please add bot automerge in the title and merge the resulting PR. This command will add our bot automerge feature to your feedstock.
5. If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/16784890575 - please use this URL for debugging.}

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

• ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/17433404366. Examine the logs at this URL for more detail.}

[h-vetinari]

In the meantime, 3.13.7 was also released, but I think we could still build 3.13.6 in between. 🤷

[h-vetinari]

Ah, nevermind, we should probably skip 3.13.6. From the announcement linked above:

3.13.7 is an expedited release to fix a significant issue with the 3.13.6 release:

• gh-137583: Regression in ssl module between 3.13.5 and 3.13.6: reading from a TLS-encrypted connection blocks

[h-vetinari]

Hm. So post-conda-forge/linux-sysroot-feedstock#88, this is picking up

## Package Plan ##

  environment location: /home/conda/feedstock_root/build_artifacts/python-split_1755222177045/_build_env

The following NEW packages will be INSTALLED:

    [...]
    sysroot_linux-64:              2.34-h087de78_2            conda-forge
    sysroot_linux-aarch64:         2.17-h68829e0_18           conda-forge

in cross-compilation, which then leads to

+ $PREFIX/bin/embedded-python-shared
$PREFIX/bin/embedded-python-shared: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by $PREFIX/bin/embedded-python-shared)

Not sure why this doesn't happen on main or in #809. The simplest would be to add a constraint

  # ensure cross-compilation doesn't pull in too-new glibc for build arch
  - sysroot_linux-64  2.17.*  # [linux]

likely the better solution would be ensure that Python picks up the correct sysroot.

[aisven]

I had a brief look at one of the failed pipelines.

It seems that the linker has a problem. Not sure. This apparently occurs during a conda test phase.

In function 'memset',
    inlined from 'format_float_short' at /usr/local/src/conda/python-3.13.7/Python/pystrtod.c:1167:0:
/home/conda/feedstock_root/build_artifacts/python-split_1755222160136/_build_env/x86_64-conda-linux-gnu/sysroot/usr/include/bits/string3.h:81: warning: call to '__warn_memset_zero_len' declared with attribute warning: memset used with constant zero length parameter; this could be due to transposed parameters [-Wattribute-warning]
/home/conda/feedstock_root/build_artifacts/python-split_1755222160136/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pla/bin/../lib/gcc/x86_64-conda-linux-gnu/14.3.0/../../../../x86_64-conda-linux-gnu/bin/ld: /tmp/ccfO3tqG.lto.o: in function `format_float_short':
/home/conda/feedstock_root/build_artifacts/python-split_1755222160136/_build_env/x86_64-conda-linux-gnu/sysroot/usr/include/bits/string3.h:81:(.text.hot.format_float_short+0x1c8): undefined reference to `__warn_memset_zero_len'

collect2: error: ld returned 1 exit status

[xhochy]

The problem on Windows is that it picks up the LLVM tools from MSVC which are not the right version. We need to change the PATH order.

[h-vetinari]

No idea what changed recently; the same problem occurred on the clangdev feedstock.

Not sure if we can influence the global PATH (more than environment activation already tries to do, by sorting the environment folders before the rest). Perhaps we need to patch in using full paths upon invocation in Python.

The cheap alternative is something like conda-forge/clangdev-feedstock@cb0d977

[xhochy]

This ia coming from the MSVC scripts. I think I did workaround this in some other feedstock (maybe jaxlib or r_clang). I will look into this tomorrow.

[xhochy]

We did this here: https://github.com/conda-forge/r_clang_activation-feedstock/pull/10/files This doesn't work here in the same fashion.

[xhochy]

Submitted the patch to upstream: python/cpython#138452