Mariadb-dyncol

------------------

* Update Python support to 3.5-3.8, as 3.4 has reached its end of life.
* Converted setuptools metadata to configuration file. This meant removing the
``__version__`` attribute from the package. If you want to inspect the
installed version, use
``importlib.metadata.version("mariadb-dyncol")``
(`docs <https://docs.python.org/3.8/library/importlib.metadata.html#distribution-versions>`__ /
`backport <https://pypi.org/project/importlib-metadata/>`__).

------------------

* Drop Python 2 support, only Python 3.4+ is supported now.

------------------

* Use ``utf8mb4`` character set for encoding strings. This seemed to be broken
for emoji on older versions of MariaDB (10.1 or 10.2?), so ``utf8`` was
previously used, however this may have only been a display/``COLUMN_JSON``
issue on such older versions. MariaDB internally now defaults to ``utf8mb44``
for dynamic column strings. Since this changes the output of serialization
slightly, please test before upgrading. Also you probably want to use
``utf8mb4`` for everything else MariaDB in your application if you aren't
already - it is the default on MySQL 8+.

------------------

* Fix a packaging error which caused the tests to be installed alongside the
package.
* Don't pin version of ``six`` to 1.9.0

------------------

* Disallowed ``str`` values on Python 2 - always use ``unicode``
* Added a benchmark script and made some optimizations that add up to a speed
boost of about 10%.

------------------

* Tests now verify every operation against MariaDB's ``COLUMN_CHECK`` and
``COLUMN_CREATE`` functions
* Fixed column order when >1 UTF8 byte characters are involved
* Fix encoding ``int``\s around size boundaries
* Fix encoding ``time``\s and ``datetime``\s with microseconds=0
* Fix encoding float ``-0.0``
* Fix a data size boundaries off-by-one error
* Fix decoding ``utf8mb4`` strings