ae4a1a485a
If a Python package does not come with either `format` or `pyproject` we consider it a setuptools build, that calls `setup.py` directly, which is deprecated. This change, as a first step, migrates a large chunk of these packages to set setuptools as their explicit format This is so we can unify the problem space for the next step of the migration.
42 lines
860 B
Nix
42 lines
860 B
Nix
{
|
|
lib,
|
|
callPackage,
|
|
buildPythonPackage,
|
|
fetchPypi,
|
|
mkdocs,
|
|
jinja2,
|
|
python-dateutil,
|
|
termcolor,
|
|
pyyaml,
|
|
}:
|
|
|
|
buildPythonPackage rec {
|
|
pname = "mkdocs-macros-plugin";
|
|
version = "1.0.5";
|
|
format = "setuptools";
|
|
|
|
src = fetchPypi {
|
|
inherit pname version;
|
|
hash = "sha256-/jSNdfAckR82K22ZjFez2FtQWHbd5p25JPLFEsOVwyg=";
|
|
};
|
|
|
|
propagatedBuildInputs = [
|
|
jinja2
|
|
termcolor
|
|
python-dateutil
|
|
pyyaml
|
|
mkdocs
|
|
];
|
|
|
|
passthru.tests.example-doc = callPackage ./tests.nix { };
|
|
|
|
pythonImportsCheck = [ "mkdocs_macros" ];
|
|
|
|
meta = with lib; {
|
|
homepage = "https://github.com/fralau/mkdocs_macros_plugin";
|
|
description = "Create richer and more beautiful pages in MkDocs, by using variables and calls to macros in the markdown code";
|
|
license = licenses.mit;
|
|
maintainers = with maintainers; [ tljuniper ];
|
|
};
|
|
}
|