Update to 3.11

[jschueller]

Closes #62

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

I do have some suggestions for making it better though...

For recipe:

• It looks like the 'libblas' output doesn't have any tests.
• It looks like the 'libtmglib' output doesn't have any tests.
• It looks like the 'libcblas' output doesn't have any tests.
• It looks like the 'liblapack' output doesn't have any tests.
• It looks like the 'liblapacke' output doesn't have any tests.
• It looks like the 'blas-devel' output doesn't have any tests.
• It looks like the 'lapack' output doesn't have any tests.

[jschueller]

@conda-forge-admin please rerender

[jschueller]

ready to go @conda-forge/lapack

[h-vetinari]

We waited a really long time to get #51 merged, because we basically want all BLAS/LAPACK implementations to support the same LAPACK feature level, and MKL is generally far behind.

Also, we haven't enabled 3.10 in the blas-metapackage yet, which is IMO the next reasonable step...

[jschueller]

ok, yes, I figured 3.9 was really old :)
but anyway this is independent of the global pinning and we can still update the feedstock to ease the next version update

[isuruf]

Merging this as is will make the netlib variant higher priority. Here's what we can do,

1. Merge this PR with target to conda-forge/label/lapack
2. Build blas-metapackage without MKL and drop windows for 3.11
3. Move these pacakges to main label

To be clear this only gives the ability of downstream feedstocks to target new APIs in 3.10 and 3.11, but not any performance benefits as we enable latest versions of openblas, MKL, etc with 3.9.

[jschueller]

ok, in this case it can wait, I let you decide

[h-vetinari]

The Intel team helping us with repackaging MKL has asked to be able to test blas metapackage against LAPACK 3.11, as there are failures with 3.10.1.

The main branch here already points to a separate label:

lapack-feedstock/recipe/conda_build_config.yaml

Lines 1 to 2 in f675059

	channel_targets:
	- conda-forge lapack_rc

so we can safely merge this PR. Then it becomes easy to test the various implementations against 3.11 on the blas feedstock, without yet making this generally available.

PS. Thanks a lot for the PR!