All files under examples/release_highlights lack a print(doc) so I haven't added it (yet). Should I?

I would say include them to be consistent. (Although it does not look as nice having a print(__doc__) rendered on the HTML)

The files under examples/text print doc later in the code, together with additional usage information. Not sure I should change them.

In those cases, I think it is best to leave them as is.

So historically, they were there since we'd have pretty much all of the text on top of the file, and then the print would print all the information related to the example. But these days our examples are sectioned, and suited for a nice sphinx rendering and notebooks, and users can run them in binder. I'd say it'd be nicer if we remove them from all the files.

Both are OK with me. I just need a wider agreement on what is the best solution. Can I help reach it?

pinging @scikit-learn/core-devs since we kinda need an agreement on this.

Question is: should we remove print(__doc__) from all examples or should we add it to all of them?

I'd tend towards removing as well.

The printing is useful if one blindly runs the example from the command line without even looking at the code, but I'm not sure many people do (or even should) do that.

I don't have a strong opinion for or against removing.

I prefer to remove it.

I have removed the initial __print__(doc) from all examples so that you can have a look.

Only exception, the 3 examples under examples/text. They print(__doc__) late in the source file, together with additional usage information.

I just merged master and we can check if all CIs become green.

Thanks @DimitriPapadopoulos