The europe.py file starts to be quite big, should we start splitting calendars?

[Natim]

I think a file per country could make it easier to maintain.

europe.py → europe/_init.py, europe/estonia.py, europe/france.py, europe/swiss.py, etc...

[brunobord]

good idea

[Natim]

I am starting the work here: #136
But I feel like usa.py and core.py might need to have the same treatment.

[brunobord]

But I feel like usa.py and core.py might need to have the same treatment.

AFAICT, usa.py won't evolve, since all the US states are in, and, except if global geopolitics changes happen, there won't be new states. Maybe, at some point, if Asian calendars are incoming, we may have to split (too) big modules

[Natim]

Does it means that I do not need to split usa.py and core.py ?

[brunobord]

@Natim for the "usa.py" I don't see the point. for the "core.py", I don't know for sure, but I wouldn't do it in this PR, maybe in another, when #135 is closed.

[brunobord]

merged, thanks a lot.