I'm sorry I riled everyone up. My apologies.
=== Trying to reproduce ===
Getting back to this today, I'm not sent to readthedocs.org
. I'll chalk that up to the interwebz demons fiddling around (could be anywhere between my $work, Google, and your end, including various intermediaries).
Now, back to the next problem. There doesn't seem to be any documentation on the fields in .pylintrc. I'm specifically looking for init-hook help.
I can't find anything of substance in the html docs, so I download the PDF and search for "init-hook". There are 6 hits, most only mentions.
Finally, it occurs to me (from the nature of the change summaries in the PDF) that this is probably a command line argument. Low and behold, pylint --help has a blurb. (As an aside, I'm wondering how to format this well for command line, due to the significant whitespace feature, but that's a problem for another day.)
=== Problem 1 ===
Search not helpful
For me, the web docs are not that helpful for searching, as it doesn't get me any closer. Take this screenshot of a search for init-hook:
...which I had before.
=== Problem 2 ===
Command line help not online
The command line help does not exist online or in the PDF in except in brief, as far as I can see. Perhaps this is intentional? (It makes it harder to post Stack Exchange answers, but that's SEP.)
=== Problem 3 ===
How to include multiline code in .pylintrc file in the init-hook section.
This doesn't seem to be covered anywhere in the docs, but is an obvious use case.