-
Notifications
You must be signed in to change notification settings - Fork 522
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DOC: document -dev syntactic sugar #318
Conversation
Yes please :) I thought maybe "3.11-dev" would get me the current tip of main. Oh well... :( |
It would be nice to get this into the documentation! |
Hi @vsafonkin and @marko-zivic-93, could anyone have a look please ? |
Hi @neutrinoceros, we will take a look at this, thank you for your contribution. |
@@ -150,6 +150,7 @@ Check out our detailed guide on using [Python with GitHub Actions](https://help. | |||
- For every minor version of Python, expect only the latest patch to be preinstalled. | |||
- If `3.8.1` is installed for example, and `3.8.2` is released, expect `3.8.1` to be removed and replaced by `3.8.2` in the tools cache. | |||
- If the exact patch version doesn't matter to you, specifying just the major and minor version will get you the latest preinstalled patch version. In the previous example, the version spec `3.8` will use the `3.8.2` Python version found in the cache. | |||
- Use `-dev` instead of a patch number (e.g., `3.11-dev`) to install the latest release of a minor version, *alpha and beta releases included*. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"alpha, beta and release candidates included" ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup that would be more accurate, sorry I missed that
Description:
Add missing documentation on how to install alpha and beta releases
Related issue:
fix #177
Check list: