On Tuesday, November 22, 2016, Glyph Lefkowitz <gl...@twistedmatrix.com> wrote: > > > Okay. So. > > The rule for reverts like this is: if you do something today, which is > correct usage of the API and produces an observably correct result, will > that be broken in the future if we fix it? If so, then we need to revert > because the interface as released is unsupportable. > > As it stands, we have a matrix of 4 behaviors: > > > *bytes* > *text(ascii)* > *text(nonascii)* > *py2* > works > works > UnicodeDecodeError > *py3* > garbage > works > works > > This... is actually... fine, surprisingly. >
Given that matrix, how would this work on Python 2 and 3: https://github.com/buildbot/buildbot/blob/40d5dd3d101704aa8db582e306b3c6cf7921c23c/master/buildbot/reporters/irc.py#L67-L68 And how would that code not have to change if a future release accommodates Unicode on Python 2 or bytes on Python 3?
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
