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

Python3 configuration #63

Merged

Conversation

pferate
Copy link
Contributor

@pferate pferate commented Mar 3, 2015

Setting up test environment for 3.3 and 3.4. Expect lots of red for now.

@pferate pferate mentioned this pull request Mar 3, 2015
commands = nosetests

[testenv:py34]
commands = nosetests

This comment was marked as spam.

@nathanielmanistaatgoogle
Copy link
Contributor

Diff looks good but commit chain looks really weird - let's get that cleaned up.

I'm disinclined to redden the master build of the project; would it be okay to keep this change on ice and keep updating it as the prerequisite changes to the rest of the codebase land?

@pferate pferate force-pushed the python3-configuration branch from 31e648c to 75311a8 Compare March 3, 2015 23:33
@pferate
Copy link
Contributor Author

pferate commented Mar 3, 2015

Initially, I pulled through github's web interface to update my master branch, which put in that extra commit.

I rolled back and redid the commits through CLI, so that it looks cleaner now.

I'm okay with holding off on merging this for now, I just did it so that I could see the errors from tox and travis; the only red would be from the python 3 tests until we were finished.

@pferate
Copy link
Contributor Author

pferate commented Mar 4, 2015

@nathanielmanistaatgoogle: I created my other branch (PR #64) off of this one, so it also includes these two commits.

I suppose it's up to you how you would like to merge these two PRs.

@nathanielmanistaatgoogle
Copy link
Contributor

(This pull request also smells obviated in light of #64 and like it should be closed.)

@pferate
Copy link
Contributor Author

pferate commented Mar 10, 2015

Not quite. This PR is for adding the Python 3.3 and 3.4 tests to tox (and in turn travis).

I will rebase this branch and let you know when it's ready to merge.

Should I move the IDE additions in .gitignore to another PR, or would you just want to keep it out of the master branch all together?

@nathanielmanistaatgoogle
Copy link
Contributor

My first reaction is to say that the IDE additions to .gitignore should be kept out of the master branch altogether because they strike me as one person's personal development circumstances and thus not appropriate for a shared codebase. Are there other developers who would want those additions? Are they so insignificant that I shouldn't even bother caring?

@pferate pferate force-pushed the python3-configuration branch from 75311a8 to 916ca32 Compare March 10, 2015 17:51
@pferate
Copy link
Contributor Author

pferate commented Mar 10, 2015

Understandable. This PR is now just the one commit that adds the test environments to tox.

Edit: Just noticed that I should probably update the commit message.....

@pferate pferate force-pushed the python3-configuration branch from 916ca32 to 7d43236 Compare March 10, 2015 18:02
@nathanielmanistaatgoogle
Copy link
Contributor

Any idea what's up with Travis taking forever to test this?

@pgrosu
Copy link

pgrosu commented Mar 10, 2015

Looks like it just started now based on this:

https://travis-ci.org/google/google-api-python-client/builds/53837903

nathanielmanistaatgoogle added a commit that referenced this pull request Mar 10, 2015
@nathanielmanistaatgoogle nathanielmanistaatgoogle merged commit 59a5839 into googleapis:master Mar 10, 2015
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.

3 participants