ENH: Support "compiling" source files exclusively to .pyc

[MujassimJamal]

To support “compiling” source file exclusively to .pyc, the CMake function ctkFunctionAddCompilePythonScriptTargets has been improved to accept a new parameter option SKIP_SCRIPT_COPY. This new option controls the definition of the target CopySlicerPythonScriptFiles.

---

Introduce the option CTK_COMPILE_PYTHON_SCRIPT_KEEP_ONLY_PYC to support removing *.py scripts once the corresponding .pyc file has been generated in the destination directory.

Update _ctk_add_compile_python_directories_target to accept keep_only_pyc argument.

Update CMake function ctkFunctionAddCompilePythonScriptTargets to accept the KEEP_ONLY_PYC option and call _ctk_add_compile_python_directories_target accordingly.

Update CMake macro ctkMacroCompilePythonScript to call ctkFunctionAddCompilePythonScriptTargets passing KEEP_ONLY_PYC based on the value of CTK_COMPILE_PYTHON_SCRIPT_KEEP_ONLY_PYC.

Address warning when using CMake >= 3.13, setting CMP0077 to NEW. See https://cmake.org/cmake/help/latest/policy/CMP0077.html

Related pull requests:

• https://github.com/commontk/CTK/pull/1188

Related discussions:

• How to hide the code of the script module? - #20 by jcfr

[jcfr]

More work is still need as _ctk_add_compile_python_directories_target currently expect to compile script first copied into the destination directory.

By configuring CTK with CTK_COMPILE_PYTHON_SCRIPT_SKIP_SCRIPT_COPY set to TRUE (starting from an empty build directory), there will be no .py files in the destination directory and an error like the following will be reported:

[ 72%] Performing build step for 'CTK'
make[5]: *** No rule to make target 'Libs/Scripting/Python/Core/Python/CopyCTKScriptingPythonCorePythonScriptFiles', needed by 'Libs/Scripting/Python/Core/Python/python_compile_CTKScriptingPythonCore_complete'.  Stop.
make[4]: *** [CMakeFiles/Makefile2:1308: Libs/Scripting/Python/Core/Python/CMakeFiles/CompileCTKScriptingPythonCorePythonFiles.dir/all] Error 2
make[4]: *** Waiting for unfinished jobs....
[ 51%] Built target CTKCore
make[3]: *** [Makefile:146: all] Error 2
make[2]: *** [CMakeFiles/CTK.dir/build.make:87: CTK-prefix/src/CTK-stamp/CTK-build] Error 2
make[1]: *** [CMakeFiles/Makefile2:896: CMakeFiles/CTK.dir/all] Error 2
make: *** [Makefile:146: all] Error 2

We will need to address this before moving forward. I will follow-up with some suggestions.

[jcfr]

I revisited the approach, suggested commit message for squash & Merge:

ENH: Support "compiling" source file exclusively to .pyc

Introduce the option CTK_COMPILE_PYTHON_SCRIPT_KEEP_ONLY_PYC
to support removing `*.py` script once the corresponding `.pyc`
file has been generated in the destination directory.

Update `_ctk_add_compile_python_directories_target` to accept `keep_only_pyc` argument.

Update CMake function `ctkFunctionAddCompilePythonScriptTargets` to
accept the `KEEP_ONLY_PYC` option and call `_ctk_add_compile_python_directories_target`
accordingly.

Update CMake macro `ctkMacroCompilePythonScript` to call `ctkFunctionAddCompilePythonScriptTargets`
passing KEEP_ONLY_PYC based on the value of `CTK_COMPILE_PYTHON_SCRIPT_KEEP_ONLY_PYC`.

Address warning when using CMake >= 3.13, setting CMP0077 to NEW.
See https://cmake.org/cmake/help/latest/policy/CMP0077.html

Co-authored-by: Jean-Christophe Fillion-Robin <jchris.fillionr@kitware.com>

[jcfr]

@MujassimJamal Could you test on your side ? :pray:

@jamesobutler @lassoan I revisited the original approach to instead accept the option CTK_COMPILE_PYTHON_SCRIPT_KEEP_ONLY_PYC and delete the file once it was successfully compiled:

To illustrate here is a screenshot of the generated[^1] script:

Libs/Scripting/Python/Core/Python/compile_CTKScriptingPythonCore_python_scripts.py

called by the Compile<Name>PythonFiles custom target (e.g CompileCTKScriptingPythonCorePythonFiles or CompileSlicerPythonFiles)

[^1]: Generated configuring CMake/ctk_compile_python_scripts.cmake.in

The code highlighted in red is included only if CTK_COMPILE_PYTHON_SCRIPT_KEEP_ONLY_PYC is ON

[MujassimJamal]

Thanks, @jcfr, for proposing an alternative approach.

Indeed, the previous approach of skipping the copy target created issues for me during scratch builds, as you mentioned that compiled files must be copied to the destination first. Since then, I've been using an unofficial hard-coded temporary solution, which involves completely removing 'py' files once they are compiled. To achieve this, I directly used the following code snippet in the file ctk_compile_python_scripts.cmake.in:

if 'qt-scripted-modules' in fullname:
    print('Removing', fullname, '...')
    os.remove(fullname)

I'm okay with the alternative approach you proposed, as it allows explicit control over the behavior. I'll test it from my side and provide an update here. 🚀

[jcfr]

I'm okay with the alternative approach you proposed

Were you able to test in the context of your project ?

[MujassimJamal]

@jcfr Thank you for your patience.

Yes, I've recently tested it and encountered numerous errors in the Python console. The majority of these errors were related to:

• Failed to instantiate modules
• qSlicerPythonCppAPI::instantiateClass Failed to instantiate scripted PythonQt class
• NameError: name {'getSlicerRCFileName', 'loadSlicerRCFile'} is not defined

When I open the application after a build, only a blank main window is visible; all the widgets are gone (e.g slice views, 3D view, module panel, etc.).

Perhaps this occurred because it removes ".py" files not only from the lib/{AppName}/qt-scripted-modules directory but also from other directories (e.g. bin etc.) within the Slicer-build.

[MujassimJamal]

@jcfr, I want to know if you are planning to proceed with this PR?

[jcfr]

Based on your tests^1, Slicer would need to also be updated to make this feature useful.

Would you be able to open a pull request against Slicer do address those?

[MujassimJamal]

Sure, I will open a pull request with necessary changes to the Slicer.