freebsd-ports/devel/py-pytest-asyncio/Makefile

# $FreeBSD$

PORTNAME=	pytest-asyncio
PORTVERSION=	0.8.0
CATEGORIES=	devel python
MASTER_SITES=	CHEESESHOP
PKGNAMEPREFIX=	${PYTHON_PKGNAMEPREFIX}

MAINTAINER=	jbeich@FreeBSD.org
COMMENT=	Py.test plugin providing fixtures and markers for asyncio

LICENSE=	APACHE20

RUN_DEPENDS=	${PYTHON_PKGNAMEPREFIX}pytest>=3.0.6:devel/py-pytest@${FLAVOR}

NO_ARCH=	yes
USES=		python:3.5+
USE_PYTHON=	autoplist distutils

.include <bsd.port.mk>
devel/py-pytest-asyncio: add new port asyncio code is usually written in the form of coroutines, which makes it slightly more difficult to test using normal testing tools. pytest-asyncio provides useful fixtures and markers to make testing easier. https://pypi.python.org/pypi/pytest-asyncio 2016-12-10 04:22:40 +01:00			`# $FreeBSD$`

			`PORTNAME= pytest-asyncio`
devel/py-pytest-asyncio: update to 0.8.0 Changes: https://pypi.python.org/pypi/pytest-asyncio#id1 2017-09-24 14:23:36 +02:00			`PORTVERSION= 0.8.0`
devel/py-pytest-asyncio: add new port asyncio code is usually written in the form of coroutines, which makes it slightly more difficult to test using normal testing tools. pytest-asyncio provides useful fixtures and markers to make testing easier. https://pypi.python.org/pypi/pytest-asyncio 2016-12-10 04:22:40 +01:00			`CATEGORIES= devel python`
			`MASTER_SITES= CHEESESHOP`
			`PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX}`

			`MAINTAINER= jbeich@FreeBSD.org`
			`COMMENT= Py.test plugin providing fixtures and markers for asyncio`

			`LICENSE= APACHE20`

Convert Python ports to FLAVORS. Ports using USE_PYTHON=distutils are now flavored. They will automatically get flavors (py27, py34, py35, py36) depending on what versions they support. There is also a USE_PYTHON=flavors for ports that do not use distutils but need FLAVORS to be set. A USE_PYTHON=noflavors can be set if using distutils but flavors are not wanted. A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been added to cope with Python ports that did not have the Python PKGNAMEPREFIX but are flavored. USES=python now also exports a PY_FLAVOR variable that contains the current python flavor. It can be used in dependency lines when the port itself is not python flavored. For example, deskutils/calibre. By default, all the flavors are generated. To only generate flavors for the versions in PYTHON2_DEFAULT and PYTHON3_DEFAULT, define BUILD_DEFAULT_PYTHON_FLAVORS in your make.conf. In all the ports with Python dependencies, the *_DEPENDS entries MUST end with the flavor so that the framework knows which to build/use. This is done by appending '@${PY_FLAVOR}' after the origin (or @${FLAVOR} if in a Python module with Python flavors, as the content will be the same). For example: RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}six>0:devel/py-six@${PY_FLAVOR} PR: 223071 Reviewed by: portmgr, python Sponsored by: Absolight Differential Revision: https://reviews.freebsd.org/D12464 2017-11-30 16:50:30 +01:00			`RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}pytest>=3.0.6:devel/py-pytest@${FLAVOR}`
devel/py-pytest-asyncio: add new port asyncio code is usually written in the form of coroutines, which makes it slightly more difficult to test using normal testing tools. pytest-asyncio provides useful fixtures and markers to make testing easier. https://pypi.python.org/pypi/pytest-asyncio 2016-12-10 04:22:40 +01:00
Oops, mark as NO_ARCH 2016-12-10 04:39:37 +01:00			`NO_ARCH= yes`
devel/py-pytest-asyncio: update to 0.7.0 Changes: https://pypi.python.org/pypi/pytest-asyncio#id1 2017-09-11 17:08:09 +02:00			`USES= python:3.5+`
devel/py-pytest-asyncio: add new port asyncio code is usually written in the form of coroutines, which makes it slightly more difficult to test using normal testing tools. pytest-asyncio provides useful fixtures and markers to make testing easier. https://pypi.python.org/pypi/pytest-asyncio 2016-12-10 04:22:40 +01:00			`USE_PYTHON= autoplist distutils`

devel/py-pytest-asyncio: remove always false conditional after r449654 2017-10-27 18:47:33 +02:00			`.include <bsd.port.mk>`