Closed raghur closed 4 years ago
I can confirm this. Any solution so far?
I submitted a pull request to fix this months ago but it was never merged: https://github.com/scrapinghub/dateparser/pull/530
Hi @raghur @Dimbreath this is fixed in the last version 0.7.4
:tada:
Even when 'PREFER_DATES_FROM' is set to 'future', without the 'in' keyword, the time returned in 1 min before.
Expectation is that if future dates are preferred, then
1 min
should return 1 min in future.