This is fixed in the pre-release of version 0.4.2. The attached patch solves the problem, although I suspect not in a fully "correct" manner since it seems to be done differently in 0.4.2.
This is fixed in the pre-release of version 0.4.2. The attached patch solves the problem, although I suspect not in a fully "correct" manner since it seems to be done differently in 0.4.2.