Reading date '0000-00-00' from db does not result in python datetime.date objet but is converted to string

[txicos]

A date value of 0000-00-00 is apparently valid in mysql. When attempting to read this value from the db no conversion is made to a valid python date. it should at least be converted to None, instead of keeping the '0000-00-00' string.

follows an exemple:
mysql> select DT_TESTE from TABLE_TEST;
+-------------------+
| DT_TESTE |
+-------------------+
| 0000-00-00 |
| 0000-00-00 |
| 0000-00-00 |
| 2021-03-18 |
| 2021-03-18 |
| 2021-04-01 |

result after:
row = await cur.fetchall()
print(row)

('0000-00-00')
('0000-00-00')
('0000-00-00')
(datetime.date(2021, 3, 18))
(datetime.date(2021, 3, 18))
(datetime.date(2021, 4, 1))

[ITKewai]

Maybe because of

Unix time, or POSIX time, is a system for describing points in time, defined as the number of seconds elapsed since midnight proleptic Coordinated Universal Time (UTC) of January 1, 1970, not counting leap seconds.

[Nothing4You]

from MySQL 5.7 and MySQL 8.0 docs:

Invalid DATE, DATETIME, or TIMESTAMP values are converted to the “zero” value of the appropriate type (0000-00-00 or 0000-00-00 00:00:00), if the SQL mode permits this conversion. The precise behavior depends on which if any of strict SQL mode and the NO_ZERO_DATE SQL mode are enabled; see Section 5.1.11, “Server SQL Modes”.

from MariaDB docs docs:

MariaDB also supports 0000-00-00 as a special zero-date value, unless NO_ZERO_DATE is specified in the SQL_MODE. Similarly, individual components of a date can be set to 0 (for example: 2015-00-12), unless NO_ZERO_DATE is specified in the SQL_MODE. In many cases, the result of en expression involving a zero-date, or a date with zero-parts, is NULL. If the ALLOW_INVALID_DATES SQL_MODE is enabled, if the day part is in the range between 1 and 31, the date does not produce any error, even for months that have less than 31 days.