Skip to content

Conversation

vinayinvicible
Copy link
Contributor

@vinayinvicible vinayinvicible commented Nov 16, 2016

@timgraham timgraham changed the title fixed request.POST being mutable for multipart requests Fixed #17235 -- Made MultiPartParser leave request.POST unmutable. Nov 16, 2016
Copy link
Member

@lovelydinosaur lovelydinosaur Nov 21, 2016

Choose a reason for hiding this comment

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

Is there any more graceful way we could do this? It seems odd to make request.POST immutable, but then to get past that by replacing it with a mutable instance in this cases. (May not be a show stopper, but worth considering)

Copy link
Contributor Author

@vinayinvicible vinayinvicible Nov 22, 2016

Choose a reason for hiding this comment

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

I thought of passing post_url_continue None or url, instead of messing with request.POST and in the base method checking if default of post_url_continue is overridden.
But then I felt this is not the best approach when dealing with methods.

@timgraham timgraham changed the title Fixed #17235 -- Made MultiPartParser leave request.POST unmutable. Fixed #17235 -- Made MultiPartParser leave request.POST immutable. Dec 7, 2016
@timgraham timgraham changed the title Fixed #17235 -- Made MultiPartParser leave request.POST immutable. Refs #17235 -- Made MultiPartParser leave request.POST immutable. Dec 7, 2016
@timgraham timgraham merged commit 4a246a0 into django:master Dec 7, 2016
@vinayinvicible vinayinvicible deleted the ticket_17235 branch December 7, 2016 14:59
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