Known Issues

The following list shows the currently known issues of PyCPL 1.0.0

• Recently Apple released Xcode 15 which includes a new linker. PyCPL may not build on macOS with the MacPorts GCC if Xcode 15 (15.0, 15.0.1) is installed. Trying to do so may result in an AssertionError in the linker itself (known problem which has been reported to Apple’s linker team by various developers). If you have Xcode 15 installed the easiest workaround is to use the Xcode compiler (AppleClang), or the MacPorts clang compiler (version 16 or 17 are recommended) to build PyCPL.

• Running unit tests on AppleSilicon (M1, M2) hardware some unit tests fail due to the thresholds used for comparing floating-point results. These tests pass on Intel based Macs. Adjusting the thresholds is work in progress, and the failing tests may safely be ignored.

• On macOS the recipe name prefix is not shown in the recipe message output when running CPL recipes.

• Using PyCPL to run the GIRAFFE pipeline recipe giwavecalibration may result in the recipe being terminated with a segmentation fault. This is not an issue of PyCPL, but a known problem in the GIRAFFE pipeline itself (see PIPE-9352).

• No pre-built packages of PyCPL are currently available. This is work-in-progress.