Closed project-owner closed 1 year ago
Hello! Thanks for opening an issue.
pyproject.toml
file incorrectly has requires-python = ">=3.7"
; this will be updated to requires-python = ">=3.8"
(Python 3.8 and above supports type hints) in a later update when I get some sort of continuous integration up and running.bundle.js
is valid. This is apparently by design, as the obfuscated functions in bundle.js
used to extract the pair operate fundamentally the same as how I implemented it in Python. However, this behavior may change in the future, so the current dynamic implementation is likely best practice. Based on some quick testing, it looks like this extraction step takes around 3 seconds. If this is somehow a bottleneck for your uses, you should pass in the authentication token directly."ReleaseName"
should be used if you're querying for albums by name, and "MainArtist"
if you're searching for artists.dict
index away (i.e., results = session.search("taylor swift"); albums = results["albums"];
), so there really isn't a need for a specialized function for each return type.Thank you for detailed answers!
Regarding the question #3, it looks like if I don't specify any 'type' for the 'search' it returns the 'artists' section.
qobuz.Session
constructor."ABBA"
with "MainArtist"
. This matches what I get when I search for "ABBA" directly on play.qobuz.com (since it's the same API call). Looks like I was incorrect earlier in my assumptions on how the search endpoint works. From what I can gather, if you want to search for an artist, you cannot specify any of the "types". Specifying #ByMainArtist only returns releases and tracks by artists that contain the search query. I'll probably update the documentation to be more clear about how the type
parameter works, but there isn't anything to change to the implementation as it is working as intended.qobuz.Session
. If you don't want to deal with the unformatted responses from the Qobuz API, you should use the experimental qobuz.User
instead, as all responses in that class are actually qobuz.Artist
, qobuz.Track
, etc. objects with well defined attributes. See the Using the Qobuz API guide for more information.As I mentioned, unfortunately I cannot use the library directly because I need to support Python 3.7.4 for some time. More likely I'll just use some parts of the library and convert json into my own object structure. I'll probably create some kind of common top level "interface" on top of all services (Qobuz, Tidal, Deezer, Spotify etc) and have implementation specific for each service behind that common interface/API.
Hi,
Thanks a lot for this library! Here are some questions and proposals.
Best regards