ms_cv - Correlation Vector
A correlation vector implementation in python, based on Microsoft's implementation.
Usage
import ms_cv
cll_vec = ms_cv.CorrelationVector()
print('Initial cll vector: {}'.format(cll_vec.get_value()))
print('Next iteration: {}'.format(cll_vec.increment()))
Installation
pip install ms_cv
Requirements
- None
Compatibility
- Python 3
License
MIT LICENSE
Authors
ms_cv was written by OpenXbox <noreply@openxbox.org>.
Based on the implementation by Microsoft:
https://github.com/search?q=org%3Amicrosoft+correlationVector
Metadata
Release files for ms-cv 0.1.1
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 |
|---|---|---|---|---|
| ms_cv-0.1.1.tar.gz | 2.6 kB | Without provenance | Details for ms_cv-0.1.1.tar.gz |
Release files / ms_cv-0.1.1.tar.gz
| Download URL | ms_cv-0.1.1.tar.gz |
|---|---|
| Size | 2.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0264aabba9d620ecf55816ebff3e9e7b7e727c5a9d9c07fbabef2c1ea7395a07
|
|
BLAKE2b-256 checksum How to use checksums |
1ce0581b746c4b26aa0fac038fc300c6ec8b70c2a2837860bb08c4307cba9673
|
| 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.3.1 requests-toolbelt/0.9.1 tqdm/4.48.2 CPython/3.8.5
|
Security for ms-cv 0.1.1
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.