2c12f0947dAccepting request 1237618 from devel:languages:python
factory
Ana Guerrero
2025-01-15 16:41:58 +00:00
d0f06c305e- Update to 3.10.1: * flit publish can now use PyPI tokens stored in keyring (PR #649), 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 (PR #667). * Flit will work with current development versions of Pythona again (PR #684). * The flit command line package now requires Python 3.8 or above (PR #660). 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 (PR #676, PR #697). * The flit command line package now depends on pip (PR #647). * Fix potential substitution of environment variables into passwords read from .pypirc files (PR #652). * A warning is now shown when building packages which specify the old flit.buildapi backend, which should be replaced by flit_core.buildapi (PR #674). 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() (PR #682). * Flit now has a SECURITY.md file in the Github repository (PR #665). * The tests for flit_core are no longer part of the installed package, reducing the size of the wheels (PR #691).
devel
Steve Kowalik
2025-01-14 02:40:37 +00:00
b03f61652eAccepting request 1109506 from devel:languages:python
Ana Guerrero
2023-09-08 19:15:22 +00:00
80afe3bdab- update to 3.9.0: * New options :option:flit build --use-vcs and :option:flit build --no-use-vcs to enable & disable including all committed files in the sdist. For now --use-vcs is the default, but this is likely to change in a future version, to bring flit build in line with standard build frontends like python -m build * Sdist file names, and the name of the top-level folder in an sdist, are now normalised, in accordance with PEP 625 * A statically defined version number can now be parsed from files called version.py, _version.py or __version__.py inside a packge, as well as from __init__.py, so executing code is required in fewer cases * Fix setting the flag for regular files in zip metadata * The timestamp embedded in the gzip wrapper for sdists now defaults to a fixed date, so building an sdist twice on the same machine should produce identical results, even without any special steps. - skip install tests for better interoperability with PEP 668Dirk Mueller2023-09-07 10:58:24 +00:00