←back to thread

Deprecations via warnings don't work for Python libraries

(sethmlarson.dev)
45 points scolby33 | 1 comments | 08 Dec 25 18:13 UTC | HN request time: 0s | source
Show context
superkuh ◴[10 Dec 25 17:03 UTC] No.46220253[source]▶
>We ended up adding the APIs back and creating a hurried release to fix the issue.

So it was entirely possible to keep the software working with these. Why change/remove them in the first place? Is the benefit of of the new abstraction greater than the downside of requiring everyone using the software to re-write theirs?

replies(2): >>46220931 #>>46221520 #
integralid ◴[10 Dec 25 17:51 UTC] No.46220931[source]▶
OS software maintainers don't like maintaining legacy ugly APIs forever and want to refactor/remove legacy code to keep themselves sane and the project maintainable.
replies(3): >>46221115 #>>46221398 #>>46224920 #
1. superkuh ◴[10 Dec 25 18:04 UTC] No.46221115[source]▶
Yep. Or you can see it as, "This software doesn't really care about the users and their use cases. It prioritizes making things look pretty and easier on the dev side over maintaining functionality." Or in the worse but fairly common OSS case, CADT, but that doesn't seem to apply in this context.