Julia 1.6.2 Documentationobject (function, macro, type or instance) 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 than: f(x, y) = ... This makes it clearer where docstrings start and end. 9. Respect the line length limit used in the surrounding code. Docstrings are edited using the same tools as code. Therefore are best kept separate from the main description of the function's behavior. 11. For long docstrings, consider splitting the documentation with an # Extended help header. The typical help-mode will0 码力 | 1324 页 | 4.54 MB | 2 年前3
Julia 1.7.0 Documentationobject (function, macro, type or instance) 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 than: f(x, y) = ... This makes it clearer where docstrings start and end. 9. Respect the line length limit used in the surrounding code. Docstrings are edited using the same tools as code. Therefore are best kept separate from the main description of the function's behavior. 11. For long docstrings, consider splitting the documentation with an # Extended help header. The typical help-mode will0 码力 | 1378 页 | 4.74 MB | 2 年前3
Julia 1.5.3 Documentationobject (function, macro, type or instance) 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 \cdots \end{array} $$ This makes it clearer where docstrings start and end. 9. Respect the line length limit used in the surrounding code. Docstrings are edited using the same tools as code. Therefore are best kept separate from the main description of the function's behavior. 11. For long docstrings, consider splitting the documentation with an # Extended help header. The typical help-mode will0 码力 | 1335 页 | 4.41 MB | 2 年前3
Julia 1.5.2 Documentationobject (function, macro, type or instance) 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 \cdots \end{array} $$ This makes it clearer where docstrings start and end. 9. Respect the line length limit used in the surrounding code. Docstrings are edited using the same tools as code. Therefore are best kept separate from the main description of the function's behavior. 11. For long docstrings, consider splitting the documentation with an # Extended help header. The typical help-mode will0 码力 | 1335 页 | 4.41 MB | 2 年前3
The Python Handbook
Lambda Functions • 31. Recursion • 32. Nested Functions • 33. Closures • 34. Decorators • 35. Docstrings • 36. Introspection • 37. Annotations • 38. Exceptions • 39. The with statement • 40. Installing val = func() # do something after return val return wrapper ### 35. Docstrings Documentation is hugely important, not just to communicate to other people what is the goal of so: # this is a comment num = 1 #this is another comment Another way is to use docstrings. The utility of docstrings is that they follow conventions and as such they can be processed automatically.0 码力 | 93 页 | 7.31 MB | 2 年前3
Falcon v0.3.0.1 Documentationensure your coding style follows PEP 8 and doesn’t make pyflakes sad. ## Additional Style Rules • Docstrings are required for classes, attributes, methods, and functions. • Use napolean-flavored [http://sphinxcontrib- [http://sphinxcontrib- napoleon.readthedocs.org/en/latest/example_google.html#example-google-style-python-docstrings] dosstrings to make them readable both when using the help function within a REPL, and when browsing documentation that you can query using the above technique. The team has worked hard to optimize the docstrings for readability, so that you can quickly scan them and find what you need. ## Tip bpython [h0 码力 | 126 页 | 345.09 KB | 2 年前3
Falcon v1.0.0 Documentationmake pyflakes sad. ## Additional Style Rules • Docstrings are required for classes, attributes, methods, and functions. • Use napolean-flavored docstrings to make them readable both when using the help documentation that you can query using the above technique. The team has worked hard to optimize the docstrings for readability, so that you can quickly scan them and find what you need. Tip: bpython is another middleware) To learn more about hooks, take a look at the docstring for the API class, as well as the docstrings for the falcon.before and falcon.after decorators. Now that you’ve added a hook to validate the0 码力 | 87 页 | 348.15 KB | 2 年前3
Falcon v0.2.0 Documentationensure your coding style follows PEP 8 and doesn’t make pyflakes sad. ## Additional Style Rules • Docstrings are required for classes, attributes, methods, and functions. • Use napolean-flavored dosstrings documentation that you can query using the above technique. The team has worked hard to optimize the docstrings for readability, so that you can quickly scan them and find what you need. Tip: bpython is another d]) To learn more about hooks, take a look at the docstring for the API class, as well as the docstrings for the falcon.before and falcon.after decorators. Now that you’ve added a hook to validate the0 码力 | 70 页 | 296.15 KB | 2 年前3
Falcon v0.3.0.1 Documentationensure your coding style follows PEP 8 and doesn’t make pyflakes sad. ## Additional Style Rules • Docstrings are required for classes, attributes, methods, and functions. • Use napolean-flavored dosstrings documentation that you can query using the above technique. The team has worked hard to optimize the docstrings for readability, so that you can quickly scan them and find what you need. Tip: bpython is another d]) To learn more about hooks, take a look at the docstring for the API class, as well as the docstrings for the falcon.before and falcon.after decorators. Now that you’ve added a hook to validate the0 码力 | 77 页 | 311.34 KB | 2 年前3
Falcon v1.0.0 Documentationensure your coding style follows PEP 8 and doesn’t make pyflakes sad. ## Additional Style Rules • Docstrings are required for classes, attributes, methods, and functions. • Use napolean-flavored [http://sphinxcontrib- [http://sphinxcontrib- napoleon.readthedocs.org/en/latest/example_google.html#example-google-style-python-docstrings] docstrings to make them readable both when using the help function within a REPL, and when browsing documentation that you can query using the above technique. The team has worked hard to optimize the docstrings for readability, so that you can quickly scan them and find what you need. ## Tip bpython [h0 码力 | 249 页 | 406.22 KB | 2 年前3
共 422 条
- 1
- 2
- 3
- 4
- 5
- 6
- 43
相关搜索词
DocumentationJuliaREPLdocstringsFunctionsMarkdownJulia 1.7.0Docstrings@doc macroControl FlowModulesPython安装数据类型控制语句函数类模块异常处理调试列表元组字典集合Falcon Web Frameworkminimalist WSGI libraryREST architectural styleWSGI containerrequest handlingFalconWSGIAPImiddlewareHTTP status codesFalcon框架性能优化模块化中间件钩子错误处理中间件组件自定义请求响应WSGI框架版本更新RESTful服务依赖管理













