This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author d3r3kk
Recipients brett.cannon, d3r3kk, paul.moore, steve.dower, tim.golden, zach.ware
Date 2020-03-23.17:02:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1584982965.36.0.938255145596.issue38972@roundup.psfhosted.org>
In-reply-to
Content
Where would we like to put this information?

My proposal would be to add this in a combination of places:

1. Add a further note near the symlinks on Windows comment in this document: `Doc\using\venv-create.inc`

2. Add a blurb in the Activate.ps1 script itself, so that any user can see it very near where the problem might occur. `Lib\venv\scripts\common\Activate.ps1`

I'd probably put something like the following in there:
---

.. note::
   On Microsoft Windows, it may be required to enable the ``Activate.ps1``
   script by setting the execution policy for the user. You can do this by
   issuing the following Powershell command from a Powershell command window:

   PS C:\Users\user> Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

   See `About Execution Policies 
   <https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_execution_policies?view=powershell-7>`_
   for more information.

---

(This would exist as a ".Notes" section in the Activate.ps1 script)


What do folks think?
History
Date User Action Args
2020-03-23 17:02:45d3r3kksetrecipients: + d3r3kk, brett.cannon, paul.moore, tim.golden, zach.ware, steve.dower
2020-03-23 17:02:45d3r3kksetmessageid: <1584982965.36.0.938255145596.issue38972@roundup.psfhosted.org>
2020-03-23 17:02:45d3r3kklinkissue38972 messages
2020-03-23 17:02:44d3r3kkcreate