There is an unjustified change of python3-flake8 executable:
This has broken build/rebuild of several packages (e.g. pki-core).
Unfortunately, there is no designated motivation (neither commit message nor BZ, nothing).
The most common way to point that an executable has python3 shebang is, for example, adding some suffix (like ".py3"). The executable which has python2 shebang is packaged as is. This is a "best practice" and as I guess current python build policy.
Of course, in the future, we should drop python2 support.
IMO, for now, the renaming (without compatibility saving) is not acceptable.
IMO, for now, the renaming (without compatibility saving) is acceptable.
Python2 EOL doesn't mean that we should drop everything about "python-" before Y2020.
There should be a correct discussed plan.
So, could I know about the real motivation?
For example, you could just provide a symbolic link to "python3-flake8" to keep some compatibility.
(In reply to comment #0)
> This has broken build/rebuild of several packages (e.g. pki-core).
Огласите весь список пжлста.