Re: [Python-Dev] PEP 394 update proposal: Allow changing the `python` command in some cases

On 04/27/18 02:03, Ben Finney wrote: Ben Finney writes: Petr Viktorin writes: […] we feel that the only way to *enforce* that guidelines is to provide environments where the `python` command does not work (unless explicitly installed).

Re: [Python-Dev] PEP 394 update proposal: Allow changing the `python` command in some cases

Ben Finney writes: > Petr Viktorin writes: > > > […] we feel that the only way to *enforce* that guidelines is to > > provide environments where the `python` command does not work > > (unless explicitly installed). > > Yes. The ‘python’ command is

Re: [Python-Dev] PEP 394 update proposal: Allow changing the `python` command in some cases

Petr Viktorin writes: > In Fedora, I found that PEP 394's strict recommendation that `python` > points to `python2` is holding us back. I have read the message, but I don't see how you draw the link that PEP 394 is holding you back. > The problems are: > - For developers

[Python-Dev] PEP 394 update proposal: Allow changing the `python` command in some cases

Hello, In Fedora, I found that PEP 394's strict recommendation that `python` points to `python2` is holding us back. From discussions on Zulip and elsewhere it's clear that this recommendation is not changing any time soon, but I would like to officially relax it in several cases. The