DisplayCAL Python 3 Project
This project intended to modernize the DisplayCAL code including Python 3 support.
Florian Höch, the original developer, did an incredible job of creating and maintaining DisplayCAL for all these years. But, it seems that, during the pandemic, very understandably, he lost his passion to the project. Now, it is time for us, the DisplayCAL community, to contribute back to this great tool.
This project is based on the HEAD of the Sourceforge version, which had 5 extra
commits that Florian has created over the 3.8.9.3 release on 14 Jan 2020.
Thanks to all the efforts put by the community DisplayCAL is now working with Python 3.9+:
Installation Instructions
Follow the instructions depending on your OS:
Have fun!
Metadata
Release files for displaycal 3.9.19
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 |
|---|---|---|---|---|
| displaycal-3.9.19.tar.gz | 12.0 MB | Without provenance | Details for displaycal-3.9.19.tar.gz |
Release files / displaycal-3.9.19.tar.gz
| Download URL | displaycal-3.9.19.tar.gz |
|---|---|
| Size | 12.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
187c7ed95c2ec7074c421e9fc58e95fc440913808fc5eaf7f408ff4253166ebc
|
|
BLAKE2b-256 checksum How to use checksums |
d58ffb4ae9ed769fb91fdaec55ddbff9ad0397f609f80dd86c697d0353c4f37b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.4
|
Security for displaycal 3.9.19
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.