LightGlue: Local Feature Matching at Light Speed
Slightly modified, self-contained, packaged version of https://github.com/cvg/LightGlue. This fork exists as a stable dependency for other scm tools. If you are interested in LightGlue it might make sense to refer to the original repository. Use at your own risk!
Weights that are not shipped with the package (e.g. LightGlue for SIFT) are downloaded on first use into the torch hub cache (torch.hub.get_dir(), configurable via TORCH_HOME).
To download them only once for multiple processes that share this cache (e.g. on a cluster), call LightGlue.get_weights_path(features) once before starting them.
1 maintainer
Metadata
1 maintainer
Release files for scm-lightglue 0.2.9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| scm_lightglue-0.2.9-py3-none-any.whl | Python 3 | none | any | Details |
Release files / scm_lightglue-0.2.9-py3-none-any.whl
| Download URL | scm_lightglue-0.2.9-py3-none-any.whl |
|---|---|
| Size | 101.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
31bfdb556d713684f3d3aacde9b0ae65f7ba444e5c44948f369cc0789fcda5b9
|
|
BLAKE2b-256 checksum How to use checksums |
7b9e868d657319c0b085114c5983649c10397205867dceda46993a1f75511a52
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for scm-lightglue 0.2.9
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
