Spotipy

Latest version: v2.24.0

Safety actively analyzes 688896 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 10

2.15.0

Not secure
Added

- `SpotifyPKCE.parse_auth_response_url`, mirroring that method in
`SpotifyOAuth`

Changed

- Specifying a cache_path or username is now optional

Fixed

- Using `SpotifyPKCE.get_authorization_url` will now generate a code
challenge if needed

2.14.0

Not secure
Added

- (experimental) Support to search multiple/all markets at once.
- Support to test whether the current user is following certain
users or artists
- Proper replacements for all deprecated playlist endpoints
(See https://developer.spotify.com/community/news/2018/06/12/changes-to-playlist-uris/ and below)
- Allow for OAuth 2.0 authorization by instructing the user to open the URL in a browser instead of opening the browser.
- Reason for 403 error in SpotifyException
- Support for the PKCE Auth Flow
- Support to advertise different language to Spotify
- Added 'collaborative' parameter to user_playlist_create method.
- Enforce CHANGELOG update on PR
- Adds `additional_types` parameter to retrieve currently playing podcast episode
- Support to get info about a single category

Deprecated

- `user_playlist_change_details` in favor of `playlist_change_details`
- `user_playlist_unfollow` in favor of `current_user_unfollow_playlist`
- `user_playlist_add_tracks` in favor of `playlist_add_items`
- `user_playlist_replace_tracks` in favor of `playlist_replace_items`
- `user_playlist_reorder_tracks` in favor of `playlist_reorder_items`
- `user_playlist_remove_all_occurrences_of_tracks` in favor of
`playlist_remove_all_occurrences_of_items`
- `user_playlist_remove_specific_occurrences_of_tracks` in favor of
`playlist_remove_specific_occurrences_of_items`
- `user_playlist_follow_playlist` in favor of
`current_user_follow_playlist`
- `user_playlist_is_following` in favor of `playlist_is_following`
- `playlist_tracks` in favor of `playlist_items`

Fixed

- fixed issue where episode URIs were being converted to track URIs in playlist calls

2.13.0

Not secure
Added

- Added `SpotifyImplicitGrant` as an auth manager option. It provides
user authentication without a client secret but sacrifices the ability
to refresh the token without user input. (However, read the class
docstring for security advisory.)
- Added built-in verification of the `state` query parameter
- Added two new attributes: error and error_description to `SpotifyOauthError` exception class to show
authorization/authentication web api errors details.
- Added `SpotifyStateError` subclass of `SpotifyOauthError`
- Allow extending `SpotifyClientCredentials` and `SpotifyOAuth`
- Added the market parameter to `album_tracks`

Deprecated

- Deprecated `util.prompt_for_user_token` in favor of `spotipy.Spotify(auth_manager=SpotifyOAuth())`

2.12.0

Not secure
Added

- Added a method to update the auth token.

Fixed

- Logging regression due to the addition of `logging.basicConfig()` which was unneeded.

2.11.2

Not secure
Changed

- Updated the documentation to give more details on the authorization process and reflect
2020 Spotify Application jargon and practices.

- The local webserver is only started for localhost redirect_uri which specify a port,
i.e. it is started for `http://localhost:8080` or `http://127.0.0.1:8080`, not for `http://localhost`.

Fixed

- Issue where using `http://localhost` as redirect_uri would cause the authorization process to hang.

2.11.1

Not secure
Fixed

- Fixed miscellaneous issues with parsing of callback URL

Page 3 of 10

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.