Wet Copy
The purpose of this program is to format and print wetlab protocols that are stored as text files in git repositories. Printed out protocols are nice because they can be easily carried around lab during an experiment, annotated in real time, and ultimately taped into a lab notebook. Digital protocols stored as text files in git repositories are nice as well, because they can be updated and modified without losing any information. This script helps manage the process of printing out and keeping track of digital protocols.
To use this program, start by the adding protocols you use to a git repository. Then use the wet_copy command to print out copies of your protocols formatted with all the information needed to recover the original digital protocol (e.g. a repository URL and a commit hash), enough space to make annotations in the margins, and lines showing where to cut so the protocol can be taped into a lab notebook. The wet_copy command won’t let you print protocols that have any lines wider than 53 characters (otherwise the margin will be too small) or that have any uncommitted changes (otherwise the original protocol won’t be recoverable).
Installation
The easiest way to install wet_copy is from the PyPI:
$ pip3 install wet_copy
Alternatively, you can clone this repository and install wet_copy from source:
$ git clone git@github.com:kalekundert/wet_copy.git $ pip3 install ./wet_copy
Note that wet_copy requires python 3.
License
Copyright (C) 2015, Kale Kundert
This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>.
1 maintainer
Metadata
1 maintainer
Release files for wet_copy 1.3.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 |
|---|---|---|---|---|
| wet_copy-1.3.1.tar.gz | 15.9 kB | Without provenance | Details for wet_copy-1.3.1.tar.gz |
Release files / wet_copy-1.3.1.tar.gz
| Download URL | wet_copy-1.3.1.tar.gz |
|---|---|
| Size | 15.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f4411aeb82374cde7cbc5667e802e8e0ac53acd0bbc74479590daf775c664e7c
|
|
BLAKE2b-256 checksum How to use checksums |
96a6a60232acc793fb7de1c72d8890ffb61d41529386791957f1e1958713a892
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for wet_copy 1.3.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.
