-
steps:
- uses: actions/checkout@v3
- name: Install poetry
run: pipx install poetry==1.6.1
- uses: actions/cache@v3
with:
path: ${{ ??? }}
key: ${{ runner.os }}-${{ matrix.python-version }}-pipx-poetry-1.6.1
- uses: actions/setup-python@v4
with:
python-version: '3.9'
cache: 'poetry'
- run: poetry install
- run: poetry run pytest |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 9 replies
-
At work we cache the entire |
Beta Was this translation helpful? Give feedback.
-
Echoing these in a job step, you can see what some of them are for different OSs:
The fact that GitHub Actions doesn't explain in its documentation that it overrides these is unfortunate. Hence, simply using the default Also unfortunately, since some of these are located in An alternative might be to copy files from A second option would be to install |
Beta Was this translation helpful? Give feedback.
-
Commenting on the above since when caching poetry dependencies using the vanilla setup here, installing poetry itself usually becomes the slowest step. Any recommendation on caching pipx installs that would work nicely with this setup? |
Beta Was this translation helpful? Give feedback.
At work we cache the entire
~/.local/pipx
directory and that seems to work, or at least I never heard infra folks complain about it. Are there blockers to doing that?