charticle: Combine the best (or worst) charts for thinkpieces
charticle is an MIT-licensed Python package designed to make it very easy to build new diagrams like the Drew Conway Data Science diagram.
This may not be wise.
Release Information
0.0.3 (3 July 2016)
Changes:
Add charticle.hierarchy diagrams and examples.
Supports general text and polygon arguments for outer triangle & layers.
Cleanups:
wishlist, release procedures added to repo.
Jupyter notebooks removed from repo.
py27 testing included in tox.ini.
refactoring validators.
cleaned up release procedure.
0.0.2 (30 June 2016)
Changes:
Support Venn2 diagrams (and Venn3).
Improve documentation examples and testing.
Credits
charticle is written and maintained by Jeremy G. Kahn.
Collaboration and kibitzing due to Bill McNeill.
A full list of contributors can be found in GitHub’s overview.
Metadata
Release files for charticle 0.0.3
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 | |
|---|---|---|---|---|
| charticle-0.0.3.zip | 26.7 kB | Without provenance | Details |
Release files / charticle-0.0.3.zip
| Download URL | charticle-0.0.3.zip |
|---|---|
| Size | 26.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
541df9bb41f6725f78a4d50e96eb029f71a55a110906e67c68db627e6d5d4612
|
|
BLAKE2b-256 checksum How to use checksums |
20e19a312a08e463bbd25a8100c8e9a9da4813ecd9e20aeacc68774dcebd5111
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for charticle 0.0.3
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.