[issue32910] venv: Deactivate.ps1 is not created when Activate.ps1 was used

Change by Steve Dower : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue32910] venv: Deactivate.ps1 is not created when Activate.ps1 was used

miss-islington added the comment: New changeset 06e8fc95d138775e942c18c8e47e72cdcc32f95c by Miss Islington (bot) in branch '3.8': bpo-32910: Remove implementation detail in venv documentation. (GH-14968) https://github.com/python/cpython/commit/06e8fc95d138775e942c18c8e47e72cdcc32f95c

[issue32910] venv: Deactivate.ps1 is not created when Activate.ps1 was used

miss-islington added the comment: New changeset 4b6421c61e9335253ea7004f2878317b88096c30 by Miss Islington (bot) in branch '3.7': bpo-32910: Remove implementation detail in venv documentation. (GH-14968) https://github.com/python/cpython/commit/4b6421c61e9335253ea7004f2878317b88096c30

[issue32910] venv: Deactivate.ps1 is not created when Activate.ps1 was used

Steve Dower added the comment: New changeset 91e49575095ca16d1b67dd8822deeb7885e421da by Steve Dower (Derek Keeler) in branch 'master': bpo-32910: Remove implementation detail in venv documentation. (GH-14968) https://github.com/python/cpython/commit/91e49575095ca16d1b67dd8822deeb7885e421da

[issue32910] venv: Deactivate.ps1 is not created when Activate.ps1 was used

Change by miss-islington : -- pull_requests: +14741 pull_request: https://github.com/python/cpython/pull/14972 ___ Python tracker ___

[issue32910] venv: Deactivate.ps1 is not created when Activate.ps1 was used

Change by miss-islington : -- pull_requests: +14740 pull_request: https://github.com/python/cpython/pull/14971 ___ Python tracker ___

[issue32910] venv: Deactivate.ps1 is not created when Activate.ps1 was used

Change by Derek Keeler : -- keywords: +patch pull_requests: +14737 stage: -> patch review pull_request: https://github.com/python/cpython/pull/14968 ___ Python tracker ___

[issue32910] venv: Deactivate.ps1 is not created when Activate.ps1 was used

Kirill Balunov added the comment: Yes, I agree, I did not understand the documentation correctly. It seems to me that the problem in the perception arose because of the fact that "deactivate" is not formatted as shell command, while `Deactivate.ps1` and others are.

[issue32910] venv: Deactivate.ps1 is not created when Activate.ps1 was used

Paul Moore added the comment: As noted in the related issue that you link to, there is not meant to be a deactivate.ps1 script - the deactivate command is provided via a global deactivate function created when you run activate.ps1 (although this is an implementation

[issue32910] venv: Deactivate.ps1 is not created when Activate.ps1 was used

Kirill Balunov added the comment: Sorry, `deactivate` works in both cases `Scripts/Activate.ps1` and `Scripts/activate`. Only `Deactivate.ps1` is not created for the former, but the docs says that it should. -- ___ Python

[issue32910] venv: Deactivate.ps1 is not created when Activate.ps1 was used

New submission from Kirill Balunov : There was a related issue, which was closed https://bugs.python.org/issue26715. If virtual environment was activated using Powershell script - Activate.ps1, the Deactivate.ps1 was not created, while the documentation says that it