Re: Codec lookup fails for bad codec name, blowing up BeautifulSoup

2007-11-09 Thread Waldemar Osuch
On Nov 9, 4:15 pm, John Nagle <[EMAIL PROTECTED]> wrote: > Waldemar Osuch wrote: > >> This is a known bug. It's in the old tracker on SourceForge: > >> [ python-Bugs-960874 ] codecs.lookup can raise exceptions other > >> than LookupError > >> but not in the new tracker. > > > The ne

Re: Codec lookup fails for bad codec name, blowing up BeautifulSoup

2007-11-09 Thread John Nagle
Waldemar Osuch wrote: >> This is a known bug. It's in the old tracker on SourceForge: >> [ python-Bugs-960874 ] codecs.lookup can raise exceptions other >> than LookupError >> but not in the new tracker. > > The new tracker has it too. > http://bugs.python.org/issue960874 How

Re: Codec lookup fails for bad codec name, blowing up BeautifulSoup

2007-11-09 Thread Waldemar Osuch
> > This is a known bug. It's in the old tracker on SourceForge: > [ python-Bugs-960874 ] codecs.lookup can raise exceptions other > than LookupError > but not in the new tracker. The new tracker has it too. http://bugs.python.org/issue960874 > > The "resolution" back in

Codec lookup fails for bad codec name, blowing up BeautifulSoup

2007-11-09 Thread John Nagle
I just had our web page parser fail on "www.nasa.gov". It seems that NASA returns an HTTP header with a charset of ".utf8", which is non-standard. This goes into BeautifulSoup, which blows up trying to find a suitable codec. This happens because BeautifulSoup does this: def _codec(self,