diff options
author | R. Tyler Ballance <tyler@slide.com> | 2009-06-08 00:39:51 -0700 |
---|---|---|
committer | R. Tyler Ballance <tyler@slide.com> | 2009-06-08 00:39:51 -0700 |
commit | 60f932075c1217098b9776f7cecef8d4b39bd44f (patch) | |
tree | 5dea4d625c858e62d6c62317b78712089240420f /www | |
parent | ee54d5bbceb9a3d6f7dba9a9d73381e5d18743af (diff) | |
download | python-cheetah-60f932075c1217098b9776f7cecef8d4b39bd44f.tar.gz |
Finish up CHEP #2
Diffstat (limited to 'www')
-rw-r--r-- | www/cheps/2_import.rst | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/www/cheps/2_import.rst b/www/cheps/2_import.rst index 762d9b8..8f3a837 100644 --- a/www/cheps/2_import.rst +++ b/www/cheps/2_import.rst @@ -92,12 +92,30 @@ to the top of the generated module code (i.e. the module import) Rationale --------- +The concept of the "function import" was introduced in Cheetah v2.1.0 +and quickly retrofitted to "live" behind a compiler setting due to the +regressions with older templates or templates that were designed to utilize +module imports (through heavy #block/#end block use, etc). Through discussion +with Tavis Rudd, this middle ground between the two styles of importing was +concluded to be the most reasonable solution to providing "pythonic" import +functionality (i.e. "function import" also known as "inline imports") while +still providing the ability to have #from/#import directives declared at the +module scope within the template (within the Cheetah templates, markup and most +directives declared within the module scope are placed inside the default method). + Backwards Compatibility ----------------------- +Changes proposed in this document should be *mostly* backwards +compatible with current versions of Cheetah, Any unforeseen issues +could arise from the use of #from/#import inside of a function +expecting those symbols to be available outside of the function +that they're declared in. + Reference Implementation ------------------------ +*still in development* Copyright --------- |