head	1.1;
access;
symbols
	pkgsrc-2026Q1:1.1.0.24
	pkgsrc-2026Q1-base:1.1
	pkgsrc-2025Q4:1.1.0.22
	pkgsrc-2025Q4-base:1.1
	pkgsrc-2025Q3:1.1.0.20
	pkgsrc-2025Q3-base:1.1
	pkgsrc-2025Q2:1.1.0.18
	pkgsrc-2025Q2-base:1.1
	pkgsrc-2025Q1:1.1.0.16
	pkgsrc-2025Q1-base:1.1
	pkgsrc-2024Q4:1.1.0.14
	pkgsrc-2024Q4-base:1.1
	pkgsrc-2024Q3:1.1.0.12
	pkgsrc-2024Q3-base:1.1
	pkgsrc-2024Q2:1.1.0.10
	pkgsrc-2024Q2-base:1.1
	pkgsrc-2024Q1:1.1.0.8
	pkgsrc-2024Q1-base:1.1
	pkgsrc-2023Q4:1.1.0.6
	pkgsrc-2023Q4-base:1.1
	pkgsrc-2023Q3:1.1.0.4
	pkgsrc-2023Q3-base:1.1
	pkgsrc-2023Q2:1.1.0.2
	pkgsrc-2023Q2-base:1.1;
locks; strict;
comment	@# @;


1.1
date	2023.06.17.17.41.50;	author wiz;	state Exp;
branches;
next	;
commitid	vOv5RJKYd56UgktE;


desc
@@


1.1
log
@devel/py-plaster: import py-plaster-1.1.2

plaster is a loader interface around multiple config file formats.
It exists to define a common API for applications to use when they
wish to load configuration. The library itself does not aim to
handle anything except a basic API that applications may use to
find and load configuration settings. Any specific constraints
should be implemented in a pluggable loader which can be registered
via an entrypoint.
@
text
@# $NetBSD$

DISTNAME=	plaster-1.1.2
PKGNAME=	${PYPKGPREFIX}-${DISTNAME}
CATEGORIES=	devel python
MASTER_SITES=	${MASTER_SITE_PYPI:=p/plaster/}

MAINTAINER=	pkgsrc-users@@NetBSD.org
HOMEPAGE=	https://docs.pylonsproject.org/projects/plaster/en/latest/
COMMENT=	Loader interface around multiple config file formats
LICENSE=	mit

TEST_DEPENDS+=	${PYPKGPREFIX}-test-[0-9]*:../../devel/py-test

USE_LANGUAGES=	# none

PYTHON_VERSIONS_INCOMPATIBLE=	27

TEST_ENV+=	PYTHONPATH=${WRKSRC}/build/lib
do-test:
	cd ${WRKSRC} && ${SETENV} ${TEST_ENV} pytest-${PYVERSSUFFIX}

.include "../../lang/python/egg.mk"
.include "../../mk/bsd.pkg.mk"
@
