devel/py-pytest-asyncio: update 0.23.7 → 0.23.8

devel/py-pytest-asyncio: update 0.23.6 → 0.23.7

devel/py-pytest-asyncio: update 0.22.0 → 0.23.6

devel/py-pytest-asyncio: update 0.21.1 → 0.22.0

devel/py-pytest-asyncio: Remove outdated PYTHON_REL check after lang/python37
removal

Approved by:	portmgr (blanket)
With hat:	python

devel/py-pytest-asyncio: update 0.21.0 → 0.21.1

all: remove explicit versions in USES=python for "3.x+"

The logic in USES=python will automatically convert this to 3.8+ by
itself.

Adjust two ports that only had Python 3.7 mentioned but build fine
on Python 3.8 too.

finance/quickfix: mark BROKEN with PYTHON

libtool: compile:  c++ -DHAVE_CONFIG_H -I. -I../.. -I -I. -I.. -I../.. -I../C++
-DLIBICONV_PLUG -DPYTHON_MAJOR_VERSION=3 -Wno-unused-variable
-Wno-maybe-uninitialized -O2 -pipe -DLIBICONV_PLUG -fstack-protector-strong
-fno-strict-aliasing -DLIBICONV_PLUG -Wall -ansi
-Wno-unused-command-line-argument -Wpointer-arith -Wwrite-strings
-Wno-overloaded-virtual -Wno-deprecated-declarations -Wno-deprecated -std=c++0x
-MT _quickfix_la-QuickfixPython.lo -MD -MP -MF
.deps/_quickfix_la-QuickfixPython.Tpo -c QuickfixPython.cpp  -fPIC -DPIC -o
.libs/_quickfix_la-QuickfixPython.o
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean
'-Wno-uninitialized'? [-Wunknown-warning-option]
QuickfixPython.cpp:175:11: fatal error: 'Python.h' file not found
          ^~~~~~~~~~
1 warning and 1 error generated.

Reviewed by:	portmgr, vishwin, yuri
Differential Revision:	<https://reviews.freebsd.org/D40568>

devel/py-pytest-asyncio: update 0.20.3 → 0.21.0

*/*: rename CHEESESHOP to PYPI in MASTER_SITES

PR:			267994
Differential revision:	D37518
Approved by:		bapt

devel/py-pytest-asyncio: update 0.20.2 → 0.20.3

devel/py-pytest-asyncio: update 0.20.1 → 0.20.2

devel/py-pytest-asyncio: update 0.19.0 → 0.20.1

devel/py-pytest-asyncio: update 0.18.3 → 0.19.0, take maintainership

PR:		267525
Approved by:	jbeich@FreeBSD.org (maintainer)

Remove WWW entries moved into port Makefiles

Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.

This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.

Approved by:		portmgr (tcberner)

Add WWW entries to port Makefiles

It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.

Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.

There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.

devel/py-pytest-asyncio: convert to USE_PYTHON=pytest

devel/py-pytest-asyncio: update to 0.10.0

Changes:	https://github.com/pytest-dev/pytest-asyncio/compare/v0.18.2...v0.18.3
Reported by:	Repology

devel/py-pytest-asyncio: update to 0.18.2

PR:		256624, 262884
Approved by:	jbeich (maintainer)

devel/py-pytest4-{asyncio,cov}: preserve pytest4 counterparts of corresponding
ports

PR:		256624

One more small cleanup, forgotten yesterday.
Reported by:	lwhsu

Remove # $FreeBSD$ from Makefiles.

devel/py-pytest-asyncio: update to 0.10.0

Changes:	https://github.com/pytest-dev/pytest-asyncio/compare/v0.9.0...v0.10.0

devel/py-pytest-asyncio: update to 0.9.0

Changes:	https://github.com/pytest-dev/pytest-asyncio/compare/v0.8.0...v0.9.0

Use PY_FLAVOR for dependencies.

FLAVOR is the current port's flavor, it should not be used outside of
this scope.

Sponsored by:	Absolight

Switch all pypi.python.org WWWs to a new PyPi home pypi.org where
they now redirect to anyway. All new urls checked to return 200,
I've fixed a couple of them in the process.

Approved by:	portmgr blanket, mat

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

devel/py-pytest-asyncio: remove always false conditional after r449654

devel/py-pytest-asyncio: update to 0.8.0

Changes:	https://pypi.python.org/pypi/pytest-asyncio#id1

devel/py-pytest-asyncio: update to 0.7.0

Changes:	https://pypi.python.org/pypi/pytest-asyncio#id1

devel/py-pytest-asyncio: update to 0.6.0

Changes:	https://pypi.python.org/pypi/pytest-asyncio#id1

devel/py-pytest-asyncio: unbreak with python < 3.x by default

=======================<phase: run-depends    >============================
===>   py35-pytest-asyncio-0.5.0 depends on package: py35-pytest>=3.0.2 - not
found
===>   py35-pytest-asyncio-0.5.0 depends on package:
/packages/All/py35-pytest-3.0.3.txz - not found
===>   USE_PACKAGE_DEPENDS_ONLY set - not building missing dependency from
source
*** [run-depends] Error code 1

Reported by:	pkg-fallout

Oops, mark as NO_ARCH

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