Am 29.06.2012 um 19:45 schrieb Tres Seaver:
[…]
Hmm, I'm running into a test failure where the Message constructor blows
up with a decode error for the 'default' value here. Does that ring any
bells for anyone? I know we can't be depending on a
sys.setdefaultencoding hack.
Sorry for the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/03/2012 05:07 AM, Michael Howitz wrote:
Am 29.06.2012 um 19:45 schrieb Tres Seaver: […]
Hmm, I'm running into a test failure where the Message constructor
blows up with a decode error for the 'default' value here. Does
that ring any bells
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/14/2012 08:13 AM, Michael Howitz wrote:
Log message for revision 125861: In version 3.7.2 msgids and default
values where forced to be unicodes. This was too strict because at
least the TAL extractor returns UTF-8 encoded default values.
