torchdata v0.7.0

[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.

Dependency Analysis

We couldn't run dependency analysis due to an internal error in the bot, depfinder, or grayskull. :/ Help is very welcome!

_{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/6585204985, please use this URL for debugging.}

[conda-forge-webservices]

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) and found it was in an excellent condition.

[weiji14]

Pytorch 2.1.0 just got uploaded to conda-forge conda-forge/pytorch-cpu-feedstock#199, can someone retry the CI build please?

[Tobias-Fischer]

Needs conda-forge/conda-forge-pinning-feedstock#5123

[weiji14]

Needs conda-forge/conda-forge-pinning-feedstock#5123

Is a global pin actually needed? Or can we just set a lower pin on pytorch >=2.1.0 at L35 of recipe/meta.yaml, following meta-pytorch/data#1209?

[Tobias-Fischer]

Let's just wait for the global pin - they are there for a good reason; otherwise we get out of sync with the rest of conda-forge ..

[weiji14]

Ok, it doesn't look as though the torchdata recipe is using the global pytorch pin, but I'm with you that it's good to be in sync with other Pytorch-dependent packages across conda-forge (e.g. torchvision).

[Tobias-Fischer]

Yes, we are using the global pin, see e..g https://github.com/regro-cf-autotick-bot/torchdata-feedstock/blob/8b188f3802fa24031f81ff3cdc2fe1c2fed89a51/.ci_support/linux_64_python3.10.____cpython.yaml#L21-L22