RFC: Packaging py3 packages without setuptools
Hi folks.
So, looks that we need to deal with py3 packages that are shipped without setup.py
.
More soon than later.
I went to browse around what other distributions are doing, but I've not found anything in the official pacakge guidelines [1]
A this point, I think we have three options:
- Find a way to package with poetry
- Using dephell (which converts pyprojects.toml file into setup.py, and then proceed with the well-accustomed setuptools)
- Using an alternative to dephell.
I tried the 1, but I was unable to understand how to use a builddir. I tried the 2, but dephell, as the name suggest, it's an hell of dependencies. It has circular dependencies too (e.g. yaspin is a required package to build dephell, but yaspin requires dephell....).
Then I went to option 3, landing to pyproject2setuppy package (developed by a Gentoo developer in the Gentoo Python Guide and ArchLinux [2])
It has one simple dependency (py3-toml) and does his job.
I've built it and used to upgrade gvm-tools, and it worked correctly.
Of course, another option would be having abuild managing it, but that's another story.
What do you think? How do we want to proceed?
Any suggestions are welcome... thanks.
.: Francesco Colista
[1] Fedora: https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/
Debian: https://www.debian.org/doc/packaging-manuals/python-policy/
[2] ArchLinux: https://wiki.archlinux.org/index.php/Talk:Python_package_guidelines#pyproject2setuppy_as_dephell_alternative_for_flit/poetry
Gentoo: https://dev.gentoo.org/~mgorny/python-guide/distutils.html?highlight=poetry