You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The way that registry.txt files are parsed here does not allow filenames to contain spaces. This could be fixed by implementing advanced parsing that allows escaping using enclosing quotes or backslashes.
OSError: Invalid entry in Pooch registry file './registry.txt': expected 2 or 3 elements in line 1 but got 7. Offending entry: '"How To - Minimal Workflow.pdf" sha256:7d4da5fe4d0438437834fe846608b93959dcb80ded941eb85663b2d905c54000 https://heidata.uni-heidelberg.de/api/access/datafile/:persistentId?persistentId=doi:10.11588/data/TJNQZG/DWSXML'
The text was updated successfully, but these errors were encountered:
@dokempf thanks for reporting this as well! Indeed our parsing is very simplistic and doesn't cover this. In hindsight we should have done with a standard format like JSON for the registry file which would have covered all of this. With the current format, you're right that the only way is to improve our parsing to handle quotes and escaping.
Description of the problem:
The way that
registry.txt
files are parsed here does not allow filenames to contain spaces. This could be fixed by implementing advanced parsing that allows escaping using enclosing quotes or backslashes.Full code that generated the error
With registry.txt in path:
Full error message
The text was updated successfully, but these errors were encountered: