"Grig" <[EMAIL PROTECTED]> wrote:
"Problem with porting patterns/api's from java straight to python is that most of the outcome feels unpythonic. I'll not go about my own feelings python vs. java here now, but I just want to point out that there's already a rather large core of hard-python users who refuse to use pyUnit because of this,
I'm curious what people find "un-pythonic" about PyUnit? I've used it, and while some parts of it seem a little over-complex to me, I don't see anything about it which is inherently un-pythonic. Is this just a case of Not Invented Here?
I've seen 'py.test' proposed as as a more pythonic unit test framework. So its design may provide you with some clues. It can be found at:
http://codespeak.net/py/current/doc/test.html#starting-point-py-test-command-line-tool
As far as I can see, the defining feature of py.test is the simplicity of the API. Its impressively absent.
-- Mike -- http://mail.python.org/mailman/listinfo/python-list
