desktop-lifecycle 0.1.0__tar.gz

desktop_lifecycle-0.1.0/CHANGELOG.md

@@ -0,0 +1,35 @@
+# Changelog
+
+All notable changes to this project are documented here.
+
+The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [0.1.0] - 2026-11-11
+
+First release.
+
+### Added
+
+- `App` — one object that resolves paths, detects the session and guards
+  against a second instance.
+- `Paths` — XDG base directories on Linux/BSD, `APPDATA`/`LOCALAPPDATA` on
+  Windows, `Application Support`/`Caches` on macOS; created `0700`.
+- `SingleInstance` — advisory `flock`/`msvcrt` lock with a `0600` lock file,
+  plus a signal file so a second launch can ask the running copy to show its
+  window.
+- `Autostart` — XDG autostart entry, per-user Windows `Run` value, macOS
+  LaunchAgent; enable, disable, toggle and describe.
+- `build_entry` / `install_menu_entry` / `install_icon` / `remove_menu_entry` —
+  `.desktop` files with spec-correct `Exec=` escaping and atomic writes.
+- `session_type` — `x11`, `wayland`, `windows`, `macos` or `unknown`, based on
+  `XDG_SESSION_TYPE` rather than on `DISPLAY`.
+- `tray.backend` — reports `ayatana`, `appindicator`, `pystray` or `none`, so an
+  application can decide whether a tray is possible at all.
+- `setup_logging` — rotating log in the state directory.
+- `python -m desktop_lifecycle` — read-only environment report for bug reports.
+
+[Unreleased]: https://github.com/1emrecoskun/desktop-lifecycle/compare/v0.1.0...HEAD
+[0.1.0]: https://github.com/1emrecoskun/desktop-lifecycle/releases/tag/v0.1.0

desktop_lifecycle-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,134 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement by opening a
+private report through the repository's **Security → Report a vulnerability**
+form, which is visible only to the maintainers.
+
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

desktop_lifecycle-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,67 @@
+# Contributing
+
+Thanks for taking the time. This project is deliberately small; keeping it
+small is part of the design.
+
+## Before you start
+
+Open an issue first for anything larger than a bug fix. The scope is "the
+boring parts around a GUI application", not "a desktop framework".
+
+## What fits
+
+* fixing a platform-specific path, quoting or locking bug
+* supporting a desktop environment or tray backend that genuinely misbehaves
+* tests that reproduce a real bug report
+* documentation fixes, especially for Wayland and Windows
+
+## What does not fit
+
+* drawing UI, a widget set, or a tray implementation of our own
+* network features, telemetry, accounts
+* anything that needs `sudo` or writes outside the user's home directory
+* new runtime dependencies (the zero-dependency promise is the point)
+
+## Development
+
+```bash
+git clone https://github.com/1emrecoskun/desktop-lifecycle
+cd desktop-lifecycle
+python -m unittest discover -s tests -v
+```
+
+There is nothing to install: the package has no runtime dependencies, and the
+tests need neither a display nor hardware.
+
+A quick sanity check of the code itself:
+
+```bash
+python -m compileall -q desktop_lifecycle tests
+python -m desktop_lifecycle
+```
+
+## Pull requests
+
+* one topic per pull request
+* a test for every behaviour change — tests that fail before your fix
+* keep the public API additive where possible; this library is used by
+  applications that cannot be updated in lockstep
+* do not add a `CHANGELOG` entry; the maintainer writes it at release time
+
+## Commit messages
+
+Short imperative subject, for example:
+
+```
+Fix Exec quoting for paths containing a dollar sign
+```
+
+## Code style
+
+Plain Python, no formatter required. Type hints where they help. Comments
+should explain *why*, not restate the code. Keep functions small enough to
+read on one screen.
+
+## Conduct
+
+By participating you agree to the [Code of Conduct](CODE_OF_CONDUCT.md).

desktop_lifecycle-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 desktop-lifecycle contributors
+
+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.

desktop_lifecycle-0.1.0/MANIFEST.in

@@ -0,0 +1,10 @@
+include LICENSE
+include README.md
+include README.tr.md
+include CHANGELOG.md
+include CONTRIBUTING.md
+include SECURITY.md
+include CODE_OF_CONDUCT.md
+recursive-include docs *.md
+recursive-include examples *.py
+recursive-include tests *.py

desktop_lifecycle-0.1.0/PKG-INFO

@@ -0,0 +1,196 @@
+Metadata-Version: 2.4
+Name: desktop-lifecycle
+Version: 0.1.0
+Summary: The boring parts of a small Python desktop app: single-instance lock, XDG paths, autostart, menu entry, session and tray detection, rotating logs.
+Author: desktop-lifecycle contributors
+License-Expression: MIT
+Project-URL: Homepage, https://github.com/1emrecoskun/desktop-lifecycle
+Project-URL: Issues, https://github.com/1emrecoskun/desktop-lifecycle/issues
+Project-URL: Changelog, https://github.com/1emrecoskun/desktop-lifecycle/blob/main/CHANGELOG.md
+Keywords: desktop,linux,xdg,autostart,single-instance,system-tray,appindicator,wayland,pystray,desktop-entry
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: X11 Applications
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Operating System :: Microsoft :: Windows
+Classifier: Operating System :: MacOS
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Desktop Environment
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: tray
+Requires-Dist: pystray>=0.19; extra == "tray"
+Requires-Dist: Pillow>=10; extra == "tray"
+Provides-Extra: build
+Requires-Dist: build>=1.0; extra == "build"
+Requires-Dist: twine>=5; extra == "build"
+Dynamic: license-file
+
+# desktop-lifecycle
+
+![test](https://github.com/1emrecoskun/desktop-lifecycle/actions/workflows/test.yml/badge.svg)
+
+**The boring parts of a small Python desktop app — before you write any UI.**
+
+Single-instance lock, XDG directories, autostart, menu entry, session
+detection, tray capability and rotating logs. No framework, no dependencies,
+no root.
+
+```bash
+pip install git+https://github.com/1emrecoskun/desktop-lifecycle
+```
+
+```python
+from desktop_lifecycle import App
+
+app = App("my-tool").ensure_dirs()
+app.setup_logging()
+
+if not app.acquire():        # a second copy was launched
+    raise SystemExit(0)      # it already asked the first one to show itself
+```
+
+That is the whole idea: the four things every small desktop app gets wrong,
+in one small library you can read in ten minutes.
+
+---
+
+## Why this exists
+
+Every Python utility that lives in the tray ends up re-implementing the same
+six things, usually differently and often incorrectly:
+
+| What you need | What usually happens instead |
+|---|---|
+| One process per session | a PID file that lies after a crash, because PIDs are reused |
+| Somewhere to write | settings in `~/.config`, logs in the checkout, a state file at `/.local/state` |
+| Start at login | three platform-specific files written by hand |
+| A menu entry | an unescaped `Exec=` line that silently refuses to launch |
+| Know the session | `DISPLAY` is set, so it must be X11 — except under XWayland it is not |
+| A tray icon | `pystray` works on X11, does not on Wayland, and needs PyGObject built |
+
+These are not interesting problems, but each one produces a bug report that
+takes an evening to understand. `desktop-lifecycle` is the version that was
+already debugged.
+
+## What you get
+
+| Module | What it does |
+|---|---|
+| `App` | ties everything below together in one object |
+| `Paths` | `~/.config`, `~/.local/state`, `~/.local/share`, `~/.cache` (and the Windows/macOS equivalents), created with `0700` |
+| `SingleInstance` | advisory `flock` / `msvcrt` lock, plus a signal file so a second launch can raise the existing window |
+| `Autostart` | XDG autostart entry, per-user Windows `Run` key, macOS LaunchAgent — user-scoped, reversible |
+| `install_menu_entry` | spec-correct `.desktop` file with properly escaped `Exec=` and atomic writes |
+| `session_type` | `x11`, `wayland`, `windows`, `macos`, `unknown` — from `XDG_SESSION_TYPE`, not from `DISPLAY` |
+| `tray.backend` | answers *which* tray backend will appear: `ayatana`, `appindicator`, `pystray` or `none` |
+| `setup_logging` | rotating log in the state directory, so users can find it |
+
+More detail, including package names per distribution:
+[docs/tray-on-wayland.md](docs/tray-on-wayland.md).
+
+## A complete tray application
+
+See [`examples/tk_demo.py`](examples/tk_demo.py) — about sixty lines, and it
+already handles the second launch, the tray, the hide-to-tray behaviour and
+the log file. Run it twice to see the hand-over.
+
+## What this is not
+
+- **Not a GUI toolkit.** It does not draw anything. Tkinter, PyQt, GTK and
+  wxPython all work with it.
+- **Not a tray replacement.** It detects the right backend and builds a small
+  menu, but it will not pretend a tray exists where the desktop has none.
+- **Not a daemon framework.** It tells you where the lock and log live; how
+  your process loops is your business.
+
+## Platform support
+
+| | Linux X11 | Linux Wayland | Windows | macOS |
+|---|---|---|---|---|
+| Paths | ✅ | ✅ | ✅ | ✅ |
+| Single instance | ✅ | ✅ | ✅ | ✅ |
+| Autostart | ✅ XDG | ✅ XDG | ✅ `HKCU\...\Run` | ✅ LaunchAgent |
+| Menu entry | ✅ | ✅ | — | — |
+| Session detection | ✅ | ✅ | ✅ | ✅ |
+| Tray | ✅ AppIndicator | ✅ AppIndicator | ✅ pystray | ✅ pystray |
+
+Tray icons on Wayland only exist through the AppIndicator / StatusNotifierItem
+protocol. If a desktop has neither, the answer is `none` and your app must
+keep working with a visible window — that is exactly the case this library
+forces you to handle.
+
+## Security notes
+
+- Everything is **user-scoped**. Nothing here asks for root, writes outside
+  your home directory, or edits system configuration.
+- Lock files are created `0600`; configuration directories `0700`;
+  desktop entries `0644`.
+- Every file is written **atomically** (temporary file + `rename`) so a
+  crash cannot leave half an autostart entry behind.
+- `Exec=` values are escaped the way the specification requires — `"`, `` ` ``,
+  `$`, `\` and `%` cannot break out of the quoted argument or become a field
+  code.
+- No `shell=True` anywhere, no `eval`, no dynamic imports from user input.
+- Application names are validated, so a name cannot escape its own directory.
+- No network access at runtime, no telemetry, no accounts.
+
+Found a problem? See [SECURITY.md](SECURITY.md).
+
+## Checking a machine
+
+```bash
+python -m desktop_lifecycle          # human-readable
+python -m desktop_lifecycle --json   # for bug reports
+```
+
+It prints the resolved directories, the session type and the tray backend
+without writing anything. Users can paste that into an issue instead of
+`ls -la ~`.
+
+## Compared to the alternatives
+
+| | desktop-lifecycle | pystray | manual code |
+|---|---|---|---|
+| XDG paths | ✅ | — | usually wrong |
+| Single-instance lock | ✅ | — | PID file |
+| Autostart | ✅ | — | per project |
+| Menu entry | ✅ | — | per project |
+| Wayland-aware tray detection | ✅ | partial | rare |
+| GUI toolkit required | no | no | no |
+| Dependencies | none | Pillow, PyGObject | — |
+
+`pystray` is good at what it does; this library answers the questions around
+it, including "should I even try".
+
+## Requirements
+
+Python 3.9+. No third-party packages.
+
+Install from the repository until the PyPI release is published.
+
+Optional tray fallback: `pip install desktop-lifecycle[tray]` (pystray + Pillow).
+On Debian/Ubuntu/Mint the native way is `gir1.2-ayatanaappindicator3-0.1`.
+
+## Development
+
+```bash
+git clone https://github.com/1emrecoskun/desktop-lifecycle
+cd desktop-lifecycle
+python -m unittest discover -s tests -v
+```
+
+79 tests, no hardware and no display required.
+
+## License
+
+MIT — see [LICENSE](LICENSE).
+
+Türkçe: [README.tr.md](README.tr.md)

desktop_lifecycle-0.1.0/README.md

@@ -0,0 +1,161 @@
+# desktop-lifecycle
+
+![test](https://github.com/1emrecoskun/desktop-lifecycle/actions/workflows/test.yml/badge.svg)
+
+**The boring parts of a small Python desktop app — before you write any UI.**
+
+Single-instance lock, XDG directories, autostart, menu entry, session
+detection, tray capability and rotating logs. No framework, no dependencies,
+no root.
+
+```bash
+pip install git+https://github.com/1emrecoskun/desktop-lifecycle
+```
+
+```python
+from desktop_lifecycle import App
+
+app = App("my-tool").ensure_dirs()
+app.setup_logging()
+
+if not app.acquire():        # a second copy was launched
+    raise SystemExit(0)      # it already asked the first one to show itself
+```
+
+That is the whole idea: the four things every small desktop app gets wrong,
+in one small library you can read in ten minutes.
+
+---
+
+## Why this exists
+
+Every Python utility that lives in the tray ends up re-implementing the same
+six things, usually differently and often incorrectly:
+
+| What you need | What usually happens instead |
+|---|---|
+| One process per session | a PID file that lies after a crash, because PIDs are reused |
+| Somewhere to write | settings in `~/.config`, logs in the checkout, a state file at `/.local/state` |
+| Start at login | three platform-specific files written by hand |
+| A menu entry | an unescaped `Exec=` line that silently refuses to launch |
+| Know the session | `DISPLAY` is set, so it must be X11 — except under XWayland it is not |
+| A tray icon | `pystray` works on X11, does not on Wayland, and needs PyGObject built |
+
+These are not interesting problems, but each one produces a bug report that
+takes an evening to understand. `desktop-lifecycle` is the version that was
+already debugged.
+
+## What you get
+
+| Module | What it does |
+|---|---|
+| `App` | ties everything below together in one object |
+| `Paths` | `~/.config`, `~/.local/state`, `~/.local/share`, `~/.cache` (and the Windows/macOS equivalents), created with `0700` |
+| `SingleInstance` | advisory `flock` / `msvcrt` lock, plus a signal file so a second launch can raise the existing window |
+| `Autostart` | XDG autostart entry, per-user Windows `Run` key, macOS LaunchAgent — user-scoped, reversible |
+| `install_menu_entry` | spec-correct `.desktop` file with properly escaped `Exec=` and atomic writes |
+| `session_type` | `x11`, `wayland`, `windows`, `macos`, `unknown` — from `XDG_SESSION_TYPE`, not from `DISPLAY` |
+| `tray.backend` | answers *which* tray backend will appear: `ayatana`, `appindicator`, `pystray` or `none` |
+| `setup_logging` | rotating log in the state directory, so users can find it |
+
+More detail, including package names per distribution:
+[docs/tray-on-wayland.md](docs/tray-on-wayland.md).
+
+## A complete tray application
+
+See [`examples/tk_demo.py`](examples/tk_demo.py) — about sixty lines, and it
+already handles the second launch, the tray, the hide-to-tray behaviour and
+the log file. Run it twice to see the hand-over.
+
+## What this is not
+
+- **Not a GUI toolkit.** It does not draw anything. Tkinter, PyQt, GTK and
+  wxPython all work with it.
+- **Not a tray replacement.** It detects the right backend and builds a small
+  menu, but it will not pretend a tray exists where the desktop has none.
+- **Not a daemon framework.** It tells you where the lock and log live; how
+  your process loops is your business.
+
+## Platform support
+
+| | Linux X11 | Linux Wayland | Windows | macOS |
+|---|---|---|---|---|
+| Paths | ✅ | ✅ | ✅ | ✅ |
+| Single instance | ✅ | ✅ | ✅ | ✅ |
+| Autostart | ✅ XDG | ✅ XDG | ✅ `HKCU\...\Run` | ✅ LaunchAgent |
+| Menu entry | ✅ | ✅ | — | — |
+| Session detection | ✅ | ✅ | ✅ | ✅ |
+| Tray | ✅ AppIndicator | ✅ AppIndicator | ✅ pystray | ✅ pystray |
+
+Tray icons on Wayland only exist through the AppIndicator / StatusNotifierItem
+protocol. If a desktop has neither, the answer is `none` and your app must
+keep working with a visible window — that is exactly the case this library
+forces you to handle.
+
+## Security notes
+
+- Everything is **user-scoped**. Nothing here asks for root, writes outside
+  your home directory, or edits system configuration.
+- Lock files are created `0600`; configuration directories `0700`;
+  desktop entries `0644`.
+- Every file is written **atomically** (temporary file + `rename`) so a
+  crash cannot leave half an autostart entry behind.
+- `Exec=` values are escaped the way the specification requires — `"`, `` ` ``,
+  `$`, `\` and `%` cannot break out of the quoted argument or become a field
+  code.
+- No `shell=True` anywhere, no `eval`, no dynamic imports from user input.
+- Application names are validated, so a name cannot escape its own directory.
+- No network access at runtime, no telemetry, no accounts.
+
+Found a problem? See [SECURITY.md](SECURITY.md).
+
+## Checking a machine
+
+```bash
+python -m desktop_lifecycle          # human-readable
+python -m desktop_lifecycle --json   # for bug reports
+```
+
+It prints the resolved directories, the session type and the tray backend
+without writing anything. Users can paste that into an issue instead of
+`ls -la ~`.
+
+## Compared to the alternatives
+
+| | desktop-lifecycle | pystray | manual code |
+|---|---|---|---|
+| XDG paths | ✅ | — | usually wrong |
+| Single-instance lock | ✅ | — | PID file |
+| Autostart | ✅ | — | per project |
+| Menu entry | ✅ | — | per project |
+| Wayland-aware tray detection | ✅ | partial | rare |
+| GUI toolkit required | no | no | no |
+| Dependencies | none | Pillow, PyGObject | — |
+
+`pystray` is good at what it does; this library answers the questions around
+it, including "should I even try".
+
+## Requirements
+
+Python 3.9+. No third-party packages.
+
+Install from the repository until the PyPI release is published.
+
+Optional tray fallback: `pip install desktop-lifecycle[tray]` (pystray + Pillow).
+On Debian/Ubuntu/Mint the native way is `gir1.2-ayatanaappindicator3-0.1`.
+
+## Development
+
+```bash
+git clone https://github.com/1emrecoskun/desktop-lifecycle
+cd desktop-lifecycle
+python -m unittest discover -s tests -v
+```
+
+79 tests, no hardware and no display required.
+
+## License
+
+MIT — see [LICENSE](LICENSE).
+
+Türkçe: [README.tr.md](README.tr.md)