Metadata-Version: 2.4
Name: mkdocs_licenseinfo
Version: 1.0.0
Summary: mkdocs extension to visualise package dependencies license information
Author-email: David J Pugh <djpugh@gmail.com>
Maintainer-email: David J Pugh <djpugh@gmail.com>
Project-URL: homepage, https://github.com/djpugh/mkdocs_licenseinfo
Project-URL: repository, https://github.com/djpugh/mkdocs_licenseinfo
Project-URL: documentation, https://djpugh.github.io/mkdocs_licenseinfo
Keywords: mkdocs,mkdocs-plugin,license,licenseinfo,documentation,sbom
Classifier: Environment :: Console
Classifier: Topic :: Software Development :: Libraries :: Python Modules
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.9
Classifier: Programming Language :: Python :: 3.10
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Classifier: Programming Language :: Python :: 3.13
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: MIT License
Classifier: Operating System :: Microsoft :: Windows
Classifier: Operating System :: POSIX :: Linux
Classifier: Operating System :: MacOS :: MacOS X
Classifier: Natural Language :: English
Requires-Python: >=3.9
Description-Content-Type: text/markdown
License-File: LICENSE
Requires-Dist: jinja2
Requires-Dist: mkdocs>=1.4
Requires-Dist: tomli>=2; python_version < "3.11"
Requires-Dist: uv
Dynamic: license-file

# mkdocs_licenseinfo


mkdocs extension to visualise package dependencies license information


## Introduction

`mkdocs_licenseinfo` resolves licence information directly from installed package metadata and PyPI, with dependency resolution via `uv` (falling back to installed metadata). No external licence-checking tools are required.


## Contributing

To see the contribution guidelines, see [docs/source/developing/index.md](docs/source/developing/index.md).

## Setting up for development

Create a virtual environment.
Install the package using ``pip install -e .[dev]``


Then add code to the package as appropriate - submodules can be created under ``src/mkdocs_licenseinfo``
Tests can be added to the tests folder



### CI

There are a set of CI checks:

* lint: ``nox -t lint``
* test: ``nox -t test``
* build: ``nox -t build``

specific subfolders can be passed to the test tag in nox: ``nox -t test -- <subfolder1> <subfolder2>``




## Versioning

It is important to track and version code, and to aid that with the python packages and models, ``setuptools_scm`` is used.
This links the version reported at ``__version__`` to the git tag (+ commit hash if appropriate), to reduce the amount of
places that need editing when changing versions.

For describing versions we are using semantic versioning ``<major>.<minor>.<patch>``. Increment the:

* ``<major>`` version when you make incompatible API changes,
* ``<minor>`` version when you add functionality in a backwards-compatible manner, and
* ``<patch>`` version when you make backwards-compatible bug fixes.

There are also codes for pre-releases and other descriptions (see https://semver.org/)

To create a version, use ``git tag <major>.<minor>.<patch>`` and then make sure to push that tag with ``git push origin <major>.<minor>.<patch>``,
or an equivalent tagging tool (e.g. Github releases).


# TODO

- [ ] Add sbom file links for serving (::license-embed)


------------

Repo created from nskit.recipes.python.package:PackageRecipe (version 0.0.post1.dev15+ga59b052.d20231223) using ``nskit``.

