On Mar 16, 3:08 pm, a...@pythoncraft.com (Aahz) wrote: > In article <roy-c75465.16270015032...@news.panix.com>, > Roy Smith <r...@panix.com> wrote: > > >In article <mailman.1915.1237140862.11746.python-l...@python.org>, > > Chris Rebert <c...@rebertia.com> wrote: > > >> Besides your behavior, one could equally well argue that a 31st repeat > >> on months without a 31st should just be dropped, or that it should > >> carry over onto the 1st of the next month (ignoring the complications > >> of February). Which behavior one needs is completely > >> context-dependent. > > >Indeed. For example, my wife started her current job on a Feb 29th. There > >are significant financial events that happen on various anniversaries of > >her employment (vesting of stock and retirement benefits). It really is > >important that everybody know exactly what is meant by "10 years from Feb > >29th, on a given year", and what it means in one context may not mean what > >it means in another. > > Because I'm well-aware of such issues, I would have asked to make my > official start date March 1. ;-)
Which means that any goodies accruing after 4, 8, etc years are granted on 1 March instead of the (obvious?) 29 February. What you want is an agreement that the anniversary of commencement in any year is the last day of February. -- http://mail.python.org/mailman/listinfo/python-list
