News for hackers. Stuff that matters.

A comment on Python 2.7.18, the last release of Python 2. Parent comment

Re:Python 2.7.18, the last release of Python 2 by xxpor on Monday April 20, 2020 @05:01PM (#22928502)
You're supposed to pay attention to DeprecationWarnings.
[ Parent | on HN ]
Re:Python 2.7.18, the last release of Python 2 by MattGaiser on Monday April 20, 2020 @06:18PM (#22929374)
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.
[ Parent | on HN ]
Re:Python 2.7.18, the last release of Python 2 by xxpor on Monday April 20, 2020 @07:28PM (#22930058)
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.
[ Parent | on HN ]
Re:Python 2.7.18, the last release of Python 2 by scoot_718 on Monday April 20, 2020 @10:36PM (#22931264)
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.

[ Parent | on HN ]
Re:Python 2.7.18, the last release of Python 2 by xxpor on Tuesday April 21, 2020 @10:44AM (#22935334)
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.
[ Parent | on HN ]
Re:Python 2.7.18, the last release of Python 2 by scoot_718 on Monday April 20, 2020 @10:34PM (#22931249)
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.

[ Parent | on HN ]
Re:Python 2.7.18, the last release of Python 2 by takeda on Tuesday April 21, 2020 @12:21AM (#22931837)
They are still important. Because even if dependency has this warning, it will still break your code.
[ Parent | on HN ]
Re:Python 2.7.18, the last release of Python 2 by afiori on Tuesday April 21, 2020 @02:04AM (#22932439)
but they are also not actionable
[ Parent | on HN ]
Re:Python 2.7.18, the last release of Python 2 by sambe on Tuesday April 21, 2020 @12:23PM (#22936383)
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.
[ Parent | on HN ]
Re:Python 2.7.18, the last release of Python 2 by takeda on Tuesday April 21, 2020 @02:49AM (#22932621)
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.

[ Parent | on HN ]
Re:Python 2.7.18, the last release of Python 2 by scoot_718 on Tuesday April 28, 2020 @11:04PM (#23014847)
> 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.

[ Parent | on HN ]