Arwed S.

Hi @jackdewinter, no worries, thanks for considering my feature request! 🙂

> **Workarounds** > > The best workaround is to update MODULE.bazel to register the toolchain. > > ``` > # MODULE.bazel > bazel_dep(name = "rules_python") > > python = use_extension("@rules_python//python/extensions/python.bzl",...

I'd also be very interested in this to make a clean two stage build if two projects reference each other.

@MathiasMagnus : We also use intersphinx (and sphinx needs external-needs) for a multi-project sphinx build heavily. We found out a way how to do this, and created a small extension...

@chrisjsewell @danwos : Any timeline yet? I'm considering to fork sphinx-needs to create a "current main" version, I assume 2.1rc0 is safe? (no pypi upload! just internal consumption of course)

@chrisjsewell: That doesn't look like a matrix test with different python versions. What I'm trying to achieve is running the tests for python 3.8 and 3.10. I don't think that...

> > You might have to look for "generic" nox+pyenv help, like here: https://stackoverflow.com/questions/71454022/nox-does-not-find-my-pyenv-versions-in-my-python-poetry-project Ah! `pyenv local 3.8 system` did the trick! Mind if I add this short step-by-step instructions...

> > How do you test with different python versions locally? > > Honestly, I don't 😅, I just test test against one and let the CI handle the rest....

@danwos : I upvote the suggestion in comment https://github.com/useblocks/sphinx-needs/issues/996#issuecomment-1695719594, as every little bit that gets us a smaller needs.json is good.

@danwos: Well, you know our main use case (multi-project build and build caching), yet I don't find it to be represented in your list. For our use case, I'd definitely...