Holographic
It's annoying and unsustainable to author resusable code in a python notebook. This problem is exacerbated when the notebook system is not running in a local development environment or otherwise does not have access to the same filesystem as the IDEs which the author would prefer to use. So, wouldn't it be nice if you could develop your code wherever you wanted, and as long as that place had an internet connection (and as long as your notebook has an internet connection) you could create a read-only copy of your code in the notebook environment, holographic code if you will, and have the best of both worlds: a fully-featured authoring experience with static-analysis tools, multi-select, etc. and the rich interactive runtime experience of a notebook environment.
1 maintainer
Metadata
1 maintainer
Release files for holographic 0.0.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 |
|---|---|---|---|---|
| holographic-0.0.1.tar.gz | 12.2 kB | Without provenance | Details for holographic-0.0.1.tar.gz |
Release files / holographic-0.0.1.tar.gz
| Download URL | holographic-0.0.1.tar.gz |
|---|---|
| Size | 12.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
20266f11f7ff7a7d7ce5b81091521476c18a569dfce29235879f80daf4a0c261
|
|
BLAKE2b-256 checksum How to use checksums |
7fab23dcd76b52892bdab8109504c675486d2971a37c0d3e4ffd9c2335bb137d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.3
|
Security for holographic 0.0.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.
