\section{Built-in Module \module{cStringIO}}

\bimodindex{cStringIO}

\label{module-cStringIO}

The module \module{cStringIO} provides an interface similar to that of

the \module{StringIO} module. Heavy use of \class{StringIO.StringIO}

objects can be made more efficient by using the function

\function{StringIO()} from this module instead.

Since this module provides a factory function which returns objects of

built-in types, there's no way to build your own version using

subclassing. Use the original \module{StringIO} module in that case.

\section{Built-in Module \module{cPickle}}

\bimodindex{cPickle}

\label{module-cPickle}

The \module{cPickle} module provides a similar interface and identical

functionality as the \module{pickle} module, but can be up to 1000

times faster since it is implemented in \C{}. The only other

important difference to note is that \function{Pickler()} and

\function{Unpickler()} are functions and not classes, and so cannot be

subclassed. This should not be an issue in most cases.

The format of the pickle data is identical to that produced using the

\module{pickle} module, so it is possible to use \module{pickle} and

\module{cPickle} interchangably with existing pickles.

\section{Built-in Module \module{cStringIO}}

\bimodindex{cStringIO}

\label{module-cStringIO}

The module \module{cStringIO} provides an interface similar to that of

the \module{StringIO} module. Heavy use of \class{StringIO.StringIO}

objects can be made more efficient by using the function

\function{StringIO()} from this module instead.

Since this module provides a factory function which returns objects of

built-in types, there's no way to build your own version using

subclassing. Use the original \module{StringIO} module in that case.