-
Notifications
You must be signed in to change notification settings - Fork 129
Separate extra requirements for specific experiments #231
Copy link
Copy link
Open
Labels
area/devopsConcerns continuous integration, workflows, automation, maintenance, dev tools, etc.Concerns continuous integration, workflows, automation, maintenance, dev tools, etc.area/healthIssues and PRs related to code, repository, or project healthIssues and PRs related to code, repository, or project healthhelp wantedHelp with this would be appreciatedHelp with this would be appreciatedpriority/p3Low PriorityLow Priority
Metadata
Metadata
Assignees
Labels
area/devopsConcerns continuous integration, workflows, automation, maintenance, dev tools, etc.Concerns continuous integration, workflows, automation, maintenance, dev tools, etc.area/healthIssues and PRs related to code, repository, or project healthIssues and PRs related to code, repository, or project healthhelp wantedHelp with this would be appreciatedHelp with this would be appreciatedpriority/p3Low PriorityLow Priority
Right now: requirements are "best effort" separated in a single requirements.txt file by arranging them under comment-headings for the various sub-packages
We could use pip's support for extras-require, e.g.
pip install recirq[qaoa]so the extra requirements could be specified in a structured way. Specifically: I propose anextra-requirements.txtfile in each submodule (i.e. experiment) containing that sub-packages extra requirements. These files could be parsed insetup.pyto generate theextras_requireargument to setuptools.setup.Currently our notebooks
pip install +github.com/quantumlib/recirqso that they work in a colab environment. We'll need to do the change stepwise to make sure the notebooks don't breakpip install +github/recirq[qaoa]pip install recirqonly gets you the minimal, base requirements.cc @dstrain115