You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Remove support for old-style metadata, where a project is described in the [tool.flit] subtables instead of the now-standard [project] table. (but [tool.flit.module], which is used alongside [project], will continue to work).
I encourage all projects to specify something like requires = ["flit_core >=3.2,<4"] so we can make changes like this and old packages can still easily be built with 3.x. I know some projects have ignored that and don't specify an upper bound, but hopefully not too many.
What major changes do we want for Flit 4.0?
[tool.flit]subtables instead of the now-standard[project]table. (but[tool.flit.module], which is used alongside[project], will continue to work).requires = ["flit_core >=3.2,<4"]so we can make changes like this and old packages can still easily be built with 3.x. I know some projects have ignored that and don't specify an upper bound, but hopefully not too many.[project]- Consider making it possible to fail on unknown keys in[project]table #505, Add option to fail on unknown keys. #506[ ] Get rid offlit.buildapiin favour offlit_core.buildapi? Emit warnings when flit.buildapi is used #519flit buildandflit publishto not use VCS info, to get rid of the surprising difference betweenflit buildandpython -m build(see discussion on Discussion: future shape of the 'flit' command #522 & Add --use-vcs and --no-use-vcs flags for build commands #625)git archiveor similar? 🤔 - Add script to generate sdist included/exclude patterns from git #782Anything else?
There's still likely to be a 3.10 release first with assorted small fixes and improvements, and possibly more 3.x releases before 4.0.