Issues with Requests 1.0.* #140

Closed
opened 2013-01-07 07:20:20 -08:00 by simondlr · 1 comment
simondlr commented 2013-01-07 07:20:20 -08:00 (Migrated from github.com)

There's a lot of problems with the latest requests.

I've started going through them. For example. OAuth1 has been removed into another 3rd-party lib, requests_oauthlib, that has to be included.

Request sessions also don't allow you to pass kwargs anymore. I'm slowly going through and trying to fix what's wrong, but I'm not that clued up on the inner workings of requests, so it is taking some time. If someone else wants to step up and fix it, it would be appreciated. Until then, it's probably best to use an older version of requests for your app.

There's a lot of problems with the latest requests. I've started going through them. For example. OAuth1 has been removed into another 3rd-party lib, requests_oauthlib, that has to be included. Request sessions also don't allow you to pass kwargs anymore. I'm slowly going through and trying to fix what's wrong, but I'm not that clued up on the inner workings of requests, so it is taking some time. If someone else wants to step up and fix it, it would be appreciated. Until then, it's probably best to use an older version of requests for your app.
U2Ft commented 2013-01-18 10:30:47 -08:00 (Migrated from github.com)

Is there anything these changes don't fix with requests 1.1.0 and the requests-oauthlib on GitHub?

Is there anything [these changes](https://gist.github.com/4566892) don't fix with requests 1.1.0 and the requests-oauthlib on GitHub?
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: code/twython#140
No description provided.