I encountered this when setting up a wsgi-served repository.
I 'resolved' it by installing celementtree. Since the use of celementtree vs. elementree is treated by bzr as an either/or situation, having celementtree available dodged whatever namespace-related import problems seem to be occurring for elementtree. I think this amounts to the same thing as what Mike Gratton suggested above (where he just assumes celementtree is available).
My understanding is that celementtree is a performance-related option, but not a requirement. So this is still technically just a work-around and not a solution.
I encountered this when setting up a wsgi-served repository.
I 'resolved' it by installing celementtree. Since the use of celementtree vs. elementree is treated by bzr as an either/or situation, having celementtree available dodged whatever namespace-related import problems seem to be occurring for elementtree. I think this amounts to the same thing as what Mike Gratton suggested above (where he just assumes celementtree is available).
My understanding is that celementtree is a performance-related option, but not a requirement. So this is still technically just a work-around and not a solution.