[GH-ISSUE #282] hide the Request-Response Information printed out, while wanted #156

Closed
opened 2026-02-27 23:21:07 +03:00 by kerem · 3 comments
Owner

Originally created by @smyrbdr on GitHub (May 2, 2018).
Original GitHub issue: https://github.com/spotipy-dev/spotipy/issues/282

Hi,
I asked this question on StackOverflow, and not sure it is an issue related to requests package or another general .ipynb setting. If this is so, excuse me.

So the issue is while I call any function from Spotipy, I first get the long outputs as below printed out each time;

headers {' #some info here

http status 200

GET https://api. ... # GET request link here

RESP { ... # a lot of (sometimes undesired) output printed here

This info is sometimes useful. But sometimes we may want to clear them from the outputs.
Something like setting a parameter to silent. Is it possible to hide the above outputs by requests?

Originally created by @smyrbdr on GitHub (May 2, 2018). Original GitHub issue: https://github.com/spotipy-dev/spotipy/issues/282 Hi, I asked [this question](https://stackoverflow.com/questions/50142357/how-to-hide-the-request-response-cycle-information-from-the-outputs-in-ipynb-s?) on StackOverflow, and not sure it is an issue related to requests package or another general .ipynb setting. If this is so, excuse me. So the issue is while I call any function from Spotipy, I first get the long outputs as below printed out each time; ```headers {' #some info here``` ```http status 200``` ```GET https://api. ... # GET request link here``` ```RESP { ... # a lot of (sometimes undesired) output printed here``` This info is sometimes useful. But sometimes we may want to clear them from the outputs. Something like setting a parameter to silent. Is it possible to hide the above outputs by requests?
kerem closed this issue 2026-02-27 23:21:07 +03:00
Author
Owner

@smyrbdr commented on GitHub (May 2, 2018):

It is suddenly solved I don't know why and how, after running the kernel multiple times

<!-- gh-comment-id:386138246 --> @smyrbdr commented on GitHub (May 2, 2018): It is suddenly solved I don't know why and how, after running the kernel multiple times
Author
Owner

@shillshocked commented on GitHub (Oct 23, 2019):

I'm getting this too, now that I added:

client_credentials_manager = SpotifyClientCredentials()

sp = spotipy.Spotify(client_credentials_manager=client_credentials_manager)
<!-- gh-comment-id:545244568 --> @shillshocked commented on GitHub (Oct 23, 2019): I'm getting this too, now that I added: ``` client_credentials_manager = SpotifyClientCredentials() sp = spotipy.Spotify(client_credentials_manager=client_credentials_manager) ```
Author
Owner

@shillshocked commented on GitHub (Oct 23, 2019):

Ah, got it to go away with:

sp.trace = False

<!-- gh-comment-id:545249911 --> @shillshocked commented on GitHub (Oct 23, 2019): Ah, got it to go away with: `sp.trace = False`
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
starred/spotipy#156
No description provided.