optype v0.13.1

[regro-cf-autotick-bot]

It is very likely that the current package version for this feedstock is out of date.

Checklist before merging this PR:

• Dependencies have been updated if changed: see upstream
• Tests have passed
• Updated license if changed and license_file is packaged

Information about this PR:

1. Feel free to push to the bot's branch to update this PR if needed.
2. The bot will almost always only open one PR per version.
3. The bot will stop issuing PRs if more than 3 version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.
4. If you want these PRs to be merged automatically, make an issue with @conda-forge-admin,please add bot automerge in the title and merge the resulting PR. This command will add our bot automerge feature to your feedstock.
5. If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/16627908105 - please use this URL for debugging.}

[conda-forge-admin]

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/recipe.yaml) and found it was in an excellent condition.

[jorenham]

Wait wait wait; there's a bit of an issue here!

optype.numpy (still optional) also requires numpy-typing-compat to be installed since optype>=0.13.0.

With pip you can just do uv pip install optype[numpy] to install both numpy-typing-compat and numpy. But there's no such thing with conda, right? So maybe this needs a separate conda-thingy, similar like scipy-typed?

Speaking of, the upcoming scipy-stubs==1.16.1.0 release will be using optype[numpy] >=0.13.1, <0.14, so it'll require numpy-typing-compat too.

I haven't gotten to jorenham/numpy-typing-compat#6 yet though. So @lucascolley, are you perhaps willing to take that on as well? It'll probably be a lot easier for you then it would be for me, given your conda savynessitude and my conda noobynessitude.

[lucascolley]

sorry @jorenham I missed this ping, but yeah I should be able to take up jorenham/numpy-typing-compat#6!

[lucascolley]

With pip you can just do uv pip install optype[numpy] to install both numpy-typing-compat and numpy. But there's no such thing with conda, right? So maybe this needs a separate conda-thingy, similar like scipy-typed?

For now, yes. optype-numpy or some other suitable name will be the way to go for now. Prefix folks are cooking up something at conda/ceps#111 but it isn't here yet.

[jorenham]

With numpy-typing-compat now on cf (:tada:), I suppose we can move on to optype-numpy. Do you think it would it work if I'd copy the multi-package approach from https://github.com/conda-forge/scipy-stubs-feedstock/blob/main/recipe/recipe.yaml, @lucascolley ?

[lucascolley]

yep!