3 ms·

You're supposed to pay attention to DeprecationWarnings.

by xxpor 7y ago

MattGaiser 7y ago
The problem is that the entire ecosystem needs to pay attention to such warnings and it doesn't happen. As a result, these changes end up breaking code in places the program authors never touched.
- xxpor 7y ago
  That's true in one respect, but you as an end user can use them to know not to upgrade before your deps have changed what they need to.
  - scoot_718 7y ago
    What? You upgrade your dependencies when there's a feature or improvement you need. Not because they don't have some warnings. Who cares? The old version you implicitly claim is better isn't, it just doesn't have the warnings from their dependencies in place yet.
    - xxpor 7y ago
      I mean, if you're going to upgrade your python version, you should check your logs to see if you have had any DWs recently. If you have, upgrade your deps before upgrading python. If theres no new version available, you can't upgrade python yet.
scoot_718 7y 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 7y ago
  They are still important. Because even if dependency has this warning, it will still break your code.
  - afiori 7y ago
    but they are also not actionable
    - takeda 7y ago
      well 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 7y 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 7y ago
      You can file an issue/PR in most cases, and if you don't get a response you may need to worry about moving libraries.

You're supposed to pay attention to DeprecationWarnings.

by xxpor 7y ago

You're supposed to pay attention to DeprecationWarnings.

The problem is that the entire ecosystem needs to pay attention to such warnings and it doesn't happen. As a result, these changes end up breaking code in places the program authors never touched.

xxpor 7y ago
That's true in one respect, but you as an end user can use them to know not to upgrade before your deps have changed what they need to.
- scoot_718 7y ago
  What? You upgrade your dependencies when there's a feature or improvement you need. Not because they don't have some warnings. Who cares? The old version you implicitly claim is better isn't, it just doesn't have the warnings from their dependencies in place yet.
  - xxpor 7y ago
    I mean, if you're going to upgrade your python version, you should check your logs to see if you have had any DWs recently. If you have, upgrade your deps before upgrading python. If theres no new version available, you can't upgrade python yet.

scoot_718 7y 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 7y ago
They are still important. Because even if dependency has this warning, it will still break your code.
- afiori 7y ago
  but they are also not actionable
  - takeda 7y ago
    well 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 7y 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 7y ago
    You can file an issue/PR in most cases, and if you don't get a response you may need to worry about moving libraries.