| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
init.js, not sure what that is
|
|
|
|
|
|
| |
get rtd
to show both versions
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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]
|
| |
|
| |
|
|
|
|
|
|
|
| |
whereby the identity of the "caller" callable
inside the <%def> would be corrupted by the
presence of another <%call> in the same block.
[ticket:170]
|
|
|
|
| |
[ticket:169]
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
evaluates its contents in-place.
Can be named or anonymous,
the named version is intended for inheritance
layouts where any given section can be
surrounded by the <%block> tag in order for
it to become overrideable by inheriting
templates, without the need to specify a
top-level <%def> plus explicit call.
Modified scoping and argument rules as well as a
more strictly enforced usage scheme make it ideal
for this purpose without at all replacing most
other things that defs are still good for.
Lots of new docs. [ticket:164]
|
|
|
|
|
|
| |
for generating template bound stacktraces.
Will stick to known template source lines
without any extra guessing. [ticket:165]
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
because a string and an ascii encoded string are of course
different things, and we'd like render() by default to return a
string. So go the other way, use FEB in all cases,
add a new flag bytestring_passthrough which goes back to StringIO,
to support that one guy who wanted to force a bytestring through
in an expression.
|
|
|
|
| |
- misc cleanup
|
|
|
|
| |
there's a namespace or include
|
|
|
|
|
| |
- don't call os.stat twice !
- tee hee !
|
|
|
|
|
|
|
|
| |
it's internal _data dictionary, now
include just what was specified to
render() as well as Mako builtins
'caller', 'capture'. The contents
of __builtin__ are no longer copied.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- The "output encoding" now defaults
to "ascii", whereas previously
it was set to None. This has the effect
of FastEncodingBuffer being used internally
by default when render() is called, instead
of cStringIO or StringIO, which are
slower, but allow bytestrings with
unknown encoding to pass right through.
It is of course not recommended to use
bytestrings of unknown encoding. Usage of
the "disable_unicode" mode also requires
that output_encoding be set to None.
|
| |
|
| |
|
|
|
|
| |
figured out yet
|
| |
|
|
|
|
| |
- convert heading copyrights to 2006-2011, reference AUTHORS file
|
| |
|
| |
|
|\ |
|
| | |
|
|/
|
|
| |
least remove huge lines
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
- move Namespace docs inline to attributes on Namespace
- document Cache methods, add to caching.rst
- use functools.partial for partials, part of [ticket:156]
|
| |
|
| |
|
|
|
|
|
| |
'' write in the case of backslash-ended
lines. [ticket:155]
|
|
|
|
|
|
|
|
| |
is delayed until actually needed;
this to remove the performance penalty
from startup, particularly for
"single execution" environments
such as shell scripts. [ticket:153]
|
|
|
|
|
|
|
|
| |
setup.py instead of "install_requires".
This to produce a lighter weight install
for those who don't use the caching
as well as to conform to Pyramid
deployment practices. [ticket:154]
|
|
|
|
|
|
| |
setup.py which prevented setup.py
from running 2to3 on install.
[ticket:148]
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
are considered "undefined", meaning they
are pulled from the context, has been
trimmed back to not include variables
declared inside of expressions (i.e. from
list comprehensions), as well as
in the argument list of lambdas. This
to better support the strict_undefined
feature.
|