We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, most of the FFI bindings export a function version() which returns a semantic version string - except for uv.
version()
uv
For consistency and in order to allow checking for major version updates more easily, this could be changed:
version
version_string
version_no
Either way, the result should be consistent. Since git describe is used by some, version_string is likely the common denominator?
git describe
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently, most of the FFI bindings export a function
version()
which returns a semantic version string - except foruv
.For consistency and in order to allow checking for major version updates more easily, this could be changed:
version
andversion_string
are implemented for all relevant librariesuv
export could be renamed (version
returns the string andversion_string
becomesversion_no
)version
could return a number (three or four return values, for major/minor/patch)version_no
could return the combined number (although it's somewhat obsolete)version_string
could return the stringified versionEither way, the result should be consistent. Since
git describe
is used by some,version_string
is likely the common denominator?The text was updated successfully, but these errors were encountered: