calamares/ci/libcalamares/utils.py

#   SPDX-FileCopyrightText: no
#   SPDX-License-Identifier: CC0-1.0
#
# Stubs for part of the Python API from libcalamares
# (although the **actual** API is presented through
# Boost::Python, not as a bare C-extension) so that
# pylint doesn't complain about libcalamares internals.

def debug(_): pass

def warning(_): pass

def error(_): pass

def gettext_path(): pass

def gettext_languages(): pass

def target_env_call(_): return 0

def check_target_env_call(_): pass

def target_env_process_output(cmd, *args): return 0

def host_env_process_output(cmd, *args): return 0

def mount(device, mountpoint, fstype, options): return 0
CI: add stubs for libcalamares bits, to help pylint 2021-09-27 17:27:42 +02:00			`# SPDX-FileCopyrightText: no`
			`# SPDX-License-Identifier: CC0-1.0`
			`#`
			`# Stubs for part of the Python API from libcalamares`
			`# (although the actual API is presented through`
			`# Boost::Python, not as a bare C-extension) so that`
			`# pylint doesn't complain about libcalamares internals.`

			`def debug(_): pass`

			`def warning(_): pass`

CMake: if pylint is available, run it as part of the test-suite This introduces a stub-implementation (fake) that mimics the API offered by libcalamares (the library is actually exposed to Python via Boost::Python, so it doesn't act like a C-extension). Using that stub-implementation, we can check Python modules for validity as part of the test-suite. The stub-implementation is needed, because otherwise every Python module already fails at `import libcalamares`. - stub-implement the API that is actually used by the Python modules - in globalstorage, be slightly smart about what keys are being requested (so that e.g. all the modules that handle partitions information get an empty list and can manipulate that, instead of erroring out when they get a string) 2021-09-27 17:52:02 +02:00			`def error(_): pass`

CI: add stubs for libcalamares bits, to help pylint 2021-09-27 17:27:42 +02:00			`def gettext_path(): pass`

			`def gettext_languages(): pass`
CMake: if pylint is available, run it as part of the test-suite This introduces a stub-implementation (fake) that mimics the API offered by libcalamares (the library is actually exposed to Python via Boost::Python, so it doesn't act like a C-extension). Using that stub-implementation, we can check Python modules for validity as part of the test-suite. The stub-implementation is needed, because otherwise every Python module already fails at `import libcalamares`. - stub-implement the API that is actually used by the Python modules - in globalstorage, be slightly smart about what keys are being requested (so that e.g. all the modules that handle partitions information get an empty list and can manipulate that, instead of erroring out when they get a string) 2021-09-27 17:52:02 +02:00
			`def target_env_call(_): return 0`

			`def check_target_env_call(_): pass`

CI: add new Python API to the linter's library, too 2021-11-09 16:24:10 +01:00			`def target_env_process_output(cmd, *args): return 0`

			`def host_env_process_output(cmd, *args): return 0`

CMake: if pylint is available, run it as part of the test-suite This introduces a stub-implementation (fake) that mimics the API offered by libcalamares (the library is actually exposed to Python via Boost::Python, so it doesn't act like a C-extension). Using that stub-implementation, we can check Python modules for validity as part of the test-suite. The stub-implementation is needed, because otherwise every Python module already fails at `import libcalamares`. - stub-implement the API that is actually used by the Python modules - in globalstorage, be slightly smart about what keys are being requested (so that e.g. all the modules that handle partitions information get an empty list and can manipulate that, instead of erroring out when they get a string) 2021-09-27 17:52:02 +02:00			`def mount(device, mountpoint, fstype, options): return 0`