Someone dug up a 13-year-old page from the community wiki and presented it as "this is totally the official Django documentation".
I've added a gigantic warning at the top of it to address this. See also my other comments in this HN thread, for the right way to do what that particular example was trying to do.
Having dates on the pages would probably help avoid some of this in the first place.
People point to a lot of the PHP comments in their docs as "bad" (and many are) but they're also dated, and you can use a comment date of 2009 when trying to give weight to how relevant/useful something may be.
"blank=..." anything is, imo, more confusing than "required=", regardless of what version/age of the docs though.
Apparently some other people noticed this was on HN, too, so there are minor edits from a few hours ago, but the bulk of the information is still a decade old. Would you stick a date on every paragraph?
(personally I'd forgotten that this page even existed)
Honestly I'm not convinced it's worth the amount of work involved in doing all this, and the number of places available for people to share tips/tricks/etc. has drastically increased since 2005. So if it were up to me the wiki would either go away, or become read-only with prominent "only for historical purposes, don't use information here" warnings.
i was meaning probably more in a general sense, not so much for this particular page. the notice at the top of that specific entry does the trick. a notice at the top of all wikis which aren't intended as the 'official word' indicating such would mitigate a bit of this sort of confusion.
I've added a gigantic warning at the top of it to address this. See also my other comments in this HN thread, for the right way to do what that particular example was trying to do.