pixtreme-legacy
⚠️ Legacy Compatibility Package: This package provides _cp functions removed from pixtreme v0.5.2+.
Status
- Maintenance Mode: Functions migrated from main pixtreme package in v0.5.2
- Note: v0.5.1 was broken; use v0.5.2 or later
- Recommendation: Migrate to standard functions (without
_cpsuffix) when possible
Purpose
This package provides backward compatibility for _cp functions that were removed from the main pixtreme package in v0.5.1. It contains the following functions:
apply_lut_cp- Apply 3D LUT with CuPy implementationuyvy422_to_ycbcr444_cp- Convert UYVY422 to YCbCr444ndi_uyvy422_to_ycbcr444_cp- Convert NDI UYVY422 to YCbCr444yuv420p_to_ycbcr444_cp- Convert YUV420 to YCbCr444yuv422p10le_to_ycbcr444_cp- Convert YUV422p10le to YCbCr444
Installation
Requirements:
- Python >= 3.12
- CUDA Toolkit 12.x
- NVIDIA GPU with compute capability >= 6.0
pip install pixtreme-legacy
Usage
from pixtreme_legacy import apply_lut_cp
# No warnings - clean compatibility layer
result = apply_lut_cp(image, lut)
Note: This package depends on pixtreme>=0.7.3 for common utilities (to_float32, resize, etc.).
Migration Guide
Replace _cp functions with their standard equivalents:
Before (deprecated)
from pixtreme import apply_lut_cp
result = apply_lut_cp(image, lut, interpolation=0)
After (recommended)
from pixtreme import apply_lut
result = apply_lut(image, lut, interpolation=0)
Why were _cp functions deprecated?
The _cp suffix originally indicated "CuPy native" implementations, as opposed to CUDA kernel implementations. However:
- Redundancy: Both implementations exist in the main functions now
- Confusion: Users don't need to choose between implementations
- Maintenance: Duplicate APIs increase maintenance burden
The standard functions (without _cp) now automatically select the best implementation.
Timeline
- v0.4.0:
_cpfunctions available without warnings - v0.5.0:
_cpfunctions deprecated with warnings,pixtreme-legacypackage created - v0.5.1: BROKEN - Attempted
_cpfunction removal but incomplete (do not use) - v0.5.2:
_cpfunctions fully removed from main package, migrated topixtreme-legacywithout warnings - v0.6.0: Main
pixtremepackage split into modular packages (pixtreme-core,pixtreme-aces,pixtreme-filter,pixtreme-draw,pixtreme-upscale)
License
MIT License (same as pixtreme)
1 maintainer
Metadata
1 maintainer
Release files for pixtreme-legacy 0.8.7
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 | |
|---|---|---|---|---|
| pixtreme_legacy-0.8.7.tar.gz | 7.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pixtreme_legacy-0.8.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 16.8 kB
Release files / pixtreme_legacy-0.8.7.tar.gz
| Download URL | pixtreme_legacy-0.8.7.tar.gz |
|---|---|
| Size | 7.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0edbd38c28f3586c485661d5f709c8ad0d08f563e1df61839e9a66f4997000d5
|
|
BLAKE2b-256 checksum How to use checksums |
de4742d60eaa08c9601f57c574e0f0468e4ff4f54ba51ee027b977ea2d1fda07
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.11.28 {"installer":{"name":"uv","version":"0.11.28","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / pixtreme_legacy-0.8.7-py3-none-any.whl
| Download URL | pixtreme_legacy-0.8.7-py3-none-any.whl |
|---|---|
| Size | 9.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f3eaec9d5ca527ef3989c9864be94851f453abaa9b6c5eb483073bb5c5dd6ef8
|
|
BLAKE2b-256 checksum How to use checksums |
bf005b87dec1a2a40948d98f54c4fb36ab511acc170b96b1b986a48d852dcb51
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.11.28 {"installer":{"name":"uv","version":"0.11.28","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for pixtreme-legacy 0.8.7
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.
