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>

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.

net: remove 'Created by' lines

A big Thank You to the original contributors of these ports:

  *  <ports@c0decafe.net>
  *  Aaron Dalton <aaron@FreeBSD.org>
  *  Aaron Straup Cope <ascope@cpan.org>
  *  Aaron Zauner <az_mail@gmx.at>
  *  Adam Jette <jettea46@yahoo.com>
  *  Adam Weinberger <adamw@FreeBSD.org>
  *  Alan Eldridge <alane@geeksrus.net>
  *  Alex Bakhtin <Alex.Bakhtin@gmail.com>
  *  Alex Deiter <Alex.Deiter@Gmail.COM>
  *  Alex Dupre <ale@FreeBSD.org>
  *  Alex Dupre <sysadmin@alexdupre.com>

net/py-pynsq: Update version 0.9.0b1=>0.9.1

Relnotes: https://github.com/nsqio/pynsq/blob/master/setup.py

*/*: Take maintainership

all: return koobs' ports to the pool after safekeeping his commit bit.

Remove # $FreeBSD$ from Makefiles.

Change RUN_DEPENDS from py-tornado to py-tornado5

- Bump PORTREVISION for dependency change

Drop python 2.7 support from a few ports

With hat:	portmgr

net/py-pynsq: Update to 0.9.0b1

This beta brings Tornado > 5 support (our py-tornado port is > 5)

Changelog:

  https://github.com/nsqio/pynsq/blob/v0.9.0b1/ChangeLog.md

Use PY_FLAVOR for dependencies.

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

Sponsored by:	Absolight

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

Remove ${PORTSDIR}/ from dependencies, categories m, n, o, and p.

With hat:	portmgr
Sponsored by:	Absolight

net/py-pynsq: Update to 0.6.9, Modernize

- Update PORTVERSION and distinfo checksum (0.6.9)
- Update TEST_DEPENDS and test target
- Remove TESTS option bits accordingly
- Sort USE{S} entries
- Enable NO_ARCH (architecture independent)
- Patch setup.py to remove unnecessary tornado entry and exclude tests
  from installation, for a future upstream patch that adds tests to the
  PyPI sdist.

Changes:

  https://github.com/nsqio/pynsq/blob/v0.6.9/ChangeLog.md

Remove UNIQUENAME and LATEST_LINK.

UNIQUENAME was never unique, it was only used by USE_LDCONFIG and now,
we won't have conflicts there.

Use PKGBASE instead of LATEST_LINK in PKGLATESTFILE, the *only* consumer
is pkg-devel, and it works just fine without LATEST_LINK as pkg-devel
has the correct PKGNAME anyway.

Now that UNIQUENAME is gone, OPTIONSFILE is too. (it's been called
OPTIONS_FILE now.)

Reviewed by:	antoine, bapt
Exp-run by:	antoine
Sponsored by:	Absolight
Differential Revision:	https://reviews.freebsd.org/D3336

Update ports in the n* categories to not use GH_COMMIT.

With minor cleanups to make things simpler.

With hat:	portmgr
Sponsored by:	Absolight

- Convert ports of net/ to new USES=python

Approved by:	portmgr (implicit)

- Remove easy_install dependency
- Bump PORTREVISION to enforce a cleanup for the easy_install references

With hat:	python@
Approved by:	portmgr (implicit)

net/py-pynsq: Add LICENSE

- Add LICENSE (MIT), thanks Matt! [1]

[1] https://github.com/bitly/pynsq/issues/56

net/py-pynsq: Update to 0.5.1

- Update to 0.5.1
- Enable STAGE support
- Enable AUTOPLIST, delete pkg-plist
- Sort USE_* and GH_* sections
- Remove upstreamed setup.py patch and post-patch: target

Changes:

 https://github.com/bitly/pynsq/blob/v0.5.1/ChangeLog.md

Add NO_STAGE all over the place in preparation for the staging support (cat:
net)

net/py-pynsq: [NEW PORT] The official Python client library for NSQ

pynsq provides high-level nsq.Reader and nsq.Writer classes for building
consumers and producers and two low-level modules for both sync and async
communication over the NSQ Protocol (if you wanted to write your own
high-level functionality).

WWW: https://github.com/bitly/pynsq