Thank you! I ended up with a similar approach after a bunch of experimenting:

{ pkgs ? import
    (
      fetchTarball
        {
          name = "nixpkgs-21.11-2022-01-03";
          url = "https://github.com/NixOS/nixpkgs/archive/08370e1e271f6fe00d302bebbe510fe0e2c611ca.tar.gz";
          sha256 = "1s9g0vry5jrrvvna250y538i99zy12xy3bs7m3gb4iq64qhyd6bq";
        })
    { }
}:
let
  python = pkgs.python38;
  poetryEnv = pkgs.poetry2nix.mkPoetryEnv {
    projectDir = builtins.path { path = ./.; name = "geostore"; };
    inherit python;
    extraPackages = ps: [ ps.pip ];
  };
in
poetryEnv.env.overrideAttrs (
  oldAttrs: {
    buildInputs = [
      pkgs.nodePackages.aws-azure-login
      (pkgs.poetry.override {
        inherit python;
      })
    ];
  }
)

This way the poetry2nix env and the Nix shell end up with the same Python environment, rather than the same Python interpreter in two different Nix store directories.

Thank you! I ended up with a similar approach after a bunch of experimenting:

{ pkgs ? import
    (
      fetchTarball
        {
          name = "nixpkgs-21.11-2022-01-03";
          url = "https://github.com/NixOS/nixpkgs/archive/08370e1e271f6fe00d302bebbe510fe0e2c611ca.tar.gz";
          sha256 = "1s9g0vry5jrrvvna250y538i99zy12xy3bs7m3gb4iq64qhyd6bq";
        })
    { }
}:
let
  python = pkgs.python38;
  poetryEnv = pkgs.poetry2nix.mkPoetryEnv {
    projectDir = builtins.path { path = ./.; name = "geostore"; };
    inherit python;
    extraPackages = ps: [ ps.pip ];
  };
in
poetryEnv.env.overrideAttrs (
  oldAttrs: {
    buildInputs = [
      (pkgs.poetry.override {
        inherit python;
      })
    ];
  }
)

This way the poetry2nix env and the Nix shell end up with the same Python environment, rather than the same Python interpreter in two different Nix store directories.

basically the same as all the other

{ pkgs ? import <nixpkgs> {} }:
let
  myAppEnv = pkgs.poetry2nix.mkPoetryEnv {
    python = pkgs.python39;
    projectDir = ./.;
    editablePackageSources = {
      my-app = ./src;
    };
    overrides = pkgs.poetry2nix.overrides.withDefaults (
      self: super: {
        connectorx = super.connectorx.overrideAttrs (
          old: {
            buildInputs = old.buildInputs ++ [ pkgs.openssl ];
          }
        );
    });
  };
in myAppEnv.env

Took me a bit but got it

in myAppEnv.env

becomes

in pkgs.mkShell {
  buildInputs = [ myAppEnv ];
  nativeBuildInputs = [ pkgs.poetry ];
}

removing any x-y problem:

I'm attempting to set up the dev flow.

My understanding is we use shell.nix to get into your project-specific dev shell. From there you can add / remove dependencies, run tests et cetera.

Do you recommend sticking with a simpler shell.nix for that purpose, not using poetry2nix?

{ pkgs ? import <nixpkgs> {} }:
pkgs.mkShell {
    buildInputs = [ pkgs.python3 pkgs.poetry ];
}