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

I'm not sure what to make of this... here is the flake for the backend (it's in ${monorepo}/backend):

{
  description = "MyApp Backend - Python, Uvicorn & FastAPI";

  inputs = {
    nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
    poetry2nix.url = "github:nix-community/poetry2nix";
  };
  
  outputs = { self, nixpkgs, poetry2nix }:
    let
      system = "x86_64-linux";
      pkgs = nixpkgs.legacyPackages.${system};
      # create a custom "mkPoetryApplication" API function that under the hood uses
      # the packages and versions (python3, poetry etc.) from our pinned nixpkgs above:
      inherit (poetry2nix.lib.mkPoetry2Nix { inherit pkgs; }) mkPoetryApplication;
      myapp = mkPoetryApplication { projectDir = ./.; };
    in
    {
      apps.${system}.backend = {
        type = "app";
        program = "${myapp}/bin/backend";
      };
    };
}

But I get the following error:

warning: Git tree '/home/ixxie/myapp' is dirty
error:
       … while calling a functor (an attribute set with a '__functor' attribute)
         at /nix/store/lpqygnph8c5l7ajkmqr4rff0pvkfz1f6-source/default.nix:407:13:
          406|
          407|       app = py.pkgs.buildPythonPackage (
             |             ^
          408|         passedAttrs // inputAttrs // {

       … while evaluating a branch condition
         at /nix/store/dydg48djlykksz8cxq0xjplyxpa9pvf4-source/pkgs/development/interpreters/python/python-packages-base.nix:28:7:
           27|     in
           28|       if builtins.isAttrs result then result
             |       ^
           29|       else if builtins.isFunction result then {

       (stack trace truncated; use '--show-trace' to show the full, detailed trace)

       error: expected a set but found null: null

In reply to @ixxie:matrix.org
How do I control the name of the package created with mkPoetryApplication and installed with nix profile install?

In reply to @tyberius_prime:matrix.org
I thought it was taken from pyproject.toml? the source indicate that this is true

I've set the name in pyproject.toml, and set pname in mkPoetryApplication but when I run nix profile install .#package-name but then I still get something like this:

> nix profile list

Name:               path/from/git/root/to/flake
Flake attribute:    packages.x86_64-linux.default
Original flake URL: git+file:///home/ixxie/project?dir=path/from/git/root/to/flake
Locked flake URL:   git+file:///home/ixxie/project?dir=path/from/git/root/to/flake
Store paths:        /nix/store/4r112qhr7f3vsxj3jx4ynvyb8560vjxf-python3.11-cli-0.1

In reply to @tyberius_prime:matrix.org
well, the name (pname + version) ends up in the store path, which I giuess is where the python3.11-cli comes from (cli being set in your pyproject.toml).

I suppose you want to change 'Name:'?