←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
hartator ◴[10 Dec 25 17:58 UTC] No.46221036[source]▶
I think they are misreading the situation.

The devil is in the details. It seems `getHeaders` v. `headers` is non-security, non-performance related issue. Why people should spend time fixing these?

replies(2): >>46221216 #>>46223911 #
attractivechaos ◴[10 Dec 25 21:11 UTC] No.46223911[source]▶
Even if getHeaders() has security/performance concerns, the better solution is to make it an alias to the newer headers.get() in this case. Keeping the old API is a small hassle to a handful of developers but breaking existing code puts a much bigger burden on a lot more users.
replies(1): >>46224093 #
1. nodesocket ◴[10 Dec 25 21:25 UTC] No.46224093[source]▶
Ya, why not just alias old api calls to the new if implementation details changed?