flit_core-3.10.0

[Bruce Dubbs]

New minor version.

[Bruce Dubbs]

Version 3.10

flit publish can now use PyPI tokens stored in keyring, either project tokens with a ‘username’ like pypi_token:project:project_name (use the normalised form of the name) or user tokens (pypi_token:user:username).

The --python option can now take the path of a virtualenv folder, as an alternative to a Python executable.

Flit will work with current development versions of Pythona again.

The flit command line package now requires Python 3.8 or above. flit_core still works with Python 3.6 or above.

The metadata in packages now has the names of optional dependency groups (“extras”) normalised, complying with version 2.3 of the metadata standard.

The flit command line package now depends on pip.

Fix potential substitution of environment variables into passwords read from .pypirc files.

A warning is now shown when building packages which specify the old flit.buildapi backend, which should be replaced by flit_core.buildapi. It’s a good idea to always set a maximum version for the build requirement, to protect against changes in future major versions of Flit.

Avoid using the deprecated datetime.utcfromtimestamp().

Flit now has a SECURITY.md file in the Github repository.

The tests for flit_core are no longer part of the installed package, reducing the size of the wheels.

[Bruce Dubbs]

Fixed at commit a9517d383c :

Update to linux-6.11.6.
Update to libcap-2.71.
Update to setuptools-75.3.0.
Update to flit_core-3.10.0.