In reply to @mr-qubo:matrix.org
Why builtins.getFlake "nixpkgs" requires --impure, but e.g. nix shell 'nixpkgs#hello' works without --impure? Seems like I'm missing some understanding.

In reply to @crtified:crtified.me
The first one is probably evaluated in a different flake and thus "breaks" the expectation of being pure, while the second one is impure on its own as you rarely have a pure shell env (and the concrete result of nixpkgs depends on your local flake registry)

I'm trying to use flake inputs as a way to track several other non-flake git repos. The idea is that after CI passes on the other repos, I will update the lock for that particular input. I then want to use my flake to build packages for these other, non-flake, inputs. I can add the input pretty easily, and flake-parts provides me with inputs' as an attribute to my modules. This much works great, but when I go to pass the input in mkPoetryApp { projectDir = inputs'.my-python-app; }, it fails with cannot coerce a set into a string.

which is okay, I guess, it's an attrset. That makes sense... but none of the attrs that I know exist in the input schema seem to work. I can't get lib.debug.traceVal to ever print anything out, either. What can I give mkPoetryApp to figure out where the path-in-the-store-on-my-disk is for projectDir or is there a better way to manage the non-flake inputs? What I don't want to do is have to manually change the rev using fetchGit each time CI changes.