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>

*/*: rename CHEESESHOP to PYPI in MASTER_SITES

PR:			267994
Differential revision:	D37518
Approved by:		bapt

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.

www: remove 'Created by' lines

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

  *
  *  <hvo.pm@xs4all.nl>
  *  Aaron Dalton <aaron@FreeBSD.org>
  *  Aaron Dalton <aaron@daltons.ca>
  *  Aaron LI <aly@aaronly.me>
  *  Aaron Zauner <az_mail@gmx.at>
  *  Abel Chow <achow@transoft.net>
  *  Adam Weinberger <adamw@FreeBSD.org>
  *  Ade Lovett <ade@FreeBSD.org>
  *  Adrian Steinmann <ast@marabu.ch>
  *  Akinori MUSHA aka knu <knu@idaemons.org>

www/py-django32: Switch consumers over to Django 3.2

Django 2.2 became End-of-Life on 11th April 2022 and Django 3.2 is the
new LTS (= Long Term Support) release which will be supported until
April 2024.

* Switch the most ports that use www/py-django22 to www/py-django32

* Switch www/seahub over to www/py-djangorestframework

* Ports that are not yet ready for Django 3.2 (only three so far) or
  those that have already been set with an expiration date were not
  taken into account.

* Bump PORTREVISION due dependency change where necessary.

PR:		261313
Reviewed by:	bofh, dvl, koobs, ultima
Approved by:	bofh, dvl, koobs, ultima, sunpoet, Kevin Golding, Ivan Rozhuk,
		Alexander Sieg (maintainers)
		maintainer timeout (remaining maintainers)
Differential Revision:	https://reviews.freebsd.org/D34859

www/py-django-contrib-comments: Update version 2.1.0=>2.2.0

Relnotes:
https://github.com/django/django-contrib-comments/releases/tag/2.2.0

*/*: Take maintainership

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

www/py-django-contrib-comments: Update to 2.1.0

Changelog:

https://github.com/django/django-contrib-comments/blob/2.1.0/HISTORY.rst

PR:		245309
Approved by:	koobs (maintainer)

Remove # $FreeBSD$ from Makefiles.

Drop python 2.7 support from a few ports

With hat:	portmgr

www/py-django-contrib-comments: Update to 1.9.1

Changelog:

  https://github.com/django/django-contrib-comments/blob/1.9.1/HISTORY.rst

- Switch to django111
- Bump PORTREVISION

Sponsored by:	iXsystems Inc.

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

- Update to 1.7.3
- Switch to django 1.8

PR:		213009
Submitted by:	myself
Approved by:	maintainer (koobs)

Remove ${PORTSDIR}/ from dependencies, categories v, w, x, y, and z.

With hat:	portmgr
Sponsored by:	Absolight

www/py-django-contrib-comments: Use Django 1.6 for RUN_DEPENDS

Default to using Django 1.6 (www/py-django16) because the current version
of www/py-django-mezzanine does not support anything later than 1.6, and
installation currently causes a conflict as installation of both django16
and django18 are attempted:

    py-django-mezzanine -> www/django16, www/py-django-contrib-comments
    py-django-contrib-comments -> www/django (1.8)

This fixes a new (py-django-mezzanine) failure in 2015Q4 reported by
pkg-fallout.

This is the least of all current evils, without having to update Mezzanine
to it's latest versions (*and* have to MFH that update). It has zero impact

www/py-django-contrib-comments: Fix *_DEPENDS

Update RUN_DEPENDS from file based back to PKGNAME based matching. Use
a glob pattern to match multiple version suffixed versions of the
Django ports, as `pkg info -g` is used to match them, excellent! [1]

This doesn't completely solve the problem for Django ports and their
dependencies, as there is still the issue of 'which' Django port to use
if:

 * The dependency is not yet satisfied (fresh installs), AND
 * The port that depends on Django supports multiple versions, like this
   one.

While I'm here:

- Mark architecture independent (NO_ARCH)
- Remove TEST_DEPENDS (no longer necessary)
- Rename test target since the framework supports all the things now.
- Update test target to include a default timezone, otherwise the
  test suite borks.

[1] Thanks antoine!

www/py-django-contrib-comments: Update to 1.6.1

- Update to 1.6.1
- Add LICENSE file
- Switch RUN_DEPENDS to file detection

This allows for an existing installation of py-djangoXY to be
identified, which avoids attempting to install py-django (currently
1.8), which will cause installation conflicts for Ports that depend on
contrib-comments, but DONT support Django 1.8 (eg: Mezzanine) and use
www/djangoXY ports.

www/py-django-contrib-comments: Fix typo: PYTHON_PKGNAMEPREFIX

- Fix typo in PYTHON_P(K)GNAMEPREFIX

[NEW] www/py-django-contrib-comments: Code formerly known as
django.contrib.comments

Django used to include a comments framework; since Django 1.6 it's been
separated to a separate project. This is that project.

This framework can be used to attach comments to any model, so you can use
it for comments on blog entries, photos, book chapters, or anything else.

WWW: https://github.com/django/django-contrib-comments