[aur-general] Naming convention for Python 2 and 3 apps
Xyne
xyne at archlinux.ca
Wed Nov 28 23:58:28 EST 2012
On 2012-11-28 21:36 -0500
Allen Li wrote:
>On Wed, Nov 28, 2012 at 07:07:27AM -0500, Stéphane Gaudreault wrote:
>> If it is an application and does not provide a module that could be
>> included in another application, then I suggest to depend on python3
>> only and keep the name "flake8".
>>
>> Stéphane
>>
>
>That sounds reasonable enough, but I think we'll still need separate
>versions here. flake8 is a code checker, and it seems to run into
>trouble between Python 2 and 3 code since it runs the code when checking
>it. Backward incompatibility is troublesome.
>
>*-python is no good since it looks like it's used for Python APIs and
>hooks.
Use "flake8" (Python 3) and "python2-flake8". If you cannot rename the installed
files in python2-flake8 to avoid conflicts, add a "conflict=(python8)" to the
PKGBUILD.
In general the "python*-" prefix is reserved for library packages, but its real
purpose (imo) is simply to indicate that a package is closely tied to some
version of Python.
While we're on the subject, can someone please explain to me again why we use
"python-" and not "python3-" for Python 3 libraries?
Regards,
Xyne
More information about the aur-general
mailing list