Eryk Sun added the comment:
> We already update the current shell, so if you start a new
> terminal/Powershell/cmd/etc. instance it should have the
> updated variable.
The installer broadcasts an "Environment" message to top-level windows. In
practice, only Explorer listens for and
Steve Dower added the comment:
Sorry, but we don't have any way to update the current terminal process. We
already update the current shell, so if you start a new
terminal/Powershell/cmd/etc. instance it should have the updated variable.
The workaround you posted is fine. Directly adding
Forrest Shields added the comment:
As of 3.8.5 the current shell's PATH is outdated after a commandline
system-wide installation. This makes it very difficult to do a scripted
install of Python followed by the `python` or `pip` commands, as they will not
be found. In addition to modifying
Steve Dower added the comment:
That's exactly what is needed (though it still won't affect command prompts
that are already open).
The 3.5+ installer does it, so this only affects 2.7 and 3.4.
--
versions: +Python 3.4
___
Python tracker
Changes by Ned Deily n...@acm.org:
--
components: +Windows -Documentation
nosy: +paul.moore, steve.dower, tim.golden, zach.ware
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24757
___
eryksun added the comment:
I think a custom action can be added to Tools/msi/msisupport.c to send a
[WM_SETTINGCHANGE][1] Environment message to top-level windows. This makes
Explorer reload its environment from the registry, so starting a new command
prompt (cmd.exe) from Explorer will see
New submission from John Palermo:
Something I suppose many new users could stumble over: After installing Python
and trying out pip or python on the command line nothing is found. You have
to re-start Windows or re-log into your account.
I suggest adding this information to the documentation
