C/C++ wrapper around Cling, the LLVM-based interactive C++ interpreter, for use by cppyy, providing stable C and C++ Reflection APIs.
The compilation of cppyy-backend is very fast, but it will pull in cppyy-cling, which takes a long time to install if there is no matching wheel for your platform, forcing a build from source. By default, all cores will be used, but it is also recommended to add the verbose flag to see progress:
$ python -m pip install –verbose cppyy-backend
- For further details, see cppyy’s installation instructions:
- Cling documentation is here:
- Find the cppyy documentation here:
- Change log:
- Bug reports/feedback:
https://bitbucket.org/wlav/cppyy/issues?status=new&status=open
1 maintainer
Metadata
1 maintainer
Release files for cppyy-backend 1.13.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 | |
|---|---|---|---|---|
| cppyy-backend-1.13.0.tar.gz | 32.1 kB | Without provenance | Details |
Release files / cppyy-backend-1.13.0.tar.gz
| Download URL | cppyy-backend-1.13.0.tar.gz |
|---|---|
| Size | 32.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
259de15a453a778e29ed91824b401c0a8189bff3d077a809fdce5cd07e75708e
|
|
BLAKE2b-256 checksum How to use checksums |
9161a8506ece5fb7337da1dbd0d278e037002091dcc0225b056bf0670e753147
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/49.6.0 requests-toolbelt/0.9.1 tqdm/4.48.2 CPython/3.8.3
|
Security for cppyy-backend 1.13.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.
