-
Notifications
You must be signed in to change notification settings - Fork 614
Allow specification of version X.Y including prereleases #124
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
Comments
Will the following syntax not work for your use case?
Currently there is By specifying the range, the latest pre-release version will always be pulled. Once a stable version of Python 3.9 comes out (no new pre-release versions should come out for that specific version), the stable version of Python would be used. |
Thank you for the quick response and for pointing out the solution. I now see it was right there in the docs. My apologies for not finding it there myself. I ended up with python: ['3.6', '3.7', '3.8', '3.9'] python-version: '${{ matrix.python }}.0-alpha - ${{ matrix.python }}.X' Now just waiting on PySide2 and PyQt5 to release 3.9-supporting wheels... |
Actually, I suppose this points out an error (I think) in the readme. The range with the 0 micro/patch version did not (would not sensibly) allow stable releases beyond |
See also #213. |
Describe the bug
It would be nice to be able to specify a version such as 3.9 and have it get the latest prerelease if available. I am not sure exactly why but can understand that someone might want the present behavior (failure) when only prereleases are available but perhaps a markup like '3.9-+' (or something much less terrible than that) could be used to enable either pre or regular releases.
The text was updated successfully, but these errors were encountered: