Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.5%. Comparing base (19e77b7) to head (1ce6097).
Report is 1 commits behind head on main.

@@           Coverage Diff           @@
##            main    #151     +/-   ##
=======================================
- Coverage   78.9%   78.5%   -0.4%     
=======================================
  Files          6       5      -1     
  Lines        384     378      -6     
=======================================
- Hits         303     297      -6     
  Misses        81      81             

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@pmeier Thanks for your original work in creating light-the-torch. The 3D Slicer community has been using it for several years to help users install the appropriate CUDA whl through the use of the SlicerPyTorch extension. The 3D Slicer project will soon be updating the embedded python version to something newer such as Python 3.12 and so these updates in this PR will help provide official support and testing for light-the-torch for newer python and newer CUDA computation platforms for latest PyTorch such as CUDA 12.4. It would be great if you can take a look at this PR and ultimately "Rebase and Merge" to integrate the collection of individual commits in this PR into the main branch and publish a new version (0.8.0) to PyPI. Thanks!

@jamesobutler Thanks a ton for the PR! I'll find some time this week (I promise!) to merge this and push a release.

To give some context: I'm no longer a PyTorch dev / power user and thus have very little use for light-the-torch in my day-to-day. And with that maintaining this project became more of a burden to me. However, the fact that it still works and has roughly 1k downloads per week after being unmaintained for a good year, is a testament that this project shouldn't be archived.

Since you basically did all the maintainer work in this PR, would you like to have maintainer rights on this repository so that you can push fixes yourself in the future?

I appreciate your help on this!

Since you basically did all the maintainer work in this PR, would you like to have maintainer rights on this repository so that you can push fixes yourself in the future?

Yes, that would be great!

To give some context: I'm no longer a PyTorch dev / power user and thus have very little use for light-the-torch in my day-to-day. And with that maintaining this project became more of a burden to me.

I can discuss with the other Slicer main developers (e.g. @lassoan, also a light-the-torch contributor, see here), but would you potentially consider transferring the repo to the https://github.com/Slicer GitHub organization (or to me to then transfer to the Slicer org)? Any links to https://github.com/pmeier/light-the-torch would automatically redirect to a migrated https://github.com/Slicer/light-the-torch location. Then myself and other Slicer main developers could continue maintenance of the project. There are probably several of us that would like to keep this going for the Slicer community. We would additionally add props to you in the README with a history section indicating the work was primarily under your account and that it was later transferred to the Slicer organization to carry maintenance forward. If you'd like to keep this repo under your GitHub name, I totally understand. Only brought this up if this repo has become a burden to the point you want to pass it to another person/organization. Otherwise we can also work within the bounds of getting write access to this repo and get access for other potential maintainers from the Slicer community.

but would you potentially consider transferring the repo to the https://github.com/Slicer GitHub organization (or to me to then transfer to the Slicer org)?

I'm not exactly sure why, that hit hard reading it the first time. I didn't like it at all. But the longer I thought about it, the more sense it makes to me. I wanted to have this PR finished by no later than Thursday and here I am sitting on a Saturday night, because I simply didn't find any time earlier. Coupled with the fact that I'm no longer a user of this project, it makes little sense to keep me as maintainer and by proxy to keep this as my repository. So, yes, I'm happy to transfer it anywhere of your choosing. I'd prefer under the Slicer umbrella to make this a proper community project, but I'm ok with either.

Could you open an issue to discuss the details rather than doing it on this PR?

@pmeier Thanks for running through the release process and creating https://github.com/pmeier/light-the-torch/releases/tag/v0.8.0 and https://pypi.org/project/light-the-torch/0.8.0/.
🙏🏻 🎉