flicker-detector
Umbrella (metapackage) on PyPI. This project ships almost no code: it declares optional extras so you can install one Windows x64 backend with a single command.
| Extra | Pulls in | Console commands (example) |
|---|---|---|
[cpu] |
flicker-detector-cpu |
cpu-flicker-detector, cpu-flicker-detector-server, cpu-flicker-detector-client |
[gpu] |
flicker-detector-gpu |
GPU package should use a gpu- prefix when published (same pattern as CPU). |
- Python ≥ 3.10
- OS: Windows 64-bit (extras are marked for
AMD64)
Install
CPU (recommended default):
py -m pip install -U "flicker-detector[cpu]"
GPU:
py -m pip install -U "flicker-detector[gpu]"
Requires the flicker-detector-gpu package to exist on the index you use (e.g. PyPI). If resolution fails, install the GPU wheel directly from its project page.
Important: do not install two backends that register the same console script names. The CPU backend uses cpu-* scripts; a GPU backend should use gpu-* (or another distinct prefix) so both can coexist if needed.
Commands (after installing flicker-detector-cpu)
| Command | Role |
|---|---|
cpu-flicker-detector |
Local CLI: video / image folder / image sequence → JSON |
cpu-flicker-detector-server |
Web UI + HTTP API |
cpu-flicker-detector-client |
Submit jobs to a running server |
Backend-only install (skip this umbrella)
If you only want the backend package:
py -m pip install flicker-detector-cpu
# or, when available:
py -m pip install flicker-detector-gpu
Same executables as with [cpu] / [gpu]; you do not need flicker-detector on top unless you want the extra indirection.
Source and issues
Algorithm details, building from source, and bug reports: see the flicker-detector-cpu (or GPU) repository and main project README, not this empty metapackage.
1 maintainer
Metadata
1 maintainer
Release files for flicker-detector 1.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| flicker_detector-1.1.3.tar.gz | 2.7 kB | Without provenance | Details for flicker_detector-1.1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| flicker_detector-1.1.3-py3-none-any.whl | Python 3 | none | any | Details for flicker_detector-1.1.3-py3-none-any.whl |
Total release size: 5.3 kB
Release files / flicker_detector-1.1.3.tar.gz
| Download URL | flicker_detector-1.1.3.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
273cf8d42032eab35e1b03a9d09e226188eda6fd13585a3a0bb25fc7ad5c22b4
|
|
BLAKE2b-256 checksum How to use checksums |
db80a5aa3660779fc989a276ffb0fefd0a3e509130564ecd1f0eed0e2882fa57
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.28 {"installer":{"name":"uv","version":"0.9.28","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / flicker_detector-1.1.3-py3-none-any.whl
| Download URL | flicker_detector-1.1.3-py3-none-any.whl |
|---|---|
| Size | 2.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e10bc00e733dc875167b25487cfeb3a6448f4f17197720c2400a784728f6470e
|
|
BLAKE2b-256 checksum How to use checksums |
b21ab2574720c5c0a22a8b4277cfe76138cdc33dbf1e6c33db782e65e9756acb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.28 {"installer":{"name":"uv","version":"0.9.28","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for flicker-detector 1.1.3
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
