PyScript <py-config> packages without version pinning

Reproducible dependency resolution is required for PyScript pages that declare Python packages via . The packages array is documented as the configuration point for micropip installs at page load.

The current specification does not define an explicit version constraint mechanism, a lockfile format, or environment markers for the packages list. It is unclear whether version specifiers such as "==", ">=", or PEP 508 compatible strings are parsed and honored consistently, and whether behavior is stable across PyScript releases.

Clarification is needed on the intended contract for version control in :

• Does officially support version specifiers in the packages array, and if so, which syntax is guaranteed?
• Is there a supported way to lock package versions for a page without moving version logic into inline imports or external build steps?
• What is the defined behavior when a version specifier is provided and micropip resolves a different release?