I've gone full circle. The more I think about it, the more these tests seems like unit tests (and I'm sorry that I was unclear about that).
They are unit tests because: - They try to excersize only isolated functionality within the transform - Invoking the full Cython compiler (which I currently do not do) would be a disadvantage rather than an advantage They may not be considered unit tests because: - I "cheat" (but this is only to save time) and rather than constructing a real mock input from scratch I make use of the Cython parser (and potentially a limited subset of pre-transforms) to get the input tree. However, I really use the parser (rather directly) as a test utility, not as part of a compilation as such. Invoking cython.py is out of the question. In some cases, it might be impossible to cheat (the code tree needs info that can't be written in syntax) and in those case I'll be constructing trees manually. So I'll put them in Cython/Compiler/Transforms/Tests (using Python functions and doctests I imagine), if that is ok. -- Dag Sverre _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
