On 28. 06. 19 10:22, Peter Robinson wrote:
On Thu, Jun 27, 2019 at 5:20 PM Miro Hrončok
<mhroncok(a)redhat.com> wrote:
>
> On 27. 06. 19 17:15, Adam Williamson wrote:
>> On Thu, 2019-06-27 at 12:32 +0200, Miro Hrončok wrote:
>>> On 26. 06. 19 20:07, Adam Williamson wrote:
>>>> On Wed, 2019-06-26 at 13:57 -0400, Ben Cotton wrote:
>>>>>
https://fedoraproject.org/wiki/Changes/Python_means_Python3
>>>>>
>>>>> == Summary ==
>>>>> In package and command names, "Python" will mean
"Python 3".
>>>>>
>>>>> Users installing and running Python or Python packages without
>>>>> specifying a version will get Python 3.
>>>>>
>>>>> Running <code>python</code> will run
<code>python3</code>.
>>>>
>>>> Oh, man. I thought we'd decided against this in the past?
>>>
>>> We did. Circumstances changed.
>>
>> Out of interest, what circumstances?
>
> Mostly date.
>
>
https://fedoraproject.org/wiki/Changes/Python_means_Python3#Benefit_to_Fe...
>
> "The name 'Python' will not refer to software that will be unmaintained
upstream
> for most of Fedora 31's lifetime and retired from Fedora 32."
>
> Also, before, we have decided to not do this, as it was against the upstream
> recommendation. That recommendation is changing now as Python 2 approaches EOL.
>
> See
https://github.com/python/peps/pull/989
>
>>>> I'm worried
>>>> about the cost/benefit ratio on such a change.
>>>
>>> What worries you do most about "the cost"?
>>
>> I mean, generalized existential dread? :)
>>
>> The most obvious is scripts with #!/usr/bin/python . OK, we can try and
>> find every single one in the distro and patch them (though I'm sure
>> some will get missed somehow)
>
> Yes, we've already done that.
>
https://fedoraproject.org/wiki/Changes/Move_usr_bin_python_into_separate_...
>
https://fedoraproject.org/wiki/Changes/Make_ambiguous_python_shebangs_error
>
>> but there will certainly be ones that
>> *aren't part of the distro* that get bitten by this.
>
> There, you are correct. However, would we want "python" to mean Python 2
> forever? Or do we want to phase things out slowly and make a designated point in
> the future, where this is changed?
I suppose to me the big one with be pypi and what the expectation in
that community is around which version of python points to
/usr/bin/python, have they been running tests against the repositories
there and if it'll break things installed via pip.
In my experience pip installed packages generally handle shebangs well (e.g.
they set the shebang to the pip's interpreter). Of course there might be some
packages where this is not true, but the enormous adaptation of using Python
virtual environments IMHO battle tested this for years.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok