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

Timestamp:

01/05/15 09:06:27 (10 years ago)

Author:

Dominic König

Comment:

--

DeveloperGuidelines/Templates/Migration

@@ -31 +31 @@
 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.
+Note that the variable "settings" is passed in as parameter for the config() function - so there is no need for "settings = current.deployment_settings". However, make sure that other functions in the template which depend on "settings" (or T) are fixed accordingly.
+
+Remember that the config.py module is no longer executed for every request (only the config() function still is). Move therefore any module-global lookups (especially those related to the logged-in user!) into callbacks, so that functions which depend on them operate with updated data and data don't leak across threads/sessions.
 
 The config() function returns nothing.