Changes between Version 68 and Version 69 of DeveloperGuidelines/CodeConventions

Timestamp:

01/20/18 22:51:11 (7 years ago)

Author:

Dominic König

Comment:

--

DeveloperGuidelines/CodeConventions

@@ -219 +219 @@
 
 For everything that is to be executed in the restricted environment (i.e. all server code):
- - for messages explaining mandatory crashes that prevent the system from running at all (e.g. mandatory module import failures), use {{{sys.stderr.write()}}}
- - 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
+ - for messages that are relevant during system setup (e.g. 1st run, module import failures etc.), use {{{sys.stderr.write()}}}
+ - 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
  - for temporary debug output in code under development, use {{{sys.stderr.write()}}}
  - if absolutely necessary (re-think your design!), add the future-import to the file and use the print-''function''