Remove expired ports:

2021-04-30 www/py-django111: Django 1.11 is End-of-Life since April 2020. Switch
to Django 2.2+ as soon as possible.
2021-04-30 archivers/par2cmdline-tbb: Unmaintained upstream, does not build with
oneTbb. Use archivers/par2cmdline instead

www/py-django111: Set to expire

* The port was already marked as DEPRECATED a year ago and all of its
  consumers have now been switched to Django 2.2 or newer versions.

PR:		245309
Approved by:	kai (python, maintainer)

Add new port: www/py-django32
Update CONFLICTS

Remove # $FreeBSD$ from Makefiles.

Remove PY_SPHINX from ports using Python 3

Approved by:	 portmgr blanket
Differential Revision:	https://reviews.freebsd.org/D28093

Drop python 2.7 support from a few ports

With hat:	portmgr

- Adjust CONFLICTS to welcome Django31

Update Sphinx

- Repocopy textproc/py-sphinx to textproc/py-sphinx18

  Update it to 1.8.5 (latest version from 1.8.X).
  This version supports Python 2 and 3.
  Add test target.

- textproc/py-sphinx: Update to 3.0.2

  Python 3 only (3.5+).
  Add test target.

- Mk/Uses/python.mk: Add PY_SPHINX

www/py-django111: Mark as DEPRECATED

Django 1.11 has reached its End-of-Life so mark it as DEPRECATED.  Don't set
an EXPIRATION_DATE yet as various consumers need to be switched to
Django 2.2 beforehand, which will happen in the next weeks/months.

When everything is complete there should be no py-dj22-* ports left and the
Ports tree has a few Python 2.7 packages less because Django 2.2 only
supports Python 3.5 or later.

Adjust the description of Django 1.11 of the www/py-django meta-port
accordingly.  Also fix a small typo in the Django 2.2 description while I'm
here.

PR:		245309
Reviewed by:	koobs, wen (via private e-mail)
Differential Revision:	https://reviews.freebsd.org/D24221

- Update Django to 3.0.4, 2.2.11 and 1.11.29(security release)
MFH:		2020Q1
Security:	CVE-2020-9402

Update to 1.11.28

Changes:	https://docs.djangoproject.com/en/1.11/releases/
Security:	5a45649a-4777-11ea-bdec-08002728f74c
MFH:		2020Q1

- Update Django to 1.11.27, 2.2.9 and 3.0.1
  (include security fix)

MFH:		2019Q4
Security:	CVE-2019-19844

- Adjust CONFLICTS_INSTALL to welcome py-django30

- Update django to 2.2.7, 2.1.14 and 1.11.26

- Update Django to 2.2.6, 2.1.13 and 1.11.25

Update to 1.11.24

Changes:	https://docs.djangoproject.com/en/1.11/releases/

Update to 1.11.23

Changes:	https://docs.djangoproject.com/en/1.11/releases/
Security:	6e65dfea-b614-11e9-a3a2-1506e15611cc
MFH:		2019Q3

- Update Django to 1.11.22, 2.1.10 and 2.2.3
  (include security fix)

MFH:	2019Q3

- Update Django to 1.11.21, 2.1.9 and 2.2.2(security releases)

MFH:		2019Q2

- Adjust CONFLICTS to welcome py-django22

- Update django to 1.11.20, 2.0.12 and 2.1.7

- Update CONFLICTS_INSTALL since py-django18 and py-django110 had been removed
from portstree

- Update django to 2.1.5, 2.0.10, and 1.11.18
  (include security fix)

MFH:		2019Q1
Security:	CVE-2019-3498

- Update to 1.11.17

- Update to 1.11.16

- Update django to 2.0.8 and 1.11.15
- Update CONFLICTS_INSTALL

- Update to 1.11.14

Use PY_FLAVOR for dependencies.

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

Sponsored by:	Absolight

Update to 1.11.13

Changes:	https://docs.djangoproject.com/en/1.11/releases/

Update to 1.11.12

Changes:	https://docs.djangoproject.com/en/1.11/releases/

- Update to 1.11.11

Update to 1.11.10

Changes:	https://docs.djangoproject.com/en/1.11/releases/1.11.10/
Security:	d696473f-9f32-42c5-a106-bf4536fb1f74
MFH:		2018Q1

databases/py-MySQLdb only supports Python 2, restrict ports that uses it.

Sponsored by:	Absolight

Update to 1.11.9

Changes:	https://docs.djangoproject.com/en/1.11/releases/1.11.9/

Django's fastcgi support was removed in 1.9

PR:		224332
Submitted by:	Shane <FreeBSD@ShaneWare.Biz>

Fixup building docs with sphinx, and cleanup.

Sponsored by:	Absolight

Update to 1.11.8

Changes:	https://docs.djangoproject.com/en/1.11/releases/1.11.8/

- Adjust CONFLICTS_INSTALL

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.11.7

Changes:	https://docs.djangoproject.com/en/1.11/releases/1.11.7/

Update to 1.11.6

Changes:	https://docs.djangoproject.com/en/1.11/releases/1.11.6/

Update to 1.11.5

Changes:	https://docs.djangoproject.com/en/1.11/releases/1.11.5/
Security:	aaab03be-932d-11e7-92d8-4b26fc968492
MFH:		2017Q3

Add comment about www/py-django

www/py-django: Add missing runtime dependency

pytz is now a required dependency for Django 1.11 and is strongly
recommended in older releases.

Django 1.11:

https://github.com/django/django/commit/414ad25b090a63eaaf297b1164c8f7d814a710a2

Older releases: docs/topics/i18n/timezones.txt

"3. Should I install pytz?
Yes. Django has a policy of not requiring external dependencies, and for
this reason pytz_ is optional. However, it's much safer to install it."

Reviewed by:	lwhsu
MFH:		2017Q3
Differential Revision:	https://reviews.freebsd.org/D11835

Update to 1.11.4

Changes:	https://docs.djangoproject.com/en/1.11/releases/1.11.4/

Update to 1.11.3

Changes:	https://docs.djangoproject.com/en/1.11/releases/1.11.3/

Update to 1.11.2

Changes:	https://docs.djangoproject.com/en/1.11/releases/1.11.2/

Update CONFLICTS_INSTALL

- Sort SHEBANG_FILES

- Update to 1.11.1

- Fix shebangs

- Repocopy www/py-django110 --> www/py-django111 and update to 1.11