Title: Get rid of `versioneer` from cuda-bindings · Issue #233 · NVIDIA/cuda-python · GitHub
Open Graph Title: Get rid of `versioneer` from cuda-bindings · Issue #233 · NVIDIA/cuda-python
X Title: Get rid of `versioneer` from cuda-bindings · Issue #233 · NVIDIA/cuda-python
Description: Offline discussions with @vyars @bryevdv suggests that any of those tools listed here could be a good alternative. Alternatively, we can just manually bump __version__ in _version.py, as done in cuda.core, and let it propagate to other p...
Open Graph Description: Offline discussions with @vyars @bryevdv suggests that any of those tools listed here could be a good alternative. Alternatively, we can just manually bump __version__ in _version.py, as done in cu...
X Description: Offline discussions with @vyars @bryevdv suggests that any of those tools listed here could be a good alternative. Alternatively, we can just manually bump __version__ in _version.py, as done in cu...
Opengraph URL: https://github.com/NVIDIA/cuda-python/issues/233
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Get rid of `versioneer` from cuda-bindings","articleBody":"Offline discussions with @vyars @bryevdv suggests that any of those tools listed [here](https://setuptools-git-versioning.readthedocs.io/en/stable/comparison.html) could be a good alternative.\n\nAlternatively, we can just manually bump `__version__` in `_version.py`, as done in `cuda.core`, and let it propagate to other places (ex: `pyproject.toml`).\n\n`versioneer` has the following disadvantages \n- add an extra build-time dependency (to calculate the version)\n- the version scheme is nonsense for local development\n- no way to decouple release versions from git tags \n - confirmed with @vzhurba01 it is fundamentally unfriendly with our release process (that QA could discover bugs after tagging), meaning we tag first, build wheels, if there are bugs caught by QA then we fix the code, **revoke the old tag, and re-tag the same tag** at the latest commit (with the fixes included)\n - the highlighted part is the most problematic if not also confusing","author":{"url":"https://github.com/leofang","@type":"Person","name":"leofang"},"datePublished":"2024-11-09T02:02:23Z","url":"https://github.com/NVIDIA/cuda-python/issues/233"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react-reconciler,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@d5750093facf |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:ff0cce20-bb15-ff0f-1a4b-0b12542a7be1 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | D6A0:3AABB4:88733C:B38ABF:6AF844C0 |
| html-safe-nonce | 28bb02f7d730daedc04426d832e9b596739d5e6f20ea6114c77108400cc99c9d |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJENkEwOjNBQUJCNDo4ODczM0M6QjM4QUJGOjZBRjg0NEMwIiwidmlzaXRvcl9pZCI6IjE5NzY1MzA3MTQzMjQ2NDkxNTIiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | a3aaec45c9bba7baeb6ba09547dc69fe9dbd90326a0d849dde78ec9b07e170f5 |
| hovercard-subject-tag | issue:2645474890 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/NVIDIA/cuda-python/233/issue_layout |
| twitter:image | https://opengraph.githubassets.com/693c6621b2a4bb8cef15351835bb79ae5e027a702ba1300378d4d8f7e79c1a12/NVIDIA/cuda-python/issues/233 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/693c6621b2a4bb8cef15351835bb79ae5e027a702ba1300378d4d8f7e79c1a12/NVIDIA/cuda-python/issues/233 |
| og:image:alt | Offline discussions with @vyars @bryevdv suggests that any of those tools listed here could be a good alternative. Alternatively, we can just manually bump __version__ in _version.py, as done in cu... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | leofang |
| hostname | github.com |
| expected-hostname | github.com |
| None | 5713ecd83001b2f55c3509fb7a292bf7d66d0f167c7ae87a9f7eaec5a52bf8db |
| turbo-cache-control | no-preview |
| go-import | github.com/NVIDIA/cuda-python git https://github.com/NVIDIA/cuda-python.git |
| octolytics-dimension-user_id | 1728152 |
| octolytics-dimension-user_login | NVIDIA |
| octolytics-dimension-repository_id | 381173759 |
| octolytics-dimension-repository_nwo | NVIDIA/cuda-python |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 381173759 |
| octolytics-dimension-repository_network_root_nwo | NVIDIA/cuda-python |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 653be32ff5c755082a4db662491bfbbcfc9112c1 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width