@@ -273,6 +273,9 @@ metadata.
273273Backwards Compatibility
274274=======================
275275
276+ Using metadata from SDists or wheels is unaffected. The METADATA version does
277+ not need to be incremented.
278+
276279This does not affect any existing ``pyproject.toml ``'s, since this was strictly
277280not allowed before this PEP.
278281
@@ -283,8 +286,27 @@ frontends may need to be updated to benefit from the partially static metadata.
283286Some frontends and other tooling may need updating, such as schema
284287validation, just like other ``pyproject.toml `` PEPs.
285288
286- Using metadata from SDists or wheels is unaffected. The METADATA version does
287- not need to be incremented.
289+ Static analysis tools may require updating to handle this change. Tools should
290+ check the dynamic table first, like this:
291+
292+ ..code-block ::
293+
294+ match pyproject["project"]:
295+ # New in PEP 808
296+ case {my.key: value, "dynamic": dyn} if my.key in dyn:
297+ print(f"Partial {my.key}: {value}")
298+ case {"dynamic": dyn} if my.key in dyn:
299+ print(f"Fully dynamic {my.key}")
300+ case {my.key: value}:
301+ print(f"Fully static {my.key}: {value}")
302+ case _:
303+ print(f"No metadata for {my.key}")
304+
305+
306+ blocks, assuming that an entry in the project table meant it could not be
307+ dynamic. If they do this, they will now incorrectly assume they have all the
308+ metadata for a field, when they in fact only have part of it.
309+
288310
289311Security Implications
290312=====================