646b892680
Some checks failed
Periodic Merges (6h) / master → staging-nixos (push) Failing after 12m50s
Periodic Merges (6h) / master → staging-next (push) Failing after 12m54s
Periodic Merges (24h) / merge-base(master,staging) → haskell-updates (push) Failing after 11m54s
Periodic Merges (6h) / staging-next → staging (push) Failing after 12m13s
Periodic Merges (24h) / staging-next-25.05 → staging-25.05 (push) Failing after 13m24s
Periodic Merges (24h) / release-25.05 → staging-next-25.05 (push) Failing after 14m28s
41 lines
1.2 KiB
Nix
41 lines
1.2 KiB
Nix
{
|
|
lib,
|
|
buildPythonPackage,
|
|
fetchFromGitHub,
|
|
unittestCheckHook,
|
|
setuptools,
|
|
}:
|
|
buildPythonPackage rec {
|
|
pname = "mdutils";
|
|
version = "1.8.0";
|
|
pyproject = true;
|
|
|
|
src = fetchFromGitHub {
|
|
owner = "didix21";
|
|
repo = "mdutils";
|
|
tag = "v${version}";
|
|
hash = "sha256-UBq6xSGG49zaRVWe2RmsCDkpa3vZFqKRJZQEVUegTSM=";
|
|
};
|
|
|
|
build-system = [ setuptools ];
|
|
|
|
nativeCheckInputs = [ unittestCheckHook ];
|
|
|
|
pythonImportsCheck = [ "mdutils" ];
|
|
|
|
meta = {
|
|
description = "Set of basic tools that can help to create Markdown files";
|
|
longDescription = ''
|
|
This Python package contains a set of basic tools that can help to create
|
|
a Markdown file while running a Python code. Thus, if you are executing a
|
|
Python code and you save the result in a text file, Why not format it? So
|
|
using files such as Markdown can give a great look to those results. In
|
|
this way, mdutils will make things easy for creating Markdown files.
|
|
'';
|
|
homepage = "https://github.com/didix21/mdutils";
|
|
changelog = "https://github.com/didix21/mdutils/releases/tag/${src.tag}";
|
|
license = lib.licenses.mit;
|
|
maintainers = [ lib.maintainers.azahi ];
|
|
};
|
|
}
|