The documentation for ValueError currently describes it as being "Raised when a built-in operation or function receives an argument that has the right type but an inappropriate value, and the situation is not described by a more precise exception such as IndexError.", but the Python community has (quite rightly!) adopted it as the exception to raise in any system when that system is passed a value for a parameter that is type-correct but of an invalid value.

(Because what, is every library going to present a "my_library.ValueError" exception instead? That would be ridiculous.)

ValueError's documentation should drop the "a built-in operation or function" wording.

Perhaps go with something like "When raised indicates that a function or method was passed a value of the correct type but an invalid value"?

Just an FYI, Nathaniel, your title and message are bit "pushy". I've gone ahead and tweaked the title.

Nathaniel, thanks for the bug report. I've fixed the docs.

Thank you both!

stage: patch review -> resolved

messages: + msg321844
title: ValueError should not be documented as being restricted to only "a built-in operation or function" -> ValueError documented as being restricted to only "a built-in operation or function"

nosy: + rhettinger