-
-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Adding elapid #18896
Adding elapid #18896
Conversation
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 ( |
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 ( Here's what I've got... For recipes/elapid:
|
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 ( Here's what I've got... For recipes/elapid:
|
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 ( |
@conda-forge-admin, please ping team |
Hi! This is the friendly automated conda-forge-webservice. I was asked to ping @conda-forge/staged-recipes and so here I am doing that. |
recipes/elapid/meta.yaml
Outdated
- python | ||
- descartes >=1.1.0 | ||
- geopandas >=0.7.0 | ||
- glmnet # [py<39 and not win] |
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.
This seems to be the only thing here that makes this not a noarch: python
recipe. Could you explain what this is about exactly? I.e., how come there is a dependency that is only needed when Python is old? (Might also be nice to add a comment to the recipe so contributors to the recipe in the future do not stumble upon this.
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.
it's mostly because the glmnet
package doesn't include a windows build. I was under the impression from this issue that python 3.9 and above was also unavailable. After checking the conda-forge page that doesn't appear to be the case, so it looks like this could just be [not win]
.
this is a statistical modeling package that has some nice-to-have features that are unavailable in sklearn
. elapid
works around this by using glmnet
if it's installed, sklearn
otherwise. I could technically drop the requirement entirely, but imho it's worth having those nice-to-haves.
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.
@earth-chris FYI I did follow up with @civisanalytics to be able to maintain glmnet
project; No one responded tho
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.
yea, i saw that, thanks @amirhessam88. seems unlikely that they're gonna resume maintenance on the package, unfortunately, so future updates would probably have to come from someone who forks it and pushes a new package.
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.
Looks alright to me. Please have a look at the comments above.
removed <py37 restriction, added dev_url Co-authored-by: Julian Rüth <[email protected]>
hi @saraedum, thanks so much for your review! I've accepted the edits you recommended and relaxed the python version constraints on |
@conda-forge-admin, please ping team |
Hi! This is the friendly automated conda-forge-webservice. I was asked to ping @conda-forge/staged-recipes and so here I am doing that. |
recipes/elapid/meta.yaml
Outdated
- descartes >=1.1.0 | ||
- geopandas >=0.7.0 | ||
- glmnet >=2.0,<2.3 # [not win] windows build unavailable; elapid will use sklearn features instead | ||
- numpy >=1.18 | ||
- pandas >=1.0.3 | ||
- rasterio >=1.2.1 | ||
- rtree >=0.9 | ||
- scikit-learn >=0.22.2 | ||
- shapely >=1.7.0 | ||
- tqdm >=4.60.0 |
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.
- descartes >=1.1.0 | |
- geopandas >=0.7.0 | |
- glmnet >=2.0,<2.3 # [not win] windows build unavailable; elapid will use sklearn features instead | |
- numpy >=1.18 | |
- pandas >=1.0.3 | |
- rasterio >=1.2.1 | |
- rtree >=0.9 | |
- scikit-learn >=0.22.2 | |
- shapely >=1.7.0 | |
- tqdm >=4.60.0 | |
- descartes >=1.1.0,<2 | |
- geopandas >=0.7.0,<0.8 | |
- glmnet >=2.0,<2.3 # [not win] windows build unavailable; elapid will use sklearn features instead | |
- numpy >=1.18 | |
- pandas >=1.0.3,<2 | |
- rasterio >=1.2.1,<2 | |
- rtree >=0.9,<0.10 | |
- scikit-learn >=0.22.2,<0.23 | |
- shapely >=1.7.0,<2 | |
- tqdm >=4.60.0,<5 |
Assuming that these all follow semantic versioning. They probably don't but pins can still be relaxed later.
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.
ok, I've added upper bounds to some packages. I didn't accept these changes as-is because they are unnecessarily strict (elapid has been tested and works with sklearn
1.1.2, with geopandas
0.11.1, etc.).
recipes/elapid/meta.yaml
Outdated
- python | ||
- descartes >=1.1.0 | ||
- geopandas >=0.7.0 | ||
- glmnet >=2.0,<2.3 # [not win] windows build unavailable; elapid will use sklearn features instead |
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.
As a suggestion for the next release of elapid, you could consider just issuing a warning if glmnet is not available, remove this dependency and set this recipe to noarch: python
. The upside is that it will work without any further changes on apple silicon, aarch64, ….
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've removed the glmnet
requirement in the recipe and set it to noarch: python
. It already has a try/except for importing glmnet so it should be fine as-is.
Sorry for the delayed reaction here. This looks alright to me. Let me know if you want to make any further changes. |
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 ( Here's what I've got... For recipes/elapid:
|
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 ( Here's what I've got... For recipes/elapid:
|
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 ( |
alright @saraedum I think I've addressed your requested changes. |
Checklist
url
) rather than a repo (e.g.git_url
) is used in your recipe (see here for more details).