Fixed an error importing Spotify data exports from 2025#443
Open
slater-uk wants to merge 1 commit intokrateng:masterfrom
Open
Fixed an error importing Spotify data exports from 2025#443slater-uk wants to merge 1 commit intokrateng:masterfrom
slater-uk wants to merge 1 commit intokrateng:masterfrom
Conversation
… are named StreamingHistory_music_0. Added to the import_scrobbles.py script to recognise this naming scheme
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Spotify data exports from 2025 are named differently than previously. The python script
import_scrobbles.pydid not recognise the updated file names from spotify. My recent Spotify export data was named"StreamingHistory_music_0.json".I have editted the
import_scrobbles.pyscript to recognise this new naming scheme from Spotify.