We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iex (pdm venv activate)
Make sure you run commands with -v flag before pasting the output.
-v
git clone https://github.com/pdm-project/pdm.git cd pdm
pdm sync
The path to the activation script is printed and the venv is not activated.
The venv is activated for the current PowerShell instance.
> pdm info && pdm info --env PDM version: 2.15.3 Python Interpreter: $PROJECT_DIR\.venv\Scripts\python.exe (3.10) Project Root: $PROJECT_DIR Local Packages: { "implementation_name": "cpython", "implementation_version": "3.10.5", "os_name": "nt", "platform_machine": "AMD64", "platform_release": "10", "platform_system": "Windows", "platform_version": "10.0.19044", "python_full_version": "3.10.5", "platform_python_implementation": "CPython", "python_version": "3.10", "sys_platform": "win32" }
Before PDM 2.15.3
> pdm venv activate . '$PROJECT_DIR\.venv\Scripts\Activate.ps1'
PDM 2.15.3
> pdm venv activate '$PROJECT_DIR\.venv\Scripts\Activate.ps1'
I believe the missing period before the script path is causing the failure.
The text was updated successfully, but these errors were encountered:
see the context in #2854
you may need to discuss with @Pluttodk on how to solve this cleany and make both happy
Sorry, something went wrong.
No branches or pull requests
Make sure you run commands with
-v
flag before pasting the output.Steps to reproduce
pdm sync
iex (pdm venv activate)
Actual behavior
The path to the activation script is printed and the venv is not activated.
Expected behavior
The venv is activated for the current PowerShell instance.
Environment Information
Further Information
Before PDM 2.15.3
PDM 2.15.3
I believe the missing period before the script path is causing the failure.
The text was updated successfully, but these errors were encountered: