Unexpected effect when omitting request from pyramid.renderers.render_to_response

[dnouri]

It's probably convenient for some code paths to be able to leave out the request argument to pyramid.renderers.render_to_response. The docs carry as a sort of warning:

Supply a request parameter in order to provide the renderer with the most correct 'system' values (request and context in particular).

In my call to render, I didn't provide the request default argument, and was surprised to find out that writes to request.response attributes (such as request.response.content_type = 'foo') had no effect on the response produced by render_to_response.

I think either 1) the docs should be updated to be more clear about the consequences instead of "most correct system values", or ideally 2) the request argument to render_to_response be made required.

[mcdonc]

I don't think more words in the docs are going to help, but I'm fine with some being added.

We can't really make the request required, as people want to be able to render templates at module scope, where there is no request available.

I'm going to close this in a couple of days if no one volunteers to add words to the docs.

[cguardia]

Added small explanation.

[dnouri]

Thanks.

Render templates at module scope, sure. But render them to response on a module level?

Not sure if I'm assuming correctly that only render_to_response is a problem here, and not render. If I'm correct, then it feels like request should be a required for that particular function.