Message312554
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 detail, all that matters is that a "deactivate" command exists, not how it is implemented).
The documentation of the implementation-specific behaviour is incorrect, but as it's describing internal implementation details, it shouldn't be relied on anyway.
Suggested documentation fix:
"""
You can deactivate a virtual environment by typing “deactivate” in your shell. The exact mechanism is platform-specific and is an internal implementation detail (typically a script of shell function will be used).
""" |
|
Date |
User |
Action |
Args |
2018-02-22 11:49:15 | paul.moore | set | recipients:
+ paul.moore, tim.golden, zach.ware, steve.dower, godaygo |
2018-02-22 11:49:15 | paul.moore | set | messageid: <1519300155.68.0.467229070634.issue32910@psf.upfronthosting.co.za> |
2018-02-22 11:49:15 | paul.moore | link | issue32910 messages |
2018-02-22 11:49:15 | paul.moore | create | |
|