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.