John/make-torch-import-optional

[johnwalz97]

Pull Request Description

What and why?

Hotfix to make the torch import optional.

How to test

What needs special review?

Dependencies, breaking changes, and deployment notes

Release notes

Checklist

• What and why
• Screenshots or videos (Frontend)
• How to test
• What needs special review
• Dependencies, breaking changes, and deployment notes
• Labels applied
• PR linked to Shortcut
• Unit tests added (Backend)
• Tested locally
• Documentation updated (if required)
• Environment variable additions/changes documented (if required)

[github-actions]

PR Summary

This PR improves the way the torch library is imported within the client module. Instead of directly importing torch, the code now wraps the import in a try/except block. If torch fails to import (for instance, if it's not installed), the module gracefully sets torch to None, preventing potential runtime errors. This change aims to improve the overall robustness and flexibility of the client, especially in environments where torch might be unavailable. Note that version bumps in metadata files are considered non-functional changes and are not detailed here.

Test Suggestions

• Test the client module in an environment where torch is installed to verify normal functionality.
• Simulate an environment without torch (or force an ImportError) and ensure that the client handles the absence of torch gracefully by setting it to None.
• Check that downstream functions that depend on torch either operate correctly or fail with clear error messages when torch is unavailable.