Overview
Add or replace license/copyright boilerplate in source code files.
All contiguous comment blocks (bounded by empty or code lines) that contain a copyright message are stripped before injecting the new message.
You should commit all your code into a repo before running this program and check the results with a diff utility.
Features
Autodetect language from extension or shebang or header.
Force programming language to use if files cannot be autodetected.
Specify list of files to process.
Recursive or non-recursive processing from current or specific path.
Custom templates loadable from a JSON file.
Specify author(s), year(s), program and short description.
Include or exclude files or directories with wildcards or regex.
Append to file or insert after any contiguous header comment block.
Control left-hand margin padding and newline spacing.
JSON config file ingestion for repeated or automated use, overridden by command-line options.
Multi or single line comment style, such as /* */ vs. //.
Quiet mode to suppress printing of altered files.
Languages currently supported: C/C++, Java, HTML, Shell/Bash/Csh/Ksh/Tcsh/Zsh, Perl, Python, SQL, XML
Python 2 and 3.
Examples
Process current directory recursively and autodetect files.
$ copyright -c config.json
Process files matching wildcards, appending to end of file.
$ copyright -a 'Joe Smith' -p MyApp -l mit -i '*.py,foo*.h,script?' --back
Use custom template.
$ copyright -c config.json -t my_templates.json --license my-license-2.0
Installation
With PyPI.
$ pip install copyright
With tarball.
$ python setup.py install
Testing
$ make test
FAQ
Q1. How can you keep multiple licenses in a file? A1. One strategy is to create a custom templates file that has all the licenses merged into one key/value pair, and then process your specific list of files.
News
1.0.1.0
Added -q/–quiet mode.
Fixed -v/–version message.
1.0.0.0
Initial release.
License
copyright Copyright (C) 2016 Remik Ziemlinski
This program comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under the conditions of the GPLv3 license.
Metadata
Release files for copyright 1.0.1.0
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 |
|---|---|---|---|---|
| copyright-1.0.1.0.tar.gz | 12.0 kB | Without provenance | Details for copyright-1.0.1.0.tar.gz |
Release files / copyright-1.0.1.0.tar.gz
| Download URL | copyright-1.0.1.0.tar.gz |
|---|---|
| Size | 12.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
475b3a71bfffd50cabb1a7009f69650477b24bdcc089b002fbd40d057ab66d12
|
|
BLAKE2b-256 checksum How to use checksums |
b926a581b52bc311cb7e48bd50355ccfb793b47be33fc1f71b0c39400fc518e4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for copyright 1.0.1.0
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.