Holidays are rendered as tuples about workalendar HOT 2 CLOSED

My original hope was that the PR would better justify and elucidate the purpose of this ticket, but because the PR is being rejected, I want to elaborate.

The use of tuples as implicit types also has ramifications for readability. The existing implementation is using tuples to "extend" the concept of date to also have a label, but this approach has two limitations.

First, it requires any user of these new date types to know that it is a tuple and to infer the meaning of the items in the tuple. Even a namedtuple would be better. Instead, you see code like this, that looks more like Lisp than Python:

days.append((date(year, month, day), label))

You also find code like this which must assign names to the parts of the tuple in order to reference just one relevant part of it:

set([day for day, label in self.holidays(year)])

The second problem that arises is that there's no way for a client library or consumer of this library to extend the meaning of those constructs. Because they're tuples which have a specific meaning, providing additional detail, such as a observance shift, is simply not possible.

from workalendar.

If this feature would be of value to you, consider the calendra fork.

from workalendar.