Closed LukaHorvat closed 7 years ago
That's great. I put in the env change but I'm a little confused about the slashes. If the platform is windows isn't it correctly producing forward slashes? Why flip them back into the unix direction?
Forward slashes have worked on Windows for a while now. In fact, I don't really remember them ever not working. The problem seems to be that these "system specific" functions, like the temp file one, return paths with backslashes and then this gets into the Python file unescaped. The error complains about bad escape sequences. If you want you can keep backslashes and escape them instead of flipping them. I think it's pretty much the same.
Oh I see! I guess this never happens on *nix since the temp directory is just /tmp and there are no spaces but it's a problem everywhere. Did the last push help?
Yup, it works
Great! Thanks for the help in figuring this out :)
This is surely not the only way but it works for me. The requirement is msys2 (the one shipped with stack probably works fine)
Then inside of the msys environment (always use the msys console) you do this
Make sure
where python3
reports/mingw64/bin/python3
before anything else. If not, add/mingw64/bin/
to the front of your PATH variable. When running the functions from this library, make sure you're using the msys console.These are the changes I needed to make to the code
So basically
/usr/bin/env
doesn't work on Windows butenv
does (also using msys). The backslashes also need to be converted to slashes.