[PR #391] [CLOSED] allow for incorrect retry-after approximation from spotify #876

New issue

Closed

opened 2026-02-28 00:02:19 +03:00 by kerem · 0 comments

kerem commented

2026-02-28 00:02:19 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/spotipy-dev/spotipy/pull/391
Author: @darajava
Created: 7/25/2019
Status: ❌ Closed

Base: master ← Head: fix-retry

📝 Commits (1)

8160ac8 allow for incorrect retry-after approximation from spotify

📊 Changes

1 file changed (+2 additions, -2 deletions)

View changed files

📝 spotipy/client.py (+2 -2)

📄 Description

Spotify convert from millis to seconds and then floor it to give the retry-after time. This leads to multiple retrys sometimes when using their retry-after time. This adds a second so that that shouldn't happen.

Great work btw!

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/spotipy-dev/spotipy/pull/391 **Author:** [@darajava](https://github.com/darajava) **Created:** 7/25/2019 **Status:** ❌ Closed **Base:** `master` ← **Head:** `fix-retry` --- ### 📝 Commits (1) - [`8160ac8`](https://github.com/spotipy-dev/spotipy/commit/8160ac80057e940ab96b24ccf84a8ce853a0964b) allow for incorrect retry-after approximation from spotify ### 📊 Changes **1 file changed** (+2 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `spotipy/client.py` (+2 -2) </details> ### 📄 Description Spotify convert from millis to seconds and then floor it to give the retry-after time. This leads to multiple retrys sometimes when using their retry-after time. This adds a second so that that shouldn't happen. Great work btw! --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>