(Quasi-)incorrect keyword argument completion

The signature e.g. of np.frombuffer is

frombuffer(buffer, dtype=float, count=-1, offset=0)

but frombuffer(<tab> proposes completions with count=, dtype= and offset=. Note that it is unlikely that one will ever want to write a call that starts with np.frombuffer(count=...), because you’d typically want to pass the buffer argument first (yes, I know, technically you can pass it as keyword after another keyword argument. I don’t think that’s a common case 😃)

[anntzer]

On a related note, np.load("<TAB> (note the presence of the quote) completes kwargs (and globals) rather than filenames, which is incorrect.

[krassowski]

@Ark-kun the behaviour you suggest can be implemented by (conditionally) returning suppress=True using the new matcher API / docs. The python_func_kw_matcher would need to be ported to matcher API v2 which is mostly just changing the function signature.