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.
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.
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.