←back to thread

Deprecations via warnings don't work for Python libraries

(sethmlarson.dev)
60 points scolby33 | 1 comments | 08 Dec 25 18:13 UTC | HN request time: 0.2s | 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 #
eternityforest ◴[08 Dec 25 20:29 UTC] No.46197215[source]▶
Why is it that CI tools don't make warnings visible? Why are they ignored by default in the first place? Seems like that should be a rather high priority.
replies(3): >>46220771 #>>46220984 #>>46224332 #
1. michaelt ◴[10 Dec 25 21:47 UTC] No.46224332[source]▶
> Why is it that CI tools don't make warnings visible?

A developer setting up CI decides to start an ubuntu 24.04 container and run 'apt-get install npm'

This produces 3,600 lines of logging (5.4 log lines per package, 668 packages) and 22 warnings (all warnings about man page creation being skipped)

Then they decide "Nobody's going to read all that, and the large volume might bury important information. I think I'll hide console output for processes that don't fail."

Now your CI doesn't show warnings.