[GH-ISSUE #90] Spotipy Object is not threadsafe with respect to request sessions and connection pools #40

New issue

Closed

opened 2026-02-27 23:20:32 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 23:20:32 +03:00

Owner

Originally created by @jdwilkin on GitHub (Apr 15, 2016).
Original GitHub issue: https://github.com/spotipy-dev/spotipy/issues/90

When a single Spotipy object is used in multiple threads talking to the same endpoint, depending on timing, connection pool closed errors can occur. This happens because after every request made in _internal_call "close" is called on the request connection which in turn closes the session's pool for that end point. If another thread has already come in and been given a reference to that pool then tries to use it later, it will get this pool closed exception

Originally created by @jdwilkin on GitHub (Apr 15, 2016). Original GitHub issue: https://github.com/spotipy-dev/spotipy/issues/90 When a single Spotipy object is used in multiple threads talking to the same endpoint, depending on timing, connection pool closed errors can occur. This happens because after every request made in _internal_call "close" is called on the request connection which in turn closes the session's pool for that end point. If another thread has already come in and been given a reference to that pool then tries to use it later, it will get this pool closed exception

kerem closed this issue

2026-02-27 23:20:33 +03:00

kerem commented

2026-02-27 23:20:33 +03:00

Author

Owner

@jdwilkin commented on GitHub (May 12, 2016):

after going through the pull requests it seems there is already one that addresses this, (at least it appears to) #68

@jdwilkin commented on GitHub (May 12, 2016): after going through the pull requests it seems there is already one that addresses this, (at least it appears to) #68

kerem commented

2026-02-27 23:20:33 +03:00

Author

Owner

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

Yeah, it's still an issue. This repo doesn't seem to be properly maintained any more as pull requests aren't being honored.

@shillshocked commented on GitHub (Oct 23, 2019): Yeah, it's still an issue. This repo doesn't seem to be properly maintained any more as pull requests aren't being honored.

kerem commented

2026-02-27 23:20:33 +03:00

Author

Owner

@stephanebruckert commented on GitHub (Jan 17, 2020):

Hey @shillshocked, @jdwilkin, thanks for reporting this. The package is maintained again, any chance you can create a new PR?

@stephanebruckert commented on GitHub (Jan 17, 2020): Hey @shillshocked, @jdwilkin, thanks for reporting this. The package is maintained again, any chance you can create a new PR?