textproc/py-sphinx-material0.0.36_5

*/*: Bump consumers of www/beautifulsoup4 after port rename

PR:		297837
Approved by:	wen (maintainer via email)

textproc/py-sphinx-material: fix build with python 3.12

PR:		296707

textproc/py-sphinx-material: unbreak the ports tree

textproc/py-sphinx-material: supports Python up to 3.11

- Do not try to build it with Python ≥ 3.12;

- Mark deprecated (no ports dependent upon this port any more,
  and upstream dev is suspended).

See https://github.com/bashtage/sphinx-material/issues/141 .

*/*: switch dependency from devel/py-lxml5 to devel/py-lxml

Currently, there are two versions of python XML processing library
which conflict each other in the ports tree, namely:
- devel/py-lxml5 (now at version 5.4.0)
- devel/py-lxml  (now at version 6.0.1)

To avoid the situation that some ports depend on py-lxml5 and some
others do on py-lxml (by switching dependencies individually), this
commit switches the dependencies from py-lxml5 to py-lxml at once.

Additional note: There are still two ports (textproc/py-rdflib and
www/py-draftjs-exporter) depending on py-lxml5 since they limit upper
version to less than 6.

PR:		289491
Approved by:	Michiel van Baak Jansen <michiel@vanbaak.eu>, arrowd,
		crees, madpilot, delphij, marcus, nivit, kai,
		skreuzer, fluffy, bofh, thierry, stephen, sunpoet,
		0mp, Eric Camachat <eric@camachat.org>

*/*: update dependency on devel/py-lxml to devel/py-lxml5

www/py-beautifulsoup has switched dependency on devel/py-lxml to
devel/py-lxml5.

Ports which directly or indirectly depends on both
www/py-beautifulsoup and devel/py-lxml must also switch their
dependencies on devel/py-lxml to devel/py-lxml5 to avoid conflicts.

PR:		288047
Approved by:	portmgr (chase dependency change)

python.mk: rename PYTHON_EXT_SUFFIX to PYTHON_TAG, document, etc

EXT_SUFFIX, according to PEP 3149, refers to the full tag and
extension for compiled extension module objects, eg .cpython-311.so,
.cpython-313t.so, etc. We do not use the correct semantic meaning,
and this usage becomes ambiguous and confusing when tags do not
match between bytecode and compiled extension module objects.

Rename our PYTHON_EXT_SUFFIX to PYTHON_TAG to align with PEP 3147's
specification of a magic tag, which consists of implementation name
and shorthand version only. This is meant for bytecode and other
files containing this tag in their filename that do not depend on
a specific Python ABI for the same version. Chase all existing
consumers.

Introduce PYTHON_SOABI to align with PEP 3149's specification of a
tag, which consists of implementation name, shorthand version and
any ABI flags present (this and PYTHON_TAG are identical without
ABI flags). This is meant for compiled extension module objects and
other files that depend on a specific Python ABI for the same
version.

Add documentation for these variables that our PYTHON_EXT_SUFFIX
never had.

PR: 274671
Event: Kitchener-Waterloo Hackathon 202506

python: bump all USE_PYTHON=distutils consumers after RUN_DEPENDS removal

Any missed ports, feel free to bump.

Any ports that need setuptools at runtime can have the devel/py-setuptools
manually added back to RUN_DEPENDS, but understand that this practice
is deprecated; see CHANGES for details.

textproc/py-sphinx-material: adding a Material Design theme for Sphinx documentation