Hello all - I have a question about editable packages. I'll try to keep it brief but can expand as needed.

We're looking into using nix and poetry to manage a python monorepo. For a client project to depend on a local utils library, we have this dependency in the utils pyproject.toml:

[tool.poetry.dependencies]
python = "^3.11"
utils = { path = "../utils/", develop = true }

We'd also like to have utils as an editable installation in the nix development shell for client. I was able to accomplish this by redundantly stating this by using mkPoetryEditablePackage:

          devShells = {
            explicit = pkgs.mkShell {
              buildInputs = [
                (mkPoetryEditablePackage {
                  projectDir = ./.;
                  editablePackageSources = {
                    utils = ../utils;
                  };
                })
              ];
            };
          };

We'd also like to have utils as an editable installation in the nix development shell for client. I was able to accomplish this by redundantly stating this by using mkPoetryEditablePackage in the clients flake.nix:

          devShells = {
            explicit = pkgs.mkShell {
              buildInputs = [
                (mkPoetryEditablePackage {
                  projectDir = ./.;
                  editablePackageSources = {
                    utils = ../utils;
                  };
                })
              ];
            };
          };

We'd also like to have utils as an editable installation in the nix development shell for client. I was able to accomplish this by redundantly stating this intention using mkPoetryEditablePackage in the clients flake.nix:

          devShells = {
            explicit = pkgs.mkShell {
              buildInputs = [
                (mkPoetryEditablePackage {
                  projectDir = ./.;
                  editablePackageSources = {
                    utils = ../utils;
                  };
                })
              ];
            };
          };

In reply to @jameswarren-582a7124d73408ce4f35e991:gitter.im
However, this seems messy and error-prone to declare the same intention in multiple places. Reading the docs for mkPoetryEnv, the comment on editablePackageSources suggests that declaring develop = true in the pyproject.toml should install utils as editable, but empirically testing it does not. Am I misunderstanding how it should be used?

Hey folks, I'm new to poetry2nix and trying to get my first flake going for a python backend in a monorepo.

The flake quickstart example has a default app output as follows:

apps.${system}.default = {
  type = "app";
  program = "${myapp}/bin/some_script";
};

But I would like to output multiple scripts as different commands. How would I go about it? I thought I could just do apps.${system}.command_name but it complains:

error: flake 'git+file:///home/ixxie/myapp?dir=backend' does not provide attribute 'packages.x86_64-linux.default' or 'defaultPackage.x86_64-linux