Skip to content
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

markdown cells not being split for code #8543

Closed
RipPennell opened this issue Dec 14, 2021 · 2 comments · Fixed by #8683
Closed

markdown cells not being split for code #8543

RipPennell opened this issue Dec 14, 2021 · 2 comments · Fixed by #8683
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug good first issue Good for newcomers interactive-window Impacts interactive window verified Verification succeeded
Milestone

Comments

@RipPennell
Copy link

Environment data

  • VS Code version: 1.63.0
  • Jupyter Extension version (available under the Extensions sidebar): v2021.11.1001550889
  • Python Extension version (available under the Extensions sidebar): v2021.12.1559732655
  • OS (Windows | Mac | Linux distro) and version: Windows
  • Python and/or Anaconda version: 3.7.9
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
  • Jupyter server running: Local

Expected behaviour

XXX

Actual behaviour

XXX

Steps to reproduce:

[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]

  1. copy paste the following cell:
#%% [markdown]
# ## Some Markdown Text
print("hi")

The output in IPython 7.30.1 will only be the markdown text, with no code running.

Removing the "[markdown]" from the cell lets the markdown text be treated as a comment and the code executes, since it's not just a code cell. All of my python files have cells that start with markdown and go into code. Do I have to manually separate every cell?

Same problem is here microsoft/vscode-jupyter#3501

The automatic splitting appears to be a feature according to microsoft/vscode-jupyter#2285
Seems this is indeed a bug then

@RipPennell RipPennell added the bug Issue identified by VS Code Team member as probable bug label Dec 14, 2021
@RipPennell
Copy link
Author

Downgrading to an earlier version of the Jupyter Extension fixes this issue, so the issue is in the Jupyter Extension specifically

@rchiodo rchiodo removed their assignment Dec 14, 2021
@rchiodo rchiodo added the interactive-window Impacts interactive window label Dec 14, 2021
@rchiodo
Copy link
Contributor

rchiodo commented Dec 14, 2021

Thanks for the issue. This is indeed a regression.

@rchiodo rchiodo added good first issue Good for newcomers and removed needs-triage labels Dec 14, 2021
@rchiodo rchiodo added this to the January 2022 milestone Dec 16, 2021
@rchiodo rchiodo self-assigned this Jan 12, 2022
@DonJayamanne DonJayamanne added the verified Verification succeeded label Jan 27, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug good first issue Good for newcomers interactive-window Impacts interactive window verified Verification succeeded
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants