Open AndydeCleyre opened 3 years ago
Yes, it does look like Flit just needs to handle the same data from the new names. :slightly_smiling_face:
Of course, we'll need to keep supporting the tool.flit
locations as well for some time, to avoid breaking existing packaging. Specifying both fields should probably be an error.
PEP 631
I may be misunderstanding, but looking at the PEP, I think it means that dependency specification within a
pyproject.toml
is getting standardized such that we'll want to use the format specified in the PEP for required package entries, rather than (or in addition to)tool.flit.metadata[.requires-extra]
entries.Whereas a
flit
-flavoredpyproject.toml
may look like this now:I guess it should in the future look like:
I can't swear to all the syntax details, but it seems the transition for
flit
would basically be:tool.flit.metadata.requires-extra
->project.optional-dependencies
tool.flit.metadata.requires
->project.dependencies
Is that the proper response to PEP 631, for
flit
?