Added support for PEP 570 (#867)

[sandsbit]

See Issue #867 or https://www.python.org/dev/peps/pep-0570/

[asottile]

code seems fine, can you make testsuite/python38.py with:

def f(a, /, b):
    pass

[asottile]

fwiw, this patch also fixes the problem, I don't know which one is more correct (there other "unary operators" covering the splat / etc. operations in this list (it's how named-only arguments aren't flagged):

diff --git a/pycodestyle.py b/pycodestyle.py
index 6ad5456..a0c2898 100755
--- a/pycodestyle.py
+++ b/pycodestyle.py
@@ -112,7 +112,7 @@ REPORT_FORMAT = {
 PyCF_ONLY_AST = 1024
 SINGLETONS = frozenset(['False', 'None', 'True'])
 KEYWORDS = frozenset(keyword.kwlist + ['print', 'async']) - SINGLETONS
-UNARY_OPERATORS = frozenset(['>>', '**', '*', '+', '-'])
+UNARY_OPERATORS = frozenset(['>>', '**', '*', '/', '+', '-'])
 ARITHMETIC_OP = frozenset(['**', '*', '/', '//', '+', '-'])
 WS_OPTIONAL_OPERATORS = ARITHMETIC_OP.union(['^', '&', '|', '<<', '>>', '%'])
 # Warn for -> function annotation operator in py3.5+ (issue 803)
diff --git a/testsuite/python38.py b/testsuite/python38.py
new file mode 100644
index 0000000..2132cd5
--- /dev/null
+++ b/testsuite/python38.py
@@ -0,0 +1,2 @@
+def f(a, /, b):
+    pass

[mikeholler]

Any updates on this? I'm having issues as well.

[aviramha]

code seems fine, can you make testsuite/python38.py with:

def f(a, /, b):
    pass

Seems author is stale, should I/anyone else just create a new PR with a test added?

[sandsbit]

I will add tests tonight

[aviramha]

Any update?

[asottile]

needs to be python38.py

[asottile]

this seems fine to me, a smaller patch however:

-UNARY_OPERATORS = frozenset(['>>', '**', '*', '+', '-'])
+UNARY_OPERATORS = frozenset(['>>', '**', '*', '/', '+', '-'])

(this is how keyword-only arguments are handled currently)

[asottile]

actually, looks like you'll need to rebase now since python38.py got created on master

[sandsbit]

this seems fine to me, a smaller patch however:

-UNARY_OPERATORS = frozenset(['>>', '**', '*', '+', '-'])
+UNARY_OPERATORS = frozenset(['>>', '**', '*', '/', '+', '-'])

I think it is not a good idea 'cause in this case '/' is not an unary operator

[asottile]

this seems fine to me, a smaller patch however:

-UNARY_OPERATORS = frozenset(['>>', '**', '*', '+', '-'])
+UNARY_OPERATORS = frozenset(['>>', '**', '*', '/', '+', '-'])

(this is how keyword-only arguments are handled currently)
I think it is not a good idea 'cause in this case '/' is not an unary operator

neither is >> nor * nor **

[FichteFoll]

* and ** kinda are unary for unpacking, but they aren't operators in that case. I have no idea why >> is in that list, however.

Either way, since * and ** are allowed for unpacking in quite a few situations, it kind of makes sense to have them in that list, but / is really only valid in the parameter list and the suggested patch is more targeted and thus makes more sense to me.

[asottile]

>> is probably for python 2

[jakabk]

Waiting for release