4 ms·
In my experience DeprecationWarnings get turned off so frequently because I'm not forking big library to fix all of it's Deprecated uses of their dependencies.
by scoot_718 6y ago
In my experience DeprecationWarnings get turned off so frequently because I'm not forking big library to fix all of it's Deprecated uses of their dependencies.
The warnings are useless if they're not from my code, so they get turned off once globally.
- takeda 6y agoThey are still important. Because even if dependency has this warning, it will still break your code.
- afiori 6y agobut they are also not actionable
- takeda 6y agowell actually they are, they essentially saying that in future version your application will break. Yes, it is not your package that is responsible, but it still affects your application, you could open a ticket, or submit a PR. If you had that message you should also hold of with upgrading to newer python until this is resolved.
- scoot_718 6y ago> well actually they are, they essentially saying that in future version your application will break. No, you idiot. It's a deprecated usage in a dependency. What happens in the future is I update pandas, it stops using the deprecated numpy method, and the warning just disappears with very little action on my part. It's a useless warning. And submit a PR every time this happens? How about I request you pull me? > If you had that message you should also hold of with upgrading to newer python until this is resolved. 1. Upgrading to newer python? Who fucking cares 2. Upgrading resolves the warning entirely.
- sambe 6y agoYou can file an issue/PR in most cases, and if you don't get a response you may need to worry about moving libraries.