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

Introduces CI and tox testing, fixes #679 #794

Merged

Conversation

AndreMiras
Copy link
Member

  • run setup.py on both Python2 and Python3
  • runs simple test case for both Python2 and Python3
  • checks the PEP8 style
  • updates README.md adds Travis badge

- run setup.py on both Python2 and Python3
- runs simple test case for both Python2 and Python3
- checks the PEP8 style
- updates README.md adds Travis badge
@AndreMiras
Copy link
Member Author

Build is green https://travis-ci.com/kivy/buildozer/builds/97610519 ✔️

ignore =
E121, E122, E123, E125, E126, E127, E128, E129, E131, E226, E231, E241,
E262, E265, E301, E302, E303, E305, E402, E501, E502, E722, E731, E741,
F401, F821, F841, W391, W504, W605
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We will fix the most important errors little by little in subsequent pull requests

Basic test making sure the Buildozer object can be instanciated.
"""
buildozer = Buildozer()
self.assertEqual(buildozer.specfilename, 'buildozer.spec')
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This test will not catch #791 yet because buildozer.spec file doesn't exist, see https://github.com/kivy/buildozer/blob/46cc8f7/buildozer/__init__.py#L121
But I'll write a dedicated test for this case once this gets merged.


python:
- "2.7"
- "3.6"
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll purposely go for 3.6 rather because 3.7 still feels too cutting edge to me and 3.6 more mainstream while not legacy

Copy link
Contributor

@hackalog hackalog Jan 17, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure I agree with that. 3.7 is the current python release, and it's what gets installed by default if I ask for python3 in many places (e.g. my main use case: conda create -n new_environment python=3 ...

Copy link
Member Author

@AndreMiras AndreMiras Jan 17, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not on Ubuntu 18.04 LTS. Plus it's failing a lot of recipes, e.g. gevent, and when you check on upstream they say, we don't support 3.7 yet. But yes that's debatable.
In any case this PR is not about dropping some support, but more like adding testing where we had none.
Edit: thanks for the feedback by the way, very much appreciated!

@AndreMiras AndreMiras merged commit 0407331 into kivy:master Jan 17, 2019
@AndreMiras AndreMiras deleted the feature/ticket679_travis_ci_and_tox branch January 17, 2019 15:10
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