On 7 February 2018 at 19:35, Steve Dower wrote:
> Checking the Version (!=SysVersion) property should be enough (and perhaps
> we need to set it properly on install). The launcher currently only works
> with PythonCore entries anyway, so no need to worry about other
my Windows phone
From: Paul Moore
Sent: Wednesday, February 7, 2018 7:37
To: Alex Walters
Cc: Python-Ideas
Subject: Re: [Python-ideas] Possible Enhancement to py Launcher - set default
I don't think so. As an example, what registry keys would Anaconda
write to say that Release 5.2.1.7 is a pre
gt;> Cc: Steve Barnes <gadgetst...@live.co.uk>; Python-Ideas > id...@python.org>
>> Subject: Re: [Python-ideas] Possible Enhancement to py Launcher - set
>> default
>>
> ...
>>
>> IMO the biggest technical issue with this is that as far as I can see
>>
> -Original Message-
> From: Paul Moore [mailto:p.f.mo...@gmail.com]
> Sent: Wednesday, February 7, 2018 4:15 AM
> To: Alex Walters <tritium-l...@sdamon.com>
> Cc: Steve Barnes <gadgetst...@live.co.uk>; Python-Ideas id...@python.org>
> Subject: Re: [P
On 7 February 2018 at 05:36, Alex Walters wrote:
> While this thread has focused on the location and means of managing py.ini,
> I think there is a more general solution that should be considered to the
> original problem, as described. The problem isn't that it's
-ideas-bounces+tritium-
> list=sdamon@python.org] On Behalf Of Steve Barnes
> Sent: Monday, February 5, 2018 3:11 AM
> To: Python-Ideas <python-ideas@python.org>
> Subject: [Python-ideas] Possible Enhancement to py Launcher - set default
>
> When a new version of pytho
> -Original Message-
> From: Paul Moore [mailto:p.f.mo...@gmail.com]
> Sent: Tuesday, February 6, 2018 6:31 AM
> To: Alex Walters <tritium-l...@sdamon.com>
> Cc: Jan Claeys <li...@janc.be>; Python-Ideas <python-ideas@python.org>
> Subject: Re: [Pyth
as] Possible Enhancement to py Launcher - set default
I'm reluctant to expand the feature set of the launcher in this
direction. It's written in C, and tightly focused on being a
lightweight launcher. Adding code to manage user options and persist
them to the py.ini file would be a non-trivial overh
Hi all,
Just want to point out that if tools can accept a config file in
a cross-platform standard location
(perhaps in addition to a platform-specific one),
then that is incredibly useful.
Just search on Github for "dotfiles", and see how many people
store their configuration in a git repo, so
On 6 February 2018 at 15:23, Eric Fahlgren wrote:
> Right, different planets, but orbiting the same star. I was thinking about
> the consolidation of the Windows registry layout a year or two ago, don't
> recall who spearheaded that (Steve Dower?). In any case, if the
On Tue, Feb 6, 2018 at 6:47 AM, Paul Moore wrote:
> There are a few different points here:
>
> 1. There's no relationship between pip and the py launcher - they are
> separate tools/projects. Any co-operation in terms of file locations
> would have to be a result of common
There are a few different points here:
1. There's no relationship between pip and the py launcher - they are
separate tools/projects. Any co-operation in terms of file locations
would have to be a result of common standards. Those would normally be
platform standards, not Python ones.
2. On
My only request for change would be to consolidate the various tools'
behavior wrt their .ini file locations. Pip, for example, wants the file
in ~/pip/pip.ini, while py.exe (on Windows) wants its py.ini in
$LOCALAPPDATA. If they were all in a common location (or the same file
with separate
I'm reluctant to expand the feature set of the launcher in this
direction. It's written in C, and tightly focused on being a
lightweight launcher. Adding code to manage user options and persist
them to the py.ini file would be a non-trivial overhead, as well as
being hard to maintain (because C
ys
> Sent: Monday, February 5, 2018 10:47 AM
> To: python-ideas@python.org
> Subject: Re: [Python-ideas] Possible Enhancement to py Launcher - set
> default
>
> On Mon, 2018-02-05 at 11:04 +, Paul Moore wrote:
> > On 5 February 2018 at 08:10, Steve Barnes <gadgetst.
On Mon, Feb 5, 2018 at 6:04 AM, Paul Moore wrote:
> On 5 February 2018 at 08:10, Steve Barnes wrote:
>> When a new version of python is in alpha/beta it is often desirable to
>> have it installed for tests but remain on a previous version for day to
On Mon, 2018-02-05 at 11:04 +, Paul Moore wrote:
> On 5 February 2018 at 08:10, Steve Barnes
> wrote:
> > When a new version of python is in alpha/beta it is often desirable
> > to have it installed for tests but remain on a previous version for
> > day to day use.
> >
On 05/02/2018 11:04, Paul Moore wrote:
> On 5 February 2018 at 08:10, Steve Barnes wrote:
>> When a new version of python is in alpha/beta it is often desirable to
>> have it installed for tests but remain on a previous version for day to
>> day use.
>>
>> However,
On 5 February 2018 at 08:10, Steve Barnes wrote:
> When a new version of python is in alpha/beta it is often desirable to
> have it installed for tests but remain on a previous version for day to
> day use.
>
> However, currently the Windows py launcher defaults to the
When a new version of python is in alpha/beta it is often desirable to
have it installed for tests but remain on a previous version for day to
day use.
However, currently the Windows py launcher defaults to the highest
version that it finds, which means that unless you are very careful you
20 matches
Mail list logo