Hi Vinay and Aymeric,
On 04/28/2012 12:50 AM, Aymeric Augustin wrote:
On 28 avr. 2012, at 00:49, Vinay Sajip wrote:
From the discussion on python-dev, it seems possible that an optimal
fix might require changes both in Python and in Django. Before
creating a ticket about this for Django, I would like to get an
opinion about this from the Django committers - so can someone please
look at this python-dev thread and/or Python issue and comment?
Hi Vinay,
As far as I can tell, Django's patching HTMLParser [1] to work around a bug [2]
that was fixed in Python 2.7 and 3.2. If that comment is accurate, we could apply
the patch only when running on Python< 2.7.
So it seems possible to conditionally fix Django, whatever solution the Python
devs choose.
I took a look at this today and discussed it on IRC with Ezio Melotti,
who maintains HTMLParser in the standard library, and we agreed that the
best solution is to only use our custom HTMLParser subclass with older
versions of Python where the standard library HTMLParser is known to be
buggy, and just use the standard library's HTMLParser with newer
Pythons. I've filed a ticket for this
(https://code.djangoproject.com/ticket/18239) and will try to close it
this week unless someone else gets there first.
Carl
--
You received this message because you are subscribed to the Google Groups "Django
developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
