quarto-dev / quarto-dev/quarto-cli

IPython.core.page.page() doesn't display output

Open
#10,248 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug engines-jupyter
Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 9h
Merged PRs (30d)
41

Description

Bug description

IPython.core.page.page() is another way to display data in Jupyter/IPython. It doesn't seem to output anything in Quarto though.

Steps to reproduce
---
title: Reproducer
---

```{python}
from IPython.core.page import page
page("helloworld")
```

In a Jupyter notebook, this would display 'helloworld' as output, but in Quarto it displays nothing.
Expected behavior

helloworld gets printed as output.

Actual behavior

Nothing gets output.

Your environment

Linux, Python 3.11.

Quarto check output
Quarto 1.4.554
[✓] Checking versions of quarto binary dependencies...
      Pandoc version 3.1.11: OK
      Dart Sass version 1.69.5: OK
      Deno version 1.37.2: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
      Version: 1.4.554
      Path: /opt/quarto/bin

[✓] Checking tools....................OK
      TinyTeX: (not installed)
      Chromium: (not installed)

[✓] Checking LaTeX....................OK
      Using: Installation From Path
      Path: /usr/bin
      Version: 2021

[✓] Checking basic markdown render....OK

[✓] Checking Python 3 installation....OK
      Version: 3.11.9
      Path: /home/itamarst/devel/low-level-performance-book/venv/bin/python3
      Jupyter: 5.7.0
      Kernels: python3

[✓] Checking Jupyter engine render....OK

[✓] Checking R installation...........(None)

      Unable to locate an installed version of R.
      Install R from https://cloud.r-project.org/

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with the provided Quarto .qmd example and inspect the Jupyter engine render path, using IPython.core.page.page() as the entry point. Done means rendering the document produces helloworld as output, matching the expected Jupyter behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
jupyter, python
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.