Casper da Costa-Luis

alternatively, shouldn't we add these files to the [CIL-Demos repo](https://github.com/TomographicImaging/CIL-Demos) directly instead of here? Then CIL's CI could do ```sh pytest . git clone https://github.com/TomographicImaging/CIL-Demos sed -ri '/- cil($|\s|[=])/d' ./CIL-Demos/environment.yml...

I just rebased this PR to be off `master` so it can be self-contained and easy to merge :) I'll rebase #1314 afterwards.

Might [need this on `AquisitionData` too](https://github.com/SyneRBI/SIRF/pull/1314#discussion_r2081550490) @KrisThielemans?

makes sense to me... /CC @evgueni-ovtchinnikov ☝️

related: #2102 /CC @hrobarts

This is by design, as some devs deliberately define subparsers *sans*-`help` as hidden/beta APIs

Thanks for the summary! Yes I agree the FAQs should be tweaked a bit.

It's because the function is returning `args` instead of `parser`, vis. [waydroid@45ded8c:/tools/helpers/arguments.py:168](https://github.com/waydroid/waydroid/blob/45ded8c27ec83078a2319b14cccbde245f5c478c/tools%2Fhelpers%2Farguments.py#L168). This is probably bad practice, and worth opening an issue on Waydroid. Usually only `__name__ == "__main__"` guarded...

the last commit in this PR (b98ce8a) added a massive `build_safir_updates` folder which looks like a build output directory to me... Probably just need to delete that commit and try...

It's [Python's `ctypes.util.find_library`](https://docs.python.org/3/library/ctypes.html#finding-shared-libraries) (not CMake's `find_library`) failing to find the `dll`. Presumably [SuperBuild/External_CIL.cmake](https://github.com/SyneRBI/SIRF-SuperBuild/blob/master/SuperBuild/External_CIL.cmake) is installing it in the wrong place. Alternatively, if it's not super urgent, you could wait for...