Yes, PEP 621

[frostming]

As PEP 621 is finalized, the PDM project will also gradually move to PEP 621. It means project metadata under tool.pdm will eventually be deprecated and transferred to the project namespace, following the specification of PEP 621. The major changes lie in the dependency part:

• We will adopt PEP 631 as the format of dependencies definition, which is an array of PEP 508 strings.
• Editable requirements, which are not included in the above PEPs, will remain the same as Pip's standard.
• Optional dependency sections and tool.poetry.extras field, will be replaced by project.optional-dependencies table, with the keys as the extra name and values an array of PEP 508 strings. That means all optional dependencies must belong to an extra requires category and will be present in the METADATA if uploaded to PyPI.
• When the old format is detected, a prompt will be poped up to let users trigger the migration.
• The only exception is that dev-dependencies will be under project namespace to keep all dependencies in one place.

tool.pdm namespace will still remain to hold some tool-specific settings which need to be synced with the deployment environment. Examples are tool.pdm.sources and tool.pdm.scripts