That article isn't really advocating handling _all_ errors as values AFAICS - it just doesn't distinguish between _exceptional_ and _normal but unsuccessful_ paths.
For a wrapper around an HTTP transport, returning HTTP responses instead of raising an exception for stuff like "403 Forbidden" is probably reasonable. Their own example code is full of exceptions, though.
@Sternout@jnovinger
Maybe, but (apart from the "Accidental Immortalisation" case mentioned in PEP 683) these things are created deliberately by C extensions.
A sane extension shouldn't be building loads of them on the fly in the first place.
@FinishingDutch @ahornsirup
But Wikipedia aren't charging people to see the work you contributed for free. That's a significant difference.
@SittingWave @mac
That article isn't really advocating handling _all_ errors as values AFAICS - it just doesn't distinguish between _exceptional_ and _normal but unsuccessful_ paths.
For a wrapper around an HTTP transport, returning HTTP responses instead of raising an exception for stuff like "403 Forbidden" is probably reasonable. Their own example code is full of exceptions, though.
@amanaftermidnight Logo was originally designed as a teaching language, and that's where the turtle graphics came from.
@Sternout @jnovinger
Maybe, but (apart from the "Accidental Immortalisation" case mentioned in PEP 683) these things are created deliberately by C extensions.
A sane extension shouldn't be building loads of them on the fly in the first place.