On Monday, September 14, 2015 at 2:55:05 PM UTC-4, Vincent Catalano wrote: > > If each of your views is mapped to a separate template file I would > consider registering each route imperatively. That way, you can still > utilize the application's template configuration. If that's not an option, > I think #3 would be your next best bet; it seems like the DRYest of 1-3. >
Thanks. I forgot about add_view. That's a good possible option too! I can still use the template config on version 3 (which I'm currently leaning towards) via render_to_response. I did some quick tests with psutil - I'm learning to option #3 right now because it seems to be the leanest for memory -- It looks like registering everything with `@viewconfig` and `@add_route` ends up consuming over 2MB of RAM. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
