Skip to content

Warn when quarto render file.ipynb (with no --execute) finds empty ipynb output cells #10575

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
cscheid opened this issue Aug 21, 2024 · 2 comments · May be fixed by #12460
Open

Warn when quarto render file.ipynb (with no --execute) finds empty ipynb output cells #10575

cscheid opened this issue Aug 21, 2024 · 2 comments · May be fixed by #12460
Assignees
Labels
enhancement New feature or request jupyter lint linting-related issues
Milestone

Comments

@cscheid
Copy link
Collaborator

cscheid commented Aug 21, 2024

One common source of confusion for Quarto users is the difference between default execution modes in .qmd and .ipynb. We should warn users about empty cells in .ipynb files that are being rendered without --execute.

@cscheid cscheid added this to the v1.6 milestone Aug 21, 2024
@cscheid cscheid self-assigned this Aug 21, 2024
@cscheid cscheid added jupyter lint linting-related issues enhancement New feature or request labels Aug 21, 2024
@cscheid
Copy link
Collaborator Author

cscheid commented Aug 21, 2024

Although this is technically under our linter epic, it is important enough that we should have a fix before we take on the linter project.

@cscheid
Copy link
Collaborator Author

cscheid commented Apr 4, 2025

From #12460 (comment):

Blech, this interacts badly with embed (and possibly manuscripts). Punting to 1.8.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request jupyter lint linting-related issues
Projects
None yet
1 participant