Yannick Duchêne added the comment:
The documentation says:
> Reset the instance. Loses all unprocessed data.
How can parsing go ahead with all unprocessed data lost? This is the “Loses all
unprocessed data” which made me believe it is to stop it.
May be the documentation is uncl
Yannick Duchêne added the comment:
`reset` is called to stop the parser.
If really `reset` should not be called during parser hooks execution, then the
documentation should says so and an error should be raised when `reset` is
invoked
Yannick Duchêne added the comment:
Thanks Xiang, for the clear explanations.
So an error should be triggered when `reset` is invoked while it should not.
And remains the issue about how to stop the parser: should an exception be
raised and caught at an outer invocation level? Something like
Yannick Duchêne added the comment:
> And I don't see how to stop the process either.
I just did it with `raise StopIteration`, caught at a proper place (in the
procedure which invokes `feed` and `close`), and it seems to be fine, I have no
more strange behaviours. At least, I cannot
Yannick Duchêne added the comment:
I'm closing this issue, as the the issue http://bugs.python.org/issue26210 is
the real one and this one seems to be a variant of the former.
--
status: open -> closed
___
Python tracker <rep...@bugs.pyth
Changes by Yannick Duchêne <yannick_duch...@yahoo.fr>:
--
nosy: +ezio.melotti
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
New submission from Yannick Duchêne:
`HTMLParser.handle_data` may be invoked although `HTMLParser.reset` was
invoked. This occurs at least when `HTMLParser.reset` was invoked during
`HTMLParser.handle_endtag`.
According to the documentation, `HTMLParser.reset` discard all data, so it
should
New submission from Yannick Duchêne:
Using HTMLParser on the attached file, I got this:
File "/usr/lib/python3.5/html/parser.py", line 111, in feed
self.goahead(0)
File "/usr/lib/python3.5/html/parser.py", line 171, in goahead
k = self.parse_st
Yannick Duchêne added the comment:
Better at least two, if I'm not wrong: the innermost scope may be the module's
scope. So there is always at least the module scope and the built‑ins scope, at
least two up to four.
(if I have not overlooked something)
--
nosy: +Hibou57
New submission from Yannick Duchêne:
`make test` fails with Python 3.4.1 on Ubuntu 12.04 Intel 32 bits.
The single `./configure` option used, was `--prefix=$HOME/.local`.
As attached file, an archive containing both standard output and standard error
outputs.
Not some important error
10 matches
Mail list logo