Request #26340 has been rejected by ainola [1]: The name "mkdocs" appears to be correct in accordance to the rules on naming Python packages [1]. As this is a standalone program and not a library closely related to the Python ecosystem, it should remain as is and python-mkdocs should instead be merged into this package. Indeed, looking through the "getting started" guide on mkdocs' website suggests that the only interaction with mkdocs is as a utility, much like Hugo. I see that there are many "modules" for mkdoc that have a python- prefix as well; I would also argue that they should simply be "mkdoc- foo" rather than "python-mkdoc-foo" as, again, there's no real relationship to the Python ecosystem. [1] https://wiki.archlinux.org/title/Python_package_guidelines#Package_naming [1] https://aur.archlinux.org/account/ainola/