On Fri, Feb 5, 2021 at 6:17 AM Barry Scott <[email protected]> wrote:
>
> Rather than reply point by point I will summarise my input.
>
> I think that utf-8 mode is a great idea.
>
> I think that an .INI file in the style that py.exe uses is better then env 
> var.
>
> Env var on WIndows could be used but there can be surprises with the way
> windows merges user and system env vars. Maybe that only with PATH that
> is very odd.
>
> I'm hoping that the solution implemented allows new users to get a great
> experience and also that advanced users can get control of the mode.
>
> Personally I'd prefer to have files that I edit to configure python then 
> registry
> keys. I can put files into git, not exmple. I have to work hard to manage 
> registry
> keys via git.
>

I 100% agree with you. And pyvenv.cfg satisfies all your needs.

When compared pyvenv.cfg with py.ini-like new config file:

Cons:

* Need system privilege to change the setting of system installed Python.
  * But user can install another Python, or create venv anyway.

Pros:

* The file is already supported.
  * No need to lookup another file at startup.
* No need to edit any file outside the install location.
  * Easy to clean uninstall
  * Portable app friendly
* One file per environment
  * Breaking the config file affects only one environment.

So I still prefer pyvenv.cfg.

-- 
Inada Naoki  <[email protected]>
_______________________________________________
Python-ideas mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-ideas.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/BT75AQXDG6ZZ5FUF2HCO75XFR777YQ27/
Code of Conduct: http://python.org/psf/codeofconduct/

Reply via email to