In reply to @artturin:matrix.org

if i add python.pkgs.pytestCheckHook to checkInputs i get many of these

python3.10-nixos-gen-config> Found duplicated packages in closure for dependency 'pytest':
python3.10-nixos-gen-config>   pytest 6.2.5 (/nix/store/km2dg715wf31dq8vafdaplwlnh8jnqzy-python3.10-pytest-6.2.5/lib/python3.10/site-packages)
python3.10-nixos-gen-config>   pytest 6.2.5 (/nix/store/yc3jnjq6wx4zz14anjj9mj8xxv1zc57v-python3.10-pytest-6.2.5/lib/python3.10/site-packages)

Hi,
I'm trying to understand how to use poetry2nix but I've this poroblem, this is my current flake.nix:

{
  description = "My Python application";

  inputs = {
    nixpkgs.url = github:NixOS/nixpkgs/nixos-unstable;
    flake-utils-plus.url = github:gytis-ivaskevicius/flake-utils-plus/v1.3.1;
  };

  outputs = { self, nixpkgs, flake-utils-plus }:
    flake-utils-plus.lib.eachDefaultSystem (system:
      let
        pkgs = nixpkgs.legacyPackages.${system};

        caseGeneratorApp = pkgs.poetry2nix.mkPoetryEnv {
          projectDir = ./case;
          editablePackageSources = {
            src = ./case/src;
          };
        };

        packageName = "case_generator";
      in
      {

        defaultPackage = caseGeneratorApp;
        devShell = pkgs.mkShell {
          name = "development";
          buildInputs = [
            caseGeneratorApp
          ];
        };
      });
}

When I enter in the development shell withnix develop I get the scripts exposed by poetry and configured in the pyproject.toml in my PATH, and I can correctly execute them. But if I edit these sources (in ./case/src/) it makes no difference. I've to exit and re-enter in the shell to make the changes work.

Am I doing things correctly? If someone know a simple and working flake using poetry2nix I would be happy to take a look.

Thank you

In reply to @aciceri:nixos.dev

Hi,
I'm trying to understand how to use poetry2nix but I've this poroblem, this is my current flake.nix:

{
  description = "My Python application";

  inputs = {
    nixpkgs.url = github:NixOS/nixpkgs/nixos-unstable;
    flake-utils-plus.url = github:gytis-ivaskevicius/flake-utils-plus/v1.3.1;
  };

  outputs = { self, nixpkgs, flake-utils-plus }:
    flake-utils-plus.lib.eachDefaultSystem (system:
      let
        pkgs = nixpkgs.legacyPackages.${system};

        caseGeneratorApp = pkgs.poetry2nix.mkPoetryEnv {
          projectDir = ./case;
          editablePackageSources = {
            src = ./case/src;
          };
        };

        packageName = "case_generator";
      in
      {

        defaultPackage = caseGeneratorApp;
        devShell = pkgs.mkShell {
          name = "development";
          buildInputs = [
            caseGeneratorApp
          ];
        };
      });
}

When I enter in the development shell withnix develop I get the scripts exposed by poetry and configured in the pyproject.toml in my PATH, and I can correctly execute them. But if I edit these sources (in ./case/src/) it makes no difference. I've to exit and re-enter in the shell to make the changes work.

Am I doing things correctly? If someone know a simple and working flake using poetry2nix I would be happy to take a look.

Thank you

In reply to @aciceri:nixos.dev
Ahh, I understand. What do you suggest me then? What would be the correct way to use a flake to manage a development flow like this?

I've seen people using --impure combined with environment variables to reference paths outside of the store.
That could work.

I'm not a flakes user so I might not be of too much help.

here is a copy paste of an example from one of the apps I packaged last week

      devShell = (pkgs.poetry2nix.mkPoetryEnv {
        projectDir = ./.;
        editablePackageSources.YOUR_APP = ./YOUR_SRC_DIR;
      }).env.overrideAttrs (old: {
        propagatedNativeBuildInputs = (old.propagatedNativeBuildInputs or [ ]) ++ nativeDependencies;
        shellHook = (old.shellHook or "") + ''
          export GDAL_LIBRARY_PATH="${pkgs.gdal}/lib/libgdal.so"
          export GEOS_LIBRARY_PATH="${pkgs.geos}/lib/libgeos_c.so"
        '';
        buildInputs = extraDevDependencies;
      });

In reply to @averagechris:matrix.org
zrsk: I have been packaging a few python apps as nix flakes. I'm no expert, but what's worked for me with editable installs is mkPoetryEnv as devShell instead of mkShell with the env as an input