Python's official documentation contains textbook example of insecure code (XSS)

ISTM the post has a somewhat nasty and judgmental tone. Instead of saying, "ha ha, gotcha!", an issue could have been filed on GitHub and it would have been quickly fixed. Instead, the OP seems to be publicity seeking. IMO, this isn't worthy of being on Hacker News.

&gt;I am surprised this survived so long.<p>Maybe it wouldn&#x27;t survive that long if people opened issues for this sort of thing in appropriate places (perhaps <a href="https:&#x2F;&#x2F;github.com&#x2F;python&#x2F;docs-community">https:&#x2F;&#x2F;github.com&#x2F;python&#x2F;docs-community</a> ), rather than spontaneously expecting an underfunded open source project to think about the documentation of decades-old functionality that barely anyone would consider using for new code (and which has been removed in the latest version anyway).<p>(At this scale, or anywhere close to it, the only OSS orgs I would consider <i>not</i> underfunded are Linux and Mozilla. And if you count non-code Creative Commons stuff, Wikimedia.)

&quot;If you don&#x27;t Read The Fine Manual then you are uninformed, if you read it you are disinformed.&quot; This is a gem! There should be more disclaimers in the documentation about potential vulnerabilities like XSS.

My first thought was &quot;who&#x27;s still using CGI?&quot; then I read the docs:<p>&gt; Deprecated since version 3.11, will be removed in version 3.13

does it count as cross site scripting if there is no way to send the result to someone else?