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

[python] Add gitpod/workspace-python-3.11 #993

Closed
obaltian opened this issue Dec 10, 2022 · 1 comment · Fixed by #1003
Closed

[python] Add gitpod/workspace-python-3.11 #993

obaltian opened this issue Dec 10, 2022 · 1 comment · Fixed by #1003
Assignees

Comments

@obaltian
Copy link

Is your feature request related to a problem? Please describe

Python3.11 has been officially released this year and should be supported by such generic tools as gitpod, it does not contain any major changes breaking backwards compatibility with 3.10.
Can we add support for the newest python major version to provide up-to-date software?

Describe the behaviour you'd like

A new image gitpod/workspace-python-3.11 added to a list of provided images.

Describe alternatives you've considered

You may update pyenv (since by default it is outdated in image) and install python3.11 in init task, but then my prebuilds take 5 mins instead of 2 (without python3.11 installation). This is not comfortable for everyday work, so can not be considered as an alternative:

cd ~/.pyenv && git pull && cd -;
pyenv install python3.11
pyenv global 3.11
poetry env use 3.11
[...]

Too much extra movements from end user.

Additional context

Link to pyenv update request (which may be useful for python update).

@Furisto
Copy link
Member

Furisto commented Jan 4, 2023

@obaltian We have added an image for Python 3.11: https://hub.docker.com/r/gitpod/workspace-python-3.11

@Furisto Furisto moved this from In Validation to Done in 🌌 Workspace Team Jan 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants