Spliced
⭐️ View Documentation ⭐️
This library is written and maintained by @vsoch
TODO
- Can we (and do we want to) run in parallel?
License
Spack is distributed under the terms of both the MIT license and the Apache License (Version 2.0). Users may choose either license, at their option.
All new contributions must be made under both the MIT and Apache-2.0 licenses.
See LICENSE-MIT, LICENSE-APACHE, COPYRIGHT, and NOTICE for details.
SPDX-License-Identifier: (Apache-2.0 OR MIT)
LLNL-CODE-811652
Metadata
Release files for spliced 0.0.18
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 |
|---|---|---|---|---|
| spliced-0.0.18.tar.gz | 2.0 MB | Without provenance | Details for spliced-0.0.18.tar.gz |
Release files / spliced-0.0.18.tar.gz
| Download URL | spliced-0.0.18.tar.gz |
|---|---|
| Size | 2.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2d793cac6a659eb3c1b1886d5c29e28102aad506bb8a5ffa81dca6367f8db180
|
|
BLAKE2b-256 checksum How to use checksums |
1553c4aed6ddd991fbd938cc0230f0bc240a3afeb448910aa00eef9afa258adb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.12
|
Security for spliced 0.0.18
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.