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
Support numpy.repeat
#3457
Comments
Hey, I am a beginner and I would like to give this issue a try. |
Hey @stuartarchibald, I wanted to try and contribute to fixing this issue so I pulled the code from development and tried to set it up in my local. When I ran pip install -r requirements.txt, I ran into an error I couldn't solve - Can you please help me with the setup? |
Hi, thanks for wanting to contribute this feature. I'd recommend following the instructions here as they provide the fastest way to get set up to undertake development. The issue you are seeing is because Numba relies on llvmlite, and Numba master branch uses developmental (and therefore unpublished) versions of llvmlite. These Hope this helps. |
Thank you. |
@stuartarchibald , Can you help me out with what needs to be done here. I went through - #3509, which seemed like a similar issue, but could not figure what exactly needs to be done. TIA. |
First you need to write a working implementation of |
Hi @stuartarchibald , I wrote the code for repeat and added some tests to check it in test_array_methods.py. I got stuck with one error I am not able to resolve while testing - numba.errors.TypingError: Failed in nopython mode pipeline (step: nopython frontend) How do I resolve this? |
@NanduTej thanks for writing this. Without seeing the code you've written it's quite hard to guess what it is that's wrong. However, I expect the issue is that the code tries to compile something like If it's mostly working ok but with just a couple of errors, perhaps open a pull request with the code so you can get some help with the remaining issues? Thanks. |
Fixed in #3900, closing. |
Feature request
Add support for
numpy.repeat
.The text was updated successfully, but these errors were encountered: