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


Ignore:
Timestamp:
01/05/15 09:06:27 (7 years ago)
Author:
Dominic König
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DeveloperGuidelines/Templates/Migration

    v2 v3  
    3131Function and class definitions can (should) still be at the module level, not inside the config() function.
    3232
    33 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.
     33Note 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.
     34
     35Remember 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.
    3436
    3537The config() function returns nothing.