This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Michael.Brooks
Recipients Michael.Brooks, ezio.melotti
Date 2011-11-17.18:01:06
SpamBayes Score 3.4948344e-10
Marked as misclassified No
Message-id <CACDSwDm1p09B_sBpqgT_LmKw7+oHwQDmFK6ZnZ=7ZYF_8v_9MQ@mail.gmail.com>
In-reply-to <1321547064.58.0.040646161577.issue13358@psf.upfronthosting.co.za>
Content
Ok so until you fix this bug,  i'll be overriding HTMLParser with my fix,
becuase this is a blocking issue for my project.  My HTMLParser must behave
like a browser,  period end of story.

Thanks.

On Thu, Nov 17, 2011 at 9:24 AM, Ezio Melotti <report@bugs.python.org>wrote:

>
> Ezio Melotti <ezio.melotti@gmail.com> added the comment:
>
> It seems to me that the arguments are parsed correctly, but handle_data is
> called multiple time between handle_starttag and handle_endtag.
> This might happen, e.g. in case the source lines are fed one by one to the
> parser, but in this case seems to happen whenever </ is found.
> (The tests didn't detect this because they join the data to avoid buffer
> artifacts.)
> I'm not sure if this can be considered a bug, but the situation can indeed
> be improved.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue13358>
> _______________________________________
>
History
Date User Action Args
2011-11-17 18:01:07Michael.Brookssetrecipients: + Michael.Brooks, ezio.melotti
2011-11-17 18:01:06Michael.Brookslinkissue13358 messages
2011-11-17 18:01:06Michael.Brookscreate