-
-
Notifications
You must be signed in to change notification settings - Fork 750
Replace versioneer with setuptools-scm #9137
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
Conversation
| "get_client", | ||
| "get_task_metadata", | ||
| "get_task_stream", | ||
| "get_versions", |
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.
Technically this is breaking, but this internal versioneer method was never intended to be exposed publicly anyway. If anyone is depending on this they should probably switch to __version__ or importlib.metadata.version("distributed").
Unit Test ResultsSee test report for an extended history of previous test failures. This is useful for diagnosing flaky tests. 27 files ±0 27 suites ±0 9h 42m 32s ⏱️ +56s For more details on these failures, see this check. Results for commit b578cf6. ± Comparison against base commit a9ad6d4. ♻️ This comment has been updated with latest results. |
Given that
setuptools-scmis more widely used and better maintained thanversioneer(last release was July 2023) we might want to switch.pyproject.tomlto usesetuptools-scmdistributed/_version.pyfile assetuptools-scmgenerates this during sdist/wheel build (orpip install -e .)setup.py__getattr__shim added in lazily get dask version information #5822.setuptools-scmimplementation of_version.pyshould be much faster than the wayversioneerwas generating from git every import so it's better to simplify thingsxref dask/dask#12133