theskumar / theskumar/python-dotenv
[BUG] dotenv cli not used windows venv if it activated
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.9k
- Forks
- 581
- PR merge metrics
- No merged PRs in 30d
Description
I use vscode on windows
Command:
python -m venv venv
.venv\Scripts\activate
pip install python-dotenv[cli]
dotenv run -- python -c "import sys; print(sys.executable)"
Expected:
\path\to\venv\Scripts\python.exe
Real:
\path\to\system\python.exe
If needed more info - I will try to provide it ASAP.
Cc: @scad89 help to find this issue
System:
Windows 10.
python -V
Python 3.8.5
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
Start by reproducing the supplied command on Windows 10 with Python 3.8.5, comparing the executable reported inside the activated virtual environment with the one used by dotenv run. Trace how the CLI launches python; done means the command selects venv\Scripts\python.exe rather than the system interpreter.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100