delta/cpython-git.git/Lib/venv/scripts, branch refactor-lambda-parameters

bpo-38972: Link to instructions to change PowerShell execution policy (GH-19131)

2020-04-02T19:00:21+00:00

bpo-39505: delete the redundant '/' in $env:VIRTUAL_ENV (GH-18290)

2020-02-05T08:16:58+00:00

venv: Suppress warning message when bash hashing is disabled. (GH-17966)

2020-01-14T20:47:59+00:00

When using python's built-in venv activaton script
warnings are printed when hashing is disabled in
bash or zsh, like;

`bash: hash: hashing disabled`

This output is not really useful to the end-user and has
been disabled in `virtualenv` for long.

This commit is based on:
https://github.com/pypa/virtualenv/commit/28e85bcd80d04b2a7ebce0e1d0b02d432b7e5593

Fix old mention of virtualenv (GH-17417)

2019-11-29T23:37:08+00:00

Automerge-Triggered-By: @brettcannon

bpo-38899: virtual environment activation for fish should use `source` (GH-17359)

2019-11-23T07:32:27+00:00

The previously documented use of `.` is considered deprecated (https://fishshell.com/docs/current/commands.html#source).


https://bugs.python.org/issue38899



Automerge-Triggered-By: @brettcannon

bpo-38344: Fix syntax in activate.bat (GH-16533)

2019-10-07T21:07:19+00:00

bpo-37885: venv: Don't produce unbound variable warning on deactivate (GH-15330)

2019-09-11T14:58:56+00:00

Before, running deactivate from a bash shell configured to treat undefined variables as errors (`set -u`) would produce a warning:

``` 
$ python3 -m venv test
$ source test/bin/activate
(test) $ deactivate
-bash: $1: unbound variable
```

bpo-36634: Fixes activate.bat when existing values contain double quotes (GH-15924)

2019-09-11T14:41:21+00:00

bpo-37663: have venv activation scripts all consistently use __VENV_PROMPT__ for prompt customization (GH-14941)

2019-08-21T22:58:01+00:00

The activation scripts generated by venv were inconsistent in how they changed the shell's prompt. Some used `__VENV_PROMPT__` exclusively, some used `__VENV_PROMPT__` if it was set even though by default `__VENV_PROMPT__` is always set and the fallback matched the default, and one ignored `__VENV_PROMPT__` and used `__VENV_NAME__` instead (and even used a differing format to the default prompt). This change now has all activation scripts use `__VENV_PROMPT__` only and relies on the fact that venv sets that value by default.

The color of the customization is also now set in fish to the blue from the Python logo for as hex color support is built into that shell (much like PowerShell where the built-in green color is used).

bpo-37354: Make Powershell Activate.ps1 script static to allow for signing (GH-14967)

2019-08-12T20:06:02+00:00

- Remove use of replacement text in the script
- Make use of the pyvenv.cfg file for prompt value.
- Add parameters to allow more flexibility
- Make use of the current path, and assumptions about where env puts things, to compensate
- Make the script a bit more 'idiomatic' Powershell
- Add script documentation (Get-Help .\.venv\Scripts\Activate.ps1 shows PS help page now