Bug 35998

Summary:	rename of python3-flake8 executable
Product:	Sisyphus	Reporter:	Stanislav Levin <slev>
Component:	python-module-flake8	Assignee:	obirvalger <obirvalger>
Status:	CLOSED FIXED	QA Contact:	qa-sisyphus
Severity:	normal
Priority:	P3	CC:	grenka
Version:	unstable
Hardware:	all
OS:	Linux

Description Stanislav Levin 2019-01-30 09:59:06 MSK

There is an unjustified change of python3-flake8 executable:
http://git.altlinux.org/tasks/archive/done/_214/220110/gears/100/git?p=git;a=commitdiff;h=1b6b0097918fa8678462702fedc03e1d75de8e41

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.

Comment 1 obirvalger@altlinux.org 2019-01-30 15:44:27 MSK

IMO, for now, the renaming (without compatibility saving) is acceptable.

Comment 2 obirvalger@altlinux.org 2019-01-30 15:45:31 MSK

https://pythonclock.org/

Comment 3 Stanislav Levin 2019-01-30 16:08:05 MSK

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.

Comment 4 Grigory Ustinov 2019-01-30 16:39:19 MSK

(In reply to comment #0) 
> This has broken build/rebuild of several packages (e.g. pki-core).

Огласите весь список пжлста.

Comment 5 Stanislav Levin 2019-01-31 09:26:52 MSK

Thanks.