>Upstream describes itself as "a deep learning toolkit for Text-to- >Speech, battle-tested in research and production" [1], so this >software is apparently designed as a Python module rather than a CLI >application. As a result, python-tts is a better package name per >Python packaging guidelines
Nevertheless, this is an application too. From ArchWiki Python package guidelines (*emphasis* mine): " For Python 3 library modules, use python-modulename. Also use the prefix if the package provides a program that is strongly coupled to the Python ecosystem (e.g. pip or tox). For other *applications*, use only the program name. " Therefore the correct assessment in my view is still to name the package 'tts' and add provides & conflicts for 'python-tts'. On 11 December 2023 12:24:59 GMT+01:00, [email protected] wrote: >Request #47235 has been Rejected by yan12125 [1]: > >Upstream describes itself as "a deep learning toolkit for Text-to- >Speech, battle-tested in research and production" [1], so this >software is apparently designed as a Python module rather than a CLI >application. As a result, python-tts is a better package name per >Python packaging guidelines [2]. > >[1] https://github.com/coqui-ai/TTS >[2] https://wiki.archlinux.org/title/Python_package_guidelines > >[1] https://aur.archlinux.org/account/yan12125/
