shellwhat_ext
Extensions to shellwhat testing.
Including in a DataCamp course
In the course's requirements.sh, add
# replace 0.0.1 with the appropriate release version
pip3 install --no-deps shellwhat-ext==0.0.1
To use the extensions in an exercise's SCT, import the function you want into the SCT block of the exercise:
from shellwhat_ext import test_cmdline
Ex() >> test_cmdline([['wc', 'l', '+']])
Deploying to PyPI
Follow these steps
- Open a PR, merge into master when appropriate.
- Once merged, increment
__version__ = 0.0.1to reflect changes (see semver for guidance). - Create a github release labeled
vVERSION. E.g.v0.0.1. (see here).
Running tests
make install
make test
Metadata
Release files for shellwhat-ext 0.4.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 |
|---|---|---|---|---|
| shellwhat-ext-0.4.1.tar.gz | 10.5 kB | Without provenance | Details for shellwhat-ext-0.4.1.tar.gz |
Release files / shellwhat-ext-0.4.1.tar.gz
| Download URL | shellwhat-ext-0.4.1.tar.gz |
|---|---|
| Size | 10.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b7ecfa7e7c8e6c41a00ad07cfb48750ec2520b79acb78ea538f77909b69e6185
|
|
BLAKE2b-256 checksum How to use checksums |
359c0245d885134aeeb1bfd80102ecec4f7aedf7dd65531f6a6388c02400d784
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/40.2.0 requests-toolbelt/0.8.0 tqdm/4.25.0 CPython/3.5.6
|
Security for shellwhat-ext 0.4.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.