Panel 1.4 has just been released! Checkout the release notes and support Panel by giving it a 🌟 on Github.

Develop Seamlessly Across Environments#

Our objective is to empower teams to seamlessly utilize Panel regardless of the development environment, e.g. Jupyter Notebook, Jupyter Lab, Binder, Google Colab, Spyder, VS Code, and PyCharm.


We love notebooks.

Notebook friendly#

Jupyter notebooks have been supported in Panel since day 1. Notebooks are environments that allow one to iterate quickly, running some code and observing instantaneously its output. Notebooks also happen to be a valid deployment option:

  • you can actually develop apps that are meant to live only in a notebook, that you will share as a file with your colleagues and friends. Panel allows you to make your notebooks more user friendly, like IPywidgets does.

  • you can serve a notebook with panel serve file.ipynb, Panel will parse your notebook to collect all of its code and run it as if it were a Python script.

Jupyter notebooks aren’t the only flavor of notebooks available, Panel also supports Visual Studio Code and Google Colab notebooks, and probably works fine on other platforms. For Visual Studio Code notebooks, you will need to install the jupyter_bokeh package in your environment.


The first step when working in a notebook environment should always be to load the pn.extension:

import panel as pn


The extension ensures that the pyviz_comms and all required Javascript and CSS resources are added to your notebook environment. If you are going to be using any custom extensions, such as Vega or Tabulator you must ensure that you initialize these as well.

pn.extension('vega', 'tabulator')

Rich display#

One of the major benefits of notebook environments is that they support rich output. This means that if you place an object with rich output at the end of a cell the notebook will figure out how to render the rich representation. Panel uses this mechanism to ensure that all components return a rich representation.

pane = pn.panel('<marquee>Here is some custom HTML</marquee>')

To instead see a textual representation of the component, you can use the print function on any Panel object.


Callback logs#

When you set up interactivity in your app using one of the various ways Panel offers to register a callback (e.g. param.bind,, on_<event> methods), it can be useful for you as a developer to print some debug information. Panel catches all the content sent to stdout and stderr when callbacks are executed and renders it above the displayed object. The default mode of this functionality is to accumulate content, you can modify this by setting pn.config.console_output to 'replace' for instance to only see the last message caught. Move the slider in the little app below to see the stream of printed messages being displayed in the notebook.

pn.config.console_output = False
def compute(i):
    print(f'debug {i}')
    return '❤️' * i

w = pn.widgets.IntSlider(value=1, start=1, end=10)

pn.Row(w, pn.bind(compute, w))
debug 1

Render templates#

You have been told in the Panel tutorial to avoid rendering Panel templates in a notebook. That’s however not a dead end! There are two approaches you can leverage to display an app that is wrapped in a template while working from a notebook, in addition to just being able to serve the notebook with panel serve notebook.ipynb.

Templates, as any other Panel visual components, are equipped with the .show() method that when called starts a Bokeh server, serves your app and opens it in a new tab. While this approach doesn’t allow you to iterate super quickly, it’s a simple way to check what your app looks like when served.

template = pn.template.BootstrapTemplate(
    title='Loving Panel!',
    sidebar=['**Text 1**', '**Text 2**'],
    main=['Main area'],
# Uncomment the next line to try out `.show()`

The second approach deserves a section of its own.

Preview functionality#

With the Preview functionality, available in JupyterLab, you can display the app you are building in a JupyterLab tab right next to your code. This is a traditional setup for web developers, who like to quickly visualize the effects of their code changes.

To have your app appear in the Preview, you need to mark the objects you want to display with .servable(). This is identical to how you would mark objects that you want to serve with panel serve ....

You can enable the Preview by clicking on Panel’s logo in the menu bar of your notebook. Once clicked, you should see a new tab being opened next to your notebook tab, and after some moment your app will be rendered in this tab. Just try it out!

template = pn.template.BootstrapTemplate(title='HM Training!')

def compute(i):
    return '❤️' * i

w_number = pn.widgets.IntSlider(value=5, start=1, end=5)
p_hearts = pn.panel(pn.bind(compute, w_number))



Note the ; at the end of template.servable();. This is a special IPython command that prevents the output of a cell from being displayed. This comes in handy when dealing with templates in a notebook!

This is what you should be able to see after a little while. Now tick Render on Save in the Preview, change the heart for a ⭐ in the notebook and save it, shortly after the preview will display an updated app.

alt text


Editors like VS Code and PyCharm have quickly become some of the most popular Python coding environment.

Serve apps with autoreload#

To enable a quick feedback loop while developing, we support serving your apps with autoreload.

Save the content of the next cell in a file named

import panel as pn

template = pn.template.BootstrapTemplate(title='Loving Panel!')

def compute(i):
    return '❤️' * i

w_number = pn.widgets.IntSlider(value=5, start=1, end=5)
p_hearts = pn.panel(pn.bind(compute, w_number))


From the terminal run the following command.

panel serve --show --autoreload

The --show flag will open a browser tab with the live app and the --autoreload flag ensures that the app reloads whenever you make a change to the Python source. --autoreload is key to your developer experience, you will see the app being updated live when you save your app file! In the image below the windows have been re-arranged the way web developers like, on one side the code and on the other side a live view of the app, just like the Preview functionality in Jupyterlab.

VSCode Preview