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.

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

Travis CI: Detect Python syntax errors and undefined names #63

Closed
wants to merge 8 commits into from

Conversation

cclauss
Copy link
Contributor

@cclauss cclauss commented May 1, 2019

http://flake8.pycqa.org

Follow Python porting best practice: use feature detection instead of version detection

Use print() function in both Python 2 and Python 3

  • Legacy print statements are syntax errors in Python 3 but print() function works as expected in both Python 2 and Python 3. There are 245 days until Python 2 end of life.

@autocracy autocracy force-pushed the patch-1 branch 2 times, most recently from e60ce66 to f835bc6 Compare June 18, 2020 02:00
@autocracy
Copy link
Owner

Can you properly rebase this commit? I'd love to get a clean merge.

@cclauss
Copy link
Contributor Author

cclauss commented Jun 18, 2020

Ready for your review.

@autocracy
Copy link
Owner

The merge commit I did at the end doesn't make for a clean application. They actually have to be rebased similar to what I did in #70

As for the additional commits, I'm planning on keeping the tests for Python 2.7 and 3.4 until breaking them becomes a problem. I'm going to rework travis.yaml as in #71 to still test 3.4 in xenial, but to also test the newer distribution.

autocracy added a commit that referenced this pull request Jun 23, 2020
Adds flake8 checks to test runs
Updates example/confbuilder.py file for Py3 syntax
Changes to type checking in IPy.py
@cclauss cclauss closed this Oct 2, 2020
@cclauss cclauss deleted the patch-1 branch October 2, 2020 08:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants