Arch Migrator

[regro-cf-autotick-bot]

This feedstock is being rebuilt as part of the aarch64/ppc64le migration.

Feel free to merge the PR if CI is all green, but please don't close it without reaching out the the ARM migrators first at @conda-forge/arm-arch.

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 code>@<space/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/10603607149 - please use this URL for debugging.}

[conda-forge-webservices[bot]]

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:

• No valid build backend found for Python recipe for package snowflake-snowpark-python using pip. Python recipes using pip need to explicitly specify a build backend in the host section. If your recipe has built with only pip in the host section in the past, you likely should add setuptools to the host section of your recipe.

[sfc-gh-yuwang]

@conda-forge-admin please rerender

[github-actions[bot]]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/snowflake-snowpark-python-feedstock/actions/runs/10619245635.

[sfc-gh-yuwang]

@xhochy Hi, can you help take a look at this automated PR? It seems like I need to change the conda-forge.yml file but I don't have the permission. Thank you!

[sfc-gh-mkeller]

What just happened with the Travis CI build?

[hmaarrfk]

your package is effective a "python: noarch" with a constraint that makes it only installable on python 3.9.

why have all these different builds?

Consider

build:
  - noarch: python
requirements:
  host:
    - python >=3.9,<3.10.0a0
  run:
    - python >=3.9,<3.10.0a0
    - cloudpickle >=1.6.0,<=2.2.1,!=2.1.0,!=2.2.0

and it will all become 1 job.

[sfc-gh-mkeller]

@hmaarrfk We already do and should continue to be building Python 3.8-3.11 packages and in this PR we want to add support for ARM on Linux too. According to the conda-forge docs this package doesn't qualify to be a noarch package, since it has a Python version dependent dependency.

[hmaarrfk]

Sorry about that, I got confused by the skip statement.

Why do you have this requirement?

    - cloudpickle >=1.6.0,<=2.2.1,!=2.1.0,!=2.2.0  # [py<311]
    - cloudpickle >=2.2.1,<3.0.0  # [py==311]

could it just be removed?

[hmaarrfk]

@conda-forge-admin please restart cis

[hmaarrfk]

@conda-forge-admin please rerender

[hmaarrfk]

if the py==311 stuff can be removed, your whole build matrix collapses to 1.

[sfc-gh-mkeller]

if the py==311 stuff can be removed, your whole build matrix collapses to 1.

Sorry about that, I got confused by the skip statement.

Why do you have this requirement?

    - cloudpickle >=1.6.0,<=2.2.1,!=2.1.0,!=2.2.0  # [py<311]
    - cloudpickle >=2.2.1,<3.0.0  # [py==311]

could it just be removed?

No, unfortunately not in the short-term. I checked in with the devs and some versions don't work well on Python 3.8 and 3.9, but that newer version is actually the only thing working on 3.11. They are on removing these, but we'd like to get a Linux ARM build out before that happens.

[sfc-gh-mkeller]

@hmaarrfk also would you know why Python 3.8 builds were removed?

[hmaarrfk]

We dropped support for it at conda-forge like last week.

[sfc-gh-mkeller]

@hmaarrfk Also, wouldn't we have to increase the build number, or will forge just add the new files only?

[hmaarrfk]

If the ci support files don't change. It's pretty safe.

We will only upload files that change hash.

For this migration it is likely pretty safe.

[sfc-gh-mkeller]

Alright then, thank you s much @hmaarrfk for your help!