On 10/21/21 1:18 PM, Dmitry Tantsur wrote:
Side note: calling setup.py is essentially deprecated: https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html <https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html>
This is essentially bullshit: the replacement method proposed in this page is supposed to be "pip install", which does dependency resolving and download from the internet, which is not useful (and even forbidden at package build time) for downstream distributions. If using pip is the only thing that upstream Python people are proposing to distributions, without any distro-specific options (like the --install-layout=deb option of setuptools, for example), then something really wrong is going on. Unless I missed something and upstream Python likes us from now on?!?
Right now, when looking at the skyline-apiserver as the Debian OpenStack package maintainer, I'd need a lot of manual work to use pyproject.toml instead of my standard tooling.
PyProject is the universal way forward, you'll (and we'll) need to adopt sooner or later.
There's currently an effort going on to get poetry packaged in Debian. However, we're not there yet, but I have hope for it. Anyway, this is orthogonal to what I wrote: IMO skyline needs to conform with everything that's made elsewhere in OpenStack, and adopt the same standards. If OpenStack is ever to move to Poetry (which means: all projects), then maybe I will revise this thinking. Cheers, Thomas Goirand (zigo)