CATO
This module implements the necessary routines used to embed license informations into source code project files. The package installation also installs a command line utility along with the license files in textual format in a hidden directory inside the user home.
LICENSE
Cato license terms can be found in the LICENSE file distributed with the package.
INSTALLATION
after downloading the package:
$ cd cato $ python setup.py install
or via pypi automatic installation:
$ pip install cato
DOCUMENTAION
Developer documentation is distributed in html format along with the package, and can be obtained running epydoc on the source code files:
Usage: cato -l gpl-3.0 -o "John Doe" -e john@doe.com -y 2012 filename.py
Cato is free software for applying licenses to your source code files. You can customize cato changing the cato.cfg file that you find in ~/.cato/ and adding license textual files in ~/cato/licenses/. License files can contain <owner> and <email> textual tags which will be replaced with cato informations. Embedded license versions will be applied on the first empty line of each source file scanned, if no empty line is found, no license is applied. In its normal behaviour cato apply the license to the files given as arguments on the command line, while using -d option it scans the given directory for file extensions specified as command line arguments. If -r is provided in conjunction with -d, all the directory tree is scanned starting from the supplied dir.
- Options::
- -h, --help
show this help message and exit
- --list
Lists available licenses and quit
- -l LICENSE, --license=LICENSE
The license name, use –list to list all licenses available
- -o OWNER, --owner=OWNER
the copyright owner
- -e EMAIL, --email=EMAIL
email contact of the copyright owner
- -y YEAR, --year=YEAR
the copyright year, defaults to current year
- -d DIRECTORY, --directory=DIRECTORY
a target directory where to find sources and add a LICENSE file
- -r
only with -d. If set recursively parses directory tree
- -c COMMENT, --comment=COMMENT
overrides comment syntax
1 maintainer
Metadata
1 maintainer
Release files for cato 1.0.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 |
|---|---|---|---|---|
| cato-1.0.1.tar.gz | 65.4 kB | Without provenance | Details for cato-1.0.1.tar.gz |
Release files / cato-1.0.1.tar.gz
| Download URL | cato-1.0.1.tar.gz |
|---|---|
| Size | 65.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a484ead631fc25ce6c1fe7b3d7b2d4e0a2f5ac6ba597ab29de03c817e940e156
|
|
BLAKE2b-256 checksum How to use checksums |
c1f75456c3434e539d064d111dfada1b0801119161c582b07984427165338e94
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for cato 1.0.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.
