python-libei 0.7.0__tar.gz → 0.8.1__tar.gz

{python_libei-0.7.0 → python_libei-0.8.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: python-libei
-Version: 0.7.0
+Version: 0.8.1
 Summary: Inject, receive and capture input on Wayland from Python: ctypes bindings for libei, libeis and liboeffis, plus the RemoteDesktop and InputCapture portals
 Author: Dennis K. Paulsen
 License-Expression: MIT
@@ -175,7 +175,7 @@ and why, is in
 
 ## Status
 
-Beta (`0.7.0`), published on [PyPI](https://pypi.org/project/python-libei/)
+Beta (`0.8.1`), 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
@@ -228,17 +228,27 @@ Exactly what was run, when, and against which versions:
 
   | Needs | For |
   | --- | --- |
-  | 1.1 | `Region.mapping_id`, `Region.convert_point()`, `Device.region_at()` |
+  | 1.1 | `Region.mapping_id`, `Device.region_at()` |
   | 1.4 | ping/pong round trips (`Context.new_ping()`), `Context.disconnect()`, touch cancellation (`Touch.cancel()`) |
   | 1.5 | `eis.Client.pid` |
   | 1.6 | `Device.text_utf8()` / `text_keysym()` and TEXT events, `Seat.request_device()`, `Eis.set_flag()` |
 
   Nothing is resolved until it is called, so a build without one of these
   costs you only that call — it raises `LibraryNotFoundError` naming the
-  missing symbol, while the rest of the package keeps working. The one
-  exception is `Event.touch_up_event`, which degrades instead of raising:
-  on libei older than 1.4 it reports `is_cancel=False`, since a library
-  with no notion of cancellation genuinely never sends one.
+  missing symbol, while the rest of the package keeps working. Two
+  accessors degrade instead of raising, because every supported version
+  exports the symbol and only the answer changed — so there is nothing to
+  resolve and nothing to report:
+
+  - `Event.touch_up_event` reports `is_cancel=False` on libei older than
+    1.4, since a library with no notion of cancellation genuinely never
+    sends one.
+  - `eis.Event.emulating_sequence` reads 0 on libei older than 1.6
+    whatever the client sent: libeis queued the start_emulating event
+    without ever copying the sequence into it, until 1.6.0 added the
+    missing assignment. A 0 on an older build is indistinguishable from a
+    client that really sent 0. The client-side
+    `ei.Event.emulating_sequence` is unaffected.
 
   These versions were established by building libei 1.2.1 and diffing its
   exported symbols against every binding here, not by reading `@since`

{python_libei-0.7.0 → python_libei-0.8.1}/README.md

@@ -135,7 +135,7 @@ and why, is in
 
 ## Status
 
-Beta (`0.7.0`), published on [PyPI](https://pypi.org/project/python-libei/)
+Beta (`0.8.1`), 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
@@ -188,17 +188,27 @@ Exactly what was run, when, and against which versions:
 
   | Needs | For |
   | --- | --- |
-  | 1.1 | `Region.mapping_id`, `Region.convert_point()`, `Device.region_at()` |
+  | 1.1 | `Region.mapping_id`, `Device.region_at()` |
   | 1.4 | ping/pong round trips (`Context.new_ping()`), `Context.disconnect()`, touch cancellation (`Touch.cancel()`) |
   | 1.5 | `eis.Client.pid` |
   | 1.6 | `Device.text_utf8()` / `text_keysym()` and TEXT events, `Seat.request_device()`, `Eis.set_flag()` |
 
   Nothing is resolved until it is called, so a build without one of these
   costs you only that call — it raises `LibraryNotFoundError` naming the
-  missing symbol, while the rest of the package keeps working. The one
-  exception is `Event.touch_up_event`, which degrades instead of raising:
-  on libei older than 1.4 it reports `is_cancel=False`, since a library
-  with no notion of cancellation genuinely never sends one.
+  missing symbol, while the rest of the package keeps working. Two
+  accessors degrade instead of raising, because every supported version
+  exports the symbol and only the answer changed — so there is nothing to
+  resolve and nothing to report:
+
+  - `Event.touch_up_event` reports `is_cancel=False` on libei older than
+    1.4, since a library with no notion of cancellation genuinely never
+    sends one.
+  - `eis.Event.emulating_sequence` reads 0 on libei older than 1.6
+    whatever the client sent: libeis queued the start_emulating event
+    without ever copying the sequence into it, until 1.6.0 added the
+    missing assignment. A 0 on an older build is indistinguishable from a
+    client that really sent 0. The client-side
+    `ei.Event.emulating_sequence` is unaffected.
 
   These versions were established by building libei 1.2.1 and diffing its
   exported symbols against every binding here, not by reading `@since`

{python_libei-0.7.0 → python_libei-0.8.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "python-libei"
-version = "0.7.0"
+version = "0.8.1"
 description = "Inject, receive and capture input on Wayland from Python: ctypes bindings for libei, libeis and liboeffis, plus the RemoteDesktop and InputCapture portals"
 readme = "README.md"
 license = "MIT"

{python_libei-0.7.0 → python_libei-0.8.1}/src/libei/__init__.py

@@ -31,6 +31,6 @@ the full breakdown, including which features need which libei version.
 Beta: the API is not frozen.
 """
 
-__version__ = "0.7.0"
+__version__ = "0.8.1"
 
 __all__ = ["__version__"]

{python_libei-0.7.0 → python_libei-0.8.1}/src/libei/_capi/libei.py

@@ -219,7 +219,13 @@ region_get_mapping_id = lib.function(  # libei 1.1+
     "ei_region_get_mapping_id", (c_void_p,), c_char_p
 )
 # x and y are in/out parameters, overwritten only when the point is inside.
-region_convert_point = lib.function(  # libei 1.1+
+# No version marker: this one is in libei 1.0.0's own public header and
+# implemented there, so every libei at or above the declared floor exports
+# it. It carried `# libei 1.1+` alongside its genuine 1.1 neighbours
+# `ei_region_get_mapping_id` and `ei_device_region_at`, and the weekly
+# floor job caught it -- building 1.0.0 from source found the symbol
+# present where the marker promised it would be absent.
+region_convert_point = lib.function(
     "ei_region_convert_point",
     (c_void_p, POINTER(c_double), POINTER(c_double)),
     c_bool,

{python_libei-0.7.0 → python_libei-0.8.1}/src/libei/ei.py

@@ -372,8 +372,7 @@ class Region(CObject):
 
         Returns the point with the region's offset subtracted, or ``None``
         if it falls outside the region -- which is also how you test
-        membership without a second :meth:`contains` call. Requires
-        libei 1.1.
+        membership without a second :meth:`contains` call.
         """
         # x/y are in-out parameters: libei overwrites them only when the
         # point is inside, so the return value has to gate reading them.
@@ -1127,7 +1126,10 @@ class Context(CObject):
             pointer = _capi.libei.get_event(self)
             if not pointer:
                 break
-            event = Event.wrap(pointer)
+            # adopt(), not wrap(): ei_get_event() transfers ownership of
+            # the returned reference to the caller, and the unref in
+            # release() below is the one that balances it.
+            event = Event.adopt(pointer)
             assert event is not None
             # try/finally, not a bare call after yield: breaking out of a
             # `for event in ctx.events:` loop (or an exception propagating

{python_libei-0.7.0 → python_libei-0.8.1}/src/libei/eis.py

@@ -944,7 +944,18 @@ class Event(CObject):
 
     @property
     def emulating_sequence(self) -> int:
-        """Sequence number of the start_emulating transaction."""
+        """Sequence number of the start_emulating transaction.
+
+        Reads 0 on libei older than 1.6, whatever the client sent. libeis
+        queued the event without ever copying the sequence into it, so the
+        getter returned a zeroed struct field; upstream added the missing
+        assignment in libei 1.6.0. Every version from this package's 1.0.0
+        floor up exports the symbol, so there is nothing to raise and no
+        way to tell an old library apart from a client that genuinely sent
+        0 -- treat a 0 here as "unknown" unless you know both ends are on
+        1.6. :attr:`libei.ei.Event.emulating_sequence`, the receiver side
+        of the same transaction, is unaffected: libei has always stored it.
+        """
         self._require("emulating_sequence", EventType.DEVICE_START_EMULATING)
         return _capi.libeis.event_emulating_get_sequence(self)
 
@@ -1150,7 +1161,10 @@ class Eis(CObject):
             pointer = _capi.libeis.get_event(self)
             if not pointer:
                 break
-            event = Event.wrap(pointer)
+            # adopt(), not wrap(): eis_get_event() transfers ownership of
+            # the returned reference to the caller, and the unref in
+            # release() below is the one that balances it.
+            event = Event.adopt(pointer)
             assert event is not None
             # See ei.Context.events: try/finally so release() still runs
             # if the caller breaks out of the loop (GeneratorExit at the
@@ -1168,9 +1182,11 @@ class Eis(CObject):
     def set_flag(self, flag: Flag) -> None:
         """Change this context's protocol behavior. Requires libei 1.6.
 
-        Must be called before the backend is set up, so in practice
-        before :meth:`create_for_fd` / :meth:`create_for_socket` -- which
-        also means this is only reachable on a context built by hand.
+        Must be called before the backend is set up, so the supported
+        way to use it is the ``flags`` parameter of
+        :meth:`create_for_fd` / :meth:`create_for_socket`, which apply
+        each flag at exactly that point; calling it directly only works
+        on a context built by hand, before its backend is set up.
         Takes one flag, never a bitmask; call it again for another.
         """
         result = _capi.libeis.set_flag(self, flag)