pyexcel-io v0.6.7

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

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

For recipe/meta.yaml:

• noarch: python recipes should almost always follow the syntax in our documentation. For the host section of the recipe, you should almost always use python {{ python_min }} for the python entry. For the run section of the recipe, you should almost always use python >={{ python_min }} for the python entry. For the test.requires section of the recipe, you should almost always use python {{ python_min }} for the python entry. You may need to override the python_min variable in the conda_build_config.yaml/variants.yaml if the package requires a newer Python version than the currently supported minimum version on conda-forge.
• PyPI default URL is now pypi.org, and not pypi.io. You may want to update the default source url.

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

[nicoddemus]

@conda-forge/python I've read the docs on https://conda-forge.org/docs/maintainer/knowledge_base/#noarch-python about the new standard of using python_min, however it is failing here with a Jinja error about python_min not being available. From my understanding it should be available from the global pinnings? Anything that needs to be done here for that to happen?

[ocefpaf]

The only missing part is this line. The docs on python_min are still in flux. Sorry for the confusion!

[nicoddemus]

Ahh OK @ocefpaf thanks!

In that case, the version for default should be the minimum supported version by the package or by conda-forge currently?

[ocefpaf]

or by conda-forge currently.

Should be the min defined by conda-forge. I don't think we are defining that yet though.

[nicoddemus]

Thanks!

One more quick question: once conda-forge defines python_min, that {% set python_min directive wouldn't be needed in theory, right?

[ocefpaf]

In theory, yes. (To be honest, even though I started this, I did not follow thw CFEP or its implementation 😬.)

[nicoddemus]

Cool, thanks for confirming it!