A> Well, sure. But you have to do that suboptimal stuff *anyway* A> in order to maintain the separate package. How is the overall A> development process more convenient to maintain two codebases?
It isn't! And now that I've announced email 2.0, I'm going to merge it all into Python 2.3 cvs (but not the suboptimal implementation. ;). I suspect updating the docs will be the most work.