Adam Ryan reported a problem in the relativedelta implementation which

affected the yearday parameter in the month of January specifically.
This has been unittested and fixed.

3 files changed, 22 insertions, 1 deletions

diff --git a/NEWS b/NEWS
index a56018a..8738e84 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,19 @@
+
+Version 1.5
+-----------
+
+- As reported by Mathieu Bridon, rrules were matching the bysecond rules
+  incorrectly against byminute in some circumstances when the SECONDLY
+  frequency was in use, due to a copy & paste bug.  The problem has been
+  unittested and corrected.
+
+- Adam Ryan reported a problem in the relativedelta implementation which
+  affected the yearday parameter in the month of January specifically.
+  This has been unittested and fixed.
+
+- Updated timezone information.
+
+
 Version 1.4.1
 -------------
 
diff --git a/dateutil/relativedelta.py b/dateutil/relativedelta.py
index 562a7d3..6c722b2 100644
--- a/dateutil/relativedelta.py
+++ b/dateutil/relativedelta.py
@@ -190,7 +190,7 @@ Here is the behavior of operations with relativedelta:
                     if yday <= ydays:
                         self.month = idx+1
                         if idx == 0:
-                            self.day = ydays
+                            self.day = yday
                         else:
                             self.day = yday-ydayidx[idx-1]
                         break
diff --git a/test.py b/test.py
index ed23c03..049fede 100644
--- a/test.py
+++ b/test.py
@@ -131,6 +131,11 @@ class RelativeDeltaTest(unittest.TestCase):
         self.assertEqual(self.today+relativedelta(yearday=261),
                          date(2003, 9, 18))
 
+    def testYearDayBug(self):
+        # Tests a problem reported by Adam Ryan.
+        self.assertEqual(date(2010, 1, 1)+relativedelta(yearday=15),
+                         date(2010, 1, 15))
+
     def testNonLeapYearDay(self):
         self.assertEqual(date(2003, 1, 1)+relativedelta(nlyearday=260),
                          date(2003, 9, 17))