[issue13711] html.parser.HTMLParser doesn't parse tags in comments in scripts correctly
New submission from Manuel Bärenz : I've attached a script which demonstrates the bug. When feeding a
[issue13711] html.parser.HTMLParser doesn't parse tags in comments in scripts correctly
Manuel Bärenz added the comment: I forgot to say, I'm using python version 3.2.2. -- ___ Python tracker <http://bugs.python.org/issue13711> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13711] html.parser.HTMLParser doesn't parse tags in comments in scripts correctly
Manuel Bärenz added the comment: Oh, I wasn't aware of that. Then, the bug is actually calling handle_endtag. -- ___ Python tracker <http://bugs.python.org/issue13711> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13711] html.parser.HTMLParser doesn't parse tags in comments in scripts correctly
Manuel Bärenz added the comment:
To clarify this even further: Consider
parser_instance.feed("<td></td>")
It should call:
parser_instance.handle_starttag("script", [])
parser_instance.handle_data("")
parser_instance.handle_endtag("script", [])
Instead, it calls:
parser_instance.handle_starttag("script", [])
parser_instance.handle_data("")
parser_instance.handle_endtag("td", [])
parser_instance.handle_endtag("script", [])
--
___
Python tracker
<http://bugs.python.org/issue13711>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13711] html.parser.HTMLParser doesn't parse tags in comments in scripts correctly
Manuel Bärenz added the comment: Great! Thank you! -- ___ Python tracker <http://bugs.python.org/issue13711> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11146] Add a feature similar to C++ "using some_namespace"
New submission from Manuel Bärenz : In C++, the the approach to the namespace problem is having different namespaces that should not contain different definitions of the same name. Members of a namespace can be accessed explicitly by e.g. calling "std::cout << etc." or "using namespace std; cout << etc." I understand Pythons approach to be "objects can be used as namespaces and their attributes are the names they contain". I find this a very beautiful way of solving the issue, but it has a downside, in my opinion, because it lacks the "using" directive from C++. If the object is a module, we can of course do "from mymodule import spam, eggs". But if it is not a module, this does not work. Consider for example: class Spam(object): def frobnicate(self): self.eggs = self.buy_eggs() self.scrambled = self.scramble(self.eggs) return self.scrambled > 42 This could be easier to implement and read if we had something like: class Spam(object): def frobnicate(self): using self: eggs = buy_eggs() scrambled = scramble(eggs) return scrambled > 42 Of course this opens a lot of conceptual questions like how should this using block behave if self doesn't have an attribute called "eggs", but I think it is worth considering. -- messages: 128153 nosy: turion priority: normal severity: normal status: open title: Add a feature similar to C++ "using some_namespace" type: feature request ___ Python tracker <http://bugs.python.org/issue11146> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
