[issue41256] activate script created by venv is not smart enough

Jack DeVries added the comment: *please disregard the typo in the shebang line!* -- ___ Python tracker ___ ___ Python-bugs-list mai

[issue41256] activate script created by venv is not smart enough

Jack DeVries added the comment: What do you think about this as an entrypoint? ```sh #!/usr/bin/env # this becomes venv/bin/activate # the old venv/bin/activate is now venv/bin/activate.sh # Try to execute a `return` statement, # but do it in a sub-shell and catch the results. # If this scri

[issue41256] activate script created by venv is not smart enough

Eric V. Smith added the comment: Changing versions to those that are currently receiving support. -- nosy: +eric.smith versions: -Python 3.5, Python 3.6, Python 3.7 ___ Python tracker __

[issue41256] activate script created by venv is not smart enough

Change by Karthikeyan Singaravelan : -- nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue41256] activate script created by venv is not smart enough

New submission from kunaltyagi : TLDR: `activate` script should be able to: * inform user if it has been run and not sourced * act as a placeholder to detect the shell being used and source the necessary `activate.{SHELL}` instead of throwing an error --- It's mildly infuriating that `activate