#5989 new enhancement

flit_core-4.0.2 (Python module)

Reported by: Bruce Dubbs Owned by: lfs-book
Priority: normal Milestone: 13.1
Component: Book Version: git
Severity: normal Keywords:
Cc:

Description

New major version.

Version 4.0.2

  • Fix invalid metadata files with Import-Name.

Version 4.0.1

  • No changes, but a new tag to trigger an upload to PyPI now that twine will accept it.

Version 4.0

  • This version contains breaking changes, but most projects which are already using the [project] table for metadata shouldn’t be affected, and can simply change the flit_core <4 constraint to <5.
  • The [tool.flit.metadata] table is no longer used for project metadata. Use the newer [project] table instead (or if that is not possible, build with flit_core <4).
  • flit build and flit publish no longer include files in the sdist based on what is committed in git or Mercurial. These commands now build packages more like Flit does when called as a backend by e.g. python -m build. Specify sdist include & exclude patterns instead (Flit can help to generate these), or pass the --use-vcs option to get the old behaviour back.
  • flit_core now requires Python 3.8 or above

  • The --setup-py option to generate sdists containing a setup.py file is no longer available.
  • Making typing stubs packages with a -stubs suffix will now work.
  • The default glob patterns for license files have been extended to include NOTICE* and AUTHORS*.
  • license-files glob patterns can contain spaces.
  • Fix a bug where license files could be found twice on Windows.
  • The new Import-Name and Import-Namespace metadata fields (metadata 2.5) are now supported. In most cases no new input is required, as Flit will create this metadata automatically.
  • Fix creating RECORD files when file names include commas.
  • The --use-vcs option now correctly recognises git from inside a git worktree folder.
  • On Python 3.12 and above, flit build now uses the ‘data’ filter when extracting the just-created sdist prior to building a wheel. This restricts some special features of tar files, but sdists are unlikely to use these features, and they would probably break in other scenarios if you did.
  • The vendorised readme_renderer package was updated to version 44.0.

Change History (0)

Note: See TracTickets for help on using tickets.