Revert "Mk/Uses/python.mk: Fix USE_PYTHON=pep517: always compile and install
bytecode"

Despite installer's default behaviour to compile and install bytecode,
we are not doing so going forward at stage/package time. [0] During
initial development and qualification of PEP-517 framework support,
compiling and installing bytecode at stage/package time was considered,
but was found problematic, fragile and ultimately unreliable, both
currently and historically (with USE_PYTHON=distutils), due to our
fixed plist requirement. While the living binary distribution format
(wheel) specification [1] says to compile bytecode, that is in the
pure Python package management context (pip, etc); nuance always
exists when interacting with "system" package management.

Additionally, "bytecode is an implementation detail of the CPython
interpreter. No guarantees are made that bytecode will not be added,

Mk/Uses/python.mk: Fix USE_PYTHON=pep517: always compile and install bytecode

- While I'm here, use long options for easier reading [1][2]
- Bump PORTREVISION of dependent ports (USE_PYTHON=pep517) for package change

It fixes build_fs_violation of dependent ports in poudriere (with -t flag).
It is also the default behavior of installer [2].

from py-sphinx log:
=>> Checking for staging violations... done
=>> Error: Filesystem touched during stage (files must install to ${STAGEDIR}):
extra: usr/local/lib/python3.9/site-packages/importlib_metadata/__pycache__
=>> Cleaning up wrkdir

from installer documentation:
--compile-bytecode
    Possible choices: 0, 1, 2
    generate bytecode for the specified optimization level(s) (default=0, 1)
--no-compile-bytecode
    don’t generate bytecode for installed modules
    Default: False

With hat:	python
Reference:	https://pypa-build.readthedocs.io/en/stable/ [1]
		https://installer.pypa.io/en/stable/cli/installer/ [2]

security/py-tuf: Update version 2.0.0=>2.1.0

- Change to pep517 from distutils

Relnotes:
https://github.com/theupdateframework/python-tuf/releases/tag/v2.1.0

*/*: 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.

security/py-tuf: Update version 1.1.0=>2.0.0

Relnotes:
https://github.com/theupdateframework/python-tuf/releases/tag/v2.0.0

security: remove 'Created by' lines

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

  *  <ports@c0decafe.net>
  *  Aaron Dalton <aaron@FreeBSD.org>
  *  Adam Weinberger <adamw@FreeBSD.org>
  *  Ade Lovett <ade@FreeBSD.org>
  *  Aldis Berjoza <aldis@bsdroot.lv>
  *  Alex Dupre <ale@FreeBSD.org>
  *  Alex Kapranoff <kappa@rambler-co.ru>
  *  Alex Samorukov <samm@freebsd.org>
  *  Alexander Botero-Lowry <alex@foxybanana.com>
  *  Alexander Kriventsov <avk@vl.ru>
  *  Alexander Leidinger <netchild@FreeBSD.org>

security/py-tuf: Fix build with setuptools 61.0.0+

With hat:	python

security/py-tuf: Update version 1.0.0=>1.1.0

Relnotes: https://github.com/theupdateframework/python-tuf/releases/tag/v1.1.0

security/py-tuf: switch to USES=pytest, document failing tests

Reported by:	reprise
Approved by:	portmgr blanket

security/py-tuf: Update version 0.11.1=>1.0.0

- Add LICENSE_FILE_*

Relnotes:
https://github.com/theupdateframework/python-tuf/releases/tag/v1.0.0

*/*: Take maintainership

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

Remove # $FreeBSD$ from Makefiles.

Drop python 2.7 support from a few ports

With hat:	portmgr

security/py-tuf: Update to 0.11.1

  - Remove setup.py patch, we'll invoke tests directly for now

Changelog:

  https://github.com/theupdateframework/tuf/releases/tag/v0.11.1

Bump a few PORTREVISIONs after r498529

With hat:	portmgr

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

[NEW PORT] security/py-tuf: Framework for securing software update systems

TUF (The Update Framework) helps developers secure their new or existing
software update systems.

Software update systems are vulnerable to many known attacks, including
those that can result in clients being compromised or crashed. TUF helps
solve this problem by providing a flexible security framework that can
be added to software updaters.

WWW: https://www.updateframework.com