LGTM alerts . #19077
LGTM alerts . #19077
Comments
hey, can i have this issue? |
Posting for reference the LGTM alerts: https://lgtm.com/projects/g/numpy/numpy/alerts/?mode=list I can take a look at the errors in arithmetic.h, which were added during our SIMD division change. |
@ganesh-k13 so i just need to fix the errors/warnings shown in the lgtm page ? |
Welcome. Please read the developer's workflow guide, especially around commit messages. Some of those errors/warnings will be difficult to fix since LGTM's ideas may not agree with ours. Try to group the fixes in some logical way: for instance, all the unused imports in one PR and in another PR all the integer overflow warnings. |
@mattip thanks. I've removed all of the unused imports only to find out it breaks the code fsr(hoping you'll tell why), but reading the exceptions and restoring the removed imports solved the issue. I can now build and run tests. The test results are same after removing unused imports as linked below. Do you want me to go ahead and do a pr ? |
@mattip do you want me to go ahead and do a pr man? or is there I should be doing first ? Thanks |
A cleanup PR would be welcome. Please be sure it only changes the lines you intend to change: sometimes coding tools can "clean up" formatting which makes PRs harder to review. |
@charris I've raised a new PR for unused variables. Can anyone check and give a suitable review? |
Usually review requires a few days. If after a week no-one has reviewed, feel free to ping (without names) in the PR with a "please review" comment. |
thanks, noted. |
I notice that there are still a fair number LGTM alerts, many of which look pretty simple. I wonder if they would be a good source of issues for the next NumPy sprint?
The text was updated successfully, but these errors were encountered: