| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
This reverts commit 5dc95cfcd015628665d3672e56d0551943b5db6b.
|
|
|
|
|
|
|
| |
underscores
Issue originally reported by Kirill Uhanov <kirill.uhanov@intel.com> on the mailing
list (see: "problem with include directive on cheetah 2.4.0")
|
|
|
|
|
| |
Fixes from 2to3 include: xrange, ws_comma, repr, reduce,
raise, idioms, has_key, future, filter, exec, callable, apply
|
|
|
|
|
|
| |
Added a test for ArgList as well; a large amount of code in
Cheetah.Parser could do well to be cleaned up, but perhaps another
day.
|
| |
|
| |
|
|
|
|
|
|
|
| |
my PATH
Adding the "buildandrun" shortcut script so to easily rerun the
full test suite locally; usage: ./buildandrun cheetah/Tests/Test.py
|
|
|
|
|
| |
Left out cheetah/Template.py which will need to be refactored
a bit more aggressively, particularly in Template.compile()
|
|
|
|
|
| |
Removed prints in a couple places entirely, some of this
code should likely use the `logging` module instead
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
unicode object internally
There is no longer any value in having the filters return encoded str objects,
since they need to be decoded back to unicode before they can be combined with
the rest of the template text (which is managed as a unicode object). This
patch maintains API compatibility but fundamentally changes the behavior of
some of the filters. RawOrEncodedUnicode and EncodeUnicode should be
deprecated and removed from the API.
Signed-off-by: R. Tyler Ballance <tyler@monkeypox.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Template.__str__() returns encoded str() objects
Per my discussion in #cheetah on IRC with mikeb@ regarding the following issue:
https://bugzilla.redhat.com/show_bug.cgi?id=529332
This, in addition to recent patches to cheetah/DummyTransaction.py should alleviate
migration issues for users still passing a mishmash of unicode()/str() objects into
Templates. __str__() should return a str() object, whereas __unicode__() should
return a unicode() object.
No-op the EncodeUnicode filter when it encounters a unicode() object.
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
cheetah/Template.py
cheetah/Tests/Performance.py
cheetah/Version.py
|
| |
| |
| |
| |
| | |
Starting the 2.4.xx series to denote base-compatibility with Python 2.4
and up
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
a more optimistic approach
Borrowing some concepts from the "slide-compat" branch that I maintain
for Slide, Inc. for gracefully handling less-than-ideal string-encoding
situations (as is the case for Slide).
Making DummyResponse.getvalue() optimistic in trying to u''.join() a
list of random string (unicode, str (various encodings)) objects
and then only on a UnicodeDecodeError, run through the "safeConvert"
function (blech) to handle encoded str() objects
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit 9ac5e4c6ed36c3b6b1bc8340fdb69d32db9d98c4.
Left some of my previous changes in place; self._outputChunks
will deal with only utf-8 encoded strings and then decode them all
at the very end
Conflicts:
cheetah/DummyTransaction.py
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
I'm uncertain if there's any lossiness in encoding a unicode()
object 'utf-8' prior to writing to the stream, but this does
appear to inadvertantly fix another issue we had with mixing UTF-8
encoded strings and unicode() objects when filling a template.
|
| |
| |
| |
| | |
Signed-off-by: R. Tyler Ballance <tyler@monkeypox.org>
|
| |
| |
| |
| | |
Suggested by: aahz@
|
| |\ |
|
| | | |
|
| | |\ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
avoid DeprecationWarnings when running the tests on python >= 2.6
Finally got tired of 'em. :)
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
I want to print out the directories to ensure that I'm actually
testing the code I think I'm testing (*facepalm*)
|
| | | |
| | | |
| | | |
| | | | |
The amount of type-checking here is absurd for a duck-typed language
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When running cheetah.Tests.Performance.DynamicMethodCompilationTest
with 100000 iterations set, Template.__init__() is the most performance
sensitive call.
Prior to this commit:
ncalls tottime percall cumtime percall filename:lineno(function)
100000 12.558 0.000 15.274 0.000 Template.py:1025(__init__)
After this commit:
ncalls tottime percall cumtime percall filename:lineno(function)
100000 1.263 0.000 3.541 0.000 Template.py:1025(__init__)
That code need not execute every time __init__ is called
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
avoid DeprecationWarnings when running the tests on python >= 2.6
Finally got tired of 'em. :)
|
| | |/
| |/| |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When running cheetah.Tests.Performance.DynamicMethodCompilationTest
with 100000 iterations set, Template.__init__() is the most performance
sensitive call.
Prior to this commit:
ncalls tottime percall cumtime percall filename:lineno(function)
100000 12.558 0.000 15.274 0.000 Template.py:1025(__init__)
After this commit:
ncalls tottime percall cumtime percall filename:lineno(function)
100000 1.263 0.000 3.541 0.000 Template.py:1025(__init__)
That code need not execute every time __init__ is called
|
| | | |
|
| | | |
|
|/ / |
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|