[WIP] Use packaging and compare PEP-0440 vs. SEM-VER vs. legacy etc

[dazza-codes]

WIP to explore variants of version formatting and regex patterns in several version conventions and how they relate to poetry version and constraint tools

• sem-ver
• PEP-0440
• poetry

This may never get merged, but it's worth throwing it up for the curious. I might need to revise one or more other PRs in the light of looking closer at these version standards. There is no intention in this to apply a specific versioning system on poetry (AFAIK, PEP-0440 is the only thing that poetry is supposed to implement and support).

TODO

• related to similar PRs Add semver utils, using semver library #1268 and Add constraint and version utils #1375
  • probably rebase this on Add semver utils, using semver library #1268 and/or collapse that into this (although it stands on it own)
• closer analysis of the poetry version class API vs. the packaging version API
• What does conda do to handle many various version standards?
  • PEP-0440 should apply to python packages, but what about things like rasterio that wrap c++ libs where those c++ libs could use a different versioning format?

checklist

• Added tests for changed code.
• Updated documentation for changed code.
  • don't know if it needs any (yet)

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[dazza-codes]

The stale bot settings are going to kill stuff that might be useful

• poetry review and merge cycles are too slow

[sdispater]

@darrenleeweber I am sorry you feel that way but understand that doing code reviews takes time and most of it is dedicated to releasing the 1.0 release. I encourage people to create a Feature Request issue before starting to implement something to avoid the frustration of seeing your work being ignored or rejected because it does not align with the goals of the project.

Regarding your PR, I am failing to see what it's trying to solve. Is there an issue linked to it?

[dazza-codes]

In this case, this PR is an exploration of various inconsistencies in version schemas and the work resulted from initial work on trying to support sem-ver for git dependencies (#925). While working on that, I've learned that several version schemas exist and this PR takes some steps to add more version-schema support to poetry, since poetry documentation indicates that any version schema should be supported. But, given that I already have a full-time job and that I'm discouraged about the contribution process, I'm not inclined to waste my time on pursuing this any further - just to be clear about where this stands.

[Secrus]

This is no longer valid since the team has decided on sticking to pep440 and appropriate code exists in the codebase. Closing.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.