Make a tui group with all the tui only dependencies

.github/workflows/pythonpublish.yml

@@ -40,7 +40,7 @@ jobs:
         run: python -m twine check --strict dist/*
       - name: Test installed wheel
         run: |
-          python -m pip install dist/*.whl
+          python -m pip install "$(echo dist/*.whl)[tui]"
           python -I tests/test_qltool.py InstalledQltool_Test -v
       - uses: actions/upload-artifact@v4
         with:

ARCHITECTURE/modules/cli-build.md

@@ -31,8 +31,10 @@ examples/tests belongs to its runtime owner.
 
 Use the [root baseline](../../ARCHITECTURE.md#code-conventions).
 `argparse` actions convert enum/environment inputs and build `Qiling` keyword
-arguments. Preserve option names and exit status. TUI uses questionary/fx/
-termcolor; testing its import is not testing its prompts. Keep build metadata
+arguments. Preserve option names and exit status. TUI uses questionary/termcolor/fx, all
+shipped in the `tui` extra and absent from a default install; `qiling.cli`
+must degrade with an install hint rather than traceback when it is missing.
+Testing its import is not testing its prompts. Keep build metadata
 in the manifest, resolve its lock with Poetry, and retain package license
 and resource attribution. Documentation here contains coding context only.
 

ARCHITECTURE/modules/extensions.md

@@ -30,7 +30,7 @@ paths are explicitly owned by hardware/bare-metal modules.
 ## Local Conventions
 
 Use [root conventions](../../ARCHITECTURE.md#code-conventions); optional
-packages use manifest extras `fuzz` and `RE`. Format classes expose
+packages use manifest extras `fuzz` and `RE` (the terminal UI uses `tui`). Format classes expose
 `FORMAT_NAME` and activate/deactivate/dump methods; imports register subclasses
 with factories. No common C standard is declared for fuzz harnesses; inspect
 the local `fuzz.c`/build instructions. Generated SDK stubs require review;

README.md

@@ -211,6 +211,8 @@ Qiling also provides a friendly tool named `qltool` to quickly emulate shellcode
 Installing Qiling with pip also installs the `qltool` command, including
 `qltool qltui` for the terminal UI. In a source checkout, use `./qltool` as
 shown below. Example binaries and rootfs files must be downloaded separately.
+The `qltool qltui` terminal UI is an optional extra: install it with
+`pip install qiling[tui]`.
 
 With qltool, easy execution can be performed:
 

pyproject.toml

@@ -45,18 +45,20 @@ gevent = ">=24.10"
 multiprocess = ">=0.70.12.2"
 windows-curses = { version = "^2.1.0", markers = "platform_system == 'Windows'" }
 pyyaml = "^6.0.1"
-python-fx = "*"
-questionary = "*"
-termcolor = "*"
 
 unicornafl = { version = "^2.0.0", markers = "platform_system != 'Windows'", optional = true }
 fuzzercorn = { version = "^0.0.1", markers = "platform_system == 'Linux'", optional = true }
 
 r2libr = { version = "^5.7.4", optional = true }
 
+python-fx = { version = "*", optional = true }
+questionary = { version = "*", optional = true }
+termcolor = { version = "*", optional = true }
+
 [tool.poetry.extras]
 fuzz = ["unicornafl", "fuzzercorn"]
 RE = ["r2libr"]
+tui = ["python-fx", "questionary", "termcolor"]
 
 [build-system]
 requires = ["poetry-core>=2.0,<3.0"]

qiling/cli.py

@@ -246,7 +246,11 @@ def run():
     ql_args = {}
 
     if options.subcommand == 'qltui':
-        import qltui
+        try:
+            import qltui
+        except ImportError:
+            parser.error('the qltui subcommand requires the "tui" extra; install it with: pip install qiling[tui]')
+
         options = qltui.get_data()
         qltui_enabled = True