| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Change-Id: Ia047c7052a6d242c2cf1c7a83981f1e38ea4d928
|
| | |
|
| |
|
|
|
| |
having some weird unicode issues I can't debug; the meaning of
str.encode() seems to be changing globally somehow
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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]
|
| |
|
|
|
| |
- don't call os.stat twice !
- tee hee !
|
| | |
|
| |
|
|
|
|
|
|
|
| |
such that if no traceback is passed
and sys.exc_info() has been reset,
the formatter just returns blank
for the "traceback" portion.
[ticket:135]
- some long line cleanup
|
| |
|
|
|
|
| |
a given path that is a directory, not a filename,
instead of passing through to the template to
generate IOError. [ticket:73]
|
| |
|
|
|
|
|
| |
as ad-hoc
HTML file writing, consistently cleanup the modules/cache directories, use
nose skiptests for unsupported features.
|
| |
|
