Manipulating linux filepaths in windows (and vice versa)
I have a use-case where I may need to work with linux filepaths on windows, or vice-versa.
It looks a lot like the assumption that you only need to work with paths that match your operating system, while certainly mostly correct, means that my best way of doing this looks to be to duplicate the filepath package. It feels like there ought to be a better solution than that, like how in http and some other packages you can use the module level default functions or create an instance of a client with the settings you need.
Does anyone know a better way of dealing with this issue?
Posted Aug 21, 2017, 2:31 AM UTC
There is also the path package, which only handles / paths. That solves the unix filepaths on windows case, but not the other.