➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author belopolsky
Recipients Esben.Agerbæk.Black, belopolsky, lemburg, pitrou, vstinner
Date 2012-04-10.02:56:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7h-xY9sULgFXZUrCPq7o_Lc27L_8atUy0XWwCQ0srJYMN7Bg@mail.gmail.com>
In-reply-to <4F8370A6.9010405@egenix.com>
Content 
On Mon, Apr 9, 2012 at 7:28 PM, Marc-Andre Lemburg
<report@bugs.python.org> wrote:
> You don't really expect anyone to remember such rules, do you ? :-)

No, but it is still a one-line function that those who need it can
easily implement.  I am on the fence here because we already have
date.isocalendar() function, so it is natural to desire its inverse,
but still at least on this side of the pond an Easter(year) date
constructor would see more use than that.
History
Date User Action Args
2012-04-10 02:56:46belopolskysetrecipients: + belopolsky, lemburg, pitrou, vstinner, Esben.Agerbæk.Black
2012-04-10 02:56:45belopolskylinkissue14423 messages
2012-04-10 02:56:45belopolskycreate