Nick Coghlan writes:
> Personally, I think a See Also note pointing to ftfy in the "codecs"
> module documentation would be quite a reasonable outcome of the thread
Yes please. The more I hear about purported use cases (with the
exception of Nathaniel's "don't crash when I manipulate the DOM"
I actually like the idea of being able to modify the py.ini file to set the
default from py.exe. That seams like the most intuitive thing to me.
> -Original Message-
> From: Python-ideas [mailto:python-ideas-bounces+tritium-
> list=sdamon@python.org] On Behalf Of Jan Claeys
> Sent: Mo
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 cod
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 secti
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 Window
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 standards. Those would
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 various
> tools either foll
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 t
A thought for you might be to consider an option to just produce, (on request),
a template config file with the default settings and commented out options then
display the path to the user. This would fit in with other tools that I have
come across while keeping the configuration options that th
By now, it sounds right to me that I should implement these codecs in a
package. I accept that I've established the use case, but not sufficiently
established why it belongs in Python.
The package can easily be ftfy -- although I should point out that what's
in ftfy at the moment isn't quite right
> -Original Message-
> From: Paul Moore [mailto:p.f.mo...@gmail.com]
> Sent: Tuesday, February 6, 2018 6:31 AM
> To: Alex Walters
> Cc: Jan Claeys ; Python-Ideas
> Subject: Re: [Python-ideas] Possible Enhancement to py Launcher - set
> default
>
> I'm reluctant to expand the feature se
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 difficult or
non-obvious how to set the default python for the py.exe launcher (that's a
12 matches
Mail list logo