summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChris McDonough <chrism@agendaless.com>2010-07-26 04:48:24 +0000
committerChris McDonough <chrism@agendaless.com>2010-07-26 04:48:24 +0000
commit89cdda356b21f197fec4b4e7194c592e0dd2cbe2 (patch)
tree877b7f48b911f8140dde599c0c9d8f6fdbcf2fe7
parentd20a86a1b2a4372693ca9810f3270a82b1085215 (diff)
downloadpyramid-89cdda356b21f197fec4b4e7194c592e0dd2cbe2.tar.gz
pyramid-89cdda356b21f197fec4b4e7194c592e0dd2cbe2.tar.bz2
pyramid-89cdda356b21f197fec4b4e7194c592e0dd2cbe2.zip
todo gardening
-rw-r--r--TODO.txt12
1 files changed, 1 insertions, 11 deletions
diff --git a/TODO.txt b/TODO.txt
index 864eb2ab5..8d5dfc7ba 100644
--- a/TODO.txt
+++ b/TODO.txt
@@ -20,14 +20,4 @@
documentation for reference to a renderer as *only* view
configuration (it's a larger concept now).
-- The ``system`` value passed to a renderer is not extensible. It
- should be extensible on a per-application basis. For example, you
- might want to add a top-level variable ``c`` to the values passed to
- all renderers representing a template context to emulate Pylons.
-
-- ``repoze.bfg.chameleon_zpt.render_template_to_response``, et. al. do
- not use the same machinery as view renderers. It would be useful if
- templates rendered with ``render_template_to_response`` had the same
- ``system`` values available to it as templates renderered via a view
- renderer.
-
+- Allow ``view=`` passed to add_route and add_view to be a string.