1.13.1 osx only

[ngam]

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.

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

[hmaarrfk]

I think this may be the cause conda-forge/python-feedstock#597

do yo uwant to try forcing build 0?

[hmaarrfk]

it could be that we need conda-forge/crossenv-feedstock#38 (review)

[ngam]

I am in no hurry. (Also, I will likely be away-ish for a bit, on the order of ~1 week.)

Do you know how to force the python build to 0 here? I am asking because the python version gets inherited somewhere in the process and I am not sure if adding =*=*_0 or something else will do the trick...

[ngam]

Ok thanks; btw, I tried using the py==310 for skip, i.e. skip: true # [py==310], and it didn't work... 😢

[hmaarrfk]

yeah... sometimes skipping is weird.

[hmaarrfk]

did it get further?

[ngam]

Yes, looks like it is getting further!

[ngam]

Thank you, good job!!

[hmaarrfk]

@conda-forge-admin please rerender

[github-actions]

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/pytorch-cpu-feedstock/actions/runs/3923246416.