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

Change to core modules #218

Closed

Conversation

mcbarton
Copy link
Collaborator

@mcbarton mcbarton commented Jan 13, 2025

Description

Please include a summary of changes, motivation and context for this PR.

A better alternative to the jupyter_server module we use is to use what the main jupyter lite demo has as core modules https://github.com/jupyterlite/demo/blob/0cddee229c47161aadc17e836ca0b78f991a7908/requirements.txt#L2

Fixes # (issue)

Type of change

Please tick all options which are relevant.

  • Bug fix
  • New feature
  • Added/removed dependencies
  • Required documentation updates

@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 80.72%. Comparing base (0747fb9) to head (f792724).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main     #218   +/-   ##
=======================================
  Coverage   80.72%   80.72%           
=======================================
  Files          19       19           
  Lines         970      970           
  Branches       93       93           
=======================================
  Hits          783      783           
  Misses        187      187           

@mcbarton mcbarton requested a review from anutosh491 January 14, 2025 15:07
@@ -274,7 +274,7 @@ jobs:
run: |
micromamba create -n xeus-lite-host jupyterlite-core
micromamba activate xeus-lite-host
python -m pip install jupyterlite-xeus
python -m pip install jupyterlite-xeus jupyterlite-core jupyterlab
Copy link
Collaborator

Choose a reason for hiding this comment

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

Maybe playing around with the the deploy pages is fine here but as I said on other Prs I would like to keep consistency in the CI and the readme as to how we come up with any xeus-XX-lite kernel for atleast as of now.

It only makes it easier for jupyterlite maintainers to work with xeus-cpp-lite.

@anutosh491
Copy link
Collaborator

Closing in favour of #221

@anutosh491 anutosh491 closed this Jan 16, 2025
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.

3 participants