René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Why requests return a separate `status`?","articleBody":"According to your [official docs](https://help.smartling.com/hc/en-us/articles/4412947322267#MakingAPIrequests), requests return a tuple of `(response, status)`. This is counter-intuitive for me because HTTP status is already present as a property of `response`, even if the response is other than `2xx`:\r\n```python\r\nIn [25]: resp, status = jobs_api.getJobDetails('foo')\r\nNon 200 response:404   RequestId:Unknown   URL:https://api.smartling.com/jobs-api/v3/projects/3bea86d16/jobs/foo   response:b'{\"response\":{\"code\":\"NOT_FOUND_ERROR\",\"errors\":[{\"key\":\"not.found\",\"message\":\"Translation job is not found\",\"details\":null}]}}'\r\n\r\nIn [26]: resp.statusCode\r\nOut[26]: 404\r\n\r\nIn [27]: resp.statusCode == status\r\nOut[27]: True\r\n```\r\n\r\nThat makes it slightly less convenient to use because for each request I would need to remember to ignore `status` via `resp, _ = …`.\r\n\r\n**Or is there a reason `status` is separate and I should prefer it over `resp.statusCode`?**","author":{"url":"https://github.com/Toreno96","@type":"Person","name":"Toreno96"},"datePublished":"2023-10-12T13:27:56.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/58/api-sdk-python/issues/58"}