Closed HeavyTony2 closed 2 years ago
Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe
) and found some lint.
Here's what I've got...
For recipe:
noarch
packages can't have selectors. If the selectors are necessary, please remove noarch: python
.@conda-forge-admin, please rerender
Hi! This is the friendly automated conda-forge-linting service.
I was trying to look for recipes to lint for you, but it appears we have a merge conflict. Please try to merge or rebase with the base branch to resolve this conflict.
Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.
@conda-forge-admin, please rerender
Hi! This is the friendly automated conda-forge-webservice.
I tried to rerender for you, but it looks like there was nothing to do.
This message was generated by GitHub actions workflow run https://github.com/conda-forge/anndata-feedstock/actions/runs/2029073039.
We also no longer rely on xlrd, so it probably shouldn't be added to the dependency list.
I was wondering, does noarch
imply we can't have python version restrictions?
We also no longer rely on xlrd, so it probably shouldn't be added to the dependency list.
I was wondering, does
noarch
imply we can't have python version restrictions?
Sorry for the late answer. The answer is no. In fact, with a noarch version you have to set a python version restriction. The typical one is python >=3.6
but it could be python <=4
too for example.
@conda-forge-admin, please rerender
Added the missing dependancy xlrd <2.0 and set it as noarch.
Checklist
0
(if the version changed)conda-smithy
(Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)