Python vs C for a mail server

[Randall Parker]

Magnus Lycka wrote:

> Or...don't you have automated tests? Ouch. If you (like me) feel a
> little lazy to write a lot of test scripts, you can use a test tool
> such as TextTest, that compares output between test runs, rather than
> forcing you to write lots of scripts with plenty of assertions. The
> effort required to get started is probably bigger there though. (I
> don't really know, it was all set up for me at work.)

Magnus,

The code I'm writing in Python is a test executive to test embedded C
code. Then tests get written in Python that the test executive
processes. No, I'm not going to write yet another layer of tests in
order to compensate for shortcomings in the Python language.

> It's also a pain to write unit tests, but it's much more rewarding
> than writing type declarations. Not only does it force you to think
> through the ramifications of changes, but you also document your
> intentions through your tests.

I do not have time to write unit tests for the Python classes. I  have
plenty of unit tests to write in Python for the embedded C modules.
When I run and hit a problem in Python I just  debug it and fix it.
That's a lot faster than writing unit tests.