I'm converting trunk to new division in python 3. Rev 20635 changes calendar computations to use from __future__ import division
Are there tests somewhere in Gramps to test this? Comparing with 3.4 does not show issues, but not the best way of testing such an important part of Gramps.
I ended up also changing narweb in trunk, sorry. The specific change set is uploaded with bug 2620 however, so could easily be undone. As you work in branch34 and that is already that different from trunk, heavy editing of patches on branch34 is needed anyway I assume...
There where some errors already in narweb from fixes in branch34 I assume, browse commits is not working now on sourceforge.
So, I don't know if you introduced them :-) As general note, If one updates trunk from a branch34 patch, keep in mind that all files have now lowercase, and all imports start with a . or with gramps. So changes from branch34 to that direction are always needed.
Benny2012/11/7 Benny Malengier <firstname.lastname@example.org>
If you do svn up in trunk, you will see a huge patch landing.
This is adaptation of the python 2.7 syntax to python 3.2.
Gramps does not run yet on 3.2 though, that will be more work.
Also, some things in trunk python 2.7 will be broken, I wanted this huge patch out however, as during testing I need to fix as many GTK 3 things as python 3 things :-)
For coding in trunk in the future, please don't break python 3.2 syntax, so no u'string', no iteritems or other iter friends, no xrange, add list(..) around things that are iterator in 3.2, ...
For an overview of coding things, help update: http://www.gramps-project.org/wiki/index.php?title=GEPS_031:_Python_3_support
If you want a look at the total patchset: see attached file to bug ticket http://www.gramps-project.org/bugs/view.php?id=2620