File size: 11,909 Bytes
fa0f006 |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 |
A Code Prettifier
=================
This nbextension reformats/prettifies code in notebook code cells.
Under the hood, it uses a call to the current notebook kernel to reformat the
code.
Thus the actual prettifier package has to be callable from the current kernel
language.
With an appropriately-configured prettifier for the kernel in use, the
nbextension provides
- a toolbar button (configurable to be added or not)
- a keyboard shortcut for reformatting the current code-cell (default shortcut
is `Ctrl-L`, can also be configured not to add the keyboard shortcut).
- a keyboard shortcut for reformatting the whole notebook (default shortcut
is `Ctrl-Shift-L`, can also be configured not to add the keyboard shortcut).
Syntax shall be correct. The nbextension may also point out basic syntax errors.



Compatible Kernels
------------------
Example implementations are provided for prettifiers for ipython, ir and
ijavascript kernels which should work out of the box (assuming availability of
the relevant kernel-specific [prerequisites] mentioned below), but the
kernel-specific prettifier calls are configurable, so the model is applicable
to essentially any kernel language and prettifier library.
Other languages may be added as defaults in the future, but given that there
are more than 50 [kernels] available for Jupyter, it is not easily possible to
support all of them out of the box, unless people with experience in the
relevant kernels have the time to contribute code. For information on how the
reformatting takes place, and how to adapt it for your particular
kernel/prettifier, see the [options] and [internals] sections below.
If you implement a language that isn't yet provided by default, please submit a
PR or let us know to add it to the repo :)
Under the hood, this nbextension's functionality is provided by the
[KerneExecOnCells library], a shared library for creating Jupyter nbextensions
which transform code cell text using calls to the active kernel.
Prerequisites
-------------
Of course, you must have the necessary kernel-specific packages installed for
the prettifier call to work:
- for the default python implementation, the [yapf] module is required:
pip install yapf
Others you might consider using include [autopep8] - see [README_autopep8.md].
- for R, the default implementation uses the [formatR] and [jsonlite] packages:
```r
install.packages(c("formatR", "jsonlite"), repos="http://cran.rstudio.com")
```
- for [ijavascript], the [js-beautify] package is used:
(*Under linux, in the root of your user tree = ~*)
npm install js-beautify
Under Windows, you may then need to set the `NODE_PATH` environment variable
(see [this question on stackoverflow]) to it to `%AppData%\npm\node_modules`
(Windows 7/8/10).
To be done with it once and for all, add this as a System variable in the
Advanced tab of the System Properties dialog.
Options
-------
All options are provided by the [KerneExecOnCells library]. - see the
[internals] section below for details.
There are a few nbextension-wide options, configurable using the
[jupyter_nbextensions_configurator] or by editing the `notebook` section config
file directly.
The options are as follows:
- `code_prettify.add_toolbar_button`:
Whether to add a toolbar button to transform the selected cell(s).
Defaults to `true`.
- `code_prettify.button_icon`:
A font-awesome class defining the icon used for the toolbar button and
actions. See [fontawesome] for available icon classes.
Defaults to `fa-legal`.
- `code_prettify.button_label`:
Toolbar button label text. Also used in the actions' help text.
Defaults to `Code prettify`.
- `code_prettify.register_hotkey`:
Whether to register hotkeys to transform the selected cell(s)/whole notebook.
Defaults to `true`.
- `code_prettify.hotkeys.process_all`:
Hotkey to use to transform all the code cells in the notebook.
Defaults to `Ctrl-Shift-L`.
- `code_prettify.hotkeys.process_selected`:
Hotkey to use to transform the selected cell(s).
Defaults to `Ctrl-L`.
- `code_prettify.show_alerts_for_not_supported_kernel`:
Whether to show alerts if the kernel is not supported.
Defaults to `false`.
- `code_prettify.show_alerts_for_errors`:
Whether to show alerts for errors in the kernel calls.
Defaults to `true`.
- `code_prettify.kernel_config_map_json`:
The value of this key is a string which can be parsed into a json object
giving the config for each kernel language.
The following give the per-kernel options of the parsed json, using the
language key `python `:
* `code_prettify.kernel_config_map_json.python.library`:
String to execute in the kernel in order to load any necessary kernel
libraries.
* `code_prettify.kernel_config_map_json.python.replacements_json_to_kernel`:
a list of pairs of strings, used as arguments to javascript's
`String.replace(from, to)` to translate from a json string into a valid
representation of the same string in the kernel language. Since json
strings are particularly simple, this can often (as with the python
language) be left as the default, an empty list.
* `code_prettify.kernel_config_map_json.python.prefix` and
`code_prettify.kernel_config_map_json.python.postfix`:
Strings added as bookends to the kernel string (translated from the json
string using the replacements above) to make up the kernel prettifier call
kernel's prettifier libraries.
* `code_prettify.kernel_config_map_json.python.trim_formatted_text`:
Whether to trim whitespace from the transformed cell text. Since jupyter
cells don't usually have leading or trailing whitespace, the default
behaviour is to trim the transformed text, in order to prevent the
transform adding extra newlines at the end (a common behaviour for source
files, where having a trailing newline is often considered good practice).
Internals
---------
Under the hood, this nbextension uses the [KerneExecOnCells library], a shared
library for creating Jupyter nbextensions which transform code cell text using
calls to the active kernel.
The model is essentially:
1. The cell text is grabbed by client-side javascript, then turned into a json
string using javascript `JSON.stringify`. Since json-compatible strings are
a particularly simple string format, which is compatible with many other
programming languages without much modification (e.g. a valid json string
is also a valid string in python 3, and also in python 2 when prefixed with
a `u`), and easily converted for use in others (because of its simplicity).
2. Optional regex replacements are used to translate the json-format string
into a valid kernel string. Python, R and javascript don't require this
step, but other languages may do, so it's implemented for flexibility
using the per-kernel config key `replacements_json_to_kernel`, which is a
list of pairs of arguments to javascript `String.replace`.
3. The kernel-specific prettifier call is then composed from
`kernel_config.prefix` + `kernel_text_string` + `kernel_config.postfix` and
sent to the kernel for execution. This kernel call is expected to get the
formatted cell text _printed_ as a json-compatible string. Since most
kernel languages have json packages, this should hopefully be easy to
arrange. The reason for the printing text rather than simply displaying it,
is that it prevents us having to translate from a kernel string
representing a json string.
4. The callback for the kernel execution in client-side javascript parses the
printed json-format string, optionally trims trailing whitespace according
to the `trim_formatted_text` key (which defaults to `true`) in the
per-kernel config, and then sets the cell text using the result.
The process is probably best illustrated using an example for the python
implementation:
1. **At nbextension load**, the `code_prettify.kernel_config_map_json` config
option is parsed to give the json object
```json
{
"python": {
"library": "import json\nimport yapf.yapflib.yapf_api",
"prefix": "print(json.dumps(yapf.yapflib.yapf_api.FormatCode(u",
"postfix": ")[0]))"
}
}
```
(other kernel languages are omitted for clarity).
2. **On kernel becoming ready**, the nbextension looks up the config for the
kernel's language (in our example, this is the `python` key of the kernel
config json object above). It then sends the kernel config's `library`
string to the kernel for execution. Thus the python implementation above
executes
```python
import json
import yapf.yapflib.yapf_api
```
3. **On requesting a cell be prettified** which can happen by clicking the
toolbar, or with a (configurable) hotkey, the following happens:
Say the cell to be formatted contains the following ugly python code:
```python
msg= 'hello '+"world"
print (
msg )
```
Then the result of the `JSON.stringify` call will be a string containing
```json
"msg= 'hello '+\"world\"\nprint (\n msg )"
```
(note the opening and closing quotes). Concatenating this with the prefix &
postfix strings from the python kernel config above, gives us the kernel
code to execute. The call sent to the python kernel is therefore
```python
print(json.dumps(yapf.yapflib.yapf_api.FormatCode(u"msg= 'hello '+\"world\"\nprint (\n msg )")[0]))
```
4. What gets 'printed' by the kernel (i.e. returned to the javascript stream
callback) is the following json-format string:
```json
"msg = 'hello ' + \"world\"\nprint(msg)\n"
```
The default is to trim whitepace from the returned prettified text, which
results in the final prettified python code for the cell:
```python
msg = 'hello ' + "world"
print(msg)
```
History
-------
- [@jfbercher], august 14, 2016, first version, named `yapf_ext`
- [@jfbercher], august 19, 2016, second version `code_prettify`
- introduced support for R and javascript.
- changed extension name from `yapf_ext` to `code_prettify`
- [@jcb91], december 2016
- made addition of toolbar button & hotkey configurable
- reworked to avoid regex replacements for conversion to/from kernel string
formats, in favour of json-string interchange
- made kernel-specific prettifier calls configurable, allowing support for
different prettifiers & arbitrary kernels
- improved documentation
- [@jfbercher], december 2016-january 2017
- added a configurable shortkey to reflow the whole notebook
- extracted most of the code to build a general library of functions,
`kernel_exec_on_cell.js`, which can be used for all nbextensions which
needs to exec some code (via the current kernel) on the text from cells.
[@jcb91]: https://github.com/jcb91
[@jfbercher]: https://github.com/jfbercher
[autopep8]: https://github.com/hhatto/autopep8
[formatR]: https://yihui.name/formatr
[fontawesome]: https://fontawesome.com/icons
[ijavascript]: https://n-riesco.github.io/ijavascript
[internals]: #Internals
[js-beautify]: https://github.com/beautify-web/js-beautify
[jsonlite]: https://github.com/jeroen/jsonlite
[jupyter_nbextensions_configurator]: https://github.com/Jupyter-contrib/jupyter_nbextensions_configurator
[KerneExecOnCells library]: README.md
[kernels]: https://github.com/ipython/ipython/wiki/IPython-kernels-for-other-languages
[options]: #Options
[prerequisites]: #Prerequisites
[README_autopep8.md]: README_autopep8.md
[this question on stackoverflow]: https://stackoverflow.com/questions/9587665/nodejs-cannot-find-installed-module-on-windows
[yapf]: https://github.com/google/yapf
|