"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "docs/dev_guide/patching.rst" between
cheetah3-3.1.0.tar.gz and cheetah3-3.2.0.tar.gz

About: Cheetah3 is a template engine and code generation tool for e.g. for Web development or Java, SQL, LaTeX, form email ... (written in Python).

patching.rst  (cheetah3-3.1.0):patching.rst  (cheetah3-3.2.0)
Patching Cheetah Patching Cheetah
================ ================
(patching)
How to commit changes to CVS or submit patches, how to run the test How to commit changes to CVS or submit patches, how to run the test
suite. Describe distutils and how the regression tests work. suite. Describe distutils and how the regression tests work.
File Requirements File Requirements
----------------- -----------------
(patching.fileRequirements)
The code{Template} class contains not only the Cheetah The code{Template} class contains not only the Cheetah
infrastructure, but also some convenience methods useful in all infrastructure, but also some convenience methods useful in all
templates. More methods may be added if it's generally agreed among templates. More methods may be added if it's generally agreed among
Cheetah developers that the method is sufficiently useful to all Cheetah developers that the method is sufficiently useful to all
types of templates, or at least to all types of HTML-output types of templates, or at least to all types of HTML-output
templates. If a method is too long to fit into {Template} - templates. If a method is too long to fit into {Template} -
especially if it has helper methods - put it in a mixin class under especially if it has helper methods - put it in a mixin class under
{Cheetah.Utils} and inherit it. {Cheetah.Utils} and inherit it.
Routines for a specific problem domain should be put under Routines for a specific problem domain should be put under
skipping to change at line 40 skipping to change at line 36
breaking Cheetah's core services. breaking Cheetah's core services.
If a core method needs to look up an attribute defined under If a core method needs to look up an attribute defined under
{Cheetah.Tools}, it should use {hasattr()} and gracefully provide a {Cheetah.Tools}, it should use {hasattr()} and gracefully provide a
default if the attribute does not exist (meaning the user has not default if the attribute does not exist (meaning the user has not
imported that subsystem). imported that subsystem).
Testing Changes and Building Regression Tests Testing Changes and Building Regression Tests
--------------------------------------------- ---------------------------------------------
(patching.testing)
Cheetah ships with a regression test suite. To run the built-in Cheetah ships with a regression test suite. To run the built-in
tests, execute at the shell prompt: tests, execute at the shell prompt:
:: ::
cheetah test cheetah test
Before checking any changes in, run the tests and verify they all Before checking any changes in, run the tests and verify they all
pass. That way, users can check out the CVS version of Cheetah at pass. That way, users can check out the CVS version of Cheetah at
any time with a fairly high confidence that it will work. If you any time with a fairly high confidence that it will work. If you
 End of changes. 3 change blocks. 
6 lines changed or deleted 0 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)