This has been happening from the past week or so. Discarded it as a transient thing initially, but looks like it is persisting. So thought of reporting the same. Any pointers will be helpful.
File "/usr/local/lib/python3.11/dist-packages/kiteconnect/connect.py", line 433, in trades return self._format_response(self._get("trades")) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/dist-packages/kiteconnect/connect.py", line 409, in _format_response item[field] = dateutil.parser.parse(item[field]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/dist-packages/dateutil/parser/_parser.py", line 1374, in parse return DEFAULTPARSER.parse(timestr, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/dist-packages/dateutil/parser/_parser.py", line 657, in parse six.raise_from(ParserError(e.args[0] + ": %s", timestr), e) File "", line 3, in raise_from dateutil.parser._parser.ParserError: year 0 is out of range: 0000-01-01 11:07:45
We checked for one of our id and it seems fine.