Is it possible to automatically get the torch version from the pdm.lock?

[amitkparekh]

Hi! Thank you for creating and maintaining this! I think it's an excellent resource and it's something that I'll be recommending to many people going forwards!

I noticed that we currently need to specify the version for each package/dependency we want to update/get from the torch repository. Do you think it could be possible that, if the version is not specified in the dependencies array, the plugin checks the current pdm.lock file for the torch version, and then downloads/installs the backend but using that version?

I'm thinking about this because in that way, once a user installs the dependency with pdm add (e.g. pdm add torch), the plugin can then just automatically install the desired backend given the version.

[tgolsson]

In theory this is possible, and I had something similar at point. The problem is that the version selected by PDM might not be available for all hardware configurations that the user desires. Forcing the user to specify the exact constraint makes this less fragile.

[amitkparekh]

I understand what you're referring to. What if when no version is present, it grabs from the lockfile? And when a version is present, it uses that one.

(Edit for more background)

One of my personal annoyances is needing to pip install torch again with the right computation backend depending on the hardware I'm using. While I'm used to it, it's something that might not be as obvious or understandable by others who use my codebase.

I'm considering the use-case for ML researchers, who will likely want to just do pdm add torch and leave it. The benefit of encouraging the use of this plugin means that the "right" backend is installed and tracked and explicit for all future users of the codebase.

I am also more than happy to get stuck in with creating a PR if you need an extra pair of hands!

[tgolsson]

PRs are always welcome! Maybe setting the constraint to "auto" or similar in the configuration would be a nice way of opting in? If we "default" to discover I think it should be with a warning, so users have to be explicit about what they expect.

I'm hoping to merge #11 soon, just an FYI. It has a few changes to structure as it drops a bunch of PDM versions and adds a few new ones.

[amitkparekh]

I agree that a warning/info log there might be useful so that users are aware of the version that is being used when downloading torch.

I have take a run at a PR once #11 goes in? I'm going on vacation soon so it might be in a couple of weeks if that's okay?

[tgolsson]

No worries if it takes time, there is no urgency from my side.