Untar processor cannot handle members within subfolders #223
Comments
|
👋 Thanks for opening your first issue here! Please make sure you filled out the template with as much detail as possible. You might also want to take a look at our Contributing Guide and Code of Conduct. |
This was referenced Jan 4, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the problem
individual member files of an archive cannot be selected if they reside within a subfolder inside the archive.
For demonstration, I'm using an archive called
MNE-kiloword-data.tar.gz(URL for it is in the code below).Inside that archive is one folder with one file in it:
MNE-kiloword-data/kword_metadata-epo.fifI want to end up with the file here:
/home/username/Desktop/MNE-kiloword-data/kword_metadata-epo.fifIn other words, I want the whole archive's contents to end up on my Desktop (this is just for illustration purposes; in reality we will put it somewhere more sensible).
I have tried several combinations of
fname,path, andmembersbelow, and always end up with aFileNotFounderror. I've also tried explicitly passing the subdirectory inside the archive as one of themembers, like this:...which also didn't work.
Full code that generated the error
Full error message
System information
conda listbelow:output of conda list
Additional notes
FWIW, ultimately I will want to use the Pooch class; I had similar difficulties getting this to work with
pooch.Pooch.fetch()however. My basic problem seems to be that when using a processor likeUnzip()orUntar(), there is no option to put the output of the unzipping/untarring in an arbitrary location (i.e., there is only asuffixattribute). I think that if it were possible to do this:...then my difficulties would go away (i.e., for my use case, if I could specify where to untar the archive, then I wouldn't need to bother with the
membersparameter at all, so I wouldn't hit the problem of members nested within subfolders). I suspect that implementing the target directory forUntar()is probably easier anyway, though I can imagine cases where both capabilities would be useful.The text was updated successfully, but these errors were encountered: