Add test+build infrastructure (Tox and Travis CI)

[bittner]

First steps towards automatic builds. Adds:

• a Tox configuration for running linting and tests (locally), and
• a Travis CI configuration.

See https://travis-ci.org/bittner/PythonTurtle while I'm testing the results of this implementation.

[cool-RR]

Great job!

[bittner]

You now need to activate this repository on Travis CI:

1. Log in to your Travis CI account
2. Go to https://travis-ci.org/cool-RR/PythonTurtle
3. Push the "Activate this repository" button

[cool-RR]

It wasn't exactly a button like you described, but I think I activated it, could you verify?

…

On Sun, Sep 16, 2018 at 10:34 AM Peter Bittner ***@***.***> wrote: You now need to activate this repository on Travis CI: 1. Log in to your Travis CI account 2. Go to https://travis-ci.org/cool-RR/PythonTurtle 3. Push the "Activate this repository" button — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#100 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADdysP-nlKW7mAKx6xOlN5iLqV79Ymoks5ubf8KgaJpZM4Wqt-2> .

[bittner]

Yeah, that looks good! https://travis-ci.org/cool-RR/PythonTurtle

Next Steps

1. I'll add a cute build status badge on top of the README for this.
2. I'll make sure we get a green tick for the build status for new commits and PRs.

Afterwards, I'll try to:

1. Make the code base comply with PEP8 using flake8 linting.
2. Fix issues Pylint complains about.

Finally, the less trivial tasks:

1. Figure out whether I can port the codebase to wxgtk4.0, still staying compatible with wxgtk3.0. (This may be impractical, we'll see.) -- Migrate PythonTurtle to wxgtk4.0 #99
2. Make the code base work across all Python versions we're testing against (including Python 3 and PyPy).
3. Add a few tests that actually make sense and help with refactoring.

In the end, we can look into automating the building of the installer packages.

[cool-RR]

Sounds good to me!

…

On Sun, Sep 16, 2018, 10:55 Peter Bittner ***@***.***> wrote: Yeah, that looks good! https://travis-ci.org/cool-RR/PythonTurtle Next Steps 1. I'll add a cute *build status button* on top of the README for this. 2. I'll make sure we get *a green tick* for the build status for new commits and PRs. Afterwards, I'll try to: 1. Make the code base comply with PEP8 using flake8 linting. 2. Fix issues Pylint complains about. Finally, the less trivial tasks: 1. Figure out whether I can port the codebase to wxgtk4.0, still staying compatible withwxgtk3.0. (This may be impractical, we'll see.) -- #99 <#99> 2. Make the code base work across all Python version we're testing against (including Python 3 and PyPy). 3. Add a few tests that actually makes sense and help with refactoring. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#100 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADdytsQbQPCu835zlPOJeGQL2USxp6bks5ubgPUgaJpZM4Wqt-2> .

[bittner]

Thanks for merging so quickly, by the way! 👍 😃