python-libei 0.4.0__tar.gz → 0.4.1__tar.gz

{python_libei-0.4.0/src/python_libei.egg-info → python_libei-0.4.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: python-libei
-Version: 0.4.0
+Version: 0.4.1
 Summary: Inject and receive input on Wayland from Python: ctypes bindings for libei, libeis and liboeffis
 Author: Dennis K. Paulsen
 License-Expression: MIT
@@ -136,7 +136,7 @@ pointer.
 
 ## Status
 
-Beta (`0.4.0`), published on [PyPI](https://pypi.org/project/python-libei/)
+Beta (`0.4.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. What
 that qualifier covers, concretely:
 

{python_libei-0.4.0 → python_libei-0.4.1}/README.md

@@ -100,7 +100,7 @@ pointer.
 
 ## Status
 
-Beta (`0.4.0`), published on [PyPI](https://pypi.org/project/python-libei/)
+Beta (`0.4.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. What
 that qualifier covers, concretely:
 

{python_libei-0.4.0 → python_libei-0.4.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "python-libei"
-version = "0.4.0"
+version = "0.4.1"
 description = "Inject and receive input on Wayland from Python: ctypes bindings for libei, libeis and liboeffis"
 readme = "README.md"
 license = "MIT"
@@ -101,6 +101,24 @@ strict = true
 # Every property in ei.py/eis.py/oeffis.py re-types a raw C call's result,
 # so this fires everywhere in the wrapper layer for no actionable reason.
 warn_return_any = false
+# mypy defaults this to true and imports sqlite3 unconditionally to honor
+# it -- a crash, not a fallback, on a Python built without it. Confirmed on
+# FreeBSD 15 (GhostBSD's python3.11 port has no _sqlite3), which is the
+# only place this has come up, but the flag is harmless anywhere the
+# module is present: the cache just becomes one file per module instead of
+# one sqlite db.
+sqlite_cache = false
+# Without this, results depend on the OS mypy happens to run on: it
+# defaults to `sys.platform` of the invoking interpreter, and typeshed
+# gates os.memfd_create to sys.platform == "linux" even though FreeBSD has
+# implemented the syscall for years -- confirmed working at runtime on
+# FreeBSD 15 (hasattr(os, "memfd_create") is True, round-trips real data),
+# so the three call sites in tests/test_ei_objects.py,
+# tests/test_eis_objects.py and tests/test_integration_extras.py are
+# correct and this was a typeshed staleness false-positive, not a bug.
+# Pinning to "linux" makes CI and every contributor's machine check the
+# same thing regardless of what they develop on.
+platform = "linux"
 
 # PyGObject is an optional extra (see [project.optional-dependencies].portal),
 # so `gi` may or may not be importable where mypy runs. Without this, the two

{python_libei-0.4.0 → python_libei-0.4.1}/src/libei/__init__.py

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

{python_libei-0.4.0 → python_libei-0.4.1/src/python_libei.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: python-libei
-Version: 0.4.0
+Version: 0.4.1
 Summary: Inject and receive input on Wayland from Python: ctypes bindings for libei, libeis and liboeffis
 Author: Dennis K. Paulsen
 License-Expression: MIT
@@ -136,7 +136,7 @@ pointer.
 
 ## Status
 
-Beta (`0.4.0`), published on [PyPI](https://pypi.org/project/python-libei/)
+Beta (`0.4.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. What
 that qualifier covers, concretely:
 

{python_libei-0.4.0 → python_libei-0.4.1}/tests/test_loader.py

@@ -1,18 +1,27 @@
 """Unit tests for the deferred-loading mechanism itself.
 
-Uses libc.so.6 as a stand-in shared library (present on every Linux system)
-so these run without libei installed at all -- they're testing the loader,
-not libei.
+Uses the C library as a stand-in shared library (present on every POSIX
+system) so these run without libei installed at all -- they're testing the
+loader, not libei. The soname isn't portable -- glibc is libc.so.6, FreeBSD
+is libc.so.7 -- so it's resolved with ctypes.util.find_library rather than
+hardcoded; a hardcoded libc.so.6 here once made every test below fail on
+FreeBSD, not because LazyLibrary was wrong but because the soname it was
+asked to load doesn't exist there.
 """
 
 from __future__ import annotations
 
-from ctypes import c_char_p, c_int
+from ctypes import c_char_p, c_int, util
 
 import pytest
 
 from libei._capi.loader import LazyLibrary, LibraryNotFoundError
 
+_found_libc = util.find_library("c")
+if _found_libc is None:
+    raise RuntimeError("no C library found -- these tests need one to stand in")
+_LIBC: str = _found_libc
+
 
 def test_import_does_not_touch_the_filesystem() -> None:
     # Constructing a LazyLibrary and declaring functions on it must not
@@ -35,12 +44,12 @@ def test_missing_library_is_not_available() -> None:
 
 
 def test_real_library_is_available() -> None:
-    lib = LazyLibrary("libc.so.6")
+    lib = LazyLibrary(_LIBC)
     assert lib.is_available() is True
 
 
 def test_real_function_call_round_trips() -> None:
-    lib = LazyLibrary("libc.so.6")
+    lib = LazyLibrary(_LIBC)
     abs_ = lib.function("abs", (c_int,), c_int)
     assert abs_(-7) == 7
     assert abs_(7) == 7
@@ -59,14 +68,14 @@ def test_function_result_is_cached_across_calls() -> None:
 
 
 def test_missing_symbol_raises_library_not_found_error() -> None:
-    lib = LazyLibrary("libc.so.6")
+    lib = LazyLibrary(_LIBC)
     nonexistent = lib.function("this_symbol_does_not_exist_in_libc", (c_char_p,), c_int)
     with pytest.raises(LibraryNotFoundError, match="does not export"):
         nonexistent(b"x")
 
 
 def test_two_lazy_libraries_are_independent() -> None:
-    good = LazyLibrary("libc.so.6")
+    good = LazyLibrary(_LIBC)
     bad = LazyLibrary("this-library-definitely-does-not-exist.so.999")
     assert good.is_available() is True
     assert bad.is_available() is False