Use a new jinja2 templating process to update library to latest unicode (14.0)

[jquast]

• update tox.ini, requirements* files
  • use pip-compile with "requirements.in" files to generate "requirements.txt" files
  • use older testing tools for older python versions (requirements-tests38.in and requirements-tests39.in)
  • use python3.10 for most build steps
• bin/update-tables.py changes,
  • use https
  • use jinja2 (.j2) templating to generate code and documentation,
    • easier to support code generation of other languages
  • unreliable connection support using tenacity library to retry on connection timeout, etc.
  • optional --check-last-modified will compare last-modified for redownload
    • a unicode.org data file was only once updated for a botched release
• for wcwidth/table*.py files
  • uses new template system to generate new table data files for unicode version 14
  • when a description of unicode is single codepoint, describe only as 'A' instead of 'A..A'

[lgtm-com]

This pull request fixes 2 alerts when merging bbe041b into 4d45480 - view on LGTM.com

fixed alerts:

• 2 for Variable defined multiple times

[jquast]

thanks for the help, I'll merge & release in ~8 hours or so, I just want to be sure I am home to address any issues in release, and maybe address a few small open issues as well, #22, #24, #55, #56.

With any luck I will be able to work on Cythonification tomorrow, I found this stack overflow solution that addresses my concern, that we can include a cython or c extension as optional and fallback to pure python if it is not able to compile, https://stackoverflow.com/questions/41778153/compiling-an-optional-cython-extension-only-when-possible-in-setup-py

[GalaxySnail]

thanks for the help, I'll merge & release in ~8 hours or so, I just want to be sure I am home to address any issues in release, and maybe address a few small open issues as well, #22, #24, #55, #56.

Thanks for your efforts! Everything LGTM. Updating to python 3.11 in tox.ini can be done in another PR.

With any luck I will be able to work on Cythonification tomorrow, I found this stack overflow solution that addresses my concern, that we can include a cython or c extension as optional and fallback to pure python if it is not able to compile, https://stackoverflow.com/questions/41778153/compiling-an-optional-cython-extension-only-when-possible-in-setup-py

This anwser looks really old, we have pyproject.toml and PEP 517 nowadays. The get_requires_for_build_wheel hook and an in-tree build backend will be helpful. Please see: psycopg/psycopg#471 (comment). Also, I think it can be done in another PR.