Awesome!
On Fri, Apr 27, 2012 at 3:07 PM, Carl Meyer wrote:
> On 04/27/2012 08:36 AM, Guido van Rossum wrote:
>>
>> Someone should contact the Django folks. Alex Gaynor?
>
>
> I committed the relevant code to Django (though I didn't write the patch),
> and I've been following this thread. I have
On 04/27/2012 08:36 AM, Guido van Rossum wrote:
Someone should contact the Django folks. Alex Gaynor?
I committed the relevant code to Django (though I didn't write the
patch), and I've been following this thread. I have it on my todo list
to review this code again with Ezio's suggestions in
On 4/27/2012 1:23 AM, Ezio Melotti wrote:
html.parser doesn't use any private _name, so I was considering part of
the public API only the documented names. Several methods are marked
with an "# internal" comment, but that's not visible unless you go read
the source code.
I could not find __all
Someone should contact the Django folks. Alex Gaynor?
On Thursday, April 26, 2012, Ezio Melotti wrote:
> Hi,
>
> On 26/04/2012 22.10, Vinay Sajip wrote:
>
>> Following recent changes in html.parser, the Python 3 port of Django I'm
>> working
>> on has started failing while parsing HTML.
>>
>> The
Hi,
On 26/04/2012 22.10, Vinay Sajip wrote:
Following recent changes in html.parser, the Python 3 port of Django I'm working
on has started failing while parsing HTML.
The reason appears to be that Django uses some module-level data in html.parser,
for example tagfind, which is a regular expres
On Fri, Apr 27, 2012 at 5:21 AM, Guido van Rossum wrote:
> Traditionally we've been really lax about this stuff. We should strive
> to improve and clarify the exact boundaries of our APIs better.
Yeah, I must admit in my own projects these days I habitually mark all
module level and class level n
On Thu, Apr 26, 2012 at 12:10 PM, Vinay Sajip wrote:
> Following recent changes in html.parser, the Python 3 port of Django I'm
> working
> on has started failing while parsing HTML.
>
> The reason appears to be that Django uses some module-level data in
> html.parser,
> for example tagfind, whi
On 26.04.2012 21:10, Vinay Sajip wrote:
> Following recent changes in html.parser, the Python 3 port of Django I'm
> working
> on has started failing while parsing HTML.
>
> The reason appears to be that Django uses some module-level data in
> html.parser,
> for example tagfind, which is a regul
Following recent changes in html.parser, the Python 3 port of Django I'm working
on has started failing while parsing HTML.
The reason appears to be that Django uses some module-level data in html.parser,
for example tagfind, which is a regular expression pattern. This has changed
recently (Ezio c
