Tidy selectors

[jakirkham]

Cleans up the selectors a bit to delineate the cases that we skip a bit more. Namely Python 2.7 is dropped in CuPy 7. PyPy has some issues (hopefully all now fixed upstream 🍀). Finally CUDA support is required to build.

As a last tweak, we now skip builds only when cuda_compiler_version is undefined or None (as opposed to skipping on linux64 builds). This should make it trivial to add new architectures as CUDA builds become available for them without requiring changes here (outside of a re-render).

Checklist

• [x] Used a 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)
• [x] Re-rendered with the latest conda-smithy (Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• [x] Ensured the license file is being packaged.

Edit: Ignoring build number as this doesn't change how the packages are built.

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

• Failed to even lint the recipe, probably because of a conda-smithy bug :cry:. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint . from the recipe directory.

[conda-forge-linter]

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.

[jakirkham]

@conda-forge-admin, please re-render.

(should be a no-op)

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

[jakirkham]

@conda-forge-admin, please re-render.

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

[leofang]

Hi @jakirkham, sorry for my slowness. I have a few questions:

• Doesn't undefined for cuda_compiler_version need to be a string ("undefined")? Is it a variable defined somewhere?
• Are we expecting support for new architectures coming soon? 🙂

[jakirkham]

No worries. Sorry had figured this was probably not too interesting to others.

Jinja defines undefined to make it easier to check if a variable is not defined.

This still depends on Anaconda to publish cudatoolkit packages for other architectures. That said, it seems like a good idea to adopt this practice early so we are ready once that happens. Plus it can be included in docs for others to use 😉

[leofang]

Got it, thanks John!

[leofang]

Not sure what happened, but this PR didn't upload while #51 did...

[jakirkham]

Hmm...probably the package hash changed for some reason. It's probably harmless, but would be ok pulling the package if you prefer. WDYT?

[leofang]

Yeah it's ok to leave them. It's harmless indeed. Just wondered why. 🙂