Implicit string joining in the function signature

[vaultah]

PI does not properly handle/highlight the'second part' in the function signature, although Python allows string concatenation via implicit line joining:

OTOH, function calls are handled well:

[MattDMo]

Thanks, I'll look into it.

[MattDMo]

The reason for this is complicated, and I still don't know how to fix it. Basically, dunder methods like __init__, __add__, etc. are not treated quite like normal functions in PI, and I can't yet figure out what scoping I need to mess with in order to fix that. Also, your second example isn't quite equivalent to the first, as the first split string is in the arguments of a function definition, while the second split string is in the arguments of a function call.

Here's an example:

[MattDMo]

I just noticed this again. @FichteFoll, any thoughts?

[FichteFoll]

I didn't take a look at function definitions when I worked on PyI.

Anyway, the problem is here, where a newline terminates further parsing of keyword argument default values, although it should only be terminated by , or ).

[MattDMo]

This has been fixed in the 2.0 release: