Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Streamline versioning APIs for the various FFI bindings (and embedded C API bindings) #405

Open
rdw-software opened this issue Jan 9, 2024 · 0 comments

Comments

@rdw-software
Copy link
Member

Currently, most of the FFI bindings export a function version() which returns a semantic version string - except for uv.

For consistency and in order to allow checking for major version updates more easily, this could be changed:

  • Either version and version_string are implemented for all relevant libraries
  • Or the uv export could be renamed (version returns the string and version_string becomes version_no)
  • Alternatively, version could return a number (three or four return values, for major/minor/patch)
  • In this case, version_no could return the combined number (although it's somewhat obsolete)
  • And optionally, version_string could return the stringified version

Either way, the result should be consistent. Since git describe is used by some, version_string is likely the common denominator?

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
Status: No status
Status: Soon™
Development

No branches or pull requests

1 participant