Writing new codecs

Brian Quinlan brian at sweetapp.com
Sat Jun 16 23:09:04 CEST 2001


> It's really your choice. For rarely-used encodings, writing them in
> Python might make them more maintainable. But then, dealing with
> individual bytes in C is often easier than in Python.

Hopefully it won't need that much maintenance. And the C implementation
is probably going to be at least 2 orders of magnitude faster than the
Python implementation.
 
> I hope not. New codecs should certainly use their own modules, which
> still leaves the question whether these should be C or Python modules.

That would be a bit odd too, I think. The number of C modules in Python
could really blow up.





More information about the Python-list mailing list