Rebuild for python 3.13

[regro-cf-autotick-bot]

This PR has been triggered in an effort to update python313.

Notes and instructions for merging this PR:

1. Please merge the PR only after the tests have passed.
2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.

---

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/11952899979 - 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.

[megies]

Conda doesn't seem to be able to set up a py3.13 env yet

[regro-cf-autotick-bot]

Due to the bot-rerun label I'm closing this PR. I will make another one as appropriate.

_{This message was generated by https://github.com/regro/cf-scripts/actions/runs/12182551937 - please use this URL for debugging.}

[megies]

@conda-forge-admin, please rerun bot

[megies]

Hmm trying to get a new build but failing 🤣

[megies]

@conda-forge-admin, please

[megies]

@conda-forge-admin, please rerender

[megies]

Not sure what's going on here. Somehow the 3.13 build tries to install 3.13.0rc1 for whatever reason and fails when there is final non-rc versions available. Locally conda has no issues to install 3.13 with all our dependencies.

Trying to force a higher version number, just to see what happens..

[megies]

Well, no idea what's going on.

Build fails with:

WARNING: failed to get package records, retrying.  exception was: Unsatisfiable dependencies for platform linux-64: {MatchSpec("python==3.13.1=ha99a958_101_cp313"), MatchSpec("python_abi=3.13[build=*_cp313]")}
Encountered problems while solving:
  - package python-3.13.1-ha99a958_101_cp313 requires python_abi 3.13.* *_cp313, but none of the providers can be installed

But locally, there is no issue at all trying to install these exact specs..

$ conda create -n trash "python==3.13.1=ha99a958_101_cp313" "python_abi=3.13[build=*_cp313]"
conda-forge/linux-64                                        Using cache
conda-forge/noarch                                          Using cache
Collect all metadata (repodata.json): done
Solving environment: done


==> WARNING: A newer version of conda exists. <==
    current version: 23.3.1
    latest version: 24.11.0

Please update conda by running

    $ conda update -n base -c conda-forge conda



## Package Plan ##

  environment location: miniconda3/envs/trash

  added / updated specs:
    - pip
    - python==3.13.1=ha99a958_101_cp313
    - python_abi=3.13[build=*_cp313]


The following NEW packages will be INSTALLED:

  _libgcc_mutex      conda-forge/linux-64::_libgcc_mutex-0.1-conda_forge 
  _openmp_mutex      conda-forge/linux-64::_openmp_mutex-4.5-2_gnu 
  bzip2              conda-forge/linux-64::bzip2-1.0.8-h4bc722e_7 
  ca-certificates    conda-forge/linux-64::ca-certificates-2024.8.30-hbcca054_0 
  ld_impl_linux-64   conda-forge/linux-64::ld_impl_linux-64-2.43-h712a8e2_2 
  libexpat           conda-forge/linux-64::libexpat-2.6.4-h5888daf_0 
  libffi             conda-forge/linux-64::libffi-3.4.2-h7f98852_5 
  libgcc             conda-forge/linux-64::libgcc-14.2.0-h77fa898_1 
  libgcc-ng          conda-forge/linux-64::libgcc-ng-14.2.0-h69a702a_1 
  libgomp            conda-forge/linux-64::libgomp-14.2.0-h77fa898_1 
  liblzma            conda-forge/linux-64::liblzma-5.6.3-hb9d3cd8_1 
  libmpdec           conda-forge/linux-64::libmpdec-4.0.0-h4bc722e_0 
  libsqlite          conda-forge/linux-64::libsqlite-3.47.0-hadc24fc_1 
  libuuid            conda-forge/linux-64::libuuid-2.38.1-h0b41bf4_0 
  libzlib            conda-forge/linux-64::libzlib-1.3.1-hb9d3cd8_2 
  ncurses            conda-forge/linux-64::ncurses-6.5-he02047a_1 
  openssl            conda-forge/linux-64::openssl-3.4.0-hb9d3cd8_0 
  pip                conda-forge/noarch::pip-24.3.1-pyh145f28c_0 
  python             conda-forge/linux-64::python-3.13.1-ha99a958_101_cp313 
  python_abi         conda-forge/linux-64::python_abi-3.13-5_cp313 
  readline           conda-forge/linux-64::readline-8.2-h8228510_1 
  tk                 conda-forge/linux-64::tk-8.6.13-noxft_h4845f30_101 
  tzdata             conda-forge/noarch::tzdata-2024b-hc8b5060_0 


Proceed ([y]/n)?

[megies]

Problem seems to be that we have numpy <2 pinned for this release and there might not be any is no numpy <2 for python 3.13.
So we can't build this release for 3.13

[ThomasLecocq]

naaaah ? really ?

[megies]

Yes, there is no conda package for numpy <2 for py 3.13. we should just get 1.5 out and ignore this, ideally. Other way would be to backport some of the recent fixes and make another 1.4.x release, but that's just extra work and no point really I would say.

[dopplershift]

Just to be clear, numpy itself didn't support 3.13 until numpy 2.1, so it's not so much a conda-forge issue as numpy.

[megies]

Just to be clear, numpy itself didn't support 3.13 until numpy 2.1, so it's not so much a conda-forge issue as numpy.

Yes, I realized that point, thanks!