console-window 2.1.3__tar.gz → 2.2.0__tar.gz

console_window-2.1.3/README.md → console_window-2.2.0/PKG-INFO

@@ -1,3 +1,34 @@
+Metadata-Version: 2.4
+Name: console-window
+Version: 2.2.0
+Summary: A robust curses wrapper for creating Text User Interfaces (TUIs).
+Author-email: Joe Defen <joedef@duck.com>
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Programming Language :: Python :: 3
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Topic :: Terminals
+Classifier: Topic :: Software Development :: User Interfaces
+License-File: LICENSE
+Requires-Dist: pytest >= 7.0 ; extra == "dev"
+Requires-Dist: pytest-cov >= 4.0 ; extra == "dev"
+Requires-Dist: ruff >= 0.9 ; extra == "dev"
+Requires-Dist: build >= 1.2 ; extra == "dev"
+Requires-Dist: twine >= 7 ; extra == "dev"
+Requires-Dist: packaging >= 26 ; extra == "dev"
+Requires-Dist: tomli >= 2.0 ; extra == "dev" and ( python_version < "3.11")
+Requires-Dist: pytest >= 7.0 ; extra == "test"
+Requires-Dist: pytest-cov >= 4.0 ; extra == "test"
+Requires-Dist: tomli >= 2.0 ; extra == "test" and ( python_version < "3.11")
+Project-URL: Changelog, https://github.com/joedefen/console-window/blob/main/CHANGELOG.md
+Project-URL: Homepage, https://github.com/joedefen/console-window
+Project-URL: Issues, https://github.com/joedefen/console-window/issues
+Project-URL: Repository, https://github.com/joedefen/console-window
+Provides-Extra: dev
+Provides-Extra: test
+
 
 # console-window 
 
@@ -392,7 +423,7 @@ degrades by itself:
   or pass it with the window: `ConsoleWindowOpts(glyphs={'tick': ('✓', 'OK')},
   glyphs_probe=('tick',))`. Once registered, the glyph both degrades with
   `Glyphs.get('tick')` and appears in the font check via `Glyphs.probe_text()`.
-* **Two switches, no argparse boilerplate.** The bundled helper adds them:
+* **The switches, with no argparse boilerplate.** The bundled helper adds them:
 
   ```python
   parser = cli.add_display_arguments(argparse.ArgumentParser())
@@ -402,9 +433,10 @@ degrades by itself:
 
   `--ascii` forces the fallback (`--ascii=no` forces the full set) and
   `--glyphs {auto,ascii,unicode}` is its symmetric spelling; `--glyphs` wins if
-  both are given. `--theme` seeds the first window's colour theme. Apps without
-  argparse can use `CONSOLE_WINDOW_GLYPHS=auto|ascii|unicode`, which outranks
-  detection.
+  both are given. `--theme` seeds the first window's colour theme and
+  `--no-color` draws the semantic roles with bold/reverse attributes instead of
+  colour. Apps without argparse can use
+  `CONSOLE_WINDOW_GLYPHS=auto|ascii|unicode`, which outranks detection.
 * **The mode is process-wide**, like the colour-pair table, because there is one
   terminal. `ConsoleWindowOpts(ascii=...)` seeds it and `win.ascii_mode` reads
   it; a window constructed later never reverts an explicit choice.
@@ -420,6 +452,17 @@ line, remembers the choice through any object with `load()`/`save()`, and
 `Theme.initial(cli_theme, store)` returns the theme a new process should start
 on. The library never opens a file.
 
+The appearance layer is shared too. `console_window.appearance.semantic_attr(role)`
+returns the installed colour pair for a semantic role, or the matching attribute
+from `MONO_ROLES` when colour is off; it degrades to plain text when the terminal
+has no colour or curses has not been initialised, so a redraw is never aborted by
+a colour. `set_colors_enabled()` / `colors_enabled()` hold the process-wide
+switch, and `resolve_appearance(cli_theme=None, no_color=False, saved_theme='',
+saved_colors=True, environ=None)` returns the `(theme, colors)` to start with:
+`--no-color` first, then an explicit `--theme`, then `NO_COLOR`, then the
+remembered choice. Apps keep their preference file and their own pseudo-themes;
+the library gives them the policy, not the storage.
+
 ## Versioning and Deprecation
 
 `console-window` follows semantic versioning: patch releases fix behaviour
@@ -472,3 +515,4 @@ For more extensive examples, you can look at some projects using `console-window
   * viewer of /proc/meminfo that shows historical values
 * [vappman](https://github.com/joedefen/vappman)
   * convenince wrapper to mostly hide CLI of [AppMan](https://github.com/ivan-hc/AppMan), a life-cycle manager for 2000+ AppImages
+

console_window-2.1.3/PKG-INFO → console_window-2.2.0/README.md

@@ -1,22 +1,3 @@
-Metadata-Version: 2.4
-Name: console-window
-Version: 2.1.3
-Summary: A robust curses wrapper for creating Text User Interfaces (TUIs).
-Author-email: Joe Defen <joedef@duck.com>
-Requires-Python: >=3.10
-Description-Content-Type: text/markdown
-Classifier: Development Status :: 5 - Production/Stable
-Classifier: Programming Language :: Python :: 3
-Classifier: License :: OSI Approved :: MIT License
-Classifier: Operating System :: POSIX :: Linux
-Classifier: Topic :: Terminals
-Classifier: Topic :: Software Development :: User Interfaces
-License-File: LICENSE
-Project-URL: Changelog, https://github.com/joedefen/console-window/blob/main/CHANGELOG.md
-Project-URL: Homepage, https://github.com/joedefen/console-window
-Project-URL: Issues, https://github.com/joedefen/console-window/issues
-Project-URL: Repository, https://github.com/joedefen/console-window
-
 
 # console-window 
 
@@ -411,7 +392,7 @@ degrades by itself:
   or pass it with the window: `ConsoleWindowOpts(glyphs={'tick': ('✓', 'OK')},
   glyphs_probe=('tick',))`. Once registered, the glyph both degrades with
   `Glyphs.get('tick')` and appears in the font check via `Glyphs.probe_text()`.
-* **Two switches, no argparse boilerplate.** The bundled helper adds them:
+* **The switches, with no argparse boilerplate.** The bundled helper adds them:
 
   ```python
   parser = cli.add_display_arguments(argparse.ArgumentParser())
@@ -421,9 +402,10 @@ degrades by itself:
 
   `--ascii` forces the fallback (`--ascii=no` forces the full set) and
   `--glyphs {auto,ascii,unicode}` is its symmetric spelling; `--glyphs` wins if
-  both are given. `--theme` seeds the first window's colour theme. Apps without
-  argparse can use `CONSOLE_WINDOW_GLYPHS=auto|ascii|unicode`, which outranks
-  detection.
+  both are given. `--theme` seeds the first window's colour theme and
+  `--no-color` draws the semantic roles with bold/reverse attributes instead of
+  colour. Apps without argparse can use
+  `CONSOLE_WINDOW_GLYPHS=auto|ascii|unicode`, which outranks detection.
 * **The mode is process-wide**, like the colour-pair table, because there is one
   terminal. `ConsoleWindowOpts(ascii=...)` seeds it and `win.ascii_mode` reads
   it; a window constructed later never reverts an explicit choice.
@@ -439,6 +421,17 @@ line, remembers the choice through any object with `load()`/`save()`, and
 `Theme.initial(cli_theme, store)` returns the theme a new process should start
 on. The library never opens a file.
 
+The appearance layer is shared too. `console_window.appearance.semantic_attr(role)`
+returns the installed colour pair for a semantic role, or the matching attribute
+from `MONO_ROLES` when colour is off; it degrades to plain text when the terminal
+has no colour or curses has not been initialised, so a redraw is never aborted by
+a colour. `set_colors_enabled()` / `colors_enabled()` hold the process-wide
+switch, and `resolve_appearance(cli_theme=None, no_color=False, saved_theme='',
+saved_colors=True, environ=None)` returns the `(theme, colors)` to start with:
+`--no-color` first, then an explicit `--theme`, then `NO_COLOR`, then the
+remembered choice. Apps keep their preference file and their own pseudo-themes;
+the library gives them the policy, not the storage.
+
 ## Versioning and Deprecation
 
 `console-window` follows semantic versioning: patch releases fix behaviour
@@ -491,4 +484,3 @@ For more extensive examples, you can look at some projects using `console-window
   * viewer of /proc/meminfo that shows historical values
 * [vappman](https://github.com/joedefen/vappman)
   * convenince wrapper to mostly hide CLI of [AppMan](https://github.com/ivan-hc/AppMan), a life-cycle manager for 2000+ AppImages
-

{console_window-2.1.3 → console_window-2.2.0}/console_window/__init__.py

@@ -1,7 +1,14 @@
 # Single source of truth for the package version: pyproject.toml declares
 # ``dynamic = ["version"]``, so flit reads this value instead of duplicating it.
-__version__ = "2.1.3"
+__version__ = "2.2.0"
 
+from .appearance import (
+    MONO_ROLES,
+    colors_enabled,
+    resolve_appearance,
+    semantic_attr,
+    set_colors_enabled,
+)
 from .context import Context
 from .glyphs import Glyph, Glyphs
 from .header import HeaderLine, Span
@@ -22,6 +29,7 @@ from .window import ConsoleWindow, TerminalTooSmallError
 
 __all__ = [
     'HOME_ST',
+    'MONO_ROLES',
     'NAVIGATION_KEYS',
     'BasicHelpScreen',
     'BasicTextScreen',
@@ -41,5 +49,9 @@ __all__ = [
     'TerminalTooSmallError',
     'Theme',
     'ThemeStore',
+    'colors_enabled',
     'reset_ctrl_c',
+    'resolve_appearance',
+    'semantic_attr',
+    'set_colors_enabled',
 ]

console_window-2.2.0/console_window/appearance.py

@@ -0,0 +1,135 @@
+"""Semantic colour roles, and one resolver for the colour switch.
+
+Colour here is decoration, never information.  Every role degrades to an
+attribute when colour is off, so the same hierarchy survives on a monochrome
+terminal or under ``--no-color``.  Applications kept writing this layer twice:
+the role-to-attribute mapping, the process-wide switch seeded by ``--no-color``
+or ``NO_COLOR``, and a lookup that must never abort a redraw.  It now lives
+here.
+
+The role ids are :class:`Theme`'s semantic pairs rather than literal colour
+numbers.  The library installs those pairs at startup and re-installs them
+whenever a theme is applied, so changing the active theme recolours the whole UI
+without an edit to any draw code.
+
+``--no-color`` is a per-run switch, not a saved preference: it replaces the
+pairs with the attributes in :data:`MONO_ROLES` for this process.  Picking a
+theme from the colour-theme screen is a request for colour, so the caller can
+lift the switch again -- :func:`resolve_appearance` does that when it sees an
+explicit theme.
+
+Nothing application-specific belongs in this module: preference files, app
+vocabulary and app pseudo-themes stay with the application.  An app that has a
+``mono`` pseudo-theme normalises that name to ``''`` plus ``saved_colors=False``
+before calling :func:`resolve_appearance`.
+"""
+
+from __future__ import annotations
+
+import curses
+import os
+from collections.abc import Mapping
+
+from .theme import Theme
+
+__all__ = [
+    'MONO_ROLES',
+    'colors_enabled',
+    'resolve_appearance',
+    'semantic_attr',
+    'set_colors_enabled',
+]
+
+# Role -> attribute used when colour is off.  The hierarchy is kept with
+# emphasis instead of hue: the destructive roles are bold+reverse, warnings,
+# successes and emphasis are bold, and the informational roles carry nothing
+# (their surrounding structure already distinguishes them).
+MONO_ROLES: dict[int, int] = {
+    Theme.DANGER: curses.A_BOLD | curses.A_REVERSE,
+    Theme.ERROR: curses.A_BOLD | curses.A_REVERSE,
+    Theme.WARNING: curses.A_BOLD,
+    Theme.SUCCESS: curses.A_BOLD,
+    Theme.EMPHASIS: curses.A_BOLD,
+    Theme.INFO: curses.A_NORMAL,
+    Theme.PROGRESS: curses.A_NORMAL,
+    Theme.OLD_SUCCESS: curses.A_NORMAL,
+    Theme.HOTSWAP: curses.A_NORMAL,
+}
+
+# Process-wide switch, seeded at startup by --no-color / NO_COLOR.  One
+# terminal, so one decision.
+_COLORS_ENABLED = True
+
+
+def set_colors_enabled(enabled: bool) -> None:
+    """Turn semantic colour on or off for the whole process."""
+    global _COLORS_ENABLED  # one terminal, one process-wide switch
+    _COLORS_ENABLED = bool(enabled)
+
+
+def colors_enabled() -> bool:
+    """True while semantic roles resolve to colour pairs rather than attributes."""
+    return _COLORS_ENABLED
+
+
+def resolve_appearance(
+    cli_theme: str | None = None,
+    no_color: bool = False,
+    saved_theme: str | None = '',
+    saved_colors: bool = True,
+    environ: Mapping[str, str] | None = None,
+) -> tuple[str, bool]:
+    """Starting ``(theme, colors)`` from the switches, environment and memory.
+
+    Precedence, highest first: ``--no-color``, an explicit ``--theme`` (a
+    statement of intent, so it is honoured even when ``NO_COLOR`` is set), the
+    ``NO_COLOR`` convention (any non-empty value disables colour, per
+    no-color.org), then the remembered choice.
+
+    ``cli_theme``/``saved_theme`` are returned resolved to a known library
+    theme; ``''`` means "no explicit theme, keep the library default".  An
+    unknown name resolves to ``'default'``, exactly like :meth:`Theme.resolve`.
+
+    The result is a decision, not an action: call
+    :func:`set_colors_enabled` with the second value (or pass both on to
+    whatever applies themes) when the process should start that way.
+    """
+    env = os.environ if environ is None else environ
+
+    if no_color:
+        colors = False
+    elif cli_theme:
+        colors = True
+    elif env.get('NO_COLOR'):
+        colors = False
+    else:
+        colors = bool(saved_colors)
+
+    if cli_theme:
+        theme = Theme.resolve(cli_theme)
+    elif saved_theme:
+        theme = Theme.resolve(saved_theme)
+    else:
+        theme = ''
+    return theme, colors
+
+
+def semantic_attr(pair_id: int) -> int:
+    """Attribute for a :class:`Theme` role, or plain when colour is off.
+
+    With colour off the role becomes an attribute from :data:`MONO_ROLES`.
+    Otherwise both ``curses.has_colors()`` and ``curses.color_pair()`` can raise
+    before ``initscr()`` (``color_pair()`` refuses to run until then), and a
+    failed lookup must never abort a redraw, so any failure degrades to plain
+    text.  The ``except`` is deliberately broad for that reason: a guarded
+    redraw is worth more than a precise exception list, and the fallback is
+    always the same.
+    """
+    if not _COLORS_ENABLED:
+        return MONO_ROLES.get(pair_id, curses.A_NORMAL)
+    try:
+        if not curses.has_colors():
+            return 0
+        return curses.color_pair(pair_id)
+    except Exception:  # terminal not initialised yet; never abort a redraw
+        return 0

{console_window-2.1.3 → console_window-2.2.0}/console_window/cli.py

@@ -1,18 +1,22 @@
 """Argument-parser boilerplate for the display options.
 
-Every curses app ends up writing the same three switches: a way to force the
-plain-ASCII symbol set, a way to pick a colour theme, and a way to print what
-was detected.  This module supplies them, so an app's ``main()`` gains two
-lines instead of sixty:
+Every curses app ends up writing the same four switches: a way to force the
+plain-ASCII symbol set, a way to pick a colour theme, a way to turn semantic
+colour off, and a way to print what was detected.  This module supplies them,
+so an app's ``main()`` gains two lines instead of sixty:
 
     parser = cli.add_display_arguments(parser)
     ...
     cli.apply_display_arguments(opts, prog='myapp')
 
-The two switches are deliberately symmetric.  ``--ascii`` accepts an optional
-boolean (``--ascii``, ``--ascii=no``) and ``--glyphs`` accepts a mode
+``--ascii`` and ``--glyphs`` are deliberately symmetric.  ``--ascii`` accepts an
+optional boolean (``--ascii``, ``--ascii=no``) and ``--glyphs`` accepts a mode
 (``auto``, ``ascii``, ``unicode``); ``--glyphs`` wins when both are given, and
 "absent" everywhere means *detect*, never "assume Unicode".
+
+``--no-color`` is the appearance switch.  :func:`apply_display_arguments` acts on
+it, and an app that remembers a colour preference can settle the whole decision
+with :func:`console_window.appearance.resolve_appearance`.
 """
 
 from __future__ import annotations
@@ -22,11 +26,16 @@ import sys
 from collections.abc import Callable, Mapping
 from typing import TextIO
 
-from . import glyphs
+from . import appearance, glyphs
 from .glyphs import TerminalReport
 from .theme import Theme, ThemeStore
 
-__all__ = ['add_display_arguments', 'apply_display_arguments', 'resolve_force_ascii']
+__all__ = [
+    'add_display_arguments',
+    'apply_display_arguments',
+    'resolve_force_ascii',
+    'resolve_no_color',
+]
 
 _TRUE_WORDS = frozenset({'1', 'true', 'yes', 'y', 'on'})
 _FALSE_WORDS = frozenset({'0', 'false', 'no', 'n', 'off'})
@@ -51,7 +60,7 @@ def add_display_arguments(
     theme_store: ThemeStore | None = None,
     prog: str | None = None,
 ) -> argparse.ArgumentParser:
-    """Add ``--ascii``, ``--glyphs`` and ``--theme`` to *parser*.
+    """Add ``--ascii``, ``--glyphs``, ``--theme`` and ``--no-color`` to *parser*.
 
     Returns *parser* so a call site can wrap its own construction.  *theme_store*
     is accepted for symmetry with :func:`apply_display_arguments` (an app that
@@ -87,6 +96,15 @@ def add_display_arguments(
         default=None,
         help=f'color theme{remembered}',
     )
+    parser.add_argument(
+        '--no-color',
+        action='store_true',
+        default=None,
+        help=(
+            'draw the semantic roles with attributes instead of colour; wins '
+            'over --theme, and NO_COLOR does the same when the switch is absent'
+        ),
+    )
     return parser
 
 
@@ -108,6 +126,11 @@ def resolve_force_ascii(args: argparse.Namespace) -> bool | None:
     )
 
 
+def resolve_no_color(args: argparse.Namespace) -> bool:
+    """Map a parsed namespace to the ``--no-color`` switch (absent means off)."""
+    return bool(getattr(args, 'no_color', False))
+
+
 def apply_display_arguments(
     args: argparse.Namespace,
     *,
@@ -116,13 +139,19 @@ def apply_display_arguments(
     environ: Mapping[str, str] | None = None,
     stream: TextIO | None = None,
 ) -> TerminalReport:
-    """Set the glyph mode, print the report's notes, seed the theme.
+    """Set the glyph mode, print the report's notes, seed the theme, honour colour.
 
     Call this once, *before* any window is created, so the mode is decided while
     nothing has been drawn.  Returns the :class:`~console_window.glyphs.
     TerminalReport` so a caller can react to ``ascii_required`` (for example by
     printing a warning of its own).
 
+    An explicit ``--no-color`` turns the process-wide colour switch off here; an
+    absent switch is left alone, so an app with a remembered preference is free
+    to call ``set_colors_enabled()`` with its own decision.  The two halves of
+    that decision -- the theme to install and whether colour is on -- come from
+    :func:`console_window.appearance.resolve_appearance`.
+
     *printer* is a callable taking one string; pass ``sys.stderr.write`` style
     wrappers through ``lambda line: print(line, file=...)`` if needed.
     """
@@ -134,6 +163,10 @@ def apply_display_arguments(
     for note in report.notes:
         printer(f'{prog}: {note}' if prog else note)
 
+    if resolve_no_color(args):
+        # Only the explicit flag is acted on; "absent" belongs to the caller.
+        appearance.set_colors_enabled(False)
+
     theme = getattr(args, 'theme', None)
     if theme:
         if theme in Theme.list_all():

{console_window-2.1.3 → console_window-2.2.0}/pyproject.toml

@@ -34,12 +34,50 @@ classifiers = [
     "Topic :: Software Development :: User Interfaces",
 ]
 
+[project.optional-dependencies]
+# The minimum a contributor needs to run the suite, and the release toolchain.
+# `./bless` refuses to start unless `twine` and `packaging` meet its own floors
+# (`twine>=7`, `packaging>=26`), so the dev extra installs a toolchain the gate
+# accepts.  `tomli` is the 3.10 fallback for `bless` and for the tests' use of
+# `tomllib`; `requires-python` still allows 3.10.
+test = [
+    'pytest >= 7.0',
+    'pytest-cov >= 4.0',
+    'tomli >= 2.0; python_version < "3.11"',
+]
+dev = [
+    'pytest >= 7.0',
+    'pytest-cov >= 4.0',
+    'ruff >= 0.9',
+    'build >= 1.2',
+    'twine >= 7',
+    'packaging >= 26',
+    'tomli >= 2.0; python_version < "3.11"',
+]
+
 [project.urls]
 Homepage = "https://github.com/joedefen/console-window"
 Repository = "https://github.com/joedefen/console-window"
 Issues = "https://github.com/joedefen/console-window/issues"
 Changelog = "https://github.com/joedefen/console-window/blob/main/CHANGELOG.md"
 
+# ----------------------------------------------------------------------
+# RELEASE GATE CONFIGURATION
+[tool.bless]
+# The branch model `./bless` keeps.  `["main"]` releases from the trunk alone;
+# `["main", "dev"]` -- the default when this table says nothing -- requires a
+# `dev` branch both locally and on origin, and fast-forwards whichever of the
+# two lags onto the other before tagging.  This tree commits to the trunk, so a
+# release is `main` and the tag.
+branches = ["main"]
+
+# The rest is derived rather than written here: the distribution name comes
+# from `[project] name`, the package holding `__version__` from that name with
+# `-` and `.` turned into `_`, and the inspector from
+# `tests/inspect_dist.py`.  There is no `[project.scripts]` entry on purpose:
+# this is a library, so the smoke stage of `bless` imports the installed
+# package and prints `__version__` instead of running a console script.
+
 [tool.pytest.ini_options]
 testpaths = ["tests"]
 # Pad overflow is a UserWarning rather than an error, by design: a user's app
@@ -48,6 +86,19 @@ testpaths = ["tests"]
 # sample app's too-small head pad and its truncated help screen were found.
 filterwarnings = ["error::UserWarning"]
 
+[tool.coverage.run]
+# Pin the measured package so the number the release gate prints is the same
+# whichever directory pytest is started from.
+source = ["console_window"]
+omit = ["tests/*"]
+
+[tool.coverage.report]
+# Measured at 90.69% when the shared release gate was adopted.  The floor is a
+# ratchet against new code arriving without a test, not a target to optimise;
+# raise it when the number rises, never lower it.
+fail_under = 90
+show_missing = true
+
 # ----------------------------------------------------------------------
 # RUFF LINT CONFIGURATION
 [tool.ruff]

console_window-2.1.3/.github/workflows/ci.yml

@@ -1,66 +0,0 @@
-name: CI
-
-on:
-  push:
-  pull_request:
-
-jobs:
-  test:
-    name: tests (Python ${{ matrix.python-version }})
-    runs-on: ubuntu-latest
-    strategy:
-      fail-fast: false
-      matrix:
-        python-version: ["3.10", "3.11", "3.12", "3.13"]
-    steps:
-      - uses: actions/checkout@v4
-      - name: Set up Python
-        uses: actions/setup-python@v5
-        with:
-          python-version: ${{ matrix.python-version }}
-      - name: Install test dependencies
-        run: python -m pip install pytest==9.1.1 pytest-cov==7.1.0
-      - name: Run tests (TTY-free) with coverage floor
-        run: python -m pytest -q --cov=console_window --cov-fail-under=80
-
-  lint:
-    name: ruff
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - name: Set up Python
-        uses: actions/setup-python@v5
-        with:
-          python-version: "3.13"
-      - name: Install ruff
-        run: python -m pip install ruff==0.17.0
-      - name: Lint
-        run: ruff check .
-
-  types:
-    name: mypy
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - name: Set up Python
-        uses: actions/setup-python@v5
-        with:
-          python-version: "3.13"
-      - name: Install mypy
-        run: python -m pip install mypy==2.4.0
-      - name: Type check
-        run: python -m mypy
-
-  pylint:
-    name: pylint
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - name: Set up Python
-        uses: actions/setup-python@v5
-        with:
-          python-version: "3.13"
-      - name: Install pylint
-        run: python -m pip install pylint==3.3.4
-      - name: Lint
-        run: python -m pylint console_window SampleApp.py runner --disable=C,R