conda-forge / conda-forge/mkdocstrings-python-xref-feedstock
Clean up recipe per recommendation
- Dominant language
- No language data
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
noarch: python recipes should usually follow the syntax in our [documentation](https://urldefense.com/v3/__https://conda-forge.org/docs/maintainer/knowledge_base/*noarch-python__;Iw!!A3Ni8CS0y2Y!7PZ8k4ULt2wE-SNI7FY8PJ9DPZHbq2twmrwC1Llj6N6b4wvE2JPyjxzUIlczcMF2K9mtXLwCGPlbD5apkvg3BfAOv-zeRZg$) for specifying the Python version.
* [ ] For the host section of recipe, you should usually use python {{ python_min }} for the python entry.*
* [ ] For the run section of recipe, you should usually use python >={{ python_min }} for the python entry.
* [ ] For the test.requires section of recipe, you should usually use python {{ python_min }} for the python entry.
If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).
Contributor guide
Research direction
Start by locating the package recipe and compare its host, run, and test.requires Python entries with the linked conda-forge noarch Python documentation. The work is done when the recipe follows the requested python_min syntax, or explicitly documents an applicable override.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100