actions/setup-python
actions/setup-python
1
0
Fork 0
mirror of https://github.com/actions/setup-python.git synced 2024-12-22 13:42:09 -05:00
Code Issues Projects Releases Packages Wiki Activity

Improve wording and "fix example" (remove 3.13) on testing against pre-releases

Browse source 
3.13 was added in a mass tune up in 0b93645e9f , without
adjusting the wording. With 3.13 listed there too, example does not really make much
sense. So I decided to make it explicit in wording and remove 3.13, so whenever next
refactoring to add 3.14 to be added to every line where 3.13 is -- this would not
even come to attention
This commit is contained in:
Yaroslav Halchenko 2024-12-05 16:10:52 -05:00
parent 55aad42e46
commit 3b11caf218
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/advanced-usage.md
View file

@ -587,7 +587,7 @@ The `allow-prereleases` flag defaults to `false`.
If `allow-prereleases` is set to `true`, the action will allow falling back to pre-release versions of Python when a matching GA version of Python is not available.
This allows for example to simplify reuse of `python-version` as an input of nox for pre-releases of Python by not requiring manipulation of the `3.y-dev` specifier.
For CPython, `allow-prereleases` will only have effect for `x.y` version range (e.g. `3.12`).
Let's say that python 3.12 is not generally available, the following workflow will fallback to the most recent pre-release of python 3.12:
Let's say that in the past, when python 3.12 was not yet generally available, the following workflow would have fallback to the most recent pre-release of python 3.12:
```yaml
jobs:
test:
@ -597,7 +597,7 @@ jobs:
fail-fast: false
matrix:
os: [Ubuntu, Windows, macOS]
python_version: ["3.11", "3.12", "3.13"]
python_version: ["3.11", "3.12"]
steps:
- uses: actions/checkout@v4