Repository navigation
Add automatic runtime setup and shared tracking lifecycle - #1
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an installable Python 3.10+ package for the Original Leap Motion Controller, with automatic Windows runtime delivery, verified caching, first-use device setup, and a shared private engine. Applications can use
Tracker()without specifying DLL or runtime paths; closing one client preserves tracking for other leased clients.Includes recording/replay, coordinate mapping, diagnostics, experimental Linux/macOS LeapC loading, and CI/release workflows. The Windows runtime is a separate release asset; the Python wheel contains no vendor binaries or recordings.
Validation: automated tests across project-local Python 3.10–3.15 venvs, real camera capture, offline cache reuse, two-client sharing, repeated engine restart, abrupt client exit, and restored-service live frames. Clean-PC driver setup and Linux/macOS hardware tests remain pending. Public runtime availability and PyPI Trusted Publishing must be configured before publishing the package.