Modernize packaging a bit

[bluetech]

Adding pyproject.toml allows the package to be installed using PEP517 instead of legacy setup.py install method. At least pip says so in a warning when installing without the wheel package available.

Change setup.py to setup.cfg (using a script[0]) because setup.py is out of fashion these days.

Remove MANIFEST.ini since LICENSE is implied[1].

[0] https://github.com/gvalkov/setuptools-py2cfg
[1] https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-license-files

[JelleZijlstra]

Might as well put this config in pyproject.toml?

[bluetech]

I don't have python 3.5 installed, but I suspect it won't work with it. I'll try getting py3.5 and check it though.

[hauntsaninja]

We can drop 3.5, 3.6 and 3.7 support

[bluetech]

@hauntsaninja great, that might help. I'll send a PR to do this first.

[bluetech]

Changed from setup.cfg to pyproject.toml, seems to work. Added it in a separate commit just in case.

One final change can be done to eliminate the tool.setuptools py-modules section by moving from a single module mypy_extensions.py to a package, then setuptools can auto-discover it. Actually seems to work with the module as well, so just removed it.

[nicoonoclaste]

I'm absolutely not a mypy dev, but I noticed this PR while reporting an issue so have a drive-by review ❤️

This all seems good to me, and I only found a minor issue that (I believe) is present in the current version as well.

Thanks a bunch for tidying up the packaging :)

[nicoonoclaste]

This should specify the content type, as setuptools otherwise assumes it's ReStructured Text:

Suggested change

	readme = "README.md"
	readme = { file = "README.md", content-type = "text/markdown; charset=UTF-8" }

[cdce8p]

That's not necessary. Setuptools can detect that it's a markdown file and adds Description-Content-Type: text/markdown to the core metadata.

[cdce8p]

One final change can be done to eliminate the tool.setuptools py-modules section by moving from a single module mypy_extensions.py to a package, then setuptools can auto-discover it. Actually seems to work with the module as well, so just removed it.

I'd keep it. Explicit is often better than implicit. I.e. add

[tool.setuptools]
py-modules = ["mypy_extensions"]

--
There are also some conflicts which need to be resolved.

[cdce8p]

That's not necessary. Setuptools can detect that it's a markdown file and adds Description-Content-Type: text/markdown to the core metadata.

[cdce8p]

Suggested change

	license = {file = "LICENSE"}
	license = {text = "MIT"}

I'd suggest to use the SPDX license string here instead. The license file is already included by setuptools.

[cdce8p]

Suggested change

	"Programming Language :: Python :: 3.11",
	"Topic :: Software Development",
	"Programming Language :: Python :: 3.11",
	"Programming Language :: Python :: 3.12",
	"Topic :: Software Development",

Support for 3.12 was declared in 9dd6d98

[cdce8p]

The changes here have been merged as part of 6d9c7b7. Thanks a lot @bluetech!
Guess this one can be closed now.

[hauntsaninja]

Thank you!