Skip to content
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.

Sign up for GitHub

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

Jump to bottom

pycodestyle conformance for fparser2 #89

Closed
rupertford opened this issue Jul 7, 2018 · 2 comments
Closed

pycodestyle conformance for fparser2 #89

rupertford opened this issue Jul 7, 2018 · 2 comments
Assignees
@rupertford

Comments

@rupertford
Copy link
Collaborator

fparser2 code does not conform to pycodestyle which makes it difficult to check whether new code conforms to pycodestyle. Therefore it would be useful if the existing code was made to conform.
@rupertford rupertford self-assigned this Jul 7, 2018
@rupertford
Copy link
Collaborator Author

Created branch fparser2_pycodestyle

rupertford added a commit that referenced this issue Jul 8, 2018
@rupertford
issue #89. Partial pycodestyle update for Fortran2003.py
f6d4a89
rupertford added a commit that referenced this issue Jul 8, 2018
@rupertford
issue #89 Fortran2003.py is now pycodestyle compliant
b33ba56
rupertford added a commit that referenced this issue Jul 8, 2018
@rupertford
issue #89. pattern_tools.py is now pycodestyle compliant
8a47efa
rupertford added a commit that referenced this issue Jul 8, 2018
@rupertford
issue #89. Made all tests pycodestyle compliant.
93409cd
TeranIvy added a commit that referenced this issue Jul 9, 2018
@TeranIvy
Merge pull request #90 from stfc/fparser2_pycodestyle
2ce2457 
Fparser2 pycodestyle issue #89
@TeranIvy
Copy link
Collaborator

TeranIvy commented Jul 9, 2018

PR #90 merged so closing issue.

@TeranIvy TeranIvy closed this as completed Jul 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rupertford rupertford

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rupertford @TeranIvy