mirror of
https://github.com/kuhyx/diet-guard.git
synced 2026-11-11 13:47:38 +01:00
0.2.0's recovery loop scheduled the next tick after running it, so any exception out of a tick permanently ended all re-assertion of coverage, grab and VT for the rest of the lock -- silently, since Tk logs and swallows exceptions from `after` callbacks. 0.2.1 moves the reschedule into a `finally`. Also in 0.2.1: `holds_grab` no longer reads a grab held by one of our own transient children (a posted menu) as "the grab was lost" and takes it back. That one was a real, user-visible bug on screen-locker's gate windows; the same class of widget on a diet_guard gate would have behaved the same way. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
20 lines
538 B
Plaintext
20 lines
538 B
Plaintext
# Diet Guard — runtime + development dependencies
|
|
# Runtime: tkinter/json/hmac/fcntl (stdlib) plus gatelock and requests below.
|
|
bandit>=1.7.0
|
|
codespell>=2.2.0
|
|
coverage>=7.4.0
|
|
crdt-sync @ git+https://github.com/kuhyx/utils@crdt-sync-v0.1.0#subdirectory=crdt-sync
|
|
gatelock @ git+https://github.com/kuhyx/utils@gatelock-v0.2.1#subdirectory=gatelock
|
|
mcp>=1.9
|
|
mypy>=1.8.0
|
|
pre-commit>=3.6.0
|
|
pydantic>=2
|
|
pylint>=3.0.0
|
|
pytest>=8.0.0
|
|
pytest-cov>=4.1.0
|
|
pytest-randomly>=3.15.0
|
|
pytest-sugar>=1.0.0
|
|
pytest-xdist>=3.5.0
|
|
requests>=2.31.0
|
|
ruff>=0.8.0
|