Re: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6

2015-09-02 Thread Laura Creighton
If some code has from __future__ import unicode_literals that might go a long way to explaining things. see: see: https://docs.python.org/2/whatsnew/2.6.html -- Mailman-Users mailing list Mailman-Users@python.org

Re: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6

2015-09-02 Thread Stephen J. Turnbull
David Magda writes: > Debian is fairly conservative about these things, Debian may be conservative, but individual maintainers vary. Cf. that OpenSSL patch fiasco. There was no excuse for that patch, the maintainer just thought he was smarter than the OpenSSL people. Mailman itself has spent

Re: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6

2015-09-02 Thread Mark Sapiro
On 09/02/2015 07:31 AM, David Magda wrote: > On Tue, September 1, 2015 22:43, Mark Sapiro wrote: >> >> So what has probably happened is that archiving has been broken since >> the upgrade on Aug 25. There should be a an error message with traceback >> in Mailman's 'error' log for each message that

Re: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6

2015-09-02 Thread David Magda
On Tue, September 1, 2015 22:43, Mark Sapiro wrote: > On 09/01/2015 06:55 PM, David Magda wrote: >> >> The message in question seems to be from October 2005, and it has the >> "Subject: Você […]” header. Running under Debian 5 (Python 2.5), archive >> processing wasn’t an issue: messages were

Re: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6

2015-09-01 Thread Stephen J. Turnbull
Mark Sapiro writes: > I don't know what you are grepping, but if it's the mbox, you shouldn't > be looking for "\xea", you should be looking for "ê". At least on recent BSD-based systems "\xea" is a well-defined escape sequence, interpreted as the hexadecimal representation of a byte. Dunno

Re: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6

2015-09-01 Thread David Magda
On Tue, September 1, 2015 13:53, Mark Sapiro wrote: > There shouldn't be any non-ascii in a mbox. Well, maybe in a > "Content-Transfer-Encoding: 8bit" (or binary?) body part, but certainly > not in any headers. > > I don't know what you are grepping, but if it's the mbox, you shouldn't > be

Re: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6

2015-09-01 Thread Mark Sapiro
On 09/01/2015 10:26 AM, David Magda wrote: > > Looking at the mbox, there was only one place where \xea was in the > header, in a Subject line, using `grep --color='auto' -P -n "\xea"`. I > manually edited the mbox (making a copy first) and remove the accented-e > character with an ASCII "e", and

Re: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6

2015-09-01 Thread David Magda
On Tue, September 1, 2015 14:35, Stephen J. Turnbull wrote: > Mark Sapiro writes: > > > I don't know what you are grepping, but if it's the mbox, you shouldn't > > be looking for "\xea", you should be looking for "ê". > > At least on recent BSD-based systems "\xea" is a well-defined escape >

Re: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6

2015-09-01 Thread David Magda
[Actually send the reply to the list as well.] On Tue, September 1, 2015 12:15, Stephen J. Turnbull wrote: > David Magda writes: > > > When I run 'bin/arch mylistname' I get the following: > > > > [...] > > figuring article archives > > 2005-October > >

Re: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6

2015-09-01 Thread David Magda
> On Sep 1, 2015, at 21:02, Mark Sapiro wrote: > > In my testing with GNU grep on Ubuntu 15.04, 'grep "\xea"' interprets \x > as a literal x and therefore looks for the string "xea", not for the > character whose hex value is EA. For the record/archives: GNU grep also as the

Re: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6

2015-09-01 Thread David Magda
> On Sep 1, 2015, at 21:14, Mark Sapiro wrote: > > On 09/01/2015 12:09 PM, David Magda wrote: >> >> Could the new version of Python been chocking on a binary file whose >> format has changed from the old version? Is it prudent to do an "arch >> --wipe" when changing versions

Re: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6

2015-09-01 Thread Mark Sapiro
On 09/01/2015 12:09 PM, David Magda wrote: > > Could the new version of Python been chocking on a binary file whose > format has changed from the old version? Is it prudent to do an "arch > --wipe" when changing versions of Python? The exception is thrown in Python's sort() method. There are no

Re: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6

2015-09-01 Thread Mark Sapiro
On 09/01/2015 12:16 PM, David Magda wrote: > On Tue, September 1, 2015 14:35, Stephen J. Turnbull wrote: >> Mark Sapiro writes: >> >> > I don't know what you are grepping, but if it's the mbox, you shouldn't >> > be looking for "\xea", you should be looking for "ê". >> >> At least on recent

Re: [Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6

2015-09-01 Thread Mark Sapiro
On 09/01/2015 06:55 PM, David Magda wrote: > > The message in question seems to be from October 2005, and it has the > "Subject: Você […]” header. Running under Debian 5 (Python 2.5), archive > processing wasn’t an issue: messages were coming into the mbox and the HTML > page was being