terminator-dbus 0.1.0__tar.gz

terminator_dbus-0.1.0/AI_POLICY.md

@@ -0,0 +1,15 @@
+# AI Contribution Policy
+
+We accept AI-*assisted* contributions, both for code and documentation, with the following expectations:
+
+- AI-assisted contributions must disclaim their use of AI.
+- Contributors must fully understand the proposed changes and be able to explain why they are the correct approach.
+- Issues must be created before creating pull requests (unless there is already a relevant issue).
+- Issue and pull request templates must be followed.
+- Comments (including bodies) in issues and pull requests must be written by humans. If you use LLMs to translate from one language to another, please include your original comment and the translated one.
+- Git commits must be authored by humans, not AI/bot accounts or identities.
+- Git commit messages must be written by humans, in English. If you cannot write English, please state so in the pull request body and we will write the commit messages ourselves.
+
+Failure to comply with any of these requirements will result in issues or pull requests being closed immediately without comment. Repeated violations of this policy will result in a ban of the offending accounts/identities from contributing to this project and any related project from the same author/organization.
+
+We do not accept AI-generated content in community spaces we maintain or moderate, such as GitHub discussions or Matrix rooms.

terminator_dbus-0.1.0/CHANGELOG.md

@@ -0,0 +1,16 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
+and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).
+
+<!-- insertion marker -->
+## [0.1.0](https://github.com/pawamoy/terminator-dbus/releases/tag/0.1.0) - 2026-09-26
+
+<small>[Compare with first commit](https://github.com/pawamoy/terminator-dbus/compare/a9264b4e46ff2d7602c587aa3da07d0d73b3be89...0.1.0)</small>
+
+### Features
+
+- Implement Python interface to Terminator ([05d5b03](https://github.com/pawamoy/terminator-dbus/commit/05d5b0304b5e1283e5fede7b8732420a4c6f0218) by Timothée Mazzucotelli).
+- Generate project with copier-uv template ([a9264b4](https://github.com/pawamoy/terminator-dbus/commit/a9264b4e46ff2d7602c587aa3da07d0d73b3be89) by Timothée Mazzucotelli).

terminator_dbus-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,84 @@
+# 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 at dev@pawamoy.fr. 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
+

terminator_dbus-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,112 @@
+# Contributing
+
+Contributions are welcome, and they are greatly appreciated. Every little bit helps, and credit will always be given.
+
+**Please always create an issue before working on a new feature or a bug fix, so that we can discuss the implementation and make sure that your work will be merged.**
+
+## Environment setup
+
+Install [uv](https://github.com/astral-sh/uv) and [direnv](https://direnv.net/), fork and clone the repository, then:
+
+```bash
+cd terminator-dbus
+direnv allow
+make setup
+```
+
+You now have the dependencies installed.
+
+You can run the application with `make run terminator-dbus [ARGS...]`.
+
+Run `make help` to see all the available actions!
+
+## Tasks
+
+The entry-point to run commands and tasks is the `make` Python script, located in the `scripts` directory. Try running `make` to show the available commands and tasks. The *commands* do not need the Python dependencies to be installed, while the *tasks* do. The cross-platform tasks are written in Python, thanks to [duty](https://github.com/pawamoy/duty).
+
+If you work in VSCode, we provide [an action to configure VSCode](https://pawamoy.github.io/copier-uv/work/#vscode-setup) for the project.
+
+## Development
+
+As usual:
+
+1. create a new branch: `git switch -c feature-or-bugfix-name`
+1. edit the code and/or the documentation
+
+**Before committing:**
+
+1. run `make format` to auto-format the code
+1. run `make check` to check everything (fix any warning)
+1. run `make test` to run the tests (fix any issue)
+1. if you updated the documentation or the project dependencies:
+    1. run `make docs`
+    1. go to http://localhost:8000 and check that everything looks good
+1. follow our [commit message convention](#commit-message-convention)
+
+If you are unsure about how to fix or ignore a warning, just let the continuous integration fail, and we will help you during review.
+
+Don't bother updating the changelog, we will take care of this.
+
+## Commit message convention
+
+Commit messages must follow our convention based on the [Angular style](https://gist.github.com/stephenparish/9941e89d80e2bc58a153#format-of-the-commit-message) or the [Karma convention](https://karma-runner.github.io/4.0/dev/git-commit-msg.html):
+
+```
+<type>[(scope)]: Subject
+
+[Body]
+```
+
+**Subject and body must be valid Markdown.** Subject must have proper casing (uppercase for first letter if it makes sense), but no dot at the end, and no punctuation in general.
+
+Scope and body are optional. Type can be:
+
+- `build`: About packaging, building wheels, etc.
+- `chore`: About packaging or repo/files management.
+- `ci`: About Continuous Integration.
+- `deps`: Dependencies update.
+- `docs`: About documentation.
+- `feat`: New feature.
+- `fix`: Bug fix.
+- `perf`: About performance.
+- `refactor`: Changes that are not features or bug fixes.
+- `style`: A change in code style/format.
+- `tests`: About tests.
+
+If you write a body, please add trailers at the end (for example issues and PR references, or co-authors), without relying on GitHub's flavored Markdown:
+
+```
+Body.
+
+Issue #10: https://github.com/namespace/project/issues/10
+Related to PR namespace/other-project#15: https://github.com/namespace/other-project/pull/15
+```
+
+These "trailers" must appear at the end of the body, without any blank lines between them. The trailer title can contain any character except colons `:`. We expect a full URI for each trailer, not just GitHub autolinks (for example, full GitHub URLs for commits and issues, not the hash or the #issue-number).
+
+We do not enforce a line length on commit messages summary and body, but please avoid very long summaries, and very long lines in the body, unless they are part of code blocks that must not be wrapped.
+
+## Pull requests guidelines
+
+Link to any related issue in the Pull Request message.
+
+During the review, we recommend using fixups:
+
+```bash
+# SHA is the SHA of the commit you want to fix
+git commit --fixup=SHA
+```
+
+Once all the changes are approved, you can squash your commits:
+
+```bash
+git rebase -i --autosquash main
+```
+
+And force-push:
+
+```bash
+git push -f
+```
+
+If this seems all too complicated, you can push or force-push each new commit, and we will squash them ourselves if needed, before merging.

terminator_dbus-0.1.0/LICENSE

@@ -0,0 +1,15 @@
+ISC License
+
+Copyright (c) 2026, Timothée Mazzucotelli and contributors
+
+Permission to use, copy, modify, and/or distribute this software for any
+purpose with or without fee is hereby granted, provided that the above
+copyright notice and this permission notice appear in all copies.
+
+THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
+WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
+ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
+OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

terminator_dbus-0.1.0/PKG-INFO

@@ -0,0 +1,159 @@
+Metadata-Version: 2.4
+Name: terminator-dbus
+Version: 0.1.0
+Summary: Python library to interact with Terminator through D-Bus.
+Author-Email: =?utf-8?q?Timoth=C3=A9e_Mazzucotelli?= <dev@pawamoy.fr>
+License-Expression: ISC
+License-File: LICENSE
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+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: Programming Language :: Python :: 3.14
+Classifier: Topic :: Documentation
+Classifier: Topic :: Software Development
+Classifier: Topic :: Utilities
+Classifier: Typing :: Typed
+Project-URL: Homepage, https://pawamoy.github.io/terminator-dbus
+Project-URL: Documentation, https://pawamoy.github.io/terminator-dbus
+Project-URL: Changelog, https://pawamoy.github.io/terminator-dbus/changelog
+Project-URL: Repository, https://github.com/pawamoy/terminator-dbus
+Project-URL: Issues, https://github.com/pawamoy/terminator-dbus/issues
+Project-URL: Discussions, https://github.com/pawamoy/terminator-dbus/discussions
+Project-URL: Gitter, https://gitter.im/terminator-dbus/community
+Project-URL: Funding, https://github.com/sponsors/pawamoy
+Requires-Python: >=3.10
+Requires-Dist: dbus-python>=1.3.2
+Description-Content-Type: text/markdown
+
+# Terminator D-Bus
+
+
+[![ci](https://github.com/pawamoy/terminator-dbus/workflows/ci/badge.svg)](https://github.com/pawamoy/terminator-dbus/actions?query=workflow%3Aci)
+[![documentation](https://img.shields.io/badge/docs-zensical-FF9100.svg?style=flat)](https://pawamoy.github.io/terminator-dbus/)
+[![pypi version](https://img.shields.io/pypi/v/terminator-dbus.svg)](https://pypi.org/project/terminator-dbus/)
+[![gitter](https://img.shields.io/badge/matrix-chat-4DB798.svg?style=flat)](https://app.gitter.im/#/room/#terminator-dbus:gitter.im)
+
+
+Python library to interact with Terminator through D-Bus.
+
+
+## Installation
+
+
+```bash
+pip install terminator-dbus
+```
+
+
+With [`uv`](https://docs.astral.sh/uv/):
+
+
+```bash
+uv tool install terminator-dbus
+```
+
+
+`dbus-python` needs the D-Bus development files when no system package or wheel is available.
+
+
+## Usage
+
+
+Create one client and reuse it for all calls:
+
+
+```python
+from terminator_dbus import Terminator
+
+terminator = Terminator()
+terminal = terminator.get_focused_terminal()
+
+if terminal is not None:
+    new_terminal = terminator.vsplit(
+        terminal,
+        {"execute": "htop", "title": "Processes"},
+    )
+    terminator.switch_profile(new_terminal, {"profile": "work"})
+```
+
+
+The client uses the current X11 or Wayland display by default. Pass `display` if the current environment does not identify the correct display:
+
+
+```python
+terminator = Terminator(display=":1")
+```
+
+
+Pass `bus_name` when you already know the complete D-Bus service name:
+
+
+```python
+terminator = Terminator(bus_name="net.tenshu.Terminator2...")
+```
+
+
+`dbus.DBusException` reports connection and remote method failures. Terminator itself returns strings that start with `ERROR:` for some tab and split failures.
+
+
+## D-Bus interface
+
+
+This package follows the interface in [Terminator 2.1.6 `ipc.py`](https://github.com/gnome-terminator/terminator/blob/v2.1.6/terminatorlib/ipc.py).
+
+
+- Base service and interface name: `net.tenshu.Terminator2`
+- Object path: `/net/tenshu/Terminator2`
+- Display-specific name: the base name followed by the MD5 digest of the GDK display name
+
+
+Terminator removes the screen suffix before it creates the digest. Thus, `:0` and `:0.0` use the same service name.
+
+
+The `Terminator` class exposes every method in the service:
+
+
+| Python method | D-Bus input | Purpose | Result |
+| --- | --- | --- | --- |
+| `new_window_cmdline(options)` | `a{ss}` | Create a window from serialized command-line options. | `None` |
+| `new_tab_cmdline(options)` | `a{ss}` | Create a tab from serialized command-line options. | `None` |
+| `toggle_visibility_cmdline(options)` | `a{ss}` | Toggle all window visibility. | `None` |
+| `unhide_cmdline(options)` | `a{ss}` | Show all hidden windows. | `None` |
+| `new_window()` | empty | Create a window. | New terminal UUID or error string |
+| `new_tab(uuid)` | `v` | Create a tab in a terminal's window. | New terminal UUID or error string |
+| `reload_configuration()` | empty | Reload configuration for all terminals. | `None` |
+| `bg_img_all(options)` | `v` | Set all background images from the `file` option. | `None` |
+| `bg_img(uuid, options)` | `vv` | Set one background image from the `file` option. | `None` |
+| `hsplit(uuid, options=None)` | `vv` | Split a terminal horizontally. | New terminal UUID or error string |
+| `vsplit(uuid, options=None)` | `vv` | Split a terminal vertically. | New terminal UUID or error string |
+| `get_terminals()` | empty | Get all terminal UUIDs. | `list[str]` |
+| `get_focused_terminal()` | empty | Get the focused terminal UUID. | `str \| None` |
+| `get_window(uuid)` | `v` | Get a terminal's window UUID. | `str` |
+| `get_window_title(uuid)` | `v` | Get a terminal's window title. | `str` |
+| `get_tab(uuid)` | `v` | Get a terminal's tab identifier. | `str \| None` |
+| `get_tab_title(uuid)` | `v` | Get a terminal's tab title. | `str \| None` |
+| `set_tab_title(uuid, options)` | `vv` | Set a tab title from the `tab-title` option. | `None` |
+| `switch_profile(uuid, options)` | `vv` | Set one profile from the `profile` option. | `None` |
+| `switch_profile_all(options)` | `v` | Set all profiles from the `profile` option. | `None` |
+
+
+Terminator does not assign identifiers to tabs. Its `get_tab` method returns an empty string for a terminal in a notebook.
+
+
+The four `*_cmdline` methods require string-to-string dictionaries. The window and tab creation methods require the complete option mapping from Terminator's command-line parser.
+
+
+Terminator does not declare D-Bus output signatures. `dbus-python` infers each output signature from the value returned by the service method.
+
+
+## Sponsors
+
+
+<!-- sponsors-start -->
+<!-- sponsors-end -->

terminator_dbus-0.1.0/README.md

@@ -0,0 +1,126 @@
+# Terminator D-Bus
+
+
+[![ci](https://github.com/pawamoy/terminator-dbus/workflows/ci/badge.svg)](https://github.com/pawamoy/terminator-dbus/actions?query=workflow%3Aci)
+[![documentation](https://img.shields.io/badge/docs-zensical-FF9100.svg?style=flat)](https://pawamoy.github.io/terminator-dbus/)
+[![pypi version](https://img.shields.io/pypi/v/terminator-dbus.svg)](https://pypi.org/project/terminator-dbus/)
+[![gitter](https://img.shields.io/badge/matrix-chat-4DB798.svg?style=flat)](https://app.gitter.im/#/room/#terminator-dbus:gitter.im)
+
+
+Python library to interact with Terminator through D-Bus.
+
+
+## Installation
+
+
+```bash
+pip install terminator-dbus
+```
+
+
+With [`uv`](https://docs.astral.sh/uv/):
+
+
+```bash
+uv tool install terminator-dbus
+```
+
+
+`dbus-python` needs the D-Bus development files when no system package or wheel is available.
+
+
+## Usage
+
+
+Create one client and reuse it for all calls:
+
+
+```python
+from terminator_dbus import Terminator
+
+terminator = Terminator()
+terminal = terminator.get_focused_terminal()
+
+if terminal is not None:
+    new_terminal = terminator.vsplit(
+        terminal,
+        {"execute": "htop", "title": "Processes"},
+    )
+    terminator.switch_profile(new_terminal, {"profile": "work"})
+```
+
+
+The client uses the current X11 or Wayland display by default. Pass `display` if the current environment does not identify the correct display:
+
+
+```python
+terminator = Terminator(display=":1")
+```
+
+
+Pass `bus_name` when you already know the complete D-Bus service name:
+
+
+```python
+terminator = Terminator(bus_name="net.tenshu.Terminator2...")
+```
+
+
+`dbus.DBusException` reports connection and remote method failures. Terminator itself returns strings that start with `ERROR:` for some tab and split failures.
+
+
+## D-Bus interface
+
+
+This package follows the interface in [Terminator 2.1.6 `ipc.py`](https://github.com/gnome-terminator/terminator/blob/v2.1.6/terminatorlib/ipc.py).
+
+
+- Base service and interface name: `net.tenshu.Terminator2`
+- Object path: `/net/tenshu/Terminator2`
+- Display-specific name: the base name followed by the MD5 digest of the GDK display name
+
+
+Terminator removes the screen suffix before it creates the digest. Thus, `:0` and `:0.0` use the same service name.
+
+
+The `Terminator` class exposes every method in the service:
+
+
+| Python method | D-Bus input | Purpose | Result |
+| --- | --- | --- | --- |
+| `new_window_cmdline(options)` | `a{ss}` | Create a window from serialized command-line options. | `None` |
+| `new_tab_cmdline(options)` | `a{ss}` | Create a tab from serialized command-line options. | `None` |
+| `toggle_visibility_cmdline(options)` | `a{ss}` | Toggle all window visibility. | `None` |
+| `unhide_cmdline(options)` | `a{ss}` | Show all hidden windows. | `None` |
+| `new_window()` | empty | Create a window. | New terminal UUID or error string |
+| `new_tab(uuid)` | `v` | Create a tab in a terminal's window. | New terminal UUID or error string |
+| `reload_configuration()` | empty | Reload configuration for all terminals. | `None` |
+| `bg_img_all(options)` | `v` | Set all background images from the `file` option. | `None` |
+| `bg_img(uuid, options)` | `vv` | Set one background image from the `file` option. | `None` |
+| `hsplit(uuid, options=None)` | `vv` | Split a terminal horizontally. | New terminal UUID or error string |
+| `vsplit(uuid, options=None)` | `vv` | Split a terminal vertically. | New terminal UUID or error string |
+| `get_terminals()` | empty | Get all terminal UUIDs. | `list[str]` |
+| `get_focused_terminal()` | empty | Get the focused terminal UUID. | `str \| None` |
+| `get_window(uuid)` | `v` | Get a terminal's window UUID. | `str` |
+| `get_window_title(uuid)` | `v` | Get a terminal's window title. | `str` |
+| `get_tab(uuid)` | `v` | Get a terminal's tab identifier. | `str \| None` |
+| `get_tab_title(uuid)` | `v` | Get a terminal's tab title. | `str \| None` |
+| `set_tab_title(uuid, options)` | `vv` | Set a tab title from the `tab-title` option. | `None` |
+| `switch_profile(uuid, options)` | `vv` | Set one profile from the `profile` option. | `None` |
+| `switch_profile_all(options)` | `v` | Set all profiles from the `profile` option. | `None` |
+
+
+Terminator does not assign identifiers to tabs. Its `get_tab` method returns an empty string for a terminal in a notebook.
+
+
+The four `*_cmdline` methods require string-to-string dictionaries. The window and tab creation methods require the complete option mapping from Terminator's command-line parser.
+
+
+Terminator does not declare D-Bus output signatures. `dbus-python` infers each output signature from the value returned by the service method.
+
+
+## Sponsors
+
+
+<!-- sponsors-start -->
+<!-- sponsors-end -->

terminator_dbus-0.1.0/config/coverage.ini

@@ -0,0 +1,25 @@
+[coverage:run]
+branch = true
+parallel = true
+source =
+  src/
+  tests/
+
+[coverage:paths]
+equivalent =
+  src/
+  .venv/lib/*/site-packages/
+  .venvs/*/lib/*/site-packages/
+
+[coverage:report]
+precision = 2
+omit =
+  src/*/__init__.py
+  src/*/__main__.py
+  tests/__init__.py
+exclude_lines =
+  pragma: no cover
+  if TYPE_CHECKING
+
+[coverage:json]
+output = htmlcov/coverage.json

terminator_dbus-0.1.0/config/git-changelog.toml

@@ -0,0 +1,9 @@
+bump = "auto"
+convention = "angular"
+in-place = true
+output = "CHANGELOG.md"
+parse-refs = false
+parse-trailers = true
+sections = ["build", "deps", "feat", "fix", "perf", "refactor"]
+template = "keepachangelog"
+versioning = "pep440"

terminator_dbus-0.1.0/config/pytest.ini

@@ -0,0 +1,16 @@
+[pytest]
+python_files =
+  test_*.py
+addopts =
+  --cov
+  --cov-config config/coverage.ini
+testpaths =
+  tests
+
+# action:message_regex:warning_class:module_regex:line
+filterwarnings =
+  error
+  default::EncodingWarning
+  error::EncodingWarning:terminator_dbus
+  # TODO: remove once pytest-xdist 4 is released
+  ignore:.*rsyncdir:DeprecationWarning:xdist

terminator_dbus-0.1.0/config/ruff.toml

@@ -0,0 +1,76 @@
+target-version = "py310"
+line-length = 120
+output-format = "concise"
+
+[lint]
+exclude = [
+    "tests/fixtures/*.py",
+]
+select = ["ALL"]
+ignore = [
+    "A001",  # Variable is shadowing a Python builtin
+    "ANN204",  # Missing return type annotation for special method __str__
+    "ANN401",  # Dynamically typed expressions (typing.Any) are disallowed
+    "ARG005",  # Unused lambda argument
+    "C901",  # Too complex
+    "D105",  # Missing docstring in magic method
+    "D417",  # Missing argument description in the docstring
+    "E501",  # Line too long
+    "EM101",  # String literal when raising exception
+    "EM102",  # f-string when raising exception
+    "ERA001",  # Commented out code
+    "FIX",  # TODO, FIXME, etc.
+    "G004",  # Logging statement uses f-string
+    "PLR0911",  # Too many return statements
+    "PLR0912",  # Too many branches
+    "PLR0913",  # Too many arguments to function call
+    "PLR0915",  # Too many statements
+    "SLF001", # Private member accessed
+    "TD002",  # Missing author in TODO
+    "TD003",  # Missing issue link for TODO
+    "TRY003",  # Avoid specifying long messages outside the exception class
+]
+
+[lint.per-file-ignores]
+"src/**/cli.py" = [
+    "T201",  # Print statement
+]
+"src/*/debug.py" = [
+    "T201",  # Print statement
+]
+"!src/*/*.py" = [
+    "D100",  # Missing docstring in public module
+]
+"!src/**.py" = [
+    "D101",  # Missing docstring in public class
+    "D103",  # Missing docstring in public function
+]
+"scripts/*.py" = [
+    "INP001",  # File is part of an implicit namespace package
+    "T201",  # Print statement
+]
+"tests/**.py" = [
+    "ARG005",  # Unused lambda argument
+    "FBT001",  # Boolean positional arg in function definition
+    "PLR2004",  # Magic value used in comparison
+    "S101",  # Use of assert detected
+]
+
+[lint.flake8-quotes]
+docstring-quotes = "double"
+
+[lint.flake8-tidy-imports]
+ban-relative-imports = "all"
+
+[lint.isort]
+known-first-party = ["terminator_dbus"]
+
+[lint.pydocstyle]
+convention = "google"
+
+[format]
+exclude = [
+    "tests/fixtures/*.py",
+]
+docstring-code-format = true
+docstring-code-line-length = 80

terminator_dbus-0.1.0/config/ty.toml

@@ -0,0 +1,6 @@
+[src]
+exclude = ["tests/fixtures"]
+
+[terminal]
+error-on-warning = true
+output-format = "concise"