mirror of
https://github.com/spotipy-dev/spotipy.git
synced 2026-04-27 00:25:54 +03:00
[GH-ISSUE #784] How to change location of .cache? (Reading or writing) #484
Labels
No labels
api-bug
bug
dependencies
documentation
duplicate
enhancement
external-ide
headless-mode
implicit-grant-flow
invalid
missing-endpoint
pr-welcome
private-api
pull-request
question
spotipy3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotipy#484
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 @clemwo on GitHub (Feb 22, 2022).
Original GitHub issue: https://github.com/spotipy-dev/spotipy/issues/784
Hi, I wrote a little command line interface that can be used to merge playlists. Code can be found here:
https://gitlab.com/clemwo/spotify-playlist-merger
I used setuptools for installation and click to make the cli.
Now when I run the script in the terminal in the folder where it is installed at
~/.local/share/SpotifyPMeverything works fine. However if I execute the command from another place such as my home directory I get the followinge message:Couldn't read cache at: .cacheThe error isn't surprising because apparently spotipy looks for the .cache file in the current working directory (this is just my assumption).
How can I make spotipy look for the .cache file in another place? I have used platformdirs to generate a config file in the user data location so it would be nice if that could also be the location where I save the .cache.
Thanks for any help and for the great library!
@Peter-Schorn commented on GitHub (Feb 23, 2022):
You can specify an absolute path for where the authorization information should be stored, as described here.
@dieser-niko commented on GitHub (May 21, 2024):
Closing as the issue seems to be resolved.