* Added test_categories_country to use optional country selection for categories method.
* Added test_categories_locale for testing locale method of categories.
* Added test_categories_limit_low and test_categories_limit_high to test the limit method of categories for edge cases.
* Rearranged for flow
* Added test_category_playlists_limit_low and test_category_playlists_limit_high for testing the limit method.
* fixed docstring for current_user_following_users_function
* Edited docstrings for playlist_cover_image, user_playlist, user_playlist_replace_tracks, user_playlist_reorder_tracks functions
* expanded docstring description of playlist_change_details function to include changes to collaborative state and/or description
For a final assignment in a class, I've created a How-To video that showcases how to get setup with API credentials, Redirect URIs, and Spotify Developer Accounts, all of which are necessary prerequisites to using the Spotipy library.
I wanted to do this because, in my past experience, the most frustrating thing about working with APIs and libraries is authentication. Spotipy does a nice job of wrapping some of this and making it easier on the developer, but it still takes some setup before successful use.
Specifically, my video goes through the following:
* Installing Spotipy
* Setting up a Spotify Developer Account
* Configuring the Redirect URI
* Getting the Client Secret and Public Keys
* Setting the envars for use with Spotipy
* Running a sample piece of code from Spotipy to show that things are setup properly
* Updated references to ISO 639 standard to clarify that the ISO 639-1 alpha-2 standard is used.
* Added `market` parameter to `album` and `albums`
* fix formatting change
playlist_items(), playlist_cover_image() functions can take ID, URI or URL. Current docstring only mentions ID. This can also be verified and tested out. Example in examples folder also uses URI with playlist_items().
Not sure how to edit RSt properly, but wanted to point out for others the superhelpful feature that spotipy already includes code to launch an http server to listen for the http callback
* Fixed a bug in the initializers for the auth managers that produced a spurious warning message if you provide a cache handler and you set a value for the "SPOTIPY_CLIENT_USERNAME" environment variable.
* fixed a bug in _get_auth_response_local_server which occurs if you provide a state parameter and click cancel in the authorization dialog
* Fallback on decoding the error response body into text if decoding into JSON fails.
* Fall back on decoding oauth errors into text if decoding into JSON fails.
* Fixed unused `http_error` name in exeception clause.
* Updated CHANGELOG
Co-authored-by: Stéphane Bruckert <stephane.bruckert@gmail.com>
* Added DjangoSessionCacheHandler
Added `DjangoSessionCacheHandler`, a cache handler that stores the token in the session framework provided by Django. Web apps using spotipy with Django can directly use this for cache handling.
* removed whitespaces
* Added `MemoryCacheHandler`, a cache handler that simply stores the token info in memory as an instance attribute of this class.
* Fixed a bug in `CacheFileHandler.__init__`: The documentation says that the username will be retrieved from the environment, but it wasn't.
