-
Notifications
You must be signed in to change notification settings - Fork 23
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
Windows compatibility try #18
Windows compatibility try #18
Conversation
errrr....... I fear I did something wrong, there... edit: ah, no, that's the write access apparently... But so, I cannot see if that works... ('should have use my fork, I guess...) |
No, let me merge #17 first, and I'll rebase this so the test will run for Windows. |
0a6eb33
to
5f40bb7
Compare
nice, now macos fails too... x/ That should be manageable, adding specific executions (sys stuff) any idea about what's going on with this?
|
macOS is failing because it has
|
Nevermind, it's |
I guess for Windows you need to pass |
OK, now it's failing because of the CRLF line ending ( |
That shouldn't be necessary. Windows is failing because it includes a comma |
dunno... The more we dig, the craziest all of this seems... XD Let's just drop windows support... |
We never supported it, so no problem. |
I got a different kind of error, locally, and could get the stdout properly with this.
new error is:
Wanting to see how this behaves here...
edit: "reason" for the stderr change: https://stackoverflow.com/questions/10406532/python-subprocess-output-on-windows