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 Esben.Agerbæk.Black
Recipients Esben.Agerbæk.Black, belopolsky, lemburg, pitrou
Date 2012-04-10.09:48:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CADonfAR6Phm4rZ7uFJA3OjVvMYdyunmOq_WN0xq9bfPVcpAycA@mail.gmail.com>
In-reply-to <1334011854.3379.53.camel@localhost.localdomain>
Content
I believe that it is a good solution to have, for lack of a better term;
bi-directional features so
in my opinion .isocalendar()  merits having a constructor that takes an ISO
format.

Sadly no :-(
I looked it over once more and it seems there is an error where the date is
not offset correctly
for years beginning on Tuesday, Wednesday or Thursday.
I will updater my patch ASAP.

+        if self.isocalendar()[1] != 1:
+            if self.weekday() > 3:  # Jan 1 is not in week one

+                 self += timedelta(7 - self.weekday())

+        else:

+            self -= timedelta(self.weekday())

----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue14423>
> _______________________________________
>
History
Date User Action Args
2012-04-10 09:48:21Esben.Agerbæk.Blacksetrecipients: + Esben.Agerbæk.Black, lemburg, belopolsky, pitrou
2012-04-10 09:48:20Esben.Agerbæk.Blacklinkissue14423 messages
2012-04-10 09:48:20Esben.Agerbæk.Blackcreate