-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Deprecation warnings: scipy.sparse.sparsetools
and np.float
#3014
Comments
Thanks for trying the beta and reporting! I don't think we can do much about sparsetools (scipy provides no alternative AFAIK), but we can definitely fix the |
@raffaem can you run whatever steps you used before, but on the current We removed and fixed a bunch of code, so maybe this is not relevant any more. Thanks. |
Removing from 4.0.0. Will revisit when @raffaem follows up. |
#3066 is related to this |
I can confirm that the sparsetools DeprecationWarning still exists in gensim 4.0.1. Would it make sense to just squash this warning by surrounding the import with a try/except? The warning is certainly relevant to gensim maintainers, but for gensim users, it's mainly just an annoyance. |
Getting rid of (not showing) the sparsetools warning makes sense. But I don't think try-expect will help here – it's not an exception. As far as I'm aware scipy doesn't offer any alternative for its deprecated (but still functional) sparsetools module. So "fixing" the warning properly is not possible. |
I seem to remember there is a way to achieve this sort of thing I think using |
Update from me: So it turns out that Python's default warning filters will actually filter out DeprecationWarnings, so if you don't for some reason override this, gensim user's won't see these warnings. For some reason though pytest will show these warnings, which is where I was seeing it (see https://stackoverflow.com/a/53218641/896660). I don't really understand why pytest is not using the default warning filters of the python interpreter, but at least there is a way to configure this, so this is the solution in my particular case. I don't think there's anything that needs to be done on gensim's end. |
This was previously discussed in #462 (including with scipy upstream devs). |
Removing scipy from the dependencies was also discussed in #557. |
And in scipy/scipy#5348 by the scipy team. Scipy (and the whole pydata ecosystem) is much easier to deploy and manage than it was 7 years ago. Plus gensim now compiles its modules too, it's no longer pure python. So many of the assumptions and design edges from the original discussion are no longer relevant. |
Problem description
Run the test for the new version of WEFE
Steps/code/corpus to reproduce
Versions
Please provide the output of:
The text was updated successfully, but these errors were encountered: