(Please don't set keywords/CC arches yet.) ISTR we thought there might be problems with stabilizing newer requests because the API changed significantly in 1.x. Did this actually happen? I don't recall many problems. It would be nice to stabilize something newer than 0.13.
This would also need a stable =dev-python/charade-1.0.3.
Current stable also fails its tests, because it tries to contact the site https://kennethreitz.com (why this site?), which doesn't have a https setup. I hope a newer version would fix this.
Yes, there was a big API change. Someone should test any stable reverse dependencies of dev-python/requests to see if they work.
(In reply to Myckel Habets from comment #2) > https://kennethreitz.com (why this site?) Because Kenneth Reitz is the original author of the requests package.
Initial results of a coarse grep: dev-python/discogs-client dev-python/python-cinderclient dev-python/python-keystoneclient dev-python/python-novaclient dev-python/requests dev-python/requests-cache dev-python/sphinxcontrib-issuetracker dev-python/urllib3 dev-python/wsgiproxy2 dev-util/howdoi media-video/subliminal net-misc/flexget net-misc/httpie sys-cluster/nova www-apps/nikola www-servers/pathod
None of those packages with a stable keyword fail to build against 1.2.0
Alright, let's go.
Also needs =dev-python/charade-1.0.3.
Could you please specify the versions of the packages?
The list in comment 5 are RDEPs. We only need to stabilize requests-1.2.3 and charade-1.0.3.
amd64 stable
x86 stable. Last arch, closing
