-
-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Add a recipe for pydata/sparse #5631
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 ( |
recipes/sparse/meta.yaml
Outdated
- pip | ||
run: | ||
- python | ||
- numpy >= 1.14 |
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.
remove the space between the logical sign and the version number, i.e:
- numpy >=1.14
recipes/sparse/meta.yaml
Outdated
description: | | ||
sparse implements sparse multidimensional arrays on top of Numpy | ||
and scipy.sparse. It tries to mimic Numpy's ndarray API. | ||
doc_url: https://sparse.pydata.org/en/0.3.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.
Maybe drop the version number from the doc_url
? I'm afraid it might not get updated when the recipe does since it's buried far down in the recipe.
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 could, but since this package is currently not mature I expect the information on there to get out of sync with what's in the recipe quite quickly, which is why I added a link to the release version.
extra: | ||
recipe-maintainers: | ||
- hameerabbasi | ||
- mrocklin |
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.
@mrocklin -- are ok with being a co-maintainer of the sparse
recipe on conda-forge?
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.
Yes, I am ok with being a co-maintainer of the sparse package on conda-forge.
Additionally lets ping @jakevdp to see if he is interested.
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.
Sure, sounds good
recipes/sparse/meta.yaml
Outdated
- scipy >= 0.19 | ||
- numba >= 0.37 | ||
|
||
test: |
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.
You can run pytest
here using the command
section of test
:
https://conda.io/docs/user-guide/tasks/build-packages/define-metadata.html#test-commands
You'll need to add pytest
and any other testing-only requirement in the requires
section:
https://conda.io/docs/user-guide/tasks/build-packages/define-metadata.html#test-requirements
Also being able to run the test suite depends on the test files being included in the source distribution.
Well, this is weird. Do I need to add all requirements to the |
Anything in the |
You're going to want the requirements under both |
fa9996c
to
67788f0
Compare
Looks like the MANIFEST.in in the package needs to be updated: it specifies |
I pushed |
Hmm. It seems I need to run |
recipes/sparse/meta.yaml
Outdated
- pytest-cov | ||
- pytest-flake8 | ||
commands: | ||
- py.test |
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.
Perhaps py.test sparse
?
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 may be mistaken, but I think the preference is to not run full test suites as part of a conda-forge recipe, because it eats up too many CI resources.
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.
See the user guide here: https://conda-forge.org/docs/testing.html#should-a-recipe-run-all-of-a-package-s-tests
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.
Fair enough. I'll just take out the test and we'll do the testing on our own CI.
@synapticarbors I apologize for this, but could you either merge or re-trigger Travis? The failure seems to be related to not being able to download the package, and it downloaded fine in the other CI services. |
I restarted the Travis build |
Another intermittent error. 😐 Edit: And a different one at that. Best to wait a bit I guess. Travis might be having issues. |
This shouldn't be needed any more now that it is not importing the package, correct? |
Unfortunately, the release version is still doing that. I'm hesitating on releasing now because we made some backwards incompatible changes (feature removals) I need to clean up and add back with new logic. |
Looks good to me. 👍 for merge |
FWIW was able to build locally when dropping basically everything from |
That makes sense: I think numpy, scipy, and numba can be removed from build_deps. If you look at the v0.3.1 setup.py file you can see that it doesn't import those or import anything that uses those. |
Ah, you're both right. I removed those from the build deps, and I also removed numba as it was introduced as a dependency after 0.3.1. |
Do you still want to wait on this or is it good to merge? |
+1 to merge from me. 😄 |
Sorry for the delay. Thanks also for your patience. This is now in a feedstock with builds triggered. |
This is to add a recipe for pydata/sparse.
As an aside, can we install the requirements for
py.test
and run it as a command, if possible?Edit: And how do I specify minimum versions?