-
-
Notifications
You must be signed in to change notification settings - Fork 13.5k
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
Merging JupyterWith in Nixpkgs #79703
Comments
|
Hello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use Git blame or GitHub's web interface on the relevant files to find them. Lastly, you can always ask for help at our Discourse Forum or at #nixos' IRC channel. |
Closing for the moment, will reopen if needed. |
Just want to point out the new Jupyter Hub service here #94783. |
I am the maintainer of JupyterWith, a system for setting up JupyterLab severs in a deterministic way using Nix, and I would like to work on a PR to merge it in Nixpkgs. This would give access to many Jupyter kernels to standard Nix users. I have been tracking my progress inside the project in this issue: tweag/jupyenv#71
I am opening this issue in order to ask some questions:
I plan to do most of the work inside the current Jupyter folder. Is this the appropriate place for doing it?
It may happen that we need to override some global packages so that they work correctly with Jupyter. What is the correct way for doing that? As an user, I use overlays, but this doesn't seem to make sense inside Nixpkgs. Maybe standard overrides? Should these overridden packages available only locally or also globally?
I would like to add tests to every Jupyter kernel, which will involve running Jupyter on a sample Notebook. What would be the appropriate location for theses tests?
All feedback is welcome. As soon as I start the pull request, I will link it here.
The text was updated successfully, but these errors were encountered: