-
Notifications
You must be signed in to change notification settings - Fork 182
[enhancement] change versioning format for local builds #2413
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
return os.environ["SKLEARNEX_VERSION"] | ||
output = time.strftime("%Y.%#m.%#d+" if IS_WIN else "%Y.%-m.%-d+") | ||
try: | ||
return output + subprocess.check_output(["git", "rev-parse", "--short", "HEAD"]).decode("ascii").strip() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why decode specifically as ascii? What happens if the system has a different encoding (such as UTF8) and the commit contains a non-ascii character?
@icfaust Could this perhaps try to detect if it is being built from a release branch? |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
Description
Follow-on to #2409 which will switch how we write the version for local/prototype builds (which will solve this code comment): #2409 (comment)
It will use subprocess to call git to yield the short form of the commit. If sklearnex is not built in a repo (which users can download the source code without git via a .zip file), then it must still function, so a try catch is added on the case of failure when the subprocess fails, and will revert to the hour time second format.
A
+
is used instead of a.
upon request.Please see public CI for verification.
PR should start as a draft, then move to ready for review state after CI is passed and all applicable checkboxes are closed.
This approach ensures that reviewers don't spend extra time asking for regular requirements.
You can remove a checkbox as not applicable only if it doesn't relate to this PR in any way.
For example, PR with docs update doesn't require checkboxes for performance while PR with any change in actual code should have checkboxes and justify how this code change is expected to affect performance (or justification should be self-evident).
Checklist to comply with before moving PR from draft:
PR completeness and readability
Testing
Performance