Skip to content
Snippets Groups Projects
  1. Jul 08, 2012
  2. May 14, 2012
  3. Apr 13, 2012
  4. Apr 06, 2012
  5. Apr 03, 2012
  6. Mar 30, 2012
  7. Mar 24, 2012
  8. Mar 12, 2012
  9. Mar 09, 2012
  10. Feb 21, 2012
  11. Feb 02, 2012
  12. Jan 28, 2012
  13. Jan 21, 2012
  14. Jan 19, 2012
  15. Jan 18, 2012
  16. Jan 16, 2012
  17. Jan 12, 2012
  18. Dec 05, 2011
  19. Oct 02, 2011
  20. Oct 01, 2011
    • Mike Bayer's avatar
      install extreme hoops for pkg_resources and I'm starting to wonder if · b19513c8
      Mike Bayer authored
      I really want to do it like this
      b19513c8
    • Mike Bayer's avatar
      pkg_resources hoops · 907a37e7
      Mike Bayer authored
      907a37e7
    • Mike Bayer's avatar
      need this too · a6b60799
      Mike Bayer authored
      a6b60799
    • Mike Bayer's avatar
      - Template caching has been converted into a plugin · 643701f1
      Mike Bayer authored
        system, whereby the usage of Beaker is just the
        default plugin.   Template and TemplateLookup
        now accept a string "cache_impl" parameter which
        refers to the name of a cache plugin, defaulting
        to the name 'beaker'.  New plugins can be
        registered as pkg_resources entrypoints under
        the group "mako.cache", or registered directly
        using mako.cache.register_plugin().  The
        core plugin is the mako.cache.CacheImpl
        class.
      
      - The <%def>, <%block> and <%page> tags now accept
        any argument named "cache_*", and the key
        minus the "cache_" prefix will be passed as keyword
        arguments to the CacheImpl methods.
      
      - Template and TemplateLookup now accept an argument
        cache_args, which refers to a dictionary containing
        cache parameters.  The cache_dir, cache_url, cache_type,
        cache_timeout arguments are deprecated (will probably
        never be removed, however) and can be passed
        now as cache_args={'url':<some url>, 'type':'memcached',
        'timeout':50, 'dir':'/path/to/some/directory'}
      643701f1
  21. Sep 28, 2011
    • Mike Bayer's avatar
      - A Template is explicitly disallowed · 5cd508ff
      Mike Bayer authored
        from having a url that normalizes to relative outside
        of the root.   That is, if the Lookup is based
        at /home/mytemplates, an include that would place
        the ultimate template at
        /home/mytemplates/../some_other_directory,
        i.e. outside of /home/mytemplates,
        is disallowed.   This usage was never intended
        despite the lack of an explicit check.
        The main issue this causes
        is that module files can be written outside
        of the module root (or raise an error, if file perms aren't
        set up), and can also lead to the same template being
        cached in the lookup under multiple, relative roots.
        TemplateLookup instead has always supported multiple
        file roots for this purpose.
        [ticket:174]
      rel_0_5_0
      5cd508ff
  22. Aug 05, 2011
  23. Jul 08, 2011
Loading