busymeter 0.2.0__tar.gz

busymeter-0.2.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 The Busy Meter authors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

busymeter-0.2.0/PKG-INFO

@@ -0,0 +1,169 @@
+Metadata-Version: 2.4
+Name: busymeter
+Version: 0.2.0
+Summary: Client and MCP server for the Busy Meter status light's local plugin API
+Author: The Busy Meter authors
+License-Expression: MIT
+Project-URL: Homepage, https://thebusymeter.com
+Project-URL: Source, https://github.com/RIPBillyMays/busy-meter-plugins
+Project-URL: Issues, https://github.com/RIPBillyMays/busy-meter-plugins/issues
+Keywords: busy light,status light,do not disturb,mcp,plugin
+Classifier: Programming Language :: Python :: 3
+Classifier: Operating System :: Microsoft :: Windows
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: mcp
+Requires-Dist: mcp==2.3.0; extra == "mcp"
+Dynamic: license-file
+
+# busymeter (Python)
+
+Client and MCP server for the Busy Meter status light's local plugin API. MIT licensed.
+
+- `busymeter`: the client and the bundled recipes (`busymeter.recipes`). Standard library only (no third-party
+  packages). Python 3.10+.
+- `busymeter_mcp`: `busymeter-mcp`, an MCP server over stdio so an AI assistant can read and set the meter. Needs the
+  official MCP SDK (`mcp==2.3.0`, the `mcp` extra).
+
+Before anything works, turn on **Settings → Sources → External connections** in the Busy Meter app. When it's off
+(or the app isn't running) every call fails with `NotListeningError` and a message saying exactly that.
+
+## Install
+
+```
+pip install --user busymeter            # client + `busymeter` command
+pip install --user "busymeter[mcp]"     # also busymeter-mcp, for AI assistants
+```
+
+`--user` installs for your Windows account only; starting recipes at sign-in needs that. From a checkout of this
+folder: `pip install --user ".[mcp]"`.
+
+Or without installing: put this folder on `PYTHONPATH` and run `python -m busymeter.cli` / `python -m busymeter_mcp`.
+
+## Client
+
+```python
+from busymeter import BusyMeter
+
+meter = BusyMeter("com.example.heartrate")          # your plugin id: 3-64 of a-z 0-9 . -
+meter.connect(                                       # first time: registers and waits for Allow in the tray
+    name="Heart-rate heat",
+    signals=[{"name": "hr-high", "label": "Heart rate 140+", "suggest": 5}],
+    wants=["signals", "status"],
+)
+meter.set_signals(["hr-high"], ttl_seconds=30)      # refresh before the TTL runs out
+meter.set_level(4, ttl_seconds=600)                 # or a level: 0-6 stars, "flash"
+print(meter.status())                               # {"level": 4, "paused": false, "source": "plugin", ...}
+meter.alert("lip-pulse")                            # needs "effects" in wants; one every 10 s
+meter.clear()
+```
+
+- **Port:** read from `%LOCALAPPDATA%\BusyMeter\plugin-api.json` (written by the app only while it listens). Only the
+  port is taken from the file; the host is always `127.0.0.1`. `BUSYMETER_DISCOVERY_FILE` overrides the file's path.
+  Without the file the client still probes and registers on 47820, but never sends a token there: calls that need
+  one fail with "Busy Meter isn't running, or External connections is off".
+- **Never sends an `Origin` header** (the app refuses those), no query strings, JSON bodies only.
+- **Errors:** every failure is a `BusyMeterError` with `.code` (the API's error code), `.status` and a `.message` you
+  can show as is: `NotListeningError` (turn on External connections), `AppNotRespondingError` (connected, but no
+  answer in time or the connection broke), `UnauthorizedError` (401: register again),
+  `ForbiddenError` (403: switched off, or not in `wants`), `ConflictError` (409), `RateLimitedError` (429, with
+  `.retry_after`), `DeniedError` (the user clicked Deny, or 2 minutes passed), `ApprovalTimeoutError`.
+- **Withdraw:** `meter.withdraw()` takes back a registration still waiting in the tray (its prompt closes). If the
+  user already answered, it collects the answer instead (a token is saved as usual). The same plugin id can't register
+  again for 5 seconds afterwards. The recipe runner does this when a recipe stops.
+- **Revoked tokens:** a 401 deletes the saved token. `connect()` checks a saved token before using it and registers
+  again when the app no longer knows it; `meter.reconnecting(lambda: meter.set_level(4, 60))` does the same in the
+  middle of a run (the user clicks Allow again) and retries once.
+- **Longer than 10 minutes:** the API caps a TTL at 600 s so a crashed plugin can't leave the meter stuck. Keep running
+  and refresh (the `busymeter` command does this for `--for` over 10 minutes).
+
+### Where the token is kept
+
+One JSON file per plugin id, readable by the current user only:
+
+- Windows: `%LOCALAPPDATA%\busymeter-plugins\tokens\<plugin-id>.json`. Before every write the folder (also one set
+  with `BUSYMETER_TOKEN_DIR`) loses its inherited permissions and grants only the current user, by SID from
+  `whoami /user` (`icacls`). If that fails, a `PermissionWarning` says so and the file is still written.
+- macOS/Linux: `$XDG_CONFIG_HOME/busymeter-plugins/tokens/` (else `~/.config/...`); the folder is set to 0700 (also an
+  existing looser one), files 0600.
+- `BUSYMETER_TOKEN_DIR` overrides the folder.
+
+The token is a bearer secret: whoever reads it can set this plugin's signals until the user revokes the plugin under
+Settings → Sources → External connections. `meter.forget()` deletes the file. While a registration waits, the file
+also holds its request id, so the next run keeps waiting instead of asking again.
+
+## Command line
+
+```
+busymeter level 5 --for 10m
+busymeter level flash --for 30s
+busymeter level 4 --for 2h     # stays running and refreshes; Ctrl+C clears
+busymeter clear
+busymeter status
+busymeter run vibe_meter       # a bundled recipe: stream_status, game_state, focus_timer, vibe_meter
+busymeter focus 25m            # one focus block (--pomodoro for cycles)
+busymeter recipes              # bundled recipes: installed? running? settings file
+busymeter stop vibe_meter      # stop one running in the background (it clears its signals)
+busymeter autostart vibe_meter on   # Windows: start it every time you sign in (off by default; `off` undoes it)
+busymeter autostart            # which recipes start at sign-in
+```
+
+Recipes, their settings files and what each one reads: `../recipes/README.md`. `python -m busymeter ...` works the
+same as the `busymeter` command.
+
+## MCP server (`busymeter-mcp`)
+
+Tools: `get_status`, `list_sources`, `register_plugin`, `set_signals`, `set_level` (0-6 or `"flash"`, with a TTL such as
+`"10m"`; over 10 minutes the server keeps refreshing while it runs), `clear`. The assistant can **ask** to register;
+only you can approve it, by clicking **Allow** in the Busy Meter tray. `register_plugin` waits up to 110 s and returns
+"Waiting for you to click Allow in the Busy Meter tray" if you haven't yet; calling it again keeps waiting on the same
+request. `list_sources` says what it can't know: the API doesn't list the app's sources or mappings (those are on
+Settings → Levels). The server registers as `com.thebusymeter.mcp` (`BUSYMETER_PLUGIN_ID` changes it).
+
+Recipe tools: `list_recipes`, `install_recipe(name)` (bundled names only: writes the default settings and starts the
+recipe in the background for this user; it then waits for Allow in the tray), `stop_recipe`, `uninstall_recipe`
+(stops it, clears its signals, deletes its settings and saved token; revoke the approval in the app),
+`get_recipe_settings` and `set_recipe_settings(name, changes)` (checked against the recipe's schema; the OBS password,
+the game-state token and folder paths are never shown or accepted: the reply names the settings file to edit),
+`set_recipe_autostart(name, on)` (Windows: start that recipe every time you sign in, or stop doing that; off by
+default, bundled names only, needs a `pip install --user` install; the first run still needs Allow in the tray, and
+after a Deny it isn't started at sign-in again until turned on again). `list_recipes` shows `startsAtSignIn` for
+each, and `uninstall_recipe` removes the sign-in entry.
+
+Claude Desktop (`claude_desktop_config.json`) or any client with the same format:
+
+```json
+{
+  "mcpServers": {
+    "busymeter": {
+      "command": "busymeter-mcp"
+    }
+  }
+}
+```
+
+Running from a checkout instead of an install:
+
+```json
+{
+  "mcpServers": {
+    "busymeter": {
+      "command": "python",
+      "args": ["-m", "busymeter_mcp"],
+      "env": { "PYTHONPATH": "C:\\path\\to\\plugins\\python" }
+    }
+  }
+}
+```
+
+Claude Code:
+
+```
+claude mcp add busymeter -- busymeter-mcp
+```
+
+## Tests
+
+From this folder: `python -m unittest`. The MCP server test is skipped when the `mcp` package isn't installed, and
+fails instead when `BUSYMETER_REQUIRE_PYTHON=1`.

busymeter-0.2.0/README.md

@@ -0,0 +1,150 @@
+# busymeter (Python)
+
+Client and MCP server for the Busy Meter status light's local plugin API. MIT licensed.
+
+- `busymeter`: the client and the bundled recipes (`busymeter.recipes`). Standard library only (no third-party
+  packages). Python 3.10+.
+- `busymeter_mcp`: `busymeter-mcp`, an MCP server over stdio so an AI assistant can read and set the meter. Needs the
+  official MCP SDK (`mcp==2.3.0`, the `mcp` extra).
+
+Before anything works, turn on **Settings → Sources → External connections** in the Busy Meter app. When it's off
+(or the app isn't running) every call fails with `NotListeningError` and a message saying exactly that.
+
+## Install
+
+```
+pip install --user busymeter            # client + `busymeter` command
+pip install --user "busymeter[mcp]"     # also busymeter-mcp, for AI assistants
+```
+
+`--user` installs for your Windows account only; starting recipes at sign-in needs that. From a checkout of this
+folder: `pip install --user ".[mcp]"`.
+
+Or without installing: put this folder on `PYTHONPATH` and run `python -m busymeter.cli` / `python -m busymeter_mcp`.
+
+## Client
+
+```python
+from busymeter import BusyMeter
+
+meter = BusyMeter("com.example.heartrate")          # your plugin id: 3-64 of a-z 0-9 . -
+meter.connect(                                       # first time: registers and waits for Allow in the tray
+    name="Heart-rate heat",
+    signals=[{"name": "hr-high", "label": "Heart rate 140+", "suggest": 5}],
+    wants=["signals", "status"],
+)
+meter.set_signals(["hr-high"], ttl_seconds=30)      # refresh before the TTL runs out
+meter.set_level(4, ttl_seconds=600)                 # or a level: 0-6 stars, "flash"
+print(meter.status())                               # {"level": 4, "paused": false, "source": "plugin", ...}
+meter.alert("lip-pulse")                            # needs "effects" in wants; one every 10 s
+meter.clear()
+```
+
+- **Port:** read from `%LOCALAPPDATA%\BusyMeter\plugin-api.json` (written by the app only while it listens). Only the
+  port is taken from the file; the host is always `127.0.0.1`. `BUSYMETER_DISCOVERY_FILE` overrides the file's path.
+  Without the file the client still probes and registers on 47820, but never sends a token there: calls that need
+  one fail with "Busy Meter isn't running, or External connections is off".
+- **Never sends an `Origin` header** (the app refuses those), no query strings, JSON bodies only.
+- **Errors:** every failure is a `BusyMeterError` with `.code` (the API's error code), `.status` and a `.message` you
+  can show as is: `NotListeningError` (turn on External connections), `AppNotRespondingError` (connected, but no
+  answer in time or the connection broke), `UnauthorizedError` (401: register again),
+  `ForbiddenError` (403: switched off, or not in `wants`), `ConflictError` (409), `RateLimitedError` (429, with
+  `.retry_after`), `DeniedError` (the user clicked Deny, or 2 minutes passed), `ApprovalTimeoutError`.
+- **Withdraw:** `meter.withdraw()` takes back a registration still waiting in the tray (its prompt closes). If the
+  user already answered, it collects the answer instead (a token is saved as usual). The same plugin id can't register
+  again for 5 seconds afterwards. The recipe runner does this when a recipe stops.
+- **Revoked tokens:** a 401 deletes the saved token. `connect()` checks a saved token before using it and registers
+  again when the app no longer knows it; `meter.reconnecting(lambda: meter.set_level(4, 60))` does the same in the
+  middle of a run (the user clicks Allow again) and retries once.
+- **Longer than 10 minutes:** the API caps a TTL at 600 s so a crashed plugin can't leave the meter stuck. Keep running
+  and refresh (the `busymeter` command does this for `--for` over 10 minutes).
+
+### Where the token is kept
+
+One JSON file per plugin id, readable by the current user only:
+
+- Windows: `%LOCALAPPDATA%\busymeter-plugins\tokens\<plugin-id>.json`. Before every write the folder (also one set
+  with `BUSYMETER_TOKEN_DIR`) loses its inherited permissions and grants only the current user, by SID from
+  `whoami /user` (`icacls`). If that fails, a `PermissionWarning` says so and the file is still written.
+- macOS/Linux: `$XDG_CONFIG_HOME/busymeter-plugins/tokens/` (else `~/.config/...`); the folder is set to 0700 (also an
+  existing looser one), files 0600.
+- `BUSYMETER_TOKEN_DIR` overrides the folder.
+
+The token is a bearer secret: whoever reads it can set this plugin's signals until the user revokes the plugin under
+Settings → Sources → External connections. `meter.forget()` deletes the file. While a registration waits, the file
+also holds its request id, so the next run keeps waiting instead of asking again.
+
+## Command line
+
+```
+busymeter level 5 --for 10m
+busymeter level flash --for 30s
+busymeter level 4 --for 2h     # stays running and refreshes; Ctrl+C clears
+busymeter clear
+busymeter status
+busymeter run vibe_meter       # a bundled recipe: stream_status, game_state, focus_timer, vibe_meter
+busymeter focus 25m            # one focus block (--pomodoro for cycles)
+busymeter recipes              # bundled recipes: installed? running? settings file
+busymeter stop vibe_meter      # stop one running in the background (it clears its signals)
+busymeter autostart vibe_meter on   # Windows: start it every time you sign in (off by default; `off` undoes it)
+busymeter autostart            # which recipes start at sign-in
+```
+
+Recipes, their settings files and what each one reads: `../recipes/README.md`. `python -m busymeter ...` works the
+same as the `busymeter` command.
+
+## MCP server (`busymeter-mcp`)
+
+Tools: `get_status`, `list_sources`, `register_plugin`, `set_signals`, `set_level` (0-6 or `"flash"`, with a TTL such as
+`"10m"`; over 10 minutes the server keeps refreshing while it runs), `clear`. The assistant can **ask** to register;
+only you can approve it, by clicking **Allow** in the Busy Meter tray. `register_plugin` waits up to 110 s and returns
+"Waiting for you to click Allow in the Busy Meter tray" if you haven't yet; calling it again keeps waiting on the same
+request. `list_sources` says what it can't know: the API doesn't list the app's sources or mappings (those are on
+Settings → Levels). The server registers as `com.thebusymeter.mcp` (`BUSYMETER_PLUGIN_ID` changes it).
+
+Recipe tools: `list_recipes`, `install_recipe(name)` (bundled names only: writes the default settings and starts the
+recipe in the background for this user; it then waits for Allow in the tray), `stop_recipe`, `uninstall_recipe`
+(stops it, clears its signals, deletes its settings and saved token; revoke the approval in the app),
+`get_recipe_settings` and `set_recipe_settings(name, changes)` (checked against the recipe's schema; the OBS password,
+the game-state token and folder paths are never shown or accepted: the reply names the settings file to edit),
+`set_recipe_autostart(name, on)` (Windows: start that recipe every time you sign in, or stop doing that; off by
+default, bundled names only, needs a `pip install --user` install; the first run still needs Allow in the tray, and
+after a Deny it isn't started at sign-in again until turned on again). `list_recipes` shows `startsAtSignIn` for
+each, and `uninstall_recipe` removes the sign-in entry.
+
+Claude Desktop (`claude_desktop_config.json`) or any client with the same format:
+
+```json
+{
+  "mcpServers": {
+    "busymeter": {
+      "command": "busymeter-mcp"
+    }
+  }
+}
+```
+
+Running from a checkout instead of an install:
+
+```json
+{
+  "mcpServers": {
+    "busymeter": {
+      "command": "python",
+      "args": ["-m", "busymeter_mcp"],
+      "env": { "PYTHONPATH": "C:\\path\\to\\plugins\\python" }
+    }
+  }
+}
+```
+
+Claude Code:
+
+```
+claude mcp add busymeter -- busymeter-mcp
+```
+
+## Tests
+
+From this folder: `python -m unittest`. The MCP server test is skipped when the `mcp` package isn't installed, and
+fails instead when `BUSYMETER_REQUIRE_PYTHON=1`.

busymeter-0.2.0/busymeter/__init__.py

@@ -0,0 +1,39 @@
+"""Busy Meter plugin API client (MIT). Standard library only. See README.md."""
+
+from .client import (
+    API_VERSION,
+    NOT_RESPONDING_MESSAGE,
+    NOT_RUNNING_MESSAGE,
+    AppNotRespondingError,
+    DEFAULT_PORT,
+    EFFECTS,
+    LEVELS,
+    MAX_TTL_SECONDS,
+    TURN_ON_MESSAGE,
+    WANTS,
+    ApprovalTimeoutError,
+    BusyMeter,
+    BusyMeterError,
+    CancelledError,
+    ConflictError,
+    DeniedError,
+    Endpoint,
+    ForbiddenError,
+    NotListeningError,
+    RateLimitedError,
+    UnauthorizedError,
+    discover,
+    discovery_path,
+    normalize_level,
+    parse_duration,
+)
+from .tokens import TokenStore, default_token_dir
+
+__version__ = "0.2.0"
+
+__all__ = [
+    "API_VERSION", "NOT_RESPONDING_MESSAGE", "NOT_RUNNING_MESSAGE", "AppNotRespondingError", "DEFAULT_PORT", "EFFECTS", "LEVELS", "MAX_TTL_SECONDS", "TURN_ON_MESSAGE", "WANTS",
+    "ApprovalTimeoutError", "BusyMeter", "BusyMeterError", "CancelledError", "ConflictError", "DeniedError", "Endpoint",
+    "ForbiddenError", "NotListeningError", "RateLimitedError", "TokenStore", "UnauthorizedError",
+    "default_token_dir", "discover", "discovery_path", "normalize_level", "parse_duration",
+]

busymeter-0.2.0/busymeter/__main__.py

@@ -0,0 +1,7 @@
+"""python -m busymeter ... (same as the busymeter command)."""
+
+import sys
+
+from .cli import main
+
+sys.exit(main())

busymeter-0.2.0/busymeter/cli.py

@@ -0,0 +1,120 @@
+"""``busymeter`` command: set a level from the command line.
+
+    busymeter level 5 --for 10m     # 5 stars for 10 minutes, then back to whatever the app shows
+    busymeter level flash --for 30s
+    busymeter level 4 --for 2h      # longer than 10 minutes: stays running and refreshes; Ctrl+C clears
+    busymeter clear
+    busymeter status
+    busymeter run vibe_meter        # a bundled recipe: stream_status, game_state, focus_timer, vibe_meter
+    busymeter focus 25m             # a focus block (--pomodoro for cycles)
+    busymeter recipes               # which recipes are installed or running
+    busymeter stop vibe_meter       # stop one running in the background
+
+The first run asks you to click Allow in the Busy Meter tray (needs Settings > Sources > External connections on).
+"""
+
+from __future__ import annotations
+
+import argparse
+import sys
+import time
+
+from .client import MAX_TTL_SECONDS, BusyMeter, BusyMeterError, normalize_level, parse_duration
+
+DEFAULT_ID = "com.thebusymeter.cli"
+REFRESH_TTL = 60
+
+
+def safe_console() -> None:
+    """Messages use arrows (Settings → Sources); don't crash on a console code page without them."""
+    for stream in (sys.stdout, sys.stderr):
+        try:
+            stream.reconfigure(errors="replace")
+        except (AttributeError, ValueError):
+            pass
+
+
+def call(meter, fn):
+    """Run fn; if the token was revoked, register again (the user clicks Allow in the tray) and retry once."""
+    reconnecting = getattr(meter, "reconnecting", None)
+    return reconnecting(fn) if reconnecting is not None else fn()
+
+
+def _connect(meter: BusyMeter) -> None:
+    meter.connect(
+        name="Busy Meter command line",
+        wants=("signals", "status"),
+        on_wait=lambda: print("Waiting for you to click Allow in the Busy Meter tray...", file=sys.stderr),
+    )
+
+
+def hold_level(meter: BusyMeter, level: int | str, seconds: int, *, sleep=time.sleep, clock=time.monotonic) -> None:
+    """Show ``level`` for ``seconds``. Up to 10 minutes is one call; longer refreshes every 30 s, then clears."""
+    if seconds <= MAX_TTL_SECONDS:
+        call(meter, lambda: meter.set_level(level, seconds))
+        return
+    end = clock() + seconds
+    try:
+        while True:
+            left = end - clock()
+            if left <= 0:
+                break
+            ttl = max(1, min(REFRESH_TTL, int(left + 0.999)))
+            call(meter, lambda: meter.set_level(level, ttl))
+            sleep(min(REFRESH_TTL / 2, max(left, 0)))
+    finally:
+        try:
+            meter.clear()
+        except BusyMeterError:
+            pass
+
+
+def main(argv: list[str] | None = None) -> int:
+    safe_console()
+    parser = argparse.ArgumentParser(prog="busymeter", description="Set the Busy Meter's level from the command line.")
+    parser.add_argument("--id", default=DEFAULT_ID, help=f"plugin id to register as (default {DEFAULT_ID})")
+    sub = parser.add_subparsers(dest="command", required=True)
+    level = sub.add_parser("level", help="show a level for a while")
+    level.add_argument("level", help="0-6 (stars; 0 = lip accent only) or flash")
+    level.add_argument("--for", dest="duration", default="10m", help="how long, e.g. 30s, 10m, 2h (default 10m)")
+    sub.add_parser("clear", help="clear this command's level now")
+    sub.add_parser("status", help="print what the meter shows")
+    from .recipes import cli as recipes_cli
+
+    recipes_cli.add_commands(sub)
+    args = parser.parse_args(argv)
+    if recipes_cli.handles(args.command):
+        return recipes_cli.dispatch(args, parser)
+
+    meter = BusyMeter(args.id)
+    try:
+        if args.command == "level":
+            try:
+                value = normalize_level(args.level)
+                seconds = parse_duration(args.duration)
+            except ValueError as e:
+                parser.error(str(e))
+            _connect(meter)
+            if seconds > MAX_TTL_SECONDS:
+                print(f"Holding {value} for {seconds} s; keep this running (Ctrl+C clears).", file=sys.stderr)
+            hold_level(meter, value, seconds)
+            if seconds <= MAX_TTL_SECONDS:
+                print(f"Level {value} for {seconds} s.")
+        elif args.command == "clear":
+            _connect(meter)
+            call(meter, meter.clear)
+            print("Cleared.")
+        else:
+            _connect(meter)
+            s = call(meter, meter.status)
+            print(f"level={s.get('level')} paused={str(s.get('paused')).lower()} source={s.get('source')}")
+    except KeyboardInterrupt:
+        return 130
+    except BusyMeterError as e:
+        print(e.message, file=sys.stderr)
+        return 1
+    return 0
+
+
+if __name__ == "__main__":
+    sys.exit(main())