Marc Hernández
Marc Hernández
SECURITY: bad regex pattern in 'dateparser/languages/locale.py' will cause 'ReDos' security problem.
Hi @leveryd I tried running `%time search_dates("x"*100000+"x")` (note that the first character is an "x") and I got: ``` CPU times: user 3min 27s, sys: 6.04 s, total: 3min 33s...
Added a comment in this related issue: https://github.com/scrapinghub/dateparser/issues/679 linking to a draft PR with a possible workaround.
_Maybe_ we could move the `date_formats` to the settings instead of using a parameter. I didn't think this to much, but it could make sense to change this API (first...
could this be the reason behind this? :thinking: https://github.com/scrapinghub/dateparser/issues/857
Hi @thomasleveil Is not "incompatibility" but something not documented: "now the `Locale.translate()` method only accepts Unicode strings". To fix it, you can pin an old version of dateparser (0.7.4), but...
hey, yeah, really interesting, thanks @abdulniyaspm!
Updated @Gallaecio
It sounds interesting. We could also use a parameter like `join_delimiter` or something like that to choose how to join the followed numbers (that are followed omitting spaces, commas, etc)....
Here ("Using neither" section): https://en.wikipedia.org/wiki/Long_and_short_scales#Using_neither there is a list of different numeral systems.
BTW, this resource has a lot of useful information: https://www.languagesandnumbers.com/site-map/en/