build(deps): pynput needs python 3.13

[Game4Move78]

Internal changes to the Python threading library in 3.13 breaks pynput. Likely to be fixed when fixup/listener-thread-handle is merged, but at the moment Python 3.13 will throw this error:

2024-12-26 15:58:58 [ERROR]: Unhandled exception in listener callback  (pynput.mouse.Listener:233)
Traceback (most recent call last):
  File "/usr/lib/python3.13/site-packages/pynput/_util/__init__.py", line 229, in inner
    return f(self, *args, **kwargs)
  File "/usr/lib/python3.13/site-packages/pynput/_util/xorg.py", line 470, in _handler
    self._handle(self._display_stop, event)
    ~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: '_thread._ThreadHandle' object is not callable

Related to activitywatch#1122, pynput#614

---

Important

Update Python version constraint in pyproject.toml to exclude 3.13 due to pynput compatibility issue.

• Dependencies:
  • Update Python version constraint in pyproject.toml to ^3.8,<3.13 due to pynput compatibility issue with Python 3.13.
  • Reference issue pynput#614 for more details.

^{This description was created by for 1f5ac1f. It will automatically update as commits are pushed.}

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to 1f5ac1f in 21 seconds

More details

• Looked at 14 lines of code in 1 files
• Skipped 1 files when reviewing.
• Skipped posting 2 drafted comments based on config settings.

1. pyproject.toml:13

• Draft comment:
  The version constraint '^3.8,<3.13' correctly prevents Python 3.13 usage due to pynput issues. Ensure to update this once the upstream fix is merged.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  This comment is purely informative, explaining the reason behind a version constraint. It doesn't provide a specific code suggestion or ask for a test to be written. It also doesn't ask for confirmation of intention or any other action from the PR author.

2. pyproject.toml:13

• Draft comment:
  Restricting Python version to <3.13 is a good temporary workaround for the pynput issue. Consider adding a note linking the expected fix branch (e.g., fixup/listener-thread-handle) so it's easier to revert this when the issue is resolved.
• Reason this comment was not posted:
  Marked as duplicate.

Workflow ID: wflow_4wCZaK646s5X0HVY

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[TimeToBuildBob]

The fix exists in pynput's fixup/listener-thread-handle branch but hasn't been released yet (latest release is still v1.8.1). The upstream issue moses-palmer/pynput#614 is still open.

Workarounds for Python 3.13 users:

1. Pin pynput from the fix branch (in your local install):

   pip install git+https://github.com/moses-palmer/pynput.git@fixup/listener-thread-handle
   

2. Use Python 3.12 until pynput releases a fix

3. Use the prebuilt release bundles — they ship with their own Python runtime (typically 3.11/3.12), so this issue doesn't affect them

For the project: once pynput releases a version with the fix, we should update the dependency pin. Until then, adding python_requires = ">=3.8,<3.13" to pyproject.toml (as Ellipsis suggested) would at least give users a clear error instead of a confusing runtime crash.