Menu

#616 Week numbering options

Release_0.78.0
open
windows
3
2013-02-08
2010-01-11
No

The following discussion took place in the TaskCoach Y! Group:

The 1st week of 2010, according to the calendar is the week from the 1st to the 2nd January. In TaskCoach, however, it is marked as the week from the 3rd to
the 9th January, which corresponds in fact to the 2nd week of 2010.

Task Coach uses the ISO standard for weeknumbers that's build into the Python programming language. To quote from the Python documentation:

"The ISO calendar is a widely used variant of the Gregorian calendar. See http://www.phys.uu.nl/~vgent/calendar/isocalendar.htm for a good explanation. The ISO year consists of 52 or 53 full weeks, and where a week starts on a Monday and ends on a Sunday. The first week of an ISO year is the first (Gregorian) calendar week of a year containing a Thursday. This is called week number 1, and the ISO year of that Thursday is the same as its Gregorian year." (Quoted from http://docs.python.org/library/datetime.html#datetime.date.isocalendar).

Is there a way to correct this in TaskCoach, or is it a System bug?

There's no way to configure this at the moment. Python does provide two other ways to calculate the week number:
- Week number of the year (Sunday as the first day of the week) as a decimal number [00,53]. All days in a new year preceding the first
Sunday are considered to be in week 0.
- Week number of the year (Monday as the first day of the week) as a decimal number [00,53]. All days in a new year preceding the first
Monday are considered to be in week 0.

Discussion

  • Frank Niessink

    Frank Niessink - 2010-01-11

    We could reproduce the bug you reported. We'll do our best to fix it as soon as possible.

    Thanks, Task Coach development team

     
  • Aaron Wolf

    Aaron Wolf - 2013-02-08
    • platform_s: --> windows
     
  • Aaron Wolf

    Aaron Wolf - 2013-02-08

    I don't understand what this is about. Is it still relevant in the current version?

     
  • Jérome Laheurte

    I'm not sure what the bug is: that we're using ISO week numbers or that we're supposed to be and it doesn't quite work ? Anyway AFAIK we didn't change anything related to this so it's probably still relevant, whatever it is.

     

Log in to post a comment.