Artist.set_picker explicitly accepts both None and bool inputs.

However, Line2D.set_picker is not documented to accept these types.

My instinct is to be in favor of supporting them, as they are supported by the superclass, however, I think that we should also update the docstring (and type hints, for that matter).

should I update this in this PR? Or maybe start a feature type issue with this?

I would lean toward it being done together, but yeah, some care to be taken in making it behave as expected (with some weight towards existing behavior, at least for the case of float input)

Also consider integer input (e.g. 5 in the original report), isinstance(5, float) is false...

But further beware of isinstance(True, int), which is true.

We may have to explicitly handle the None/boolean cases here instead.

actually, when I set a integer value, isinstance(x, float) returns true, so it fixes the original report (I tested it). I don't know exactly why this happens but I found some people trying to check if a input were int or float and isinstance wasn't working for them.
I could do something like:

if float(i).is_integer():
        // int values
    else:
        // float values

but I don't know if it's necessary. What do you think?

isinstance(3, float) certainly returns False, so not sure what you mean?

certainly you can pass the otherwise equivalent 3.0 which will return True, but it is possible to pass an int which does not pass the isinstance check. and also it is certain that if we want special handling for bools we have to be careful of isinstance checks for ints still too.

It is not the case that integers need to be handled differently than floats, other than that bools count as integers.

hello, I'm having a problem with matplotlib installation in my ve, i think it's a problem with my operational system and I'll have to format my computer, but I'm waiting till the end of semester for it. To get this PR accepted I should change this details you mentioned, right?