livedc

useful mathmatical models/caculators for daily life and cloud deployment

tdm23_vr setup for colab

!pip install livedc
from livedc import url_vrpkl,url_vrlib
import pickle
with open(url_vrpkl, "rb") as f:
    prereq = pickle.load(f)
tdmvr, installed_packages = prereq.env(furl=url_vrlib)

Metadata

Release files for livedc 0.0.17

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for livedc 0.0.17
File	Size	Uploaded	Provenance
livedc-0.0.17.tar.gz	148.7 kB	Apr 16, 2025	With provenance	Details

Built distribution (wheel)

Table of built distributions (wheels) for livedc 0.0.17
File	Interpreter	ABI	Platform	Reset
livedc-0.0.17-py3-none-any.whl 152.1 kB Apr 16, 2025 With provenance	Python 3	none	any	Details

Total release size: 300.7 kB

Release files / livedc-0.0.17.tar.gz

Download URL	livedc-0.0.17.tar.gz
Size	148.7 kB
Tags	Source
SHA-256 checksum How to use checksums	`f0e4b5e79c639f6c336d4707f2de56f773b033456c0191c4b9257dfdd502fab6`
BLAKE2b-256 checksum How to use checksums	`e9523b59bdf46740f400bbb24b531f709ced2517a66c825c38a56c1775c56117`
Upload date	Apr 16, 2025
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/6.1.0 CPython/3.12.9`

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.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/jinsanity07git/livedc
Publishing commit: github.com/jinsanity07git/livedc/tree/19ad8ac442bc6f417aea83948ad885c7117ea948

Workflow

Publishing configuration: github.com/jinsanity07git/livedc/blob/19ad8ac442bc6f417aea83948ad885c7117ea948/.github/workflows/python-publish.yml
Publishing logs: github.com/jinsanity07git/livedc/actions/runs/14501063570/attempts/1

Artifact

Subject: livedc-0.0.17.tar.gz
SHA-256 checksum: f0e4b5e79c639f6c336d4707f2de56f773b033456c0191c4b9257dfdd502fab6 Verifying attestations

Release files / livedc-0.0.17-py3-none-any.whl

Download URL	livedc-0.0.17-py3-none-any.whl
Size	152.1 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`3b030fa8772335eee6ed4e872efd1512a4247f51fdba49fbf990294e3888e5d2`
BLAKE2b-256 checksum How to use checksums	`e3c382b0d0faeb548d46d4cb5f2e5462d5cc38f20a1a64584e99aeebeee0eb0e`
Upload date	Apr 16, 2025
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/6.1.0 CPython/3.12.9`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/jinsanity07git/livedc
Publishing commit: github.com/jinsanity07git/livedc/tree/19ad8ac442bc6f417aea83948ad885c7117ea948

Workflow

Publishing configuration: github.com/jinsanity07git/livedc/blob/19ad8ac442bc6f417aea83948ad885c7117ea948/.github/workflows/python-publish.yml
Publishing logs: github.com/jinsanity07git/livedc/actions/runs/14501063570/attempts/1

Artifact

Subject: livedc-0.0.17-py3-none-any.whl
SHA-256 checksum: 3b030fa8772335eee6ed4e872efd1512a4247f51fdba49fbf990294e3888e5d2 Verifying attestations

Security for livedc 0.0.17

Report project as malware

Provenance

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Attestation for livedc-0.0.17.tar.gz

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/jinsanity07git/livedc
Publishing commit: github.com/jinsanity07git/livedc/tree/19ad8ac442bc6f417aea83948ad885c7117ea948

Workflow

Publishing configuration: github.com/jinsanity07git/livedc/blob/19ad8ac442bc6f417aea83948ad885c7117ea948/.github/workflows/python-publish.yml
Publishing logs: github.com/jinsanity07git/livedc/actions/runs/14501063570/attempts/1

Artifact

Subject: livedc-0.0.17.tar.gz
SHA-256 checksum: f0e4b5e79c639f6c336d4707f2de56f773b033456c0191c4b9257dfdd502fab6 Verifying attestations

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.