Loosen aiida-core version pin to >=2.7.1
aiida-workgraph pins aiida-core~=2.7.1 in pyproject.toml (both main deps and docs extra), which means >=2.7.1, <2.8.0. This prevents installation alongside aiida-core >=2.8 or dev versions, breaking CI/RTD builds and user installs.
Proposed: change to >=2.7.1 (or >=2.7.1,<3 if an upper bound is preferred).
The same applies to aiida-pythonjob (~=0.5.1 / ~=0.5.2).
We're integrating WorkGraph into the aiida-core tutorials (PR #7205). Module 3 teaches workflows using @task.graph, shelljob, and Map. The tutorial modules are executable MyST notebooks built by Sphinx, so aiida-workgraph must be installable alongside the current aiida-core during the docs build.
Adding aiida-workgraph to aiida-core's tutorials extra creates a circular dependency (workgraph depends on aiida-core, which is the package being built). With uv, this fails outright during resolution. With pip, it can resolve if aiida-core is already installed, but only if the version pin is satisfied. Since the aiida-core dev branch is >=2.8, the ~=2.7.1 pin rejects it either way.
Currently we work around this locally with an editable install from a branch that has the dependency restriction removed.
Loosen
aiida-coreversion pin to>=2.7.1aiida-workgraphpinsaiida-core~=2.7.1inpyproject.toml(both main deps and docs extra), which means>=2.7.1, <2.8.0. This prevents installation alongside aiida-core>=2.8or dev versions, breaking CI/RTD builds and user installs.Proposed: change to
>=2.7.1(or>=2.7.1,<3if an upper bound is preferred).The same applies to
aiida-pythonjob(~=0.5.1/~=0.5.2).We're integrating WorkGraph into the aiida-core tutorials (PR #7205). Module 3 teaches workflows using
@task.graph,shelljob, andMap. The tutorial modules are executable MyST notebooks built by Sphinx, soaiida-workgraphmust be installable alongside the current aiida-core during the docs build.Adding
aiida-workgraphto aiida-core'stutorialsextra creates a circular dependency (workgraph depends on aiida-core, which is the package being built). Withuv, this fails outright during resolution. Withpip, it can resolve if aiida-core is already installed, but only if the version pin is satisfied. Since the aiida-core dev branch is>=2.8, the~=2.7.1pin rejects it either way.Currently we work around this locally with an editable install from a branch that has the dependency restriction removed.