Set up your GitHub Actions workflow with a specific version of Python
Go to file
2019-07-25 22:59:00 -04:00
__tests__ Clean up tests 2019-07-11 17:12:03 -04:00
.github Steps not actions 2019-07-25 22:59:00 -04:00
docs Initial pass 2019-06-26 21:12:00 -04:00
lib Add matcher 2019-07-08 14:43:29 -04:00
node_modules Update tool-cache.js 2019-07-17 10:19:53 -04:00
src Add matcher 2019-07-08 14:43:29 -04:00
toolkit Initial pass 2019-06-26 21:12:00 -04:00
.gitignore Initial pass 2019-06-26 21:12:00 -04:00
.prettierrc.json Initial pass 2019-06-26 21:12:00 -04:00
action.yml Add default arch 2019-07-19 16:07:45 -04:00
jest.config.js Initial pass 2019-06-26 21:12:00 -04:00
LICENSE Initial pass 2019-06-26 21:12:00 -04:00
package-lock.json Clean up node_modules 2019-07-11 16:52:31 -04:00
package.json Fix husky 2019-07-12 11:00:11 -04:00
README.md actions to steps 2019-07-25 21:29:46 -04:00
tsconfig.json Initial pass 2019-06-26 21:12:00 -04:00

setup-python

This action sets up a python environment for use in actions by:

  • optionally installing a version of python and adding to PATH. Note that this action only uses versions of Python already installed in the cache. The action will fail if no matching versions are found.
  • registering problem matchers for error output

Usage

See action.yml

Basic:

steps:
- uses: actions/checkout@master
- uses: actions/setup-python@master
  with:
    version: 3.x // Version range or exact version of a Python version to use, using semvers version range syntax.
    architecture: x64 // (x64 or x86)
- run: python my_script.py

Matrix Testing:

jobs:
  build:
    strategy:
      matrix:
        python: [ 2.x, 3.x, pypy3 ]
    name: Python ${{ matrix.python }} sample
    steps:
      - uses: actions/checkout@master
      - name: Setup python
        uses: actions/setup-python@master
        with:
          version: ${{ matrix.python }}
          architecture: x64
      - run: python my_script.py

License

The scripts and documentation in this project are released under the MIT License

Contributions

Contributions are welcome! See Contributor's Guide