-
-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add run_export
to pytorch
#43
Conversation
@conda-forge-admin, please rerender |
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 ( Here's what I've got... For recipe:
For recipe:
|
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 |
|
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 ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug. |
@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. |
…nda-forge-pinning 2021.07.19.17.59.15
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 ( Here's what I've got... For recipe:
For recipe:
|
@hmaarrfk Done |
Thanks. lets see what happens. |
Checklist
Reset the build number to0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)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.