No apparent way to get a list of accepted regions for use with the region argument for parse.

[ismaelharunid]

No apparent way to get a list of accepted regions for use with the region argument for parse.
If there is it should be in the docs.
Also I went through the code and still not clear what exactly a region even is. ie US works but ID does not.
The following is an attempt to parse a date in Asia/Makassar timezone, to show that the region is either not working or there is not enough documentation to understand how to use it properly. Again Locale should only be about the content parsing in terms of format and language, it should not be part of timezone determination or reducing/eliminating ambiguity.

>>> import dateparser as dtp
>>> dtp.parse("March 29, 1961 6:24pm", region='id')
>>> dtp.parse("March 29, 1961 6:24pm", region='ID')
>>> dtp.parse("March 29, 1961 6:24pm", region='IDN')
>>> dtp.parse("March 29, 1961 6:24pm", region='360')
>>> dtp.parse("March 29, 1961 6:24pm", region='WITA')
>>> dtp.parse("March 29, 1961 6:24pm", region='Indonesia')
>>> dtp.parse("March 29, 1961 6:24pm", region='Makassar')
>>> dtp.parse("March 29, 1961 6:24pm", region='LMT')
>>> 

[noviluni]

There is a list of supported locales in the README.md: https://github.com/scrapinghub/dateparser#supported-languages-and-locales

The "region" means the second pair of letters, for example:

• en-AU --> region = AU (Australia)
• fr-CH --> region = CH (Switzerland)

It has no sense to list the regions as they are language-specific, but it could be a good idea to improve the documentation around the region parameter to explain this better.