On Thursday, August 1, 2019 4:37:01 AM EDT Miro HronĨok wrote:
On 01. 08. 19 4:43, Steve Grubb wrote:
> Audit. But is seems that autotools shoul hard code the old sematics so
> that all packages do the right thing. It seems that python3 equivalents
> have been introduced. They do the right thing with the python migration.
> But there are things that are expectd to defaulto python 2.
https://src.fedoraproject.org/rpms/audit/pull-request/4
Autotools usually already does the right thing, aka choosing python2 if it
cannot find python. Using "python" in Fedora packages is forbidden anyway.
I applied your patch. Thanks.
But I am concerned that this is a bandaid because it patches the spec file and
all distributions will have to do the same thing.
-Steve
>>> Should they be hardcoded to mean python2 in autotools
and swig?
>>
>> No. That was kinda the point of this change: "python" means Python 3.
>>
>> Python 2 is deprecated and will be retired.
>
> Of course. But there is a legacy pyexec_PYTHON and there is a
> py3exec_PYTHON. What this change means is that they are one in the same.
> I do not think that is the intention. Because...is there a
> py2exec_PYTHON? I do not find it grepping my system. And this would need
> to have been advanced years ago, not today.
I don't know if there is py2exec_PYTHON. But autotools is no magic
(although it might appear as such), it just uses the commands available.
"python" command being forbidden in Fedora packages and "python"
command
meaning Python 3 have been advocated for years.
https://fedoraproject.org/wiki/FinalizingFedoraSwitchtoPython3
I'm sorry if that made you packaging work more complicated. But I just
don't agree that we should make exceptions here. (Nevertheless I would
have no idea how to do that, since every project ships their own pile of
autotools that may or may not use the "python" command that way or
another).