python-libei 0.1.0__py3-none-any.whl → 0.2.0__py3-none-any.whl

libei/__init__.py

@@ -26,6 +26,6 @@ the full breakdown, including which features need which libei version.
 Alpha: the API is not frozen.
 """
 
-__version__ = "0.1.0"
+__version__ = "0.2.0"
 
 __all__ = ["__version__"]

{python_libei-0.1.0.dist-info → python_libei-0.2.0.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: python-libei
-Version: 0.1.0
+Version: 0.2.0
 Summary: Inject and receive input on Wayland from Python: ctypes bindings for libei, libeis and liboeffis
 Author: Dennis K. Paulsen
 License-Expression: MIT
@@ -133,8 +133,9 @@ pointer.
 
 ## Status
 
-Alpha (`0.1.0`), not yet on PyPI, and the API is not frozen — expect
-renames before 1.0. What that qualifier covers, concretely:
+Alpha (`0.2.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. What
+that qualifier covers, concretely:
 
 - The injection path — connect, bind, wait for a device, send events — is
   exercised end-to-end against the real libraries by
@@ -194,17 +195,29 @@ renames before 1.0. What that qualifier covers, concretely:
 
 ## Install
 
-Not published to PyPI yet — install from a checkout:
+From [PyPI](https://pypi.org/project/python-libei/):
 
 ```sh
-git clone https://github.com/ctrondlp/python-libei.git
-cd python-libei
-pip install .
+pip install python-libei
 ```
 
 The distribution is named `python-libei`, the import is `libei` -- so
 `pip show python-libei`, but `from libei import ei`.
 
+Pure Python, no build step: the wheel is `py3-none-any` and ctypes talks to
+the native libraries directly, so there is no compiler, no headers and no
+`libei-devel` involved at install time. What `pip` does *not* bring is the
+native libraries themselves -- see [Requirements](#requirements) above; on
+Fedora, `sudo dnf install libei libeis liboeffis`.
+
+To track `main` instead, or to hack on it, install from a checkout:
+
+```sh
+git clone https://github.com/ctrondlp/python-libei.git
+cd python-libei
+pip install .          # or `pip install -e '.[dev]'` to develop
+```
+
 Importing is always safe, even where the native libraries are missing — they
 are loaded on first use, not at import. Check before you rely on them:
 
@@ -724,9 +737,9 @@ tag. Nothing enforces that yet.
 A release is an annotated, `v`-prefixed tag plus a GitHub Release:
 
 ```sh
-git tag -a v0.1.0 -m "0.1.0"
-git push origin v0.1.0
-gh release create v0.1.0 --generate-notes --prerelease
+git tag -a v0.2.0 -m "0.2.0"
+git push origin v0.2.0
+gh release create v0.2.0 --generate-notes --prerelease
 ```
 
 `--prerelease` while the API is unfrozen -- it keeps an alpha out of the
@@ -739,22 +752,24 @@ job in `ci.yml` handles it, uploading the artifacts the `build` job already
 ran `twine check` over.
 
 That job depends on two pieces of configuration outside this repository,
-which have to exist before the first tag:
-
-1. On pypi.org, under Account settings -> Publishing, a **pending**
-   publisher -- the flow for a project that has no releases yet. Project
-   `python-libei`, owner `ctrondlp`, repository `python-libei`, workflow
-   `ci.yml`, environment `pypi`. Every field has to match the workflow
+both of which are in place as of `0.1.0`:
+
+1. On pypi.org, a trusted publisher on the `python-libei` project: owner
+   `ctrondlp`, repository `python-libei`, workflow `ci.yml`, environment
+   `pypi`. It started life as a **pending** publisher -- the flow for a
+   project with no releases yet -- and the first upload converted it into
+   an ordinary project-level one, so a fresh project is the only case that
+   needs the pending form again. Every field has to match the workflow
    exactly; a mismatch surfaces as a rejected credential at upload time,
    not when it is saved.
 2. A GitHub environment named `pypi`, in the repository settings. A
    required reviewer on it makes each publish a deliberate approval rather
    than a side effect of pushing a tag.
 
-Worth rehearsing on TestPyPI first: separate account, separate pending
-publisher, and `repository-url: https://test.pypi.org/legacy/` on the
-publish step. PyPI filenames are immutable, so a bad upload can only be
-yanked and superseded by a new version, never replaced.
+PyPI filenames are immutable, so a bad upload can only be yanked and
+superseded by a new version, never replaced -- worth rehearsing anything
+unusual on TestPyPI first (separate account, separate pending publisher,
+and `repository-url: https://test.pypi.org/legacy/` on the publish step).
 
 ## Design notes
 

{python_libei-0.1.0.dist-info → python_libei-0.2.0.dist-info}/RECORD

@@ -1,4 +1,4 @@
-libei/__init__.py,sha256=iGbXyJLQl-zAV0AMAWdEMe0WxJivQCH4NLnwmlmub2I,1511
+libei/__init__.py,sha256=EWlmUgk0QL_TNN53lDU1ypnOVJcEJAUpNwsn1TUkKxQ,1511
 libei/_cobject.py,sha256=msrbviABSWjc5fKsXHSCg7nQ0Y4Etcq_Dkh0fblW-sY,12845
 libei/ei.py,sha256=Da3ezXnFPXtejlcJFH8bcE5f4pxKZXXqb6ltCh2zAdE,46704
 libei/eis.py,sha256=aYWOCN1NlRchcWd6NjIUi1eYMFWJbp0UHMcQFEJ0ii4,43642
@@ -9,8 +9,8 @@ libei/_capi/libei.py,sha256=gpp42bhqPonhVD2zmFWCl4rdk_lm4XvD_7W2Rw5RsuI,11308
 libei/_capi/libeis.py,sha256=jQR0Z0YN9qa71mAcSJ__-UaoF8PsVsBs8OXwjfqstFk,13080
 libei/_capi/liboeffis.py,sha256=V8jdmJm3qOQUzzNiCAXt4Jr2JY11Y4-w6NIfIxbxGI4,1218
 libei/_capi/loader.py,sha256=k7fb_Nz0fg5QkuLJ_duKXj8bESSktLQ2ZyS5LNQ5v2I,4689
-python_libei-0.1.0.dist-info/licenses/LICENSE,sha256=l6xbMU6Y-JZDzmBciBj-J5t6h6jNg_Bcyp4bHxDepqU,1074
-python_libei-0.1.0.dist-info/METADATA,sha256=aY3gXPsVdtrASfC7m1JDV7-4v0wNyv8u2LTZCQLVFqs,35447
-python_libei-0.1.0.dist-info/WHEEL,sha256=YVMoNqKzERt-wjUZwJ33xBGAwnFl-4cqbYkTtWa4itE,91
-python_libei-0.1.0.dist-info/top_level.txt,sha256=_DQXzGjDsUBENI_cNkiOxPB4xi8coCbQS1lq18FMudQ,6
-python_libei-0.1.0.dist-info/RECORD,,
+python_libei-0.2.0.dist-info/licenses/LICENSE,sha256=l6xbMU6Y-JZDzmBciBj-J5t6h6jNg_Bcyp4bHxDepqU,1074
+python_libei-0.2.0.dist-info/METADATA,sha256=tdUGfZwL_MtWeduTv8wRBmNhGo0jT04PnLRVbOR6eT0,36184
+python_libei-0.2.0.dist-info/WHEEL,sha256=YVMoNqKzERt-wjUZwJ33xBGAwnFl-4cqbYkTtWa4itE,91
+python_libei-0.2.0.dist-info/top_level.txt,sha256=_DQXzGjDsUBENI_cNkiOxPB4xi8coCbQS1lq18FMudQ,6
+python_libei-0.2.0.dist-info/RECORD,,