www/py-django-filter: Update to 24.3

Changelog since 23.5:

https://github.com/carltongibson/django-filter/blob/24.3/CHANGES.rst

*: Switch consumers over to Django 4.2

Django 3.2 reached its End-of-Life on 1st April 2024 and Django 4.2 is
the new LTS (= Long Term Support) release which will be supported until
April 2026.

* Switch most ports that use www/py-django32 to www/py-django42.

* Ports that are not compatible with Django 3.2 have already been set
  with an expiration date were not taken into account.

* Bump PORTREVISION due dependency change where necessary.

PR:		276319
Reviewed by:	dvl, grembo, ultima
Approved by:	bofh (implicit), dvl, grembo, Kevin Golding, sunpoet,
		ultima, maintainer timeout (remaining maintainers)
Differential Revision:	https://reviews.freebsd.org/D44637

www/py-django-filter: Update to 23.5

Changelog:

https://github.com/carltongibson/django-filter/blob/23.5/CHANGES.rst

www/py-django-filter: Update to 23.4

Changelog:

https://github.com/carltongibson/django-filter/blob/23.4/CHANGES.rst

www/py-django-filter: Update to 23.3

* Switch to PEP517 build framework.

* Pet portclippy.

Changelog since 22.1:

https://github.com/carltongibson/django-filter/blob/23.3/CHANGES.rst

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/py-django-filter: Update to 22.1

Changelog:

https://github.com/carltongibson/django-filter/blob/22.1/CHANGES.rst

MFH:		No (not compatible with www/py-wagtail in 2022Q3)

net-mgmt/netbox: Create Django 4.0 consumers

* Django 3.2 is currently the "default" version in the ports tree due
  its long term support until April 2024.  Thus ports that are assigned
  to that version will exist until then.

  The following ports are required to make the upgrade of
  net-mgmt/netbox to the 3.2 release possible because it requires Django
  4.0.

  All of the ports listed below were created on the basis of their
  respective original ports:

  - devel/py-dj40-django-rq
  - devel/py-dj40-graphene-django

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-filter: Update to 21.1

* Upstream switched to a two-part CalVer versioning scheme where the
  first number is the year and the second is the release number within
  that year.

Changelog:

https://github.com/carltongibson/django-filter/blob/21.1/CHANGES.rst

*: Create Django 3.2 ports for net-mgmt/netbox

* Django 2.2 is currently the "default" version in the ports tree due
  its long term support until April 2022.  Thus ports that are assigned
  to that version will exist until then.

  The following ports are required to make the upgrade of
  net-mgmt/netbox to the 2.11 release possible because it requires
  Django 3.2.  All of the ports listed below were created on the basis
  of their respective original ports:

  - devel/py-dj32-django-rq
  - www/py-dj32-django-auth-ldap
  - www/py-dj32-django-cacheops (updated to a newer release)
  - www/py-dj32-django-cors-headers

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

Remove # $FreeBSD$ from Makefiles.

www/py-django-filter: Update to 2.4.0

* Improve pkg-descr while I'm here.

Changelog:

https://github.com/carltongibson/django-filter/releases/tag/2.4.0

Create some ports that are assigned to Django 3.1 instead Django 2.2

* Django 2.2 is currently the "default" version in the ports tree due its
  long term support until April 2022.  Thus ports that are assigned to that
  version will exist until then.

  The following ports are required to make the upgrade of net-mgmt/netbox to
  the 2.9 release possible because it requires Django 3.1 and provides no
  backwards compatibility for previous versions of Django.

  - www/py-dj31-django-rq
      (copied from r539662 to use the 2.3.2 release for now)
  - www/py-dj31-django-auth-ldap
  - www/py-dj31-django-cacheops
  - www/py-dj31-django-cors-headers

www/py-django-filter: Update to 2.3.0

Changelog:

https://github.com/carltongibson/django-filter/blob/2.3.0/CHANGES.rst

Assign some ports I maintain from Django 1.11 to Django 2.2

Django 1.11 is End-of-Life since April 2020 thus switch the following ports
to Django 2.2 (which has LTS support until April 2022):

* www/py-django-auth-ldap
* www/py-django-cacheops
* www/py-django-filter
* www/py-django-prometheus

Adjust the required Python version as Django 2.2 needs at least Python 3.5+
and bump the PORTREVISION for package change.

Mark the related py-dj22-* port variants as DEPRECATED because they're
obsolete now.  Don't set an expiration date yet as they're still used by
some consumers and a few more Django 1.11 ports need to be assigned to
Django 2.2 first.

www/py-django-filter: Update to 2.2.0

Changelog:

* Added DjangoFilterBackend.get_schema_operation_parameters() for DRF 3.10+
* OpenAPI schema generation
* Added lookup_expr to MultipleChoiceFilter
* Dropped support for EOL Python 3.4

https://github.com/carltongibson/django-filter/releases/tag/2.2.0

net-mgmt/netbox: Update to 2.5.12 and switch to Django 2.2

Upstream decided to switch from Django 2.1 to the 2.2 LTS release to fix a
rather annoying bug that generated intermittent errors when objects were
deleted/manipulated.

Therefore the same procedure must be done in almost the same way as in
r492690 to make NetBox compatible with Django 2.2 in the ports tree.

That means to repocopy the required Django 1.11 ports, assign them to
Django 2.2, limit them to Python 3.5+ and update all related
CONFLICTS_INSTALL entries accordingly:

* www/py-dj22-django-cors-headers [1]
* www/py-dj22-django-debug-toolbar

www/py-django-filter: Update to 2.1.0

* Remove optional dependencies that are not required for runtime.
* Limit the port to Python 3.4 or later because the support for Python 2 was
  dropped with the 2.0.0 release.

Notable changes since 1.1.0:

* Fixed a regression in FilterView introduced in 2.0. An empty QuerySet was
  incorrectly used whenever the FilterSet was unbound (i.e. when there were
  no GET parameters). The correct, pre-2.0 behaviour is now restored.
* Drop Python 2, Django < 1.11 support
* Added Django 2.0 support
* Many other bugfixes, for a full changelog see:

https://github.com/carltongibson/django-filter/blob/2.1.0/CHANGES.rst

Approved by:	mentors (implicit)

Remove dependency on the django metaport

With hat:	portmgr

Create some ports that are assigned to Django 2.1 instead Django 1.11.

Django 1.11 is currently the "default" version in the ports tree due its
long term support until April 2020 thus ports that are assigned to that
version will exist until then.

The following packages are required to make the upgrade of net-mgmt/netbox
to 2.5.x possible because upstream has decided to switch from Django 1.11
to Django 2.1:

* www/py-dj21-django-cors-headers
* www/py-dj21-django-debug-toolbar
* www/py-dj21-django-filter
* www/py-dj21-django-js-asset
* www/py-dj21-django-mptt

Change my maintainer email address to my new one at the FreeBSD project.

Reviewed by:	miwi (mentor)
Approved by:	miwi (mentor)
Differential Revision: https://reviews.freebsd.org/D19050

New port: www/py-django-filter: Dynamic filtering for querysets with Django

PR:		227007
Submitted by:	Kai <freebsd_ports@k-worx.org>