=============
C/C++ wrapper around Cling for use by cppyy.
This package will pull in cppyy-cling, which contains a version of LLVM
that is patched for interactive use.
Compilation of LLVM may take a long time, so when building from source, it is
recommended to set MAKE_NPROCS to the number of cores on your machine and to
use the verbose flag to see progress:
$ MAKE_NPROCS=32 pip install --verbose cppyy-backend
Alternatively, there are binary wheels (Mac 10.12, Linux/Gentoo)
available here:
https://cern.ch/wlav/wheels
Use '--extra-index https://cern.ch/wlav/wheels' as an argument to pip to
pick them up.
Cling documentation is here:
https://root.cern.ch/cling
----
Find the cppyy documentation here:
http://cppyy.readthedocs.io/en/latest
Metadata
Release files for cppyy-backend 0.3.0
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 |
|---|---|---|---|---|
| cppyy-backend-0.3.0.tar.gz | 19.9 kB | Without provenance | Details for cppyy-backend-0.3.0.tar.gz |
Release files / cppyy-backend-0.3.0.tar.gz
| Download URL | cppyy-backend-0.3.0.tar.gz |
|---|---|
| Size | 19.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
904477ec25f0c354bcb28947f96385181fa9b6472b42953d6cff2ea500671a54
|
|
BLAKE2b-256 checksum How to use checksums |
8df98f6a244a83cd3ff0f52ccb0fc4436e0de4f035db02a6a43a14082b2841ea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for cppyy-backend 0.3.0
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.