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
I have run into the following problem. When using glob or glob_ext files are only discovered within the first sub-directory, so there seems to be no real recursion. Is this intended?
The t.fs.glob and t.fs.glob_ext functions should behave similarly to the Python glob module. It does indeed look like we do not yet support the recursive=True flag that it documented for that module. That's something we could definitely add.
However, it's recommended that you actually use the pathlib API to access the filesystem contents:
Pretty much all read-only functionality that is documented for the official pathlib module will work. A TargetPath object returned from t.fs.path("/") will behave the same as a pathlib.Path object! In fact, isinstance(t.fs.path("/"), pathlib.Path) == True.
The t.fs.glob and t.fs.glob_ext functions should behave similarly to the Python glob module. It does indeed look like we do not yet support the recursive=True flag that it documented for that module. That's something we could definitely add.
I would very much appreciate that :)
However, it's recommended that you actually use the pathlib API to access the filesystem contents:
Hi,
I have run into the following problem. When using glob or glob_ext files are only discovered within the first sub-directory, so there seems to be no real recursion. Is this intended?
Example:
Output: /sysvol/Users/Jimmy Wilson/Desktop/Robert Ripoff/Shesa Hippo.jpg
Output: /sysvol/Users/Jimmy Wilson/Desktop/Robert Ripoff/Shesa Hippo.jpg
Output:
The text was updated successfully, but these errors were encountered: