Packagers: Can we use poetry build for package? Drop Python 2?

Goal

Consolidate project dev utilities, e.g. virtualenv, package versioning/pinning, and build + publishing: poetry

• https://repology.org/project/tmuxp/versions
• https://pkgs.org/download/tmuxp

Question Will removing setup.py from source break compatibility?

poetry build link creates:

1. dist/packagename-<version>.tar.gz (similar to python setup.py sdist), and
2. A wheel python3 setup.py bdist_wheel --universal

What would still be available?

• .tar.gz package and wheel on PyPI
• ability to create sdist / wheel via poetry build (would require having poetry installed with a compatible version)
• https://github.com/mgorny/pyproject2setuppy - generate setup.py without requiring poetry

Package maintainers (repology)

Drop Python 2?

• Gentoo - Confirmed via email Aug 17
• Redhat / Fedora - Confirmed via email Aug 23 2020
• Debian / Ubuntu - Python 2 will be removed in Bullseye (Email Aug 22nd)
• FreeBSD - Confirmed via email Aug 17
• Slackpackages
• Arch

Poetry-only (remove setup.py in src)?

• Gentoo - Confirmed via email Aug 17
• Redhat / Fedora - Confirmed via email Aug 23 2020
• Debian / Ubuntu - Possibly an issue (email Aug 22 2020)
• FreeBSD - Confirmed via email Aug 17 - ok since it generates a setup.py file
• Slackpackages
• Arch

Start by reviewing the existing setup.py and the linked poetry build documentation. Determine whether removing setup.py preserves the listed sdist and wheel packaging paths and whether the remaining distributors support dropping Python 2; done means reaching a maintainer-backed packaging decision.