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 & Python 3 #76

Closed
ib-lundgren opened this issue Nov 16, 2012 · 8 comments · Fixed by #115
Closed

Travis & Python 3 #76

ib-lundgren opened this issue Nov 16, 2012 · 8 comments · Fixed by #115
Labels

Comments

@ib-lundgren
Copy link
Collaborator

Not sure if Travis supports Python 3 yet, if it does we should add that to our config.

@lepture
Copy link
Collaborator

lepture commented Nov 22, 2012

yes. it does.

@sigmavirus24
Copy link

It supports 3.1 and 3.2 afaik. No response from them on 3.3 yet.

@ib-lundgren
Copy link
Collaborator Author

Travis does not support 3.1, 3.2 and 3.3 should work when we find a way to exclude the installation of unittest2 for python 3 envs.

@sigmavirus24
Copy link

@ib-lundgren you're correct that they stopped supporting 3.1 and now only support 3.2 and 3.3. If you want I can write something for you that will manage the dependencies based on python version, but you'll have to use python setup.py install for the install command, not pip install -r requirements.txt.

@ondrowan
Copy link
Contributor

I started to (really) slowly implement oauthlib to Django and this is setup i'm using for testing: https://github.com/ondrowan/django-oauthlib/blob/master/.travis.yml. It should solve unittest2 issues.

@ib-lundgren
Copy link
Collaborator Author

We are using pip + crate.io currently as setup.py has been flaky with PyCrypto (falls back on a ftp that quite often is unavailable if I remember correctly).

@ib-lundgren
Copy link
Collaborator Author

Hrm, using tox might very well work. Will reduce duplication of dependency spec slightly too =)

@ib-lundgren
Copy link
Collaborator Author

Updated to use tox, only failed a few times... Removed 3.1 from tox.ini, will continue to test it locally but don't think it's a major issue not having everything go through it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants