Anthony, may be we discovered a malfunction in Mercurial here?

I'm not so experienced with Mercurial until now.  To make
sure that I did not made a silly mistake I now did a fresh clone as
described here: http://www.roundup-tracker.org/code.html with the
command::

   hg clone http://hg.code.sf.net/p/roundup/code roundup-20160303-fresh
   
This file ``roundup/date.py`` looks okay to me:

pf@pfmaster-P170EM:pts/27 ~/roundup-20160303-fresh 51> hg log
roundup/date.py | head
Änderung:        4991:03505579abef
Nutzer:          Ralf Schlatterbeck <rsc@runtux.com>
Datum:           Sun Jun 21 20:55:21 2015 +0200
Zusammenfassung: Fix bug in (Date- or Interval-) Range parsing

Änderung:        4986:fe140bc0eaa9
Nutzer:          Ralf Schlatterbeck <rsc@runtux.com>
Datum:           Tue Apr 21 17:33:06 2015 +0200
Zusammenfassung: Implement (and document) timezone offsets

pf@pfmaster-P170EM:pts/27 ~/roundup-20160303-fresh 52> pr -t -n 
roundup/date.py | head -310 | tail
  301
  302           >>> test_fin(u)
  303       '''
  304
  305       def __init__(self, spec='.', offset=0, add_granularity=False,
  306               translator=i18n):
  307           """Construct a date given a specification and a time
zone offset.
  308
  309           'spec'
  310              is a full date or a partial form, with an optional
added or