On Wed, 12 Oct 2016, Simon King wrote:
So we have now a common view that 'type' in TypeError should (mostly?)
refer to types in wrong class, wrong category etc; and so for functions
having no input it should (almost?) never happen.
What about ValueError? After all, in that case, we have a *m
On 2016-10-12, Jori =?ISO-8859-1?Q?M=E4ntysalo?= wrote:
> So we have now a common view that 'type' in TypeError should (mostly?)
> refer to types in wrong class, wrong category etc; and so for functions
> having no input it should (almost?) never happen.
What about ValueError? After all, in tha
