Changes between Version 68 and Version 69 of DeveloperGuidelines/CodeConventions


Ignore:
Timestamp:
01/20/18 22:51:11 (4 years ago)
Author:
Dominic König
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DeveloperGuidelines/CodeConventions

    v68 v69  
    219219
    220220For everything that is to be executed in the restricted environment (i.e. all server code):
    221  - for messages explaining mandatory crashes that prevent the system from running at all (e.g. mandatory module import failures), use {{{sys.stderr.write()}}}
    222  - for all other permanent debug/error messages: use {{{current.log.*}}}, as it can be controlled centrally, and routed to a log file when web2py isn't console-run
     221 - for messages that are relevant during system setup (e.g. 1st run, module import failures etc.), use {{{sys.stderr.write()}}}
     222 - for run-time debug/error messages: use {{{current.log.*}}}, as it can be controlled centrally, and routed to a log file when web2py isn't console-run
    223223 - for temporary debug output in code under development, use {{{sys.stderr.write()}}}
    224224 - if absolutely necessary (re-think your design!), add the future-import to the file and use the print-''function''