This release is a pre-release and may not be stable for production use.
shrew
shrew 0.1.0
A handy way to manage your bash environment across machines.
About
A handy way to manage your bash environment across machines.
Installation
Install via pip:
$ pip install shrew
Install from source:
$ git clone git://github.com/litters/shrew.git $ cd shrew $ python setup.py install
Documentation
Full Documentation: http://shrew.readthedocs.org/en/latest.
You will need sphinx installed to generate the documentation. Documentation can be generated by running python setup.py doc. Generated documentation can be found in the doc/build/html/ directory.
Testing
The easiest way to run the tests is to install nose (pip intall nose) and run nosetests or python setup.py test in the root of the distribution. Tests are located in the tests/ directory.
Metadata
Release files for shrew 0.1.0a1
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 | |
|---|---|---|---|---|
| shrew-0.1.0a1.tar.gz | 15.2 kB | Without provenance | Details |
Release files / shrew-0.1.0a1.tar.gz
| Download URL | shrew-0.1.0a1.tar.gz |
|---|---|
| Size | 15.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ff53d349db963f774d7a6f5720e3acd2ae12ac83042ac659b908f198696928ea
|
|
BLAKE2b-256 checksum How to use checksums |
eda94c483ab5697587d690970ab055bcd0012085310fa6c7b5ae1e7c8656f873
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for shrew 0.1.0a1
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.