-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
batch files cannot be used cross-platform #209
Comments
Hey, I just ran into this issue as well. I was thinking, your solution would avoid the error, but it's still not very useful to have the string representation of a path that's not usable on your current system. The batch path gets overwritten when loading a batch anyway right after un-pickling: df = pd.read_pickle(Path(path))
df.paths.set_batch_path(path) Thus how about this attribute just gets cleared before saving? Each |
By the way, how do you quote specific lines with the line numbers and link to file? I've been wishing there was a feature like that. |
Ah yes you're right 😆 nice to have fresh eyes take a look at this
|
I just realized that the outputs are also saved as Since I believe these are all relative paths, which should be cross-platform if they use forward slashes, I think the solution is to convert the relative paths to Edit: or just save as PurePosixPath, that should also be fine. |
That's a good idea! Posix path and then string. |
I think it's because the current batch path is stored in
DataFrame.attrs
mesmerize-core/mesmerize_core/batch_utils.py
Lines 59 to 60 in f00949f
should just store this as a string and have a
@batch_path
property on the extension class which returns aPath
instead ofstr
to use within the extension functions.The text was updated successfully, but these errors were encountered: