Why do libraries such as Requests or HTTPX not support this out of the box? It would be really useful to have automatic warning or sentry event after deprecation response.
I understand that this functionality can be easily added as a plugin, but not everyone is aware that such a thing even exists. With default support, it will be easier to upgrade to new API versions and keep stuff up to date.
bayindirh•11h ago
I'll argue that if these features are more widely known and respected, we wouldn't need to re-invent these kinds of elegant solutions with clunky and thick stacks, over and over again.
AlienRobot•10h ago
I'll argue that the major problem with everything in software is that there is no place for random developers to discuss standards they might want to implement
For example, if drag and drop and copy and paste didn't exist, it probably wouldn't be created today because you need 2 programs to agree on accepting the format (you can't even drag and drop from most software except file managers...). And even conventions that ALREADY exist are being forgotten with every year.
tialaramex•7h ago
Isn't there though? I feel as though actually there usually is a place to ask if you bothered to do so and the trouble is more than people don't even check.
pimterry•9h ago
I suggested exactly that (for the closely related Deprecation header) to Requests a few years ago, they feel it's the application's responsibility, discussion here: https://github.com/psf/requests/issues/5724
It's nice when tooling builds this sort of stuff in, because it also encourages APIs to implement it.
tveita•7h ago
How would it behave? The standard as written doesn't suggest any appropriate client behaviour.
It explicitly doesn't have to mean deprecation, the standard says it could also be returned from any short-lived resource. There's no way to see if the header applies to the whole server or just the specific resource or even query parameters, and no way to deduplicate to ignore known warnings.
aiven•12h ago
I understand that this functionality can be easily added as a plugin, but not everyone is aware that such a thing even exists. With default support, it will be easier to upgrade to new API versions and keep stuff up to date.
bayindirh•11h ago
AlienRobot•10h ago
For example, if drag and drop and copy and paste didn't exist, it probably wouldn't be created today because you need 2 programs to agree on accepting the format (you can't even drag and drop from most software except file managers...). And even conventions that ALREADY exist are being forgotten with every year.
tialaramex•7h ago
pimterry•9h ago
treve•9h ago
It's nice when tooling builds this sort of stuff in, because it also encourages APIs to implement it.
tveita•7h ago
It explicitly doesn't have to mean deprecation, the standard says it could also be returned from any short-lived resource. There's no way to see if the header applies to the whole server or just the specific resource or even query parameters, and no way to deduplicate to ignore known warnings.