mirror of
https://github.com/Googolplexed0/zotify.git
synced 2026-04-25 06:15:55 +03:00
[GH-ISSUE #98] Efficient API refactor as a Python package #87
Labels
No labels
bug
considering
discussion
documentation
enhancement
enhancement
good first issue
help wanted
pull-request
question
stale
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/zotify#87
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @KyrillosL on GitHub (Oct 12, 2025).
Original GitHub issue: https://github.com/Googolplexed0/zotify/issues/98
Hello,
I'm working on an application that synchronizes two accounts (source -> target). I came across this project and saw your work about the efficient API calls.
downloadmethod from your API Code, and Zotify would just import the generic API and extend it with a download feature. In my case, it wouldn't be a download feature, but a sync feature.@Googolplexed0 commented on GitHub (Oct 12, 2025):
Directly benefit? I doubt it. This repository has a lot of extra boilerplate code that isn't necessary for what you are trying to do. You are free to fork this and adapt it into whatever you would like but it would probably not be a very efficient use of your time.
The library you are currently using should have all the tools you need to create/edit playlists using the contents of an existing playlist. I've done similar tasks using that exact library. Your current approach is on the right track.
@KyrillosL commented on GitHub (Oct 12, 2025):
Thanks for your answer, Googolplexed0.
I'm curious why you didn't use the Spotipy package and you reimplemented a lot of stuff related to API calls (such as the
invoke_url_nextable) if they are already implemented and efficient?