> On Mar 13, 2015, at 14:19 , Chris McDonough wrote:
>
>> […]
>
> OK that's a different issue, yep. It would be great if you could currently
> do this:
>
> @view_config(renderer='string')
> def myview(request):
>request.response.content_type = 'text/html'
>return 'Hi'
>
> But you ca
On 03/13/2015 04:05 PM, Jonathan Vanasco wrote:
On Friday, March 13, 2015 at 3:53:38 PM UTC-4, Chris McDonough wrote:
You mean renderers specified via view_config(renderer=...). Like I
said, I don't think this is the right place to implement caching.
Sorry, I think we're having 2 di
On Friday, March 13, 2015 at 3:53:38 PM UTC-4, Chris McDonough wrote:
>
> You mean renderers specified via view_config(renderer=...). Like I
> said, I don't think this is the right place to implement caching.
>
Sorry, I think we're having 2 different conversations about the same thing.
I'm n
On 03/13/2015 03:53 PM, Chris McDonough wrote:
On 03/13/2015 03:32 PM, Jonathan Vanasco wrote:
the `view_config` issue I encountered is that there is essentially no
native way to return HTML. view_config supports most other types
(templating engines, json, plaintext) but not HTML. that's very
On 03/13/2015 03:32 PM, Jonathan Vanasco wrote:
the `view_config` issue I encountered is that there is essentially no
native way to return HTML. view_config supports most other types
(templating engines, json, plaintext) but not HTML. that's very awkward
to me.
You mean renderers specified vi
the `view_config` issue I encountered is that there is essentially no
native way to return HTML. view_config supports most other types
(templating engines, json, plaintext) but not HTML. that's very awkward to
me.
--
a lot frameworks have application-level page/view/response caches. the
mo
On Fri, Mar 13, 2015 at 3:03 PM, Chris McDonough wrote:
> I've never seen such a thing in any Python web framework, but I haven't been
> looking either.
This has been around as long as I can remember:
https://docs.djangoproject.com/en/1.7/topics/cache/#the-per-view-cache
--
You received this me
On 03/13/2015 02:50 PM, Jonathan Vanasco wrote:
Thanks Chris. I agree with everything you said.
The reason why I found this weird, is that this "response" caching
pattern is common and supported in most Python frameworks. It's not
I've never seen such a thing in any Python web framework, but
Thanks Chris. I agree with everything you said.
The reason why I found this weird, is that this "response" caching pattern
is common and supported in most Python frameworks. It's not terribly hard
to implement -- but since view_config natively supports json, string, mako,
chamelon, et. -- b
On 03/13/2015 02:10 PM, Jonathan Vanasco wrote:
Ah, so you're not using it to cache the views. No one seems to. Odd.
I think this is because what you call "caching a view" means "caching a
response from a view", and this is typically done by caching the
rendering of those responses using V
Ah, so you're not using it to cache the views. No one seems to. Odd.
I've migrated my worst views into this pattern with little trouble. The
improvements seem great. There were a handful of page elements that were
customized based on the request status. In order to handle those, I've
been
I'm testing a server that performs certain tasks on intervals.
I have been using webtest TestApp for some functional and unit tests, but I
would like to test the timer/clock based functionality.
Is there an 'idle loop' API within webtest.TestApp that can be invoked, or
do I need to create a sl
12 matches
Mail list logo
