Per-notebook environments

Open
#19 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
jupyter-notebook, python
Domain
tooling

Research direction

The issue does not name any files, tests, or entry points. First clarify the notebook format, dependency source, and expected environment workflow; the work is done when per-notebook dependencies can be defined and used reproducibly.

Written by the indexing model from the issue text.

Description

it should be possible to define dependencies per notebook (conda envs?)

Dominant language
Python
Stars
22
Forks
18
Avg merge
3h 9m
Merged PRs (30d)
9

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from scverse/scverse-tutorials

All issues in scverse/scverse-tutorials

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.