-
Notifications
You must be signed in to change notification settings - Fork 203
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
Stop using versioneer to manage versions #1190
Stop using versioneer to manage versions #1190
Conversation
a8c6caa
to
e6fc0cb
Compare
Codecov ReportBase: 0.00% // Head: 0.00% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## branch-23.02 #1190 +/- ##
=============================================
Coverage 0.00% 0.00%
=============================================
Files 6 5 -1
Lines 421 140 -281
=============================================
+ Misses 421 140 -281
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
e6fc0cb
to
ab82618
Compare
d569446
to
3d8687f
Compare
@vyasr, the Please re-comment this PR with |
/merge |
…1212) The package name defined in setup.py needs to be modified for wheels to reflect the CUDA version that the wheel was built for. Currently that modification is done via an environment variable that is pulled in setup.py code. This changeset replaces that approach with a direct modification using a script (similar to what is done for versions in #1190) to facilitate moving towards static project metadata specification via pyproject.toml. This PR depends on rapidsai/shared-workflows#45. Authors: - Vyas Ramasubramani (https://github.com/vyasr) Approvers: - Sevag H (https://github.com/sevagh) - Ashwin Srinath (https://github.com/shwina) URL: #1212
Description
This PR replaces usage of versioneer with hard-coded version numbers in setup.py and init.py. Since rmm needs to manage versions across a wide range of file types (CMake, C++, Sphinx and doxygen docs, etc), versioneer cannot be relied on as a single source of truth and therefore does not allow us to single-source our versioning to the Git repo as is intended. Additionally, since the primary means of installing rmm is via conda packages (or now, pip packages), information from the package manager tends to be far more informative than the version strings for troubleshooting and debugging purposes. Conversely, the nonstandard version strings that it produces tend to be problematic for other tools, which at best will ignore such versions but at worst will simply fail.
Relies on rapidsai/shared-workflows#38
Checklist