Usually get_date_data will handle unparsable inputs by returning an dict with a None date_obj property. However, some inputs like this one cause it to raise errors:
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/home/nathan/venvs/main/local/lib/python2.7/site-packages/dateparser/date.py", line 371, in get_date_data
language, date_string, date_formats, settings=self._settings)
File "/home/nathan/venvs/main/local/lib/python2.7/site-packages/dateparser/date.py", line 168, in parse
return instance._parse()
File "/home/nathan/venvs/main/local/lib/python2.7/site-packages/dateparser/date.py", line 178, in _parse
date_obj = parser()
File "/home/nathan/venvs/main/local/lib/python2.7/site-packages/dateparser/date.py", line 199, in _try_parser
self._get_translated_date(), settings=self._settings)
File "/home/nathan/venvs/main/local/lib/python2.7/site-packages/dateparser/conf.py", line 84, in wrapper
return f(*args, **kwargs)
File "/home/nathan/venvs/main/local/lib/python2.7/site-packages/dateparser/date_parser.py", line 26, in parse
date_obj, period = parse(date_string, settings=settings)
File "/home/nathan/venvs/main/local/lib/python2.7/site-packages/dateparser/parser.py", line 84, in parse
raise exceptions.pop(-1)
TypeError: Required argument 'day' (pos 3) not found
Usually get_date_data will handle unparsable inputs by returning an dict with a None date_obj property. However, some inputs like this one cause it to raise errors:
Error:
Dateparser version: 0.6.0 Python version: 2.7.6