textproc/py-docxtpl0.20.2

textproc/py-docxtpl: Update to 0.20.2

*/*: 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 (2nd attempt)

This is a follow up to the commit 230fb2661c78, which updated some
ports' dependencies on devel/py-lxml to devel/py-lxml5. It was an
attempt to follow the dependency change of
www/py-beautifulsoup. However, the switch was incomplete and broke
some other ports.

It has turned out that the ports depending on devel/py-lxml (at
version 4.9.3) does not limit their dependencies' upper bound to 4.x
except for one (devel/py-pymaven-patch). So updating them to
devel/py-lxml5 (at version 5.4.0) should cause no harm.

This commit switch dependencies of all the ports (except
devel/py-pymaven-patch) to devel/py-lxml5 avoid potential conflicts.

Co-authored-by: Daniel Engberg <diizzy@FreeBSD.org>

PR:		287144, 288047
Reported by:	makc (via ports-committers),
		vvd (PR 288047),
		diizzy (PR 287144)
Approved by:	portmgr (chase dependency change, unbreak build)
Fixes:		230fb2661c78 (*/*: update dependency on devel/py-lxml to devel/py-lxml5)

textproc/py-docxtpl: Update to 0.20.0

- Remove obsolete dependency [1]

PR:		284601
Reported by:	mail_of_sergey@mail.ru [1]

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-docxtpl: Add textproc/py-docxcompose dependency

PR:		279621
Reported by:	mail_of_sergey __at __ mail.ru

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>

textproc/py-docxtpl: New port: Python docx template engine

python-docx-template has been created because python-docx is powerful for
creating documents but not for modifying them.

The idea is to begin to create an example of the document you want to generate
with microsoft word, it can be as complex as you want: pictures, index tables,
footer, header, variables, anything you can do with word. Then, as you are
still editing the document with microsoft word, you insert jinja2-like tags
directly in the document. You save the document as a .docx file (xml format).
it will be your .docx template file.

Now you can use python-docx-template to generate as many word documents you
want from this .docx template and context variables you will associate.