Deprecation warning and eventual removal makes sense for cases where the replacement follows some different programming pattern, like different arguments or different return types, but this particular deprecation appears to be merely a different way of accessing the exact same thing. The diff to add it back in was a seven-line change: https://github.com/urllib3/urllib3/pull/3732/files#diff-008f...
Was it really worth trying to force developers' hands over this in the first place? I doubt users care about the naming purity of the library code. Sure, remove it from the documentation so new users only see the preferred new way, but I would be annoyed if I used this library and had to go around renaming a bunch of call sites just to satisfy upstream's ideological purity drive.
Was it really worth trying to force developers' hands over this in the first place? I doubt users care about the naming purity of the library code. Sure, remove it from the documentation so new users only see the preferred new way, but I would be annoyed if I used this library and had to go around renaming a bunch of call sites just to satisfy upstream's ideological purity drive.