Update for cuda-python 12.0.0 / CUDA 12.

[bdice]

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.

Drafting this PR early (dependencies not yet ready). Resolves #31. Resolves #32 (replaces the autotick PR).

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

[bdice]

@conda-forge-admin, please rerender

[jakirkham]

Think we need to add conda_build_config.yaml to the recipe to get the missing pieces

Do we want to do 12.0?

[bdice]

@conda-forge-admin, please rerender

[bdice]

Think we need to add conda_build_config.yaml to the recipe to get the missing pieces

Do we want to do 12.0?

Yes and yes. I'm moving in this direction now! 😄

[bdice]

@conda-forge-admin, please rerender

[conda-forge-webservices]

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:

• Non noarch packages should have python requirement without any version constraints.
• Non noarch packages should have python requirement without any version constraints.

[bdice]

@conda-forge-admin, please rerender

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

[jakirkham]

@conda-forge-admin, please re-render

[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/cuda-python-feedstock/actions/runs/5159664135.

Addressed in discussion, raised issues, & added a comment in the recipe

[conda-forge-webservices]

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:

• pin_subpackage should be used instead of pin_compatible for cuda-python because it is one of the known outputs of this recipe: ['cuda-python'].

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

[bdice]

@jakirkham @m3vaz I took a quick look here -- all the recent changes seem good to me (though I can't review my own PR).

[m3vaz]

LGTM

[jakirkham]

Thanks all! 🙏

Adding the automerge label so the bot will merge the PR once CI passes 🙂

[github-actions]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: passed

Thus the PR was passing and merged! Have a great day!

[mmccarty]

Thanks all! Great work!