merged branch fabpot/named-args (PR #1072)
This PR was merged into the master branch.
Discussion
----------
enforced usage of named arguments after positional ones
When we introduced named arguments, the behavior for when both positional and named arguments were used in a call was not clearly defined.
This PR addresses this issue by following Python rules:
* No positional argument after named ones
* No possibility to define an argument with both a positional argument and a named one
This introduces a BC break if people were using positional arguments after named ones, but I would argue that this is never a good idea anyway.
This is an alternative to #995
Commits
-------
135b618 enforced usage of named arguments after positional ones