Skip to content

METADATA.toml versions redux#2 #6095

Closed

Description

@srittau

One practical problem with the current versioning scheme is that we can't correctly version the dataclasses stub. Current upstream version is 0.8. If we use 0.8 as version, the tests try to install dataclasses==0.8.*, which doesn't work. Similar problems would exist with calver or other exotic versioning schemes.

Currently, the tests try to install f"{distribution}=={version}.*. I would suggest that we allow standard Python version range specifiers in the version field and change most existing versions to use e.g. "5.3.*". The tests would then be changed to simply install f"{distribution}=={version}". This would give us more flexibility.

Activity

  1. srittau commented on Sep 30, 2021

    @srittau
    CollaboratorAuthor

    To clarify: We allow two forms:

    • x.y.* (the standard, any number of components) - will install the latest x.y version in tests and gets uploaded as version x.y.serial.
    • x.y (any number of components) - will install exactly that version in tests and gets uploaded as version x.y.serial.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    project: policyOrganization of the typeshed project

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions