I had to push another fix to next because some buildbots have an old six
module without add_metaclass.

However the buildbots broke down completely now, so I won't be able to see
if everything is green before I leave internet behind for the weekend.

I don't consider it safer to try to revert blindly than to let it be, so
lets hope it's ok.

Johannes: Can we get six 1.4 on all buildbots? I don't know how to fix the
metaclass in a py2/3 compatible way without it.

Martin



On 15 August 2014 14:27, Martin Sandve Alnæs <[email protected]> wrote:

> Hi,
> I've rebased Aslaks work on python3 support for dolfin on the latest
> master, fixed the conflicts, fixed a couple of bugs, seen that the
> quicktests are running locally (with python 2).
>
> It doesn't quite work with python 3 yet, but I've pushed it to next now,
> to avoid the ridiculous amount of merge conflicts that will arise if I
> wait. Most of the changes are just print statements and except statements,
> but there are also some swig/cpython api fixes.
>
> What would be really great is if everyone can change their habits right
> now and use
>
> print("foo")
> raise Exception("msg")
> except Exception as e:
>
> instead of
>
> print "foo"
> raise Exception, "msg"
> except Exception, e:
>
> In particular the print statement is a hard habit to change! But I'm sure
> we can manage.
>
> NB: remember to add
> from __future__ import print_function to the top of a file that uses
> print().
>
> --
> Martin
>
_______________________________________________
fenics mailing list
[email protected]
http://fenicsproject.org/mailman/listinfo/fenics

Reply via email to