Philipp von Weitershausen wrote:
Martijn Faassen wrote:
I think we should see to it that in cases of parallel implementations, unit tests are set up to run twice, once for the Python implementation and once for the C one. That way, by the rule of checking in no code that produces unit test failures, you are forced to modify both implementations when you modify, fix a bug, etc. in either one.
Agreed, although I'm not sure how to do that. I'm sure we can figure out something. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org _______________________________________________ Zope3-dev mailing list Zope3email@example.com Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com