Arch Linux User Repository

It seems to me that having the python as explicit is more correct, while at the same time is unnecessary. I checked the official package and almost 40% of python packages (that depend on other python modules) do not depend on python. This tells me that this is mostly optional, so for the moment I will leave the package as it is, though I may decide to change this in the future if there is, for example, a change in the guidelines.

@micwoj92 I value your contributes to Arch. I can see it going either direction. There was a time when namcap would warn you when you listed transitive dependencies. I was just pointing out that the wiki says you do not need to.

@daniel_shub There isn't a wrong answer in this, but I go around and post these things in comments because I prefer that all direct deps are listed as this is also a warning about implicit dependencies in namcap.

The wiki says you do not need to include python as a dependency. The wiki covers "transitive" dependencies at https://wiki.archlinux.org/title/Arch_package_guidelines#Package_dependencies and https://wiki.archlinux.org/title/PKGBUILD#Dependencies and the general rule is "The depends array should list all direct first level dependencies even when some are already declared transitively." This would suggest the python package should be included, but it then goes on to explain more that "In some cases this is not necessary and may or may not be listed, for example glibc cannot be uninstalled as every system needs some C library, or python for a package that already depends on another python- module, as the second module must per definition depend on python and cannot ever stop pulling it in as a dependency."

Not necessary per se, just to declare all dependencies explicitly.

Please explain (I mean, why you think is necessary, given that python is pulled anyway)

Please add python to deps.