Add run_export to pytorch

[AntoinePrv]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

Pytorch ABI is not stable, so libraries building Pyorch extensions should use the same minor version of Pyorch as the one used to build. See for instance conda-forge/pytorch_scatter-feedstock#24.

[AntoinePrv]

@conda-forge-admin, please rerender

[conda-forge-linter]

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

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

• The outputs section contained an unexpected subsection name. activate_in_script is not a valid subsection name.

For recipe:

• It looks like the 'pytorch-cpu' output doesn't have any tests.

[hmaarrfk]

These packages are really hard to build. @isuruf do you think it is acceptable to write a metadata patch to add the run exports? Then we can skip bumping the building number

[jaimergp]

@hmaarrfk: do you think it is acceptable to write a metadata patch to add the run exports?

run_exports is only available at channeldata.json or the package itself (e.g. see conda/conda-build#3583, conda/conda-build#3617), and afaik we don't patch channeldata, only repodata :/

[conda-forge-linter]

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

I was trying to look for recipes to lint for you, but it appears we have a merge conflict.
Please try to merge or rebase with the base branch to resolve this conflict.

Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.

[hmaarrfk]

@AntoinePrv are you able to rebase (or merge from) master and rebuild I think this is something I want to get in the next big pytorch push.

[conda-forge-linter]

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

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

• The outputs section contained an unexpected subsection name. activate_in_script is not a valid subsection name.

For recipe:

• It looks like the 'pytorch-cpu' output doesn't have any tests.

[AntoinePrv]

@hmaarrfk Done

[hmaarrfk]

Thanks. lets see what happens.