Based off the DocBlockr project, This extension provides the similar funtionality but for python docstrings. The default formatter for this plugin is designed around PEP-257 compliance but with more verbosity: Added variable types, listing class extensions, and listing decorators. The main goal of this project is to help developer provide better documentation by giving easy and consistent formatting.
Package Control Now you can install it with package control!
- Open your command pallete and type
Package Control: Install Package
. - Find this project
DocBlockr Python
and pressEnter
.
Manually Download the release and put it in your installed packages directory yourself
- Go to the Latest Release and download the
docblockr_python.sublime-package
file. - Move this file to your
Installed Packages
directory. (Preferences > Browse Packages...
and go up one directory to seeInstalled Packages
) - If you are updating your existing install, a restart of Sublime Text will be in order.
There isn't a command pallete command to start this plugin, it is triggerg by hitting enter or tab after opening a docstring ("""
) at the module
, class
, or function
level.
If you wanted to simply put a new line after opening a docstring and not trigger the formatter, just hold ctrl
and press enter.
You can configure which docstring format to use by updating your user settings for this package. (Preferences > Package Settings > DocBlockr Python > Settings (User)
)
For a full list of settings with documentation on what they affect, look at the Settings (Default)
file.
You can also override your user settings on a per project basis by editing your project file. Any setting will be available for overriding here.
{
"DocblockrPython": {
"formatter": "sphinx"
},
"folders": [
// ...
]
}
- Docblockr (PEP0257 with types)
- PEP0257
- Numpy
- Sphinx (reST)
If you don't like the formatting styles above, or want to make your own style to fit your use case, you can write your own formatter.
All you will need to do is extend the Base formatter class and write your formatter functions.
If you're not sure about it, you can take a look at any of the other formatters in the formatters
source dir and see how they did it.
from DocBlockr_Python.formatters.base import Base
class MyFormatter(Base):
# This will be used as your settings file value,
# and how the formatter is registered in the registry
name = 'my'
Note: The console should yell at you if you didn't write all the abstract methods. Be sure to read the docs on the Base
formatter
to make sure you understand all the caveats of each formatter function.
- Only detects closed docstring if it is on a line of the same indentation, and has no text in front of it. Single Line docstrings are converted to block
Things I want to do wtih this project. Not necessarily an exhaustive or prioritized list.
- Unit Tests!
- More completions!
- Javadoc style formatter
- Keyboard Shortcuts
- Reparsing Docstring (switch templating style)
- Command Pallete Commands for changing syntax
- Dynamic completions based on chosen syntax
- Integration back with the original DocBlockr
- Better Syntax Highlighting within docstrings (in particular for other styles)
- Examples of each style to completion
- Documentation (isn't it ironic?)