Skip to content

Conversation

@andreif
Copy link
Contributor

@andreif andreif commented Nov 18, 2015

Copy link
Contributor

Choose a reason for hiding this comment

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

This should go to the compat.py file and should be similar to the new API.

@xordoquy
Copy link
Contributor

Thanks for fixing this. I think the code should be moved to compat.py and be given an API similar to Django's new one.

@andreif
Copy link
Contributor Author

andreif commented Nov 18, 2015

Ok, I fix

@andreif andreif force-pushed the fix/deprecation-warning-1.9 branch from 3bf5dfd to 802ee5d Compare November 18, 2015 16:10
@andreif
Copy link
Contributor Author

andreif commented Nov 18, 2015

@xordoquy Done.

@lovelydinosaur
Copy link
Contributor

Looks good - thanks!

lovelydinosaur added a commit that referenced this pull request Nov 18, 2015
Fix template.render deprecation warnings for Django 1.9
@lovelydinosaur lovelydinosaur merged commit 43c45cc into encode:master Nov 18, 2015
@andreif andreif deleted the fix/deprecation-warning-1.9 branch November 18, 2015 16:19
@jezdez
Copy link

jezdez commented Nov 24, 2015

We're trying to switch to Django 1.8 using django-jinja which expects to be passed a request to the render method. I was wondering if the condition whether to pass in the request could be modified in DRF to be checking for < (1, 8) instead?

@xordoquy
Copy link
Contributor

Indeed, this seems to have slip through.

@xordoquy
Copy link
Contributor

@jezdez thanks for the report !

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 this pull request may close these issues.

4 participants