James Butler

Yeah you are running into known issue related to debug builds as mentioned at https://discourse.slicer.org/t/build-error-in-windows-in-debug-mode-due-to-python312-d-lib/43781/2.

Cc numpymaxflow developer @masadcv for adding Python 3.13 whls.

@seanm Do you use any of the itk python remote modules to have noticed there hasn’t been macOS x86_64 whls available? I haven’t seen any GitHub user reports about the...

> macOS 17 (2026) is projected to be Apple Silicon–only, ending major OS updates for Intel Macs[2](https://github.com/InsightSoftwareConsortium/ITK/issues/5326#user-content-fn-2-f7efc2e908fd923e1edf53df3d971461)[3](https://github.com/InsightSoftwareConsortium/ITK/issues/5326#user-content-fn-3-f7efc2e908fd923e1edf53df3d971461). > [!NOTE] > What would have typically been called macOS 16 will now...

> Many of my customers use air-gapped Macs, not connected to the internet. That mitigates a lot of risk. @seanm Are you all still providing new to customers 27” iMacs...

> Windows 11 drops a lot of hardware support too, and Windows 10 stops getting security updates in about 4 months. Shall ITK 6 drop Windows 10 support too? Only...

@Sunderlandkyl See the video below where the interaction handles for the ROI are positioned in the center of the compare slice viewer with the lightbox type view. https://github.com/user-attachments/assets/d4e740da-9017-4ccb-8ea2-5929719a1b59

Closing this issue as it is no longer relevant now that LightBox functionality has been removed from Slicer as of https://github.com/Slicer/Slicer/commit/9d84fd73e7dd8506dcfe95c09626135df556e4ef, https://github.com/Slicer/Slicer/commit/782d9652581daf42576e6bc277bf500002ba41ee, https://github.com/Slicer/Slicer/commit/e28552fbc999be5830356b28b7299e1d0fe94732

Adding Windows 11 arm building would likely need to be restricted to the Python 3.11+ builds. It appears that the Python organization distributed Windows arm64 installers for Python 3.11.0 (https://www.python.org/downloads/release/python-3110/),...

@fedorov This would be from running the automated testing associated with the extension at https://github.com/QIICR/QuantitativeReporting/blob/master/Testing/QuantitativeReportingTests.py. Evidently there is an action in the automation that produces the pop dialog that requires...