The gajja library provides a system of Python test double classes for specific system objects:
Filesystem entries
Subprocesses
The Korean word 가짜 (gajja; IPA ˈkaːt͡ɕ̤a) means “fake thing”.
Metadata
Release files for gajja 0.1.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 | |
|---|---|---|---|---|
| gajja-0.1.4.tar.gz | 28.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gajja-0.1.4-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 40.2 kB
Release files / gajja-0.1.4.tar.gz
| Download URL | gajja-0.1.4.tar.gz |
|---|---|
| Size | 28.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e9582b218fe27ca87fb91545b54b3eb37bb0502e9970806c624c2711440d0ee4
|
|
BLAKE2b-256 checksum How to use checksums |
22d6afcdadb2bf857d91dde2f9c549ae0595d372887b5abcce333540592b9b2e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / gajja-0.1.4-py2.py3-none-any.whl
| Download URL | gajja-0.1.4-py2.py3-none-any.whl |
|---|---|
| Size | 12.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
c02260f1f00f53427075c5ef23f9b85db687cafa74e4f06ab73b779587d70205
|
|
BLAKE2b-256 checksum How to use checksums |
02cf900ba86b97d4d6bfa6f4df2a852fa7b575e86d78b6574411a9e29911b3be
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for gajja 0.1.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.