This makes the code of get_scorer less readable since the usual lookup semantics aren’t followed. At a minimum get_scorer needs an update to its docs and probably a comment.

Might also be worth reconsidering if this is too hacky and we would be better off deprecating SCORERS and adding get_scorer_names, providing less magic with a public/private distinction. I’m not sure to what extent users/ third parties update SCORERS.

This makes the code of get_scorer less readable since the usual lookup semantics aren’t followed.

This is a valid point.

Might also be worth reconsidering if this is too hacky and we would be better off deprecating SCORERS and adding get_scorer_names, providing less magic with a public/private distinction.

I would greatly prefer adding a get_scorer_names and deprecate SCORERS.

Ok, I've introduced get_scorer_names here and deprecate SCORERS. This should make us happy now :)

classes.rst should also be updated

@jnothman happy to merge?

Ping @glemaitre

@jnothman did you mean to close or merge?

To merge! :|