Request for more info on the removal of poetry shell command

[chris48s]

This thread isn't a complaint. Just a request for information.

The release notes for poetry 2 say

we seized the chance of a major release to remove the poetry shell command . Due to several issues with poetry shell, we recommend to use the new poetry env activate command instead.

(emphasis mine)

So before deciding whether I want to modify my workflow for poetry 2 or migrate to poetry-plugin-shell I would like to understand what these several issues are.

So I looked at #9763 (linked from the changelog) but there's no explanation in the top post and no linked issue.

So what I want to understand is: What are the problems with poetry shell (in more detail than "several issues"), or what are the reasons why something different is recommended now. If by switching to poetry-plugin-shell I am effectively opting myself in to problems, then maybe I don't want to use it. But maybe the problems are issues that don't affect my use case 🤷

At the moment I feel like I do not have the information to make a good choice here.

[Secrus]

There were several issues concerning the proper launching of the subshell for different shell types, the issue of shell calling a subshell, subshells not working correctly with keyboard commands etc. You can browse the issue tracker at https://github.com/python-poetry/poetry-plugin-shell/issues

[holocronweaver]

Something along these lines should be in the release notes, for the reasons OP stated.

[mehaase]

The PR for this change doesn't seem very principled. It just says "resolves personal grudge" 😆 .