Update package metadata

[ofek]

Motivation and Context

Hello there! The Python packaging ecosystem has standardized on the interface for build backends (PEP 517/PEP 660) and the format for metadata declaration (PEP 621/PEP 631). As a result, the execution of setup.py files is now deprecated.

So, I'm spending my free time updating important projects so that they are modernized and set an example for others 😄

Some other Django projects that have been updated:

• Django Anymail
• Django Debug Toolbar (jazzband)
• Django NYT
• Django OTP
• Django OTP Agents
• Django OTP Twilio
• Django OTP YubiKey
• Django Places
• Django Simple History (jazzband)
• Django Wiki

Description

This implements PEP 621, obviating the need for setup.py, setup.cfg, and MANIFEST.in. The build backend hatchling (of which I am a maintainer in the PyPA) is now used as that is the default in the official Python packaging tutorial. Hatchling is available on all the major distribution channels such as Debian, Fedora, Arch Linux, conda-forge, Nixpkgs, Alpine Linux, FreeBSD/OpenBSD, Gentoo Linux, MacPorts, OpenEmbedded, Spack, MSYS2, etc.

Notes

• The project is no longer polluted with build artifacts such as a *.egg-info directory (the source distribution on PyPI ships that).
• The licenses are now properly included in the user's environments when installed.
• (See "Why Hatch?") The project now supports static analysis for external tools such as IDEs for editable installations. With setuptools, you must provide additional configuration which means that by default, for example, you would not get autocompletion in Visual Studio Code. This is marked as a legacy feature and may in fact be removed in future versions of setuptools.

Related Issue

jazzband/help#313