=======
Sensible repository licensing for Humans
.. image:: https://pypip.in/status/lisense/badge.svg
:target: https://pypi.python.org/pypi//
:alt: Development Status
.. image:: https://pypip.in/version/lisense/badge.svg
:target: https://pypi.python.org/pypi//
:alt: Latest Version
.. image:: https://pypip.in/py_versions/lisense/badge.svg
:target: https://pypi.python.org/pypi//
:alt: Supported Python versions
.. image:: https://pypip.in/license/lisense/badge.svg
:target: https://pypi.python.org/pypi//
:alt: License
.. image:: https://pypip.in/download/lisense/badge.svg
:target: https://pypi.python.org/pypi///
:alt: Downloads
**Sir Isaac Newton once said that**
*Open source simply isn't open source without a proper license. So add a license. Always.*
GitHub recently launched their `License API <https://developer.github.com/v3/licenses/>`__, it's still in preview stage though.
They also released a blog post showing `Open source license usage on GitHub.com <https://github.com/blog/1964-open-source-license-usage-on-github-com>`__, which is enough to convice you that why adding a license is
`sine qua non <http://lmgtfy.com/?q=define+sine+qua+non>`__.
*Newton and Open Source, Respect both, let us.*
\- Yoda
lisense in action
~~~~~~~~~~~~~~~~~
.. figure:: https://raw.githubusercontent.com/pravj/lisense/master/docs/lisense.gif
:alt: lisense
lisense. What?
~~~~~~~~~~~~~~
lisense is a command-line tool which helps you license your projects.
- Lets you have a global configuration. Use your defaults, anywhere, anytime.
- Guides you about using a particular license, better than you uncle.
- And yes! Generates licenses.
lisense. Controls?
~~~~~~~~~~~~~~~~~~
Generating a license is more easy than doing nothing.
- lisense list
List all available licenses.
- lisense guide [license]
Provide guidance about a license. Description, use cases etc.
- lisense setup
Setup global lisense configurations. Default license and owner name.
- lisense new [license] --owner="OWNER NAME"
Generates new license. Both the *license* and *owner* arguments are optional. Uses defaults when not supplied.
Automatic extra context variable handling
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Almost all the licenses have two common fields in them, *owner* and *year*. Some of them have extra fields also. For example, the GPL-v2 license
has a field *description*, which asks for the description of the project.
Lisense uses *jinja2*'s low level meta API to parse the abstract syntax tree of the template and interactively asks users to fill
extra fields, if any.
So, you don't have to worry about it.
Dependencies
~~~~~~~~~~~~
- `docopt <https://github.com/docopt/docopt>`__ - command-line argument parsing
- `jinja2 <https://github.com/mitsuhiko/jinja2>`__ - generate licenses from license templates
- `xtermcolor <https://github.com/broadinstitute/xtermcolor>`__ - colorful messages on terminal
-----
Built with :two_hearts: by `Pravendra Singh <http://pravj.github.io>`__
Metadata
Release files for lisense 1.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 | |
|---|---|---|---|---|
| lisense-1.1.0.tar.gz | 65.1 kB | Without provenance | Details |
Release files / lisense-1.1.0.tar.gz
| Download URL | lisense-1.1.0.tar.gz |
|---|---|
| Size | 65.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
61e05abb770fde3836682941c47543bf46a01d6af8c91105fa16924ae9ddc04b
|
|
BLAKE2b-256 checksum How to use checksums |
f83cb14b0a22147a119ce430a7909470086798839ef362a8f1258b777351f7b8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for lisense 1.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.