1 | initial version |

If you are using Jupyter notebooks, be aware that

- a new Sage session gets launched for each worksheet you open
- closing the worksheet's browser tab does not terminate the corresponding session (reopen a worksheet and you can resume computing without having to run all cells again)

The good practice is to make sure to "Close and halt" each worksheet when done with it, as that will terminate the corresponding Sage session.

2 | No.2 Revision |

If you are using Jupyter notebooks, be aware that

- a new Sage session gets launched for each Jupyter worksheet you open
- closing the worksheet's browser tab does not terminate the corresponding session (reopen a worksheet and you can resume computing without having to run all cells again)

The good practice is to make sure to "Close and halt" each worksheet when done with it, as that will terminate the corresponding Sage session.

If you are using JupyterLab, the interface lets you more easily - spot which Jupyter workhseets still have an active kernel (ie associated Sage session). - stop those kernels one by one - or "stop all kernels"

To install JupyterLab if you haven't yet: - if you installed Sage with a package manager, use that package manager to install JupyterLab too - if you built Sage from source or installed with binaries from the Sage download page, - open a Sage session and type

```
sage: !pip install jupyterlab
```

Then to use it, run one of the following two commands in a terminal:

```
$ sage --jupyter lab
$ sage -n jupyterlab
```

3 | No.3 Revision |

If you are using Jupyter notebooks, be aware that

- a new Sage session gets launched for each Jupyter worksheet you open
- closing the worksheet's browser tab does not terminate the corresponding session (reopen a worksheet and you can resume computing without having to run all cells again)

The good practice is to make sure to "Close and halt" each worksheet when done with it, as that will terminate the corresponding Sage session.

If you are using JupyterLab, the interface lets you more ~~easily
- ~~easily

- spot which Jupyter workhseets still have an active kernel (ie associated Sage
~~session). -~~session). - stop those kernels one by
~~one -~~one - or "stop all kernels"

To install JupyterLab if you haven't ~~yet:
- ~~yet:

- if you installed Sage with a package manager, use that package manager to install JupyterLab
~~too -~~too if you built Sage from source or installed

~~with~~binaries from the Sage download page,~~-~~open a Sage session and type

Then to use ~~it, ~~Sage in JupyterLab, run one of the following two commands in a terminal:

```
$ sage --jupyter lab
$ sage -n jupyterlab
```

Or if your system-wide Jupyter installation has Sage, this should work too

```
$ jupyter lab
```

4 | No.4 Revision |

~~If you are using Jupyter notebooks, ~~Things to be aware ~~that~~of when using Jupyter notebooks:

- a new Sage session gets launched for each Jupyter worksheet you open

If you are using JupyterLab, the interface lets you more easily

- spot which Jupyter workhseets still have an active kernel (ie associated Sage session).
- stop those kernels one by one
- or "stop all kernels"

To install JupyterLab if you haven't yet:

- if you installed Sage with a package manager, use that package manager to install JupyterLab too
if you built Sage from source or installed binaries from the Sage download page, open a Sage session and type

`sage: !pip install jupyterlab`

Then to use Sage in JupyterLab, run one of the following two commands in a terminal:

```
$ sage --jupyter lab
$ sage -n jupyterlab
```

Or if your system-wide Jupyter installation has Sage, this should work too

```
$ jupyter lab
```

Copyright Sage, 2010. Some rights reserved under creative commons license. Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.