always use StringIO, never cStringIO #783

merged 1 commit into from Sep 12, 2011


None yet

2 participants

IPython member

cStringIO is not unicode-safe, resulting sometimes in incorrect output of PyColorize, among other difficult to discern errors.

This should clean out the last remnants of cStringIO.

@minrk minrk always use StringIO, never cStringIO
cStringIO is not unicode-safe
@fperez fperez merged commit 7a7b273 into ipython:master Sep 12, 2011
IPython member

Perfect, fixes the issue. Merged and pushed, many thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment