Declare the pyspotify project as dead.
Add support for Python 3.9 and 3.10. No changes was required, but the test suite now runs on these versions too. (PR: #203)
Switch from CircleCI to GitHub Actions.
Document that the playlists API is broken. If it is used, emit a warning to notify the user of the playlist functionality.
Update project links.
Silently abort libspotify
sp_*_release()function calls that happen during process shutdown, after pyspotify’s global lock is freed. (Fixes: #202)
Add support for Python 3.8. No changes was required, but the test suite now runs on this version too.
Switch from Travis CI to CircleCI.
Drop support for Python 3.3 and 3.4, as both has reached end of life.
Add support for Python 3.6 and 3.7. No changes was required, but the test suite now runs on these versions too.
Document that the search API is broken. If it is used, raise an exception instead of sending the search to Spotify, as that seems to disconnect your session. (Fixes: #183)
Format source code with Black.
Bug fix release.
To follow up on the previous release, the getters for the proxy configs now convert empty strings in the
sp_session_configstruct back to
None. Thus, the need to set these configs to empty strings in the struct to make sure the cached settings are cleared from disk are now an internal detail, hidden from the user of pyspotify.
Noneand set to
NULLin the libspotify config struct. If it is set to an empty string by default, libspotify will try to use a file with an empty filename for cache and fail with “LibError: Unable to open trace file”. Now empty strings are set as
sp_session_configstruct. (Fixes: mopidy-spotify#70)
libspotify segfaults if the
device_idconfig is set to an empty string. We now avoid this segfault if
device_idis set to an empty string by setting the
device_idfield in libspotify’s
As some test tools (like coverage.py 4.0) no longer support Python 3.2, we no longer test pyspotify on Python 3.2. Though, we have not done anything to intentionally break support for Python 3.2 ourselves.
Bug fix release.
It has been observed that libspotify will reuse cached proxy settings from previous sessions if the proxy fields on the
sp_session_configstruct are set to
NULL. When the
sp_session_configfields are set to an empty string, the cached settings are updated. When attributes on
spotify.Configare set to
None, we now set the fields on
sp_session_configto empty strings instead of
Bug fix release.
Bug fix release.
sp_session_starred_for_user_create(session, username)instead of
sp_playlist_create(session, link)to get starred playlists by URI. The previous approach caused segfaults under some circumstances. (Fixes: mopidy-spotify#60)
Bug fix release.
spotify.Session.get_playlist()acquire the global lock before modifying the global playlist cache.
PlaylistContainerregister callbacks with libspotify if and only if a Python event handler is added to the object. Previously, we always registered the callbacks with libspotify. Hopefully, this will remove the preconditions for the crashes in #122, #153, and #165.
pyspotify 2.x is a full rewrite of pyspotify. While pyspotify 1.x is a CPython C extension, pyspotify 2.x uses CFFI to wrap the libspotify C library. It works on CPython 2.7 and 3.2+, as well as PyPy 2.6+. pyspotify 2.0 makes 100% of the libspotify 12.1.51 API available from Python, going far beyond the API coverage of pyspotify 1.x.
The following are the changes since pyspotify 2.0.0b5.
deviceto align with pyalsaaudio 0.8.
Updated to work with pyalsaaudio 0.8 which changed the signature of
spotify.AlsaSinkstill works with pyalsaaudio 0.7, but 0.8 is recommended at least for Python 3 users, as it fixes a memory leak present on Python 3 (see #127). (Fixes: #162)
A fifth beta with a couple of bug fixes.
The fourth beta includes a single API change, a couple of API additions, and otherwise minor tweaks to logging.
pyspotify 2.x has been verified to work on PyPy3, and PyPy3 is now part of the test matrix.
spotify.Link.urlwhich returns an
https://open.spotify.com/...URL for the link object.
errorlevel log messages to include the word “Spotify” or “pyspotify” for context in applications not including the logger name in the log.
debuglevel messages have not been changed, as it is assumed that more details, including the logger name, is included in debug logs.
spotify.player.Player.statewhich is maintained by calls to the various
spotify.Playlist.reorder_tracks(). It now accepts a list of track indexes instead of a list of tracks. This makes it possible to reorder any of multiple identical tracks in a playlist and is consistent with
spotify.Playlist.remove_tracks(). (Fixes: #134)
Fix pause/resume/stop in the
examples/shell.pyexample. (PR: #140)
Errors passed to session callbacks are now logged with the full error type representation, instead of just the integer value. E.g. where previously only “8” was logged, we now log “<ErrorType.UNABLE_TO_CONTACT_SERVER: 8>”.
The third beta includes a couple of changes to the API in the name of consistency, as well as three minor improvements.
Also worth noticing is that with this release, pyspotify 2.x has been in development for a year and a day. Happy birthday, pyspotify 2!
Refactoring: Connection cleanup¶
spotify.Session.offline has been
set_connection_type()has been replaced by
session.connection.type, which now also allows reading the current connection type.
set_connection_rules()has been replaced by:
The new attributes allow reading the current connection rules, so your application don’t have to keep track of what rules it has set.
session.connection_statehas been replaced by
Refactoring: position vs index¶
Originally, pyspotify named everything identically with libspotify and have thus ended up with a mix of the terms “position” and “index” for the same concept. Now, we use “index” all over the place, as that’s also the name used in the Python world at large. This changes the signature of three methods, which may affect you if you use keyword arguments to call the methods. There’s also a number of affected events, but these changes shouldn’t stop your code from working.
Affected functions include:
Affected events include:
load()methods now return the object if it is already loaded, even if
LOGGED_IN. Previously, a
RuntimeErrorwas raised requiring the session to be logged in and online before loading already loaded objects.
spotify.Playlist.tracksnow implements the
collections.MutableSequencecontract, supporting deleting items with
del playlist.tracks[i], adding items with
playlist.tracks[i] = track, etc.
spotify.Session.get_link()and all other methods accepting Spotify URIs now also understand open.spotify.com and play.spotify.com URLs.
The second beta is a minor bug fix release.
spotify.Playlist.remove_tracks. It now accepts a list of track positions instead of a list of tracks. This makes it possible to remove any of multiple identical tracks in a playlist. (Fixes: #128)
Make all objects compare as equal and have the same hash if they wrap the same libspotify object. This makes it possible to find the index of a track in a playlist by doing
playlist.tracksis a custom collection always returning new
Trackinstances. (Related to: #128)
spotify.Config.ca_certs_filenamenow works on systems where libspotify has this field. On systems where this field isn’t present in libspotify, assigning to it will have no effect. Previously, assignment to this field was a noop on all platforms because the field is missing from libspotify on OS X.
pyspotify 2.x is a full rewrite of pyspotify. While pyspotify 1.x is a CPython C extension, pyspotify 2.x uses CFFI to make 100% of the libspotify C library available from Python. It works on CPython 2.7 and 3.2+, as well as PyPy 2.1+.
Since the previous release, pyspotify has become thread safe. That is,
pyspotify can safely be used from multiple threads. The added thread safety
made an integrated event loop possible, which greatly simplifies the usage of
pyspotify, as can be seen from the updated example in
Audio sink helpers for ALSA and PortAudio have been added, together with
updated examples that can play music. A number of bugs have been fixed, and at
the time of the release, there are no known issues.
The pyspotify 2.0.0b1 release marks the completion of all planned features for pyspotify 2.x. The plans for the next releases are focused on fixing bugs as they surface, incrementally improving the documentation, and integrating feedback from increased usage of the library in the wild.
Feature: Thread safety¶
Hold the global lock while we are working with pointers returned by libspotify. This ensures that we never call libspotify from another thread while we are still working on the data returned by the previous libspotify call, which could make the data garbage.
Ensure we never edit shared data structures without holding the global lock.
Feature: Event loop¶
spotify.EventLoophelper thread that reacts to
NOTIFY_MAIN_THREADevents and calls
process_events()for you when appropriate.
examples/shell.pyto be a lot simpler with the help of the new event loop.
Feature: Audio playback¶
spotify.AlsaSink, an audio sink for playback through ALSA on Linux systems.
spotify.PortAudioSink, an audio sink for playback through PortAudio on most platforms, including Linux, OS X, and Windows.
examples/shell.pyto use the ALSA sink to play music.
examples/play_track.pyas a simpler example of audio playback.
Refactoring: Remove global state¶
To prepare for removing all global state, the use of the module attribute
spotify.session_instance has been replaced with explicit passing of the
session object to all objects that needs it. To allow for this, the following
new methods have been added, and should be used instead of their old
Refactoring: Consistent naming of
spotify.Session.starred_for_user()is replaced by
spotify.Session.starredto get the currently logged in user’s starred playlist is replaced by
get_starred()without any arguments.
published_playlists_for_user(). As previously, it returns the published playlists for the currently logged in user if no username is provided.
Refactoring: Consistent naming of
threading.Event objects have been renamed to be consistently
named across classes.
Refactoring: Change how to register image load listeners¶
pyspotify has two main schemes for registering listener functions:
Objects that only emit an event when it is done loading, like
Toplist, accept a single callback as a
callbackargument to its constructor or constructor methods.
Objects that have multiple callback events, like
Playlist, accept the registration and unregistration of one or more listener functions for each event it emits. This can happen any time during the object’s life cycle.
Due to pyspotify’s close mapping to libspotify’s organization,
objects used to use a third variant with two methods,
remove_load_callback(), for adding and removing load
callbacks. These methods have now been removed, and
callback argument to its constructor and constructor methods:
spotify.ArtistBrowser.portraits()is now a method and accepts a
spotify.Playlist.image()is now a method and accepts a
Remove multiple extra
sp_link_add_ref()calls, potentially causing memory leaks in libspotify.
Add missing error check to
Keep album, artist, image, inbox, search, and toplist objects alive until their complete/load callbacks have been called, even if the library user doesn’t keep any references to the objects. (Fixes: #121)
Fix flipped logic causing crash in
spotify.Album.cover_link(). (Fixes: #126)
Work around segfault in libspotify if
private_sessionis set before the session is logged in and the first events are processed. This is a bug in libspotify which has been reported to Spotify through their IRC channel.
Multiple attributes on
Trackraised an exception if accessed before the track was loaded. They now return
Noneor similar as documented.
Fix segfault when creating local tracks without all arguments specified.
NULLwas used as the placeholder instead of the empty string.
Support negative indexes on all custom sequence types. For example,
collection[-1]returns the last element in the collection.
We now cache playlists when created from URIs. Previously, only playlists created from
sp_playlistobjects were cached. This avoids a potentially large number of wrapper object recreations due to a flood of updates to the playlist when it is initially loaded. Combined with having registered a callback for the libspotify
playlist_update_in_progresscallback, this could cause deep call stacks reaching the maximum recursion depth. (Fixes: #122)
python setup.py testnow runs the test suite.
The tests are now compatible with CPython 3.4. No changes to the implementation was required.
The test suite now runs on Mac OS X, using CPython 2.7, 3.2, 3.3, 3.4, and PyPy 2.2, on every push to GitHub.
pyspotify 2.x is a full rewrite of pyspotify. While pyspotify 1.x is a CPython C extension, pyspotify 2.x uses CFFI to wrap the libspotify C library. It works on CPython 2.7 and 3.2+, as well as PyPy 2.1+.
This first alpha release of pyspotify 2.0.0 makes 100% of the libspotify 12.1.51 API available from Python, going far beyond the API coverage of pyspotify 1.x.
pyspotify 2.0.0a1 has an extensive test suite with 98% line coverage. All tests pass on all combinations of CPython 2.7, 3.2, 3.3, PyPy 2.2 running on Linux on i386, amd64, armel, and armhf. Mac OS X should work, but has not been tested recently.
This release does not provide:
an event loop for regularly processing libspotify events, or
audio playback drivers.
These features are planned for the upcoming prereleases.
2014-02-13: Playlist callbacks complete. pyspotify 2.x now covers 100% of the libspotify 12 API. Docs reviewed, quickstart guide extended. Redundant getters/setters removed.
2014-02-08: Playlist container callbacks complete.
2014-01-31: Redesign session event listening to a model supporting multiple listeners per event, with a nicer API for registering listeners.
2013-12-16: Ensure we never call libspotify from two different threads at the same time. We can’t assume that the CPython GIL will ensure this for us, as we target non-CPython interpreters like PyPy.
2013-12-13: Artist browsing complete.
2013-12-13: Album browsing complete.
2013-11-29: Toplist subsystem complete.
2013-11-27: Inbox subsystem complete.
2013-10-14: Playlist subsystem almost complete.
2013-06-21: Search subsystem complete.
2013-06-10: Album subsystem complete.
2013-06-09: Track and artist subsystem complete.
2013-06-02: Session subsystem complete, with all methods.
2013-06-01: Session callbacks complete.
2013-05-25: Session config complete.
2013-05-16: Link subsystem complete.
2013-05-09: User subsystem complete.
2013-05-08: Session configuration and creation, with login and logout works.
2013-05-03: The Python object
spotify.libis a working CFFI wrapper around the entire libspotify 12 API. This will be the foundation for more pythonic APIs. The library currently works on CPython 2.7, 3.3 and PyPy 2.
See the pyspotify 1.x changelog.