FUNCTIONS:
get_key(url) -> gets the key to the sourcebin out of the link(must be a valid link)
get_url(key) -> takes in the key to a sourcebin and turns it into a sourbin url
create(name, code, title=”None”, description=”None”) -> creates a sourcbin with the inputted code
read_key(key) -> returns the contents of the sourbin with that key
read_url(url) -> same as read_key but you can put in a sourbin url
1 maintainer
Metadata
1 maintainer
Release files for pysourcebin 0.0.4
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 | |
|---|---|---|---|---|
| pysourcebin-0.0.4.tar.gz | 2.7 kB | Without provenance | Details |
Release files / pysourcebin-0.0.4.tar.gz
| Download URL | pysourcebin-0.0.4.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f998c47414b09f4ad207b41e3dc2d4b16a609d36186c393b603cab7506c5853e
|
|
BLAKE2b-256 checksum How to use checksums |
a53dc1d312c748db9bf7e848ed255fc00294462d238c2043d86b5983db7874b6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.9.5
|
Security for pysourcebin 0.0.4
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.
