Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
36 changes: 35 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ All notable changes to python-libei are recorded here. The format follows
[semantic versioning](https://semver.org/spec/v2.0.0.html) — with the usual
0.x caveat that the API may still change between minor versions.

## [Unreleased]
## [0.6.0] - 2026-09-22

### Added

Expand Down Expand Up @@ -53,6 +53,28 @@ All notable changes to python-libei are recorded here. The format follows
connection and lifecycle events, which have no getter and are read through
`event_type`.

- **CI, PyPI and license badges on the README.** The three things a reader
checks before installing anything -- whether the suite is green on `main`,
what the current release is, and under what license -- each took a click
through to somewhere else. The PyPI badge is also the one version statement
in the repository that reads what is actually *published*: the prose lines
that `tests/test_documentation_shape.py` guards are held to this checkout's
`libei.__version__`, which says nothing about what `pip install` would
fetch.

- **`.coderabbit.yaml`**, turning the Docstring Coverage pre-merge check off
and telling the reviewer not to ask for docstrings under `tests/`. That
check scores a whole diff against a single percentage threshold and its
schema offers no per-path option, so it cannot see that
`[tool.ruff.lint.per-file-ignores]` ignores `D100`-`D104` and `D107` under
`tests/*` deliberately -- matching both sibling repos, on the grounds that
each test is named for the behaviour it pins -- and so it objected on every
PR that adds tests, which is most of them. Coverage of `src/` is untouched:
ruff's pydocstyle rules enforce it in `scripts/pre-commit-test.sh`, and
those *are* path-aware. The same exclusion is repeated as a
`path_instructions` entry, which is where it can be path-scoped, so it
holds whether or not the check is ever switched back on.

### Changed

- **The docstring-completeness check now runs everywhere, and covers
Expand Down Expand Up @@ -88,6 +110,18 @@ All notable changes to python-libei are recorded here. The format follows
covered -- that `CreateSession` carries a `session_handle_token`, whose
absence crashes xdg-desktop-portal 1.22.1 outright.

- **39 docstrings on the dunders and private helpers that had none.** No check
asked for them: ruff's pydocstyle rules treat an underscore-prefixed name as
non-public, and this repo's config ignores `D105` outright -- so `__init__`,
`__eq__`, `__hash__`, `__repr__`, `__del__`, `__enter__`/`__exit__`,
`__init_subclass__`, `_cobject.CObject._get_or_create()`,
`LazyLibrary._ensure_loaded()` and both `_log_callback`s went undocumented
while being the definitions whose behaviour is least guessable from the
signature: pointer adoption and the per-hierarchy identity cache, a failed
`dlopen` cached rather than retried, a C function resolved on first call
rather than at bind time. `help()` and an IDE's hover show all of them, and
neither cares that a name starts with an underscore.

### Fixed

- **The README's link to the developer pages landed on a file listing.**
Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -129,7 +129,7 @@ and why, is in

## Status

Beta (`0.5.2`), published on [PyPI](https://pypi.org/project/python-libei/)
Beta (`0.6.0`), published on [PyPI](https://pypi.org/project/python-libei/)
since `0.1.0`, and **the API is not frozen** — expect renames before 1.0.

The injection path is exercised end to end against the real libraries by the
Expand Down
2 changes: 1 addition & 1 deletion docs/developers/verification.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# What has actually been verified

The package is beta (`0.5.2`) and the API is not frozen — expect renames
The package is beta (`0.6.0`) and the API is not frozen — expect renames
before 1.0. This page is what that qualifier covers, concretely: which paths
have been driven against real libraries, which have only ever been driven
against fakes, and which libei versions the whole thing has met.
Expand Down
2 changes: 1 addition & 1 deletion pyproject.toml
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"

[project]
name = "python-libei"
version = "0.5.2"
version = "0.6.0"
description = "Inject and receive input on Wayland from Python: ctypes bindings for libei, libeis and liboeffis"
readme = "README.md"
license = "MIT"
Expand Down
2 changes: 1 addition & 1 deletion src/libei/__init__.py
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,6 @@
Beta: the API is not frozen.
"""

__version__ = "0.5.2"
__version__ = "0.6.0"

__all__ = ["__version__"]
Loading