-
Hello, I am trying to add actions on Windows to one of my repos that has existing support for Linux and MacOS. Window’s is failing in a none obvious way to me. My job description looks like -
Here is the resulting log from the build failing (and here is the [actual job).](http://%20 https://github.com/nanoporetech/fast-ctc-decode/runs/638666087)
I’m not sure which step it’s even failing on, any ideas? |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
On Windows the normal name for the python executable is python.exe (console program) or pythonw.exe (for GUI programs). The python executable is sometimes called python3 on some platforms, where the default ( python ) is the old python 2. On many UNIX-based (inc. Linux and OS X) systems, python 2 is used by system utilities, changing it could have bad consequences on those platforms, hence the name " python3". On Windows you should be fine - there are other issues on Windows but you won’t get those unless you try to use more than one python version. So, the following scripts can work on Windows (reference here):
|
Beta Was this translation helpful? Give feedback.
-
Thank you @brightran! I’m not a Windows user so I was not aware of the difference in how it’s handled. I have it working now albeit by copying the job definition completely. What would be a more elegant way to handle the difference in how the virtual environment needs to be activated?
|
Beta Was this translation helpful? Give feedback.
-
@brightran I somehow kept getting the wrong codes when UK knew i was putting the right one in. |
Beta Was this translation helpful? Give feedback.
-
If you want to integrate the jobs on different OSs into a same matrix, you can try like as below:
|
Beta Was this translation helpful? Give feedback.
@iiseymour ,
On Windows the normal name for the python executable is python.exe (console program) or pythonw.exe (for GUI programs).
The python executable is sometimes called python3 on some platforms, where the default ( python ) is the old python 2. On many UNIX-based (inc. Linux and OS X) systems, python 2 is used by system utilities, changing it could have bad consequences on those platforms, hence the name " python3".
On Windows you should be fine - there are other issues on Windows but you won’t get those unless you try to use more than one python version.
So, the following scripts can work on Windows (reference here):