pyconcord
| CI | status |
|---|---|
| conda.recipe |  |
| pip builds |  |
Installation
- Clone this repository
brew install eigencd [this_repo]uv venv .venv --python 3.9 && source .venv/bin/activateuv pip install .[test]
To run tests:
pytest -s
To install from pypi:
uv pip install pyconcord --no-sources
Test call
import numpy as np
from scipy.sparse import identity
import pyconcord as pc
x = np.random.randn(13, 9)
n, p = x.shape
x0 = identity(p).tocoo()
omega = pc.concord(x, x0=x0, lambda1=0.3)
cov = np.round(omega.todense(), 2)
assert ~np.isinf(cov[0,0])
assert cov[0, 1] == cov[1, 0]
Files
This example has several files that are a good idea, but aren't strictly necessary. The necessary files are:
pyproject.toml: The Python project fileCMakeLists.txt: The CMake configuration filesrc/main.cpp: The source file for the C++ buildsrc/pyconcord/__init__.py: The Python portion of the module. The root of the module needs to be<package_name>,src/<package_name>, orpython/<package_name>to be auto-discovered.
These files are also expected and highly recommended:
.gitignore: Git's ignore list, also used byscikit-build-coreto select files for the SDistREADME.md: The source for the PyPI descriptionLICENSE: The license file
There are also several completely optional directories:
.github: configuration for Dependabot and GitHub Actionsconda.recipe: Example recipe. Normally you should submit projects to conda-forge instead of building them yourself, but this is useful for testing the example.docs/: Documentationtests/: Tests go here
And some optional files:
.pre-commit-config.yaml: Configuration for the fantastic static-check runner pre-commit.
This is a simplified version of the recommendations in the Scientific-Python Development Guide, which is a highly recommended read for anyone interested in Python package development (Scientific or not). The guide also has a cookiecutter that includes scikit-build-core and pybind11 as a backend choice.
CI Examples
There are examples for CI in .github/workflows. A simple way to produces
binary "wheels" for all platforms is illustrated in the "wheels.yml" file,
using cibuildwheel.
License
pybind11 is provided under a BSD-style license that can be found in the LICENSE file. By using, distributing, or contributing to this project, you agree to the terms and conditions of this license.
1 maintainer
Release files for pyconcord 0.4.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pyconcord-0.4.6.tar.gz | 2.2 MB | Details |
Built distributions (wheels)
Total release size: 3.7 MB
Release files / pyconcord-0.4.6.tar.gz
| Download URL | pyconcord-0.4.6.tar.gz |
|---|---|
| Size | 2.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cd065b0655bb65f582b837276b4cab7a5d1f09f44c3e04777b7dbe420ab6dda7
|
|
BLAKE2b-256 checksum How to use checksums |
f4141f86fef2e90831c7f1bc17855b06750a2ede09f60731a9eb196fc6ebb06b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2024.
Transparency logRelease files / pyconcord-0.4.6-pp310-pypy310_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | pyconcord-0.4.6-pp310-pypy310_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 124.7 kB |
| Tags | Linux glibc 2.17+ x86-64 PyPy 3.10 PyPy 3.10 7.3 |
|
SHA-256 checksum How to use checksums |
aa032b8a62651d1b5178cd0a4c6ad24b2e1d341ce011659396c4548e304bc02c
|
|
BLAKE2b-256 checksum How to use checksums |
58c791ed0cef1409368ec912f1056e98840dce0a874842d24018eace16e935fa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2024.
Transparency logRelease files / pyconcord-0.4.6-pp310-pypy310_pp73-macosx_11_0_arm64.whl
| Download URL | pyconcord-0.4.6-pp310-pypy310_pp73-macosx_11_0_arm64.whl |
|---|---|
| Size | 95.8 kB |
| Tags | PyPy 3.10 PyPy 3.10 7.3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
2d4f0ed5c313ed352908d81dc21085c3f93a43823bc9e3eb0f091e02b9321b7c
|
|
BLAKE2b-256 checksum How to use checksums |
842a6c3e880fac0f9667b55751fed449132843a920bb5d845914d64b9216845d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2024.
Transparency logRelease files / pyconcord-0.4.6-pp39-pypy39_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | pyconcord-0.4.6-pp39-pypy39_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 124.7 kB |
| Tags | Linux glibc 2.17+ x86-64 PyPy 3.9 PyPy 3.9 7.3 |
|
SHA-256 checksum How to use checksums |
cca013e72591f78eaef83e8e4e43e06ca3546336e7a8b68c9ea0b09437faebe5
|
|
BLAKE2b-256 checksum How to use checksums |
633ead0f7e1ee28cc5668f92336d73a0946eeca59ee6fa6cacf7ad2c002efe87
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2024.
Transparency logRelease files / pyconcord-0.4.6-pp39-pypy39_pp73-macosx_11_0_arm64.whl
| Download URL | pyconcord-0.4.6-pp39-pypy39_pp73-macosx_11_0_arm64.whl |
|---|---|
| Size | 95.7 kB |
| Tags | PyPy 3.9 PyPy 3.9 7.3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
953106fc87e5e47adea0c1958beab7676a726a861c5e294e60de41c16d20ee4b
|
|
BLAKE2b-256 checksum How to use checksums |
f80b503bcc9c14d4dc375fa675851e0b0ab613335571b07f9c2c5461a54525c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2024.
Transparency logRelease files / pyconcord-0.4.6-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | pyconcord-0.4.6-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 125.3 kB |
| Tags | CPython 3.13 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
6f99da916114e06d28351eca8e728eae75126bc982312ab6162d4147d47e0256
|
|
BLAKE2b-256 checksum How to use checksums |
11f260de7db8f911e507512074b57f6ba91c7a627d40b2e5c07a2b18ba27d011
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2024.
Transparency logRelease files / pyconcord-0.4.6-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | pyconcord-0.4.6-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 96.2 kB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
993172bbd5d4976f046b172414a99a401d7685600e05c3f0363d21577486f1ab
|
|
BLAKE2b-256 checksum How to use checksums |
8c17a5e9cafcebf001b1804cffe2d5e51abf9bc8cb026d9373d0528a097f2341
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2024.
Transparency logRelease files / pyconcord-0.4.6-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | pyconcord-0.4.6-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 125.5 kB |
| Tags | CPython 3.12 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
31a42840ba2b619e2bc9cd79e6533daeadf9a685953ec70843e66d8867759e16
|
|
BLAKE2b-256 checksum How to use checksums |
a62ded114c25597a4b513f950d73b3d8c9eadebcd225948d7de51fa859adf3e9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2024.
Transparency logRelease files / pyconcord-0.4.6-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | pyconcord-0.4.6-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 96.1 kB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
659b191dd4806b8f2b1375654bc5bbf9a38426069131be9f77c7fda24ddf7092
|
|
BLAKE2b-256 checksum How to use checksums |
80f62eff80a8b6ba3374ae66347f42e19a5c35d52c12b6f9fe4a7f368efab037
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2024.
Transparency logRelease files / pyconcord-0.4.6-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | pyconcord-0.4.6-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 126.2 kB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
2724b29bb594ca6854a479fc93872d1608fa618502798839f33b22f1f3b031ae
|
|
BLAKE2b-256 checksum How to use checksums |
e3ad58f7acb4f81297b269e0cac6aee875f848c8460d360b80861caa88f24873
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2024.
Transparency logRelease files / pyconcord-0.4.6-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | pyconcord-0.4.6-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 96.9 kB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
9fbb66085cd175c62110ff605783cf342ef99a546d3c6a054510b2fcf34ee1a5
|
|
BLAKE2b-256 checksum How to use checksums |
ae77e00d4a2ecd1f27e123cbf4322ea646879b742997e1840d441beefe028d0d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2024.
Transparency logRelease files / pyconcord-0.4.6-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | pyconcord-0.4.6-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 124.9 kB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
b28612ece4f480376d90a5647279b69e604dea04871174df0b467e5e9b05db05
|
|
BLAKE2b-256 checksum How to use checksums |
89decfcd0247de97dd74fc78c38cb91fd0517c167b4395e99b1269d78ad079e7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2024.
Transparency logRelease files / pyconcord-0.4.6-cp310-cp310-macosx_11_0_arm64.whl
| Download URL | pyconcord-0.4.6-cp310-cp310-macosx_11_0_arm64.whl |
|---|---|
| Size | 95.6 kB |
| Tags | CPython 3.10 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
1addd65e3ed6122dee1c9f38767d13e91d24edad5c3b304927f6881a5d7b5e3a
|
|
BLAKE2b-256 checksum How to use checksums |
78cb85801e5f536e498a5f44f02db472cd6ce1468df4a23c4bfa8b9e4a54386c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2024.
Transparency logRelease files / pyconcord-0.4.6-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | pyconcord-0.4.6-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 125.0 kB |
| Tags | CPython 3.9 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
3c4ffa235e947caf0dbc9617484397146b7c8391b2a8524407b85b1ce7f608b8
|
|
BLAKE2b-256 checksum How to use checksums |
d88c240bbddfa499668f130b5bb63f3f3aa1d04da05c567031b991d2ec95b722
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2024.
Transparency logRelease files / pyconcord-0.4.6-cp39-cp39-macosx_11_0_arm64.whl
| Download URL | pyconcord-0.4.6-cp39-cp39-macosx_11_0_arm64.whl |
|---|---|
| Size | 95.7 kB |
| Tags | CPython 3.9 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
ce996f585599707d212b1cf79aaf6b8dd86520f50af434f6a4abeedd7576b70e
|
|
BLAKE2b-256 checksum How to use checksums |
cff369d76a26ad1ed3cfa1ed274e2464289c84c790a457b528ba48391395dbbc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2024.
Transparency log
