Skip to content

automated testing; django18, drf31 and drf32 only #66

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

Closed

Conversation

abdulhaq-e
Copy link
Contributor

No description provided.

@abdulhaq-e abdulhaq-e mentioned this pull request Aug 23, 2015
@jsenecal
Copy link
Member

Wow! that is really great work and thanks for the kind comments in #67 - I think we'll have to have the tests pass though... Maybe you could rebase to a branch we could create for that ? @jerel what do you think?

@abdulhaq-e
Copy link
Contributor Author

No problem, create the -problem fixing- branch and I will rebase this branch. I can also fix some of the problems, some are quite easy. For example, the failing tests for python 3.2 are because unicode literal are not accepted, so this is wrong u'my_string in py32. It can be easily fixed though.

jerel pushed a commit that referenced this pull request Aug 24, 2015
automated testing; django18, drf31 and drf32 only

automated testing for all environments
@jerel jerel closed this Aug 24, 2015
jerel pushed a commit that referenced this pull request Sep 15, 2015
automated testing; django18, drf31 and drf32 only

automated testing for all environments
@abdulhaq-e abdulhaq-e deleted the automated_testing branch September 18, 2015 05:19
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