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

refactor: don't use deno.core.ops in jupyter,bench,test,lint #27482

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

nathanwhit
Copy link
Member

needs denoland/deno_core#1014

the only remaining issue is the jupyter test that relies on using things from Deno[Deno.internal].jupyter. That only worked because we always executed 40_jupyter.js for deno test. With this PR, we only execute what's needed, and since deno test doesn't really need jupyter it isn't available.

We can:

  • rewrite that test in rust and use the jupyter kernel (though those tests tend to be sort of tricky and flakey)
  • continue executing 40_jupyter.js during deno test
  • drop the test

import { assertThrows } from "./test_util.ts";
// import { assertEquals } from "./test_util.ts";
//// @ts-expect-error TypeScript (as of 3.7) does not support indexing namespaces by symbol
// const format = Deno[Deno.internal].jupyter.formatInner;
Copy link
Member Author

@nathanwhit nathanwhit Dec 27, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Deno[Deno.internal].jupyter is undefined with this PR, it only gets set up during deno jupyter

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant