python-poetry / python-poetry/poetry-plugin-shell
Poetry shell command does not start shell
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 141
- Forks
- 10
- Avg merge
- 59m
- Merged PRs (30d)
- 3
Description
-
I am on the latest Poetry version.
-
I have searched the issues of this repo and believe that this is not a duplicate.
-
If an exception occurs when executing a command, I executed it again in debug mode (
-vvvoption) (Not applicable). -
OS version and name: macos 10.15.6
-
Poetry version: 1.0.10
-
Link of a Gist with the contents of your pyproject.toml file: N/A
Issue
The basic issue is that poetry shell cannot be invoked within a virtual environment. Based on how this runs, I think the expectation is that we install poetry into the system.
My expectation is that I can invoke a poetry shell and drop into a standard virtual environment (i.e. a subshell that runs similar to vex).
Reproduceable steps:
`which python3` -m venv ~/.test-venv
. ~/.test-venv/bin/activate
pip install --upgrade pip poetry
deactivate
~/.test-venv/bin/poetry shell
The error will be something like:
Skipping virtualenv creation, as specified in config file.
Virtual environment already activated: ~/.test-venv
However, the virtual environment is not active.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the documented macOS command sequence and inspect the poetry shell command handling. Verify how it behaves when run from an already activated virtual environment. Done means poetry shell opens the expected subshell instead of reporting that the virtual environment is already active.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100