FS#50091 - [python-apache-libcloud] package name not following guidelines
Attached to Project:
Community Packages
Opened by Carl George (carlwgeorge) - Monday, 18 July 2016, 22:16 GMT
Last edited by Balló György (City-busz) - Wednesday, 27 March 2019, 17:07 GMT
Opened by Carl George (carlwgeorge) - Monday, 18 July 2016, 22:16 GMT
Last edited by Balló György (City-busz) - Wednesday, 27 March 2019, 17:07 GMT
|
Details
Description:
According to the Python package guidelines [1], Python library packages should be named "python-{modulename}". Based on that, I think that the python-apache-libcloud package should be renamed to python-libcloud, since in Python you would use "import libcloud". [1]: https://wiki.archlinux.org/index.php/Python_package_guidelines |
This task depends upon
Closed by Balló György (City-busz)
Wednesday, 27 March 2019, 17:07 GMT
Reason for closing: Won't fix
Additional comments about closing: Package removed from the official repositories.
Wednesday, 27 March 2019, 17:07 GMT
Reason for closing: Won't fix
Additional comments about closing: Package removed from the official repositories.
python-novaclient -> python-python-novaclient
python-jinja -> python-Jinja2
python-crypto -> python-pycrypto
python-geoip -> python-GeoIP
On the other hand, if the guidelines stick with using the module name, other packages are already going against that and using the PyPI name (python-docker-py is imported as docker, python-beautifulsoup4 is imported as bs4, etc). Perhaps the guidelines should allow using either the PyPI project name or the importable module name, at the package maintainer's discretion.
Either way, I think the most appropriate package name for the libcloud Python library should be python-libcloud.