Martin Weinelt ae4a1a485a
treewide: add explicit format attribute for Python packages
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.
2025-07-02 05:56:47 +02:00

49 lines
1.1 KiB
Nix

{
lib,
stdenv,
buildPythonPackage,
isPy3k,
fetchPypi,
pytest,
markupsafe,
setuptools,
}:
buildPythonPackage rec {
pname = "Jinja2";
version = "2.11.3";
format = "setuptools";
src = fetchPypi {
inherit pname version;
sha256 = "a6d58433de0ae800347cab1fa3043cebbabe8baa9d29e668f1c768cb87a333c6";
};
nativeCheckInputs = [ pytest ];
propagatedBuildInputs = [
markupsafe
setuptools
];
# Multiple tests run out of stack space on 32bit systems with python2.
# See https://github.com/pallets/jinja/issues/1158
# warnings are no longer being filtered correctly for python2
doCheck = !stdenv.hostPlatform.is32bit && isPy3k;
checkPhase = ''
pytest -v tests -W ignore::DeprecationWarning
'';
meta = with lib; {
homepage = "http://jinja.pocoo.org/";
description = "Stand-alone template engine";
license = licenses.bsd3;
longDescription = ''
Jinja2 is a template engine written in pure Python. It provides a
Django inspired non-XML syntax but supports inline expressions and
an optional sandboxed environment.
'';
maintainers = with maintainers; [ pierron ];
};
}