Stefan Borer

Can confirm it works as intended! @dougthor42 @blueyed any plans to merge/release this? :)

As expected, this leads the the same issue as if the remote was not known, so: ``` * Creating venv isolated environment... * Installing packages in isolated environment... (setuptools>=45, setuptools_scm>=6.2,...

I guess this is related to: https://github.com/pypa/pip/issues/10665 However, from my experience `pip` will use the keyring for credentials if available, while `build` doesn't.

It's not as grave is I feared, the specific issue we're facing is tracked here: https://github.com/graphql-python/graphene-django/issues/906 But we should still consider trying to upstream the changes mentioned in said docstrings,...

I'm very much in favour of a shared OIDC auth backend for all related django projects. However a shared user model might be problematic, since caluma doesn't have a persistent...

Btw the workaround for this is to use `--no-build-isolation`. Which of course negates all the benefits of the nice PEPs...

This also happens with python 3.10. Edit: It seems rye uses 3.12 internally to run `rye init`, even if the config.toml contains ```toml [default] toolchain = "3.10" ```

I too miss some options, specifically `--user`: https://docs.docker.com/engine/reference/run/#user Use case: The container runs an unprivileged user but you want to run it locally using root or you local user, for...

Just as an idea (which obviously would remove the "good first issue" tag): Would it maybe be possible to just collect the gefyra-specific CLI options and "pass through" all the...

Also stuck with this issue...