Entry(tornado.web.UIModule): def render(self, entry, show_comments=False): return self.render_string( "module-entry.html", entry=entry, show_comments=show_comments) Tell Tornado to use uimodules.py using the ui_modules in entries %} {% module Entry(entry) %} {% end %} and entry.html: {% module Entry(entry, show_comments=True) %} Modules can include custom CSS and JavaScript functions by overriding the embedded_css margin-bottom: 1em; }" def render(self, entry, show_comments=False): return self.render_string( "module-entry.html", show_comments=show_comments) Module CSS and JavaScript will be included once no

UIModule): def render(self, entry, show_comments=False): return self.render_string( "module-entry.html", entry=entry, show_comments=show_comments) Tell Tornado to use uimodules.py using entries %} {% module Entry(entry) %} {% end %} and entry.html: {% module Entry(entry, show_comments=True) %} Modules can include custom CSS and JavaScript functions by overriding the embedded_css margin-bottom: 1em; }" def render(self, entry, show_comments=False): return self.render_string( "module-entry.html", show_comments=show_comments) Module CSS and JavaScript will be included

will be interpreted as documenting it (these are called docstrings). Note that no blank lines or comments may intervene between a docstring and the documented object. Here is a basic example: "Tell whether 37.3 Write docstrings Comments describing an object should typically be written as docstrings for editor and REPL accessibility. Inline comments (# comment) and multiline comments (#= comment =#) are appropriate reverse("JuliaLang") "gnaLailuJ" Note The examples below may be rendered differently on different systems. The comments indicate how they're supposed to be rendered Combining characters can lead to surprising results:

will be interpreted as documenting it (these are called docstrings). Note that no blank lines or comments may intervene between a docstring and the documented object. Here is a basic example: "Tell whether reverse("JuliaLang") "gnaLailuJ" Note The examples below may be rendered differently on different systems. The comments in- dicate how they're supposed to be rendered Combining characters can lead to surprising results: their arguments by convention # the number sign (or hash or pound) character begins single line comments #= when followed by an equals sign, it begins a multi-line comment (these are nestable) =# end

will be interpreted as documenting it (these are called docstrings). Note that no blank lines or comments may intervene between a docstring and the documented object. Here is a basic example: "Tell whether reverse("JuliaLang") "gnaLailuJ" Note The examples below may be rendered differently on different systems. The comments in- dicate how they're supposed to be rendered Combining characters can lead to surprising results: their arguments by convention # the number sign (or hash or pound) character begins single line comments #= when followed by an equals sign, it begins a multi-line comment (these are nestable) =# end

will be interpreted as documenting it (these are called docstrings). Note that no blank lines or comments may intervene between a docstring and the documented object. Here is a basic example: "Tell whether reverse("JuliaLang") "gnaLailuJ" Note The examples below may be rendered differently on different systems. The comments indicate how they're supposed to be rendered Combining characters can lead to surprising results: their arguments by convention # the number sign (or hash or pound) character begins single line comments #= when followed by an equals sign, it begins a multi-line comment (these are nestable) =# end

will be interpreted as documenting it (these are called docstrings). Note that no blank lines or comments may intervene between a docstring and the documented object. Here is a basic example: "Tell whether reverse("JuliaLang") "gnaLailuJ" Note The examples below may be rendered differently on different systems. The comments indicate how they're supposed to be rendered Combining characters can lead to surprising results: their arguments by convention # the number sign (or hash or pound) character begins single line comments #= when followed by an equals sign, it begins a multi-line comment (these are nestable) =# end

will be interpreted as documenting it (these are called docstrings). Note that no blank lines or comments may intervene between a docstring and the documented object. Here is a basic example: "Tell whether reverse("JuliaLang") "gnaLailuJ" Note The examples below may be rendered differently on different systems. The comments indicate how they're supposed to be rendered Combining characters can lead to surprising results: their arguments by convention # the number sign (or hash or pound) character begins single line comments #= when followed by an equals sign, it begins a multi-line comment (these are nestable) =# end

On the Agile for Defense Facebook group, I created a post where you can post your feedback as comments on the post. The URL to that post is: https://www.facebook.com/groups/AgileForDefense/permalink/2557027747901552/

will be interpreted as documenting it (these are called docstrings). Note that no blank lines or comments may intervene between a docstring and the documented object. Here is a basic example: "Tell whether reverse("JuliaLang") "gnaLailuJ" Note The examples below may be rendered differently on different systems. The comments indicate how they're supposed to be rendered Combining characters can lead to surprising results: their arguments by convention # the number sign (or hash or pound) character begins single line comments #= when followed by an equals sign, it begins a multi-line comment (these are nestable) =# end