Windows support #32
-
Hi, I'd like to upload wheels from Windows. However, when I tried with
I guess I go back to calling twine manually? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Trust me, you don't really want that. This is out of the scope of this project and is a discouraged approach in general. The recommended way is to use actions/upload-artifacts and actions/download-artifacts to collect all of the artifacts together and upload them all at the same time (as opposed to uploading on windows when the same version fails on Linux in a parallel job). Docker-based actions only work on Linux and I chose them because I can control the environment inside. Using JS-based actions would mean either forcing users to pre-setup the proper Python env (huge area for human errors) or mutating the state of the runner VMs potentially messing up things for end-users which is also not great. One day I'll write an extra guide (#29) for setting up a multistage workflow for platform-specific dists. Meanwhile, I have a state-of-the-art WIP prototype of this if you want to take a look: https://github.com/ansible/pylibssh/blob/devel/.github/workflows/build-test-n-publish.yml. Closing as a duplicate of #15. |
Beta Was this translation helpful? Give feedback.
-
Also, please use |
Beta Was this translation helpful? Give feedback.
Trust me, you don't really want that.
This is out of the scope of this project and is a discouraged approach in general. The recommended way is to use actions/upload-artifacts and actions/download-artifacts to collect all of the artifacts together and upload them all at the same time (as opposed to uploading on windows when the same version fails on Linux in a parallel job).
Docker-based actions only work on Linux and I chose them because I can control the environment inside. Using JS-based actions would mean either forcing users to pre-setup the proper Python env (huge area for human errors) or mutating the state of the runner VMs potentially …