On 08/31/18 13:41, Miro Hrončok wrote:
On 31.8.2018 13:30, Miro Hrončok wrote:
> On 31.8.2018 09:05, Igor Gnatenko wrote:
>> On Wed, Aug 22, 2018 at 10:02 PM Ben Cotton <bcotton(a)redhat.com
>> <mailto:firstname.lastname@example.org>> wrote:
>> == Summary ==
>> The <code>/usr/lib/rpm/redhat/brp-mangle-shebangs</code>
>> policy script will be changed to make the build fail when it sees an
>> ambiguous python shebang, such as <code>#!/usr/bin/python</code>
>> <code>#!/usr/bin/env python</code>. (The script has been warning
>> these cases for 2 Fedora releases already, saying ''This will become
>> an ERROR''.)
>> Why can't we add something like
> What about the following:
> If %_mangle_python_shebnags_to is set, the script will mangle to that
> (unless it's unversioned python again or otherwise invalid).
> If %_mangle_python_shebnags_to is not set (the default), the script
> will error (as currently proposed).
Hmm... Given that upstream PEP 394 allows unversioned "python" for
py2/py3 straddling code, maybe the name could be even shorter?
Maybe what we need is just a way to say the package(r) is aware of
python3 and the latest (as of now) upstream recommendations. With that
info, mangling "/usr/bin/env python" to "/usr/bin/python3" is the
thing to do.
Probably %_mangle_unversioned_python_shebnags_to becasue that's
BTW, if you copy/paste this, be aware there^^ is a typo :)
thing that would be changed.