-
-
Notifications
You must be signed in to change notification settings - Fork 279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ENH: Add example of conda_build_config.yaml python_min map #2370
ENH: Add example of conda_build_config.yaml python_min map #2370
Conversation
✅ Deploy Preview for conda-forge-previews ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
59fe707
to
1ebca2a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note to reviewers
docs/maintainer/knowledge_base.md
Outdated
:::tip[Hint] | ||
|
||
Adding an explicit `python_min` to your `noarch: python` recipe can be an effective way to ensure the required | ||
Python in your package's metadata is enforced at `conda-build` time, as the build will fail if the package's | ||
required Python version is different from `python_min`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If it isn't clear from this that I'm trying to explain a situation where the existing feedstock would have
python_min:
- "3.8"
and the new package metadata (e.g. from PyPI) has
[project]
...
requires-python = ">=3.9"
resulting in a build failure (which is good as the python_min
is now out of date) let me know and I can revise this.
* Add example of the map that is required for python_min to be manually enforced if it exists in recipe/conda_build_config.yaml. * Add a tip that adding an explicit python_min also ensures that python_min used by conda-build does not deviate from the required Python metadata in the Python package. If the Python package required Python metadata is updated and the feedstock's recipe is not the build will fail, signalling that there is a metadata mismatch that needs to be corrected.
1ebca2a
to
7a56541
Compare
|
||
Adding an explicit `python_min` to your `noarch: python` recipe can be an effective way to ensure the required | ||
Python in your package's metadata is enforced at `conda-build` time, as the build will fail if the package's | ||
required Python version is newer than `python_min`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I previously had this as "different from" but that's wrong. It only acts as a guard if the required Python metadata in the package advances to a newer Python than python_min
.
thank you! |
Thank you both! 🙏 |
recipe/conda_build_config.yaml
.python_min
also ensures thatpython_min
used byconda-build
does not deviate from the required Python metadata in the Python package. If the Python package required Python metadata is updated and the feedstock's recipe is not the build will fail, signalling that there is a metadata mismatch that needs to be corrected.PR Checklist:
docs/
orcommunity/
, you have added it to the sidebar in the corresponding_sidebar.json
fileRelevant section of the netlify docs preview: https://deploy-preview-2370--conda-forge-previews.netlify.app/docs/maintainer/knowledge_base/#noarch-python