Changes between Version 1 and Version 2 of DeveloperGuidelines/Templates/Migration

Timestamp:

01/05/15 09:00:48 (10 years ago)

Author:

Dominic König

Comment:

--

DeveloperGuidelines/Templates/Migration

@@ -25 +25 @@
 == Refactoring config.py ==
 
-Re-structure config.py so that all settings-assignment are inside a function config():
+Re-structure config.py so that all settings-assignment are inside a function config() (see example below, or check modules/templates/skeleton/config.py). 
+
+Do not assign any members of {{{current}}} to module-global variables (e.g. move "T = current.T" inside the config() function or wherever it is needed).
+
+Function and class definitions can (should) still be at the module level, not inside the config() function.
+
+Note that the variable "settings" is passed in as parameter for the config() function - there is no need for {{{settings = current.deployment_settings}}}. However, make sure that other functions in the template which depend on settings are fixed accordingly.
+
+The config() function returns nothing.
 
 Old config.py:
@@ -93 +101 @@
 }}}
 
-Function and class definitions can (should) still be at the module level, not inside the config() function.
-
-Note that the variable "settings" is passed in as parameter for the config() function - there is no need for {{{settings = current.deployment_settings}}}.
-
-The config() function returns nothing.
-
 == Adapt all Paths inside the Template ==