←back to thread

Deprecations via warnings don't work for Python libraries

(sethmlarson.dev)
45 points scolby33 | 2 comments | 08 Dec 25 18:13 UTC | HN request time: 0.386s | source
Show context
traverseda ◴[10 Dec 25 17:12 UTC] No.46220387[source]▶
Wait, does urlib not use semvar? Don't remove APIs on minor releases people. A major release doesn't have to be a problem or a major redesign, you can do major release 400 for all I care, just don't break things on minor releases.

Lots of things not using semvar that I always just assumed did.

replies(5): >>46220669 #>>46220824 #>>46221051 #>>46221272 #>>46224206 #
1. CaliforniaKarl ◴[10 Dec 25 18:16 UTC] No.46221272[source]▶
This, I think, is the crux of the matter.

As an example, I always knew urllib3 as one of the foundational packages that Requests uses. And I was curious, what versions of urllib3 does Requests pull in?

Well, according to https://github.com/psf/requests/blob/main/setup.cfg, it's this:

    urllib3>=1.21.1,<3
That is exactly the kind of dependency specification I would expect to see for a package that is using semver: The current version of urllib3 is 2.x, so with semver, you set up your dependencies to avoid the next major-version number (in this case, 3).

So, it seems to me that even the Requests folks assumed urllib3 was using semver.

replies(1): >>46223906 #
2. somat ◴[10 Dec 25 21:10 UTC] No.46223906[source]▶
I would almost expect the 3 in urllib3 to be the major version and if something needed to break it would become urllib4. Which, I know, is terribly naive of me. But that is how psycopg does it.