Skip to content
New issue

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

Show appropriate activation command based on shell detection #2221

Merged
merged 1 commit into from
Mar 5, 2024

Conversation

charliermarsh
Copy link
Member

Summary

Closes #2174.

Test Plan

On Nushell:

(uv) ~/workspace/uv> cargo run venv                                                                                                                                                                                      
Using Python 3.12.0 interpreter at: /Users/crmarsh/workspace/uv/.venv/bin/python3
Creating virtualenv at: .venv
Activate with: overlay use .venv/bin/activate.nu

On Bash:

❯ cargo run venv "foo bar"
Using Python 3.12.0 interpreter at: /Users/crmarsh/.local/share/rtx/installs/python/3.12.0/bin/python3
Creating virtualenv at: foo bar
Activate with: source 'foo bar/bin/activate'

@charliermarsh charliermarsh added the bug Something isn't working label Mar 5, 2024
@charliermarsh charliermarsh marked this pull request as ready for review March 5, 2024 21:42
@charliermarsh charliermarsh force-pushed the charlie/shell branch 3 times, most recently from 9c09d95 to e62c95d Compare March 5, 2024 22:16
@charliermarsh charliermarsh merged commit 9f1bb4d into main Mar 5, 2024
7 checks passed
@charliermarsh charliermarsh deleted the charlie/shell branch March 5, 2024 22:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Print shell-specific activation command in venv
1 participant