Migrate pyproject toml

[semuadmin]

setup.py is now deprecated and is scheduled to be dropped altogether in pip 23.

This PR makes a number of changes to update the project build framework:

1. It updates the paho.mqtt project structure to use pyproject.toml, while retaining setuptools as a back-end build platform.
2. It uses pyproject.toml tool configuration sections were available.
3. It drops support for Python versions <=3.6 as these are now end of life.
4. It adds a minimal VS Code workflow including the following tasks (Eclipse IDE users can simply ignore these):

• The Build task will produce wheel (.whl) and sdist (.tar.gz) install packages in the dist folder which can be uploaded to PyPi using twine.
• The Install Locally task will install this wheel using pip.
• Other VS Code tasks have been added mirroring the current GitHub Actions (GHA) CI worfklows.

NB: this PR only changes the build setup - no changes have been made to existing application code or test cases, so some existing CI workflows may still fail if they were failing previously.

Fixes #706

[cclauss]

@ralight Your review please.

[semuadmin]

@cclauss What's the game plan with regard to the lint_python pytest failures in GHA? AFAICS these are nothing to do with anything I've changed as part of this PR and I'm not best placed to resolve them?

[semuadmin]

Is this repo still actively maintained?

[PierreF]

Thanks for this contribution. Could you add a Signed-Off to your commit ? This is a requirement from Eclipse to acknowledge you agree with the ECA.

[PierreF]

We could drop this file, couldn't we ? I don't see reason to kept them.

[PierreF]

Without tox, how do we run linters ? I want to kept the ability to run linters & tests locally and not only relying on Github actions.

With tox, I only need to run two commands: tox -e py and tox -e lint. Everything was handled:

• creation of virtualenv, installation of dependency
• running test and linters command (for linters it's valuable, since we have multiple linters)

tox might not be the best tool for this usecase (here we don't use tox for it's ability to run on multiple Python versions, I use different Docker containers for that) that but it works and it's a well-known tools. I think we should kept it.

[akx]

Without tox, how do we run linters ?

One common option is https://pre-commit.com/ which can also be easily run in CI.

[cclauss]

It would probably be best to upgrade to pre-commit to automate the fast tests like ruff, codespell, black.

• https://pre-commit.com

[semuadmin]

sorry no longer have the bandwidth to progress this

[cclauss]

@akx Given that both @semuadmin and I have both closed our PRs, perhaps you can jump in with your automated tool for creating these PRs.

[akx]

@cclauss I don't have an automated tool per se - pyproject-migrator still needs hand-holding...