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

Fixing ci, adding python3.5 python3.6 #27

Merged
merged 7 commits into from Oct 24, 2017
Merged

Fixing ci, adding python3.5 python3.6 #27

merged 7 commits into from Oct 24, 2017

Conversation

GliderGeek
Copy link
Collaborator

No description provided.

@GliderGeek GliderGeek self-assigned this Oct 24, 2017
@GliderGeek GliderGeek merged commit f165dc4 into master Oct 24, 2017
@Turbo87 Turbo87 deleted the fixing-ci branch October 25, 2017 07:21
- python: 3.6
env: TOX_ENV=py36
- python: pypy
env: TOX_ENV=pypy
Copy link
Owner

Choose a reason for hiding this comment

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

I don't understand, we shouldn't need to specify the python versions here because tox should take care of that. If it doesn't then what is the point of using tox at all?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

i think the reason is that travis does not come with python3.6 pre-istalled. Tox creates a virtualenv from this executable.

Copy link
Owner

Choose a reason for hiding this comment

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

exactly, but if you're specifying python: 3.6 then you're telling TravisCI to run in a container that uses Python 3.6 by default.

we're using tox so that we can run Python 2.7 locally (or whatever version you use) and tox will take care of creating a virtualenv with the correct Python version for the test that it currently is running.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

i thought virtualenv needed an executable of the correction python version?

Copy link
Owner

Choose a reason for hiding this comment

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

nope, tox should take care of putting the correct python version into the virtualenv

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.

None yet

2 participants