Skip to content

version 1.0.4#37

Merged
Eugene-hu merged 2 commits intomainfrom
spec_version_update
Jun 9, 2023
Merged

version 1.0.4#37
Eugene-hu merged 2 commits intomainfrom
spec_version_update

Conversation

@Eugene-hu
Copy link
Contributor

@Eugene-hu Eugene-hu commented Jun 9, 2023

  • Updates version v1.0.4
  • spec version now a function of main version tag

__spec_version__ = 1003
__version__ = "1.0.3"
version_split = __version__.split(".")
__spec_version__ = (1000 * int(version_split[0])) + (10 * int(version_split[1])) + (1 * int(version_split[2]))
Copy link
Collaborator

@isabella618033 isabella618033 Jun 9, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

would it still work if the sub version is >= 10? xd
eg. 1.0.35 -> 1035
1.3.5 -> 1035

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, so v1.35.0 would work, but not 1.0.35

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fair point, but as the authors and maintainers we should hold ourselves responsible for the conventions we keep.

There should be an agreed upon limit to the sub version fields. If we are going to exceed 10 revisions (0-9) we should use different prefactors such as 10,000, 100, 1

@Eugene-hu Eugene-hu changed the title version 1.0.3 version 1.0.4 Jun 9, 2023
@Eugene-hu Eugene-hu merged commit 923431e into main Jun 9, 2023
@steffencruz steffencruz deleted the spec_version_update branch June 22, 2023 17:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants