My implementation of unicodedata is not really proceeding as I'd like,
due to the fact that I'm waiting for my employer's lawyers to
greenlight me contributing code written in my own time. I don't
pretend to understand why they need to be involved, but obviously it's
better for all involved if I do get a piece of paper agreeing that any
code I produce is mine to give away as I like and I can then sign any
contributor's agreement that may be required.
So rather than writing code, I've been doing some reading and I have a
couple of questions about general jython development.
1. JUnit / TestNG / ANOther isn't used - just CPython tests. How well
do people find that works with regard to refactoring?
2. At least for unicodedata, the existing 2.3 CPython tests aren't
quite what I'd like. CPython 2.3 and 2.4 unicodedata contains at
least one bug, which has been confirmed by via private email
discussion with one of the CPython developers (Martin von L=F6wis).
Apparently, they aren't interested in fixing the issue in the older
releases, since 2.5 is the current good release. Obviously, I don't
intend to create the same bug in any implementation I provide, but
that means that the 2.3 CPython tests won't pass. So, I would like to
change those tests for three reasons.
a) They aren't sufficiently granular.
b) They are wrong.
c) I'd prefer to use unittest anyway, rather than the custom framework
that test_unicodedata.py currently uses.
Any thoughts or pointers about that?