Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#39752 - [flake8] The naming is inconsistent with other python packages

Attached to Project: Community Packages
Opened by Wieland Hoffmann (Mineo) - Saturday, 05 April 2014, 08:16 GMT
Last edited by Felix Yan (felixonmars) - Monday, 23 June 2014, 07:54 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Felix Yan (felixonmars)
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: The flake8 PKGBUILD builds the flake8 (for python 3) and
flake8-python2 packages but depends on python-pyflakes, python-nose
and or python2-pyflakes, python2-nose. Can those packages be named
consistently either python-foobar and python2-foobar or foobar and
foobar-python2 or whatever but not follow a different naming scheme
depending on criteria I don't understand?
This task depends upon

Closed by  Felix Yan (felixonmars)
Monday, 23 June 2014, 07:54 GMT
Reason for closing:  Fixed
Additional comments about closing:  1:2.2.0-1
Comment by Doug Newgard (Scimmia) - Saturday, 05 April 2014, 15:29 GMT
Generally, the python{,2}-<name> naming scheme is for libraries, where programs will just use the normal name. Everything seems right here.
Comment by Felix Yan (felixonmars) - Saturday, 05 April 2014, 15:54 GMT
According to the wiki [1], "For applications, use the program name."

flake8 is a code checker, and used as a tool rather than a library. So I don't see a problem in the current naming scheme.

[1] https://wiki.archlinux.org/index.php/Python_Package_Guidelines#Package_naming
Comment by Wieland Hoffmann (Mineo) - Tuesday, 22 April 2014, 12:49 GMT
  • Field changed: Percent Complete (100% → 0%)
I wasn't talking about the naming scheme dictated by the packaging guidelines. Nose and pyflakes are also applications and they follow the python{,2}-foo naming scheme. All I was asking for is to have the flake8 packages named like other python applications and not randomly different.
Comment by Felix Yan (felixonmars) - Tuesday, 22 April 2014, 13:01 GMT
The name "flake8" is following the same naming scheme as other python applications like bpython, ipython, cython, etc, which is not "randomly different". The only tricky part is the python 2.x version, and I don't think "flake82" would be a better name, it only adds more confusion.
Comment by Wieland Hoffmann (Mineo) - Wednesday, 23 April 2014, 10:41 GMT
"flake8-python2" is one of only 8 packages with a "-python2" suffix (one of only two that are applications), compared to more than 300 with a "python2-" prefix (yes, I know, not all of those are applications, but those related to flake8 follow this pattern).
Comment by Felix Yan (felixonmars) - Wednesday, 23 April 2014, 10:42 GMT
So you think
pep8 / python2-pep8
flake8 / python2-flake8

is better right?

Well, it's okay for me.
Comment by Wieland Hoffmann (Mineo) - Sunday, 27 April 2014, 09:39 GMT
Yes, I would prefer those names.

Loading...