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

Moving the container to F37 or at least F36? #60

Closed
praiskup opened this issue Oct 26, 2022 · 4 comments
Closed

Moving the container to F37 or at least F36? #60

praiskup opened this issue Oct 26, 2022 · 4 comments

Comments

@praiskup
Copy link

praiskup commented Oct 26, 2022

SSIA

@hroncok
Copy link
Member

hroncok commented Oct 26, 2022

We'll be moving to F36 in a month or so. What is your use case?

@hroncok hroncok transferred this issue from fedora-python/tox-github-action Oct 26, 2022
@praiskup
Copy link
Author

I thought I could test a pre-release Python 3.12 there, but that's not yet possible. So no use-case => no problem => closing. Sorry for the rush.

Seems like you are moving to Fedora N+1 when N goes EOL? If so, just a small suggestion: it deserves a note in the README file that this is the policy. Then nobody will be "shocked" the container is too old. :)

@hroncok
Copy link
Member

hroncok commented Oct 27, 2022

I thought I could test a pre-release Python 3.12 there, but that's not yet possible.

See https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2137912 and https://src.fedoraproject.org/rpms/python3.11/pull-request/89

We plan to add it to Fedora 35 as well.

Seems like you are moving to Fedora N+1 when N goes EOL? If so, just a small suggestion: it deserves a note in the README file that this is the policy. Then nobody will be "shocked" the container is too old. :)

#61

@praiskup
Copy link
Author

Thank you @hroncok !

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

No branches or pull requests

2 participants