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

In-place upgrading of Python versions for virtualenvs #7267

Closed
2 tasks done
ghost opened this issue Dec 30, 2022 · 2 comments
Closed
2 tasks done

In-place upgrading of Python versions for virtualenvs #7267

ghost opened this issue Dec 30, 2022 · 2 comments
Labels
kind/feature Feature requests/implementations status/triage This issue needs to be triaged

Comments

@ghost
Copy link

ghost commented Dec 30, 2022

  • I have searched the issues of this repo and believe that this is not a duplicate.
  • I have searched the FAQ and general documentation and believe that my question is not already covered.

Feature Request

Having worked with Poetry for a year now, I appreciate the capabilities and ease of Python dev it introduced to my workflow!

Only one other thing I'd love to see from Poetry is the ability to upgrade virtualenvs in-place with a newer Python version installed with pyenv. Having to re-create the virtualenvs and reinstall all the dependencies feels too much, at least for minor releases (e.g 3.10.x)!

This feature alongside #461 baked in Poetry would be awesome!

@ghost ghost added kind/feature Feature requests/implementations status/triage This issue needs to be triaged labels Dec 30, 2022
@finswimmer
Copy link
Member

finswimmer commented Jan 18, 2023

Hey,

while I understand that this feature would be quite useful, this is (at least at the moment) out of scope for Poetry. We simply pass the venv creation job to virtualenv.

I'm afraid in-place upgrading the interpreter in a venv is not a trivial job at all.

fin swimmer

@finswimmer finswimmer closed this as not planned Won't fix, can't repro, duplicate, stale Jan 18, 2023
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 31, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/feature Feature requests/implementations status/triage This issue needs to be triaged
Projects
None yet
Development

No branches or pull requests

1 participant