mirror of
https://github.com/spotipy-dev/spotipy.git
synced 2026-04-26 16:15:51 +03:00
[GH-ISSUE #143] Exception on authorization #69
Labels
No labels
api-bug
bug
dependencies
documentation
duplicate
enhancement
external-ide
headless-mode
implicit-grant-flow
invalid
missing-endpoint
pr-welcome
private-api
pull-request
question
spotipy3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotipy#69
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @irskep on GitHub (Jan 2, 2017).
Original GitHub issue: https://github.com/spotipy-dev/spotipy/issues/143
I'm using Python 3.5. I ran the demo code, modified for Python 3:
But when I pasted the URL, I got this exception:
@plamere commented on GitHub (Jan 2, 2017):
what version of requests do you have?
@irskep commented on GitHub (Jan 2, 2017):
Here are the complete contents of my virtualenv:
@irskep commented on GitHub (Jan 2, 2017):
Reading the code, it looks like
SpotifyOAuthnever has a "proxies" attribute assigned to it, yet it tries to access it in a couple of places.@plamere commented on GitHub (Jan 2, 2017):
it is working for me. It is assigned here:
https://github.com/plamere/spotipy/blob/master/spotipy/oauth2.py#L47
Maybe there's some version skew?
@irskep commented on GitHub (Jan 2, 2017):
You linked to where it is assigned in
SpotifyClientCredentials. The problem is it is used inSpotifyOAuth, where it does not exist.@plamere commented on GitHub (Jan 2, 2017):
ah ok, I'll take a look, hang on
@irskep commented on GitHub (Jan 2, 2017):
Note the exception is on line 214, which reads:
self.proxiesdoes not exist on this class! If I remove theproxies=kwarg here and again on line 241, it works.@plamere commented on GitHub (Jan 2, 2017):
ok, should be fixed now, thanks for the report!
@irskep commented on GitHub (Jan 2, 2017):
No problem, thanks for the useful library and being on top of things!