posit-dev / posit-dev/positron
Poetry Virtual Enviroment Resets to Global Python Environment
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 184
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 195
Description
I am using a Poetry environment for my Python project, but as soon as I split the editor, open another editor within the same window, or even open the data explorer, the environment reverts to the global environment, and I have to manually switch the kernel back to the virtual environment.
Additionally, the "Variables" section appears to retain cached data, displaying duplicate .ipynb file names, and requires manual adjustments to view variables related to the Jupyter notebook.
Contributor guide
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
Reproduce the issue in Positron with a Poetry Python environment, then split an editor, open another editor, and open the data explorer while watching the selected kernel. Also inspect the Variables section with a Jupyter notebook. Done means the Poetry environment remains selected and variable entries do not show stale duplicate notebook names.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook, python
- Domain
- data, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100