On Sun, Feb 26, 2017 at 3:09 PM, ChrisW wrote:
> On Saturday, 25 February 2017 07:21:30 UTC, eryk sun wrote:
>> On Fri, Feb 24, 2017 at 12:38 PM, ChrisW wrote:
>> > However, I've installed Python 3.6 with the 'include PATH' checkbox ticked
>> > for my user only, and although C:\Windows\py.exe exi
On Saturday, 25 February 2017 07:21:30 UTC, eryk sun wrote:
> On Fri, Feb 24, 2017 at 12:38 PM, ChrisW wrote:
> > However, I've installed Python 3.6 with the 'include PATH' checkbox ticked
> > for my user only, and although C:\Windows\py.exe exists, it has not been
> > added to my PATH.
> >
> > I
On Friday, 24 February 2017 18:09:01 UTC, Irmen de Jong wrote:
> On 24-2-2017 13:38, ChrisW wrote:
> > The installation guidelines for Python 3.6 say:
> >
> > "Per-user installations of Python do not add the launcher to PATH unless
> > the option was selected on installation."
> > (https://docs
On Fri, Feb 24, 2017 at 12:38 PM, ChrisW wrote:
> However, I've installed Python 3.6 with the 'include PATH' checkbox ticked
> for my user only, and although C:\Windows\py.exe exists, it has not been
> added to my PATH.
>
> I also tried installing for all users, and this also doesn't add it to the
On 24-2-2017 13:38, ChrisW wrote:
> The installation guidelines for Python 3.6 say:
>
> "Per-user installations of Python do not add the launcher to PATH unless the
> option was selected on installation."
> (https://docs.python.org/3/using/windows.html#from-the-command-line).
>
> However, I've
The installation guidelines for Python 3.6 say:
"Per-user installations of Python do not add the launcher to PATH unless the
option was selected on installation."
(https://docs.python.org/3/using/windows.html#from-the-command-line).
However, I've installed Python 3.6 with the 'include PATH' che
