Skip to content
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

A better way to specify a Python prerelease version #238

Closed
dataflake opened this issue May 13, 2024 · 1 comment · Fixed by #239
Closed

A better way to specify a Python prerelease version #238

dataflake opened this issue May 13, 2024 · 1 comment · Fixed by #239
Assignees
Labels
enhancement New feature or request

Comments

@dataflake
Copy link
Member

Right now the value of FUTURE_PYTHON_VERSION in shared/packages.py is set as a range, currently 3.13.0-alpha - 3.13.0. That's a bit clunky because that version string is inserted in many places.

The documentation for the setup-python GH action mentions a cleaner way that uses the flag allow-prereleases: true, so you could define FUTURE_PYTHON_VERSION as a "clean" 3.13 and write it all like this:

- uses: actions/setup-python@v4
  with:
    python-version: "3.13"
    allow-prereleases: true

See https://github.com/actions/setup-python/blob/main/docs/advanced-usage.md#allow-pre-releases.

@dataflake dataflake added the enhancement New feature or request label May 13, 2024
@dataflake dataflake self-assigned this May 13, 2024
@icemac
Copy link
Member

icemac commented May 14, 2024

This looks interesting and I like it more than the range.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants