Skip to content

Consider prompting the user to run eval $(poetry env activate) when they mistakenly run poetry shell #10177

Closed as duplicate
@daviewales

Description

@daviewales

Issue Kind

Brand new capability

Description

Once upon a time, the steps required to activate a poetry shell were simple and easy to remember:

poetry shell

Then came 2.0, and the removal of poetry shell (to fix some bugs).

But now, I can never remember what to run to get me into a poetry shell.

It would be nice if when I run poetry shell, instead of printing The command "shell" does not exist, instead, it printed a helpful message such as:

Since 2.0, `poetry shell` no longer exists. To activate a poetry shell, run:
eval $(poetry env activate)

Impact

This would save me needing to look up the documentation when I can't remember how to activate a poetry shell.

Workarounds

I can just look up the documentation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureFeature requests/implementationsstatus/triageThis issue needs to be triaged

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions