Torch import time

tbaudier · December 14, 2023, 5:07pm

Hi @matt.mccormick , thank you for your answer.

I did the PR here:

github.com/InsightSoftwareConsortium/ITK

PERF: Do not import torch to reduce itk import time

InsightSoftwareConsortium:master ← tbaudier:import_torch

opened 05:03PM - 14 Dec 23 UTC

tbaudier

+3 -2

https://discourse.itk.org/t/torch-import-time/6354 Torch takes time to import…. In types.py torch is imported to check if it's present or not in the environment, but it's never used. Now, torch is detected with importlib.metadata.   ## PR Checklist - [X] No [API changes](https://github.com/InsightSoftwareConsortium/ITK/blob/master/CONTRIBUTING.md#breaking-changes) were made (or the changes have been approved) - [X] No [major design changes](https://github.com/InsightSoftwareConsortium/ITK/blob/master/CONTRIBUTING.md#design-changes) were made (or the changes have been approved) - [ ] Added test (or behavior not changed) - [ ] Updated API documentation (or API not changed) - [ ] Added [license](https://github.com/InsightSoftwareConsortium/ITK/blob/master/Utilities/KWStyle/ITKHeader.h) to new files (if any) - [ ] Added Python wrapping to new files (if any) as described in [ITK Software Guide](https://itk.org/ItkSoftwareGuide.pdf) Section 9.5 - [ ] Added [ITK examples](https://github.com/InsightSoftwareConsortium/ITKSphinxExamples) for all new major features (if any) Refer to the [ITK Software Guide](https://itk.org/ItkSoftwareGuide.pdf) for further development details if necessary.

It works well because:
without torch in the environment (with the python itk wrapping now)

with torch in the environment (with the python itk wrapping now)

And with the modification: