-
Notifications
You must be signed in to change notification settings - Fork 201
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python 3.4 breaks Function Argument Name checking #10
Labels
Comments
been playing with it. In ipython I see the following:
So it looks like you need |
Think you might find the same issue with
|
kdopen
added a commit
to kdopen/pep8-naming
that referenced
this issue
Mar 26, 2014
In py34, a FunctionDef object changed its underlying datastructures. FunctionDef.args.kwarg.arg changed from a string to an instance of _ast.arg. The same thing seems to have happened for the *.args and *.vararg fields. This commit adds a small version-aware method to the FunctionArgNamesCheck class which safely extracts the actual argument name. This addresses issue PyCQA#10
kdopen
added a commit
to kdopen/pep8-naming
that referenced
this issue
Mar 26, 2014
In py34, a FunctionDef object changed its underlying datastructures. FunctionDef.args.kwarg.arg changed from a string to an instance of _ast.arg. The same thing seems to have happened for the *.args and *.vararg fields. This commit adds a small version-aware method to the FunctionArgNamesCheck class which safely extracts the actual argument name. This addresses issue PyCQA#10
kdopen
added a commit
to kdopen/pep8-naming
that referenced
this issue
Mar 27, 2014
In py34, a FunctionDef object changed its underlying datastructures. FunctionDef.args.kwarg.arg changed from a string to an instance of _ast.arg. The same thing seems to have happened for the *.args and *.vararg fields. This commit adds a small method to the visit_functiondef method of the FunctionArgNamesCheck class which safely extracts the actual argument name. This addresses issue PyCQA#10
kdopen
added a commit
to kdopen/pep8-naming
that referenced
this issue
Mar 27, 2014
In py34, a FunctionDef object changed its underlying datastructures. FunctionDef.args.kwarg.arg changed from a string to an instance of _ast.arg. The same thing seems to have happened for the *.args and *.vararg fields. This commit adds a small method to the visit_functiondef method of the FunctionArgNamesCheck class which safely extracts the actual argument name. This addresses issue PyCQA#10
kdopen
added a commit
that referenced
this issue
Apr 19, 2014
In py34, a FunctionDef object changed its underlying datastructures. FunctionDef.args.kwarg.arg changed from a string to an instance of _ast.arg. The same thing seems to have happened for the *.args and *.vararg fields. This commit adds a small method to the visit_functiondef method of the FunctionArgNamesCheck class which safely extracts the actual argument name. This addresses issue #10
Merged
Closed in PR #13 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Looks like something in the AST modules change in python 3.4
<class 'str'>
<class '_ast.arg'>
This breaks
FunctionArgNamesCheck.visit_functiondef()
at line 187 when the return value is passed toLOWERCASE_REGEX.match()
which expects a string value.A simple test file with the following contents:
Will produce the following exception trace when run with python 3.4
System info:
Originally seen on OSX 10.9.1
The text was updated successfully, but these errors were encountered: