←back to thread

Deprecations via warnings don't work for Python libraries

(sethmlarson.dev)
61 points scolby33 | 1 comments | 08 Dec 25 18:13 UTC | HN request time: 0.277s | source
Show context
theamk ◴[08 Dec 25 18:24 UTC] No.46195792[source]▶
Deprecations via warnings don't reliably work anywhere, in general.

If you are a good developer, you'll have extensive unit test coverage and CI. You never see the unit test output (unless they fail) - so warnings go unnoticed.

If you are a bad developer, you have no idea what you are doing and you ignore all warnings unless program crashes.

replies(8): >>46196064 #>>46197215 #>>46203939 #>>46220846 #>>46221176 #>>46221435 #>>46221650 #>>46221723 #
Hizonner ◴[10 Dec 25 18:26 UTC] No.46221435[source]▶
If you are a good developer, you consider warnings to be errors until proven otherwise.
replies(1): >>46221912 #
hiq ◴[10 Dec 25 18:58 UTC] No.46221912[source]▶
What does a good developer do when working in a codebase with hundreds of warnings?

Or are you only considering a certain warnings?

replies(1): >>46222489 #
Hizonner ◴[10 Dec 25 19:34 UTC] No.46222489[source]▶
Why does your codebase generate hundreds of warnings, given that every time one initially appeared, you should have stamped it out (or specifically marked that one warning to be ignored)? Start with one line of code that doesn't generate a warning. Add a second line of code that doesn't generate a warning...
replies(3): >>46224192 #>>46224495 #>>46224683 #
stackskipton ◴[10 Dec 25 21:33 UTC] No.46224192[source]▶
Because most people are working at Failure/Feature factories where they might work on something and at last minute, they find out something is now warning. If they work on fixing it, the PM will screaming about time slippage and be like "I want you to work on X, not Y which can wait".

2 Years later, you have hundreds of warning.

replies(1): >>46227382 #
1. Hizonner ◴[11 Dec 25 03:39 UTC] No.46227382[source]▶
You found that out at the last minute. So then you did a release. It's no longer the last minute. Now what's your excuse for the next release?

If your management won't resource your project to the point where you can assure that the software is correct, you might want to see if you can find the free time to look for another job. You'll have to do that anyway when they either tank the company, or lay you off next time they feel they need to cut more costs.