FS#64792 - [flake8] Package name inconsistent with other python packages
Attached to Project:
Community Packages
Opened by Bradley (sirrus233) - Tuesday, 10 December 2019, 11:09 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:09 GMT
Opened by Bradley (sirrus233) - Tuesday, 10 December 2019, 11:09 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:09 GMT
|
Details
Description:
Hey, just a quick complaint (sorry!) Most python packages in the arch ecosystem are named python-{package} or python2-{package} accordingly. Even the python2 package for flake8 follows this convention. Would a name change from flake8 to python-flake8 make sense here? |
This task depends upon
Closed by Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:09 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/flake8/issues/1
Saturday, 25 November 2023, 20:09 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/flake8/issues/1
Comment by
Bruno Pagani (ArchangeGabriel) -
Tuesday, 19 October 2021, 10:37 GMT
Comment by Bradley (sirrus233) -
Tuesday, 19 October 2021, 11:44 GMT
Comment by Yauhen (actionless) -
Thursday, 24 November 2022, 18:50 GMT
Comment by
Buggy McBugFace (bugbot) - Tuesday,
08 August 2023, 19:11 GMT
Well it’s the case that it provides a binary and not just a
library. See also e.g. spyder, etc.
As does python-black, and yet that name is the other way around.
:)
lots of python packages provide "binaries", this exception feels
weird - it need some better-described ruling or just move all
packages like this to `python-` prefix
This is an automated comment as this bug is open for more then 2
years. Please reply if you still experience this bug otherwise
this issue will be closed after 1 month.