homepage

import HTMLParser
p = HTMLParser.HTMLParser()
p.feed("""
<script>
<!--
bmD.write('</sc'+'ript>');
//-->
</script>
""")
Traceback (most recent call last):
 File "<stdin>", line 4, in ?
 File "/usr/lib/python2.4/HTMLParser.py", line 108, in feed
 self.goahead(0)
 File "/usr/lib/python2.4/HTMLParser.py", line 150, in goahead
 k = self.parse_endtag(i)
 File "/usr/lib/python2.4/HTMLParser.py", line 314, in parse_endtag
 self.error("bad end tag: %r" % (rawdata[i:j],))
 File "/usr/lib/python2.4/HTMLParser.py", line 115, in error
 raise HTMLParseError(message, self.getpos())
HTMLParser.HTMLParseError: bad end tag: "</sc'+'ript>", at line 4, column 12
The JavaScript code is protected via HTML comment, so HTMLParser must skip it entirely, and the parsing must be successfull.
Instead of this, the JavaScript code is parsed as a part of the HTML page, and incorrect end tag is detected. If one move the actual end tag </script> up just after start tag <script>, the code is parsed without errors.
Hence the code seems to be artificial, it is used often in real site counters to prevent the blocking of them.

Confirmed in trunk, py3k.

I agree, I do not feel like the precise changes to the tests feel completely ideal. I feel that this problem stems from the fact that the nameCheck function as originally written doesn't seem to completely serve its originally intended purpose.
The original issue that caused the modifications of the tests were as follows:
* After adding "test_abs_path()" namecheck would pass the test when it should actually fail due to the original assert performing os.path.abspath() on both paths. The obviously solution to this seemed to be to take the abspath of the user supplied path (the variable dir in this function) relative or otherwise and compare to ndir which is derived from the passed in "name" variable, populated by the mkdtemp call.
* The second issue is a somewhat complex case of those asserts passing the atypical odd calls of nameCheck from the "test__RandomNameSequence" suite. Without absolute pathing of both parameters in the new first assert this test began to fail. This is because the original call was self.namecheck(<file name>, '', '', ''). These empty parameters when called with os.path.abspath() would return valid paths and these asserts would succeed. As a result, the abspath(join()) call built a proper path into the "name" parameter allowing the tests to pass in this case.
* For the sake of cleanliness I decided it made more sense to split the two apart. Make one assert that specifically verifies the path the file/folder is being placed in is both absolute and matching and one that will pass the file name. Perhaps the old first assert (or second assert in the patch) can actually be removed but I think it may be getting properly tested against in one of the other test classes.
I am quite confident there is a much better way to accomplish this but I did not wish to change _too_ much of the test on my first stab at this.
I appreciate your feedback very much. I will work on setting up the 2.7 environment for working on issues that span the 2x/3x gap.

Please disregard, I commented on the wrong issue.

This is a duplicate of issue 670664, which has a proposed patch.

Can't see much sense in keeping a duplicate open.