#19148: 
regressiontests.test_utils.tests.HTMLEqualTests.test_parse_html_in_script()
fails with Python 2.6.8
-------------------------------------+-------------------------------------
     Reporter:  Arfrever             |                    Owner:  nobody
         Type:  Bug                  |                   Status:  closed
    Component:  Core (Other)         |                  Version:  1.4
     Severity:  Normal               |               Resolution:  fixed
     Keywords:                       |             Triage Stage:  Ready for
    Has patch:  0                    |  checkin
  Needs tests:  0                    |      Needs documentation:  0
Easy pickings:  0                    |  Patch needs improvement:  0
                                     |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Claude Paroz <claude@…>):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"ce168bb8994b0a7e032166e63a8b1cec034694d6"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ce168bb8994b0a7e032166e63a8b1cec034694d6"
 [1.4.x] Fix an HTML-parser test that's failed in Python 2.6.8 since
 5c79dd58.

 The problem description in #18239 asserted that
 http://bugs.python.org/issue670664 was fixed in Python 2.6.8, but based on
 http://bugs.python.org/issue670664#msg146770 it appears that's not
 correct; the
 fix was only applied in 2.7, 3.2, and Python trunk. Therefore we must use
 our
 patched HTMLParser subclass in all Python 2.6 versions.

 Backport of fcec904e4f from master. Fixes #19148.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/19148#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to