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 ];
}

WARNING: Built wheel for hy is invalid: Metadata 1.2 mandates PEP 440 version, but 'unknown' is not
Failed to build hy

Looks like pip has a no-verify option. Can I pass --no-verify into mkPoetryEnv, which is what I'm using to source this dev dependency into my devShell?

In reply to @worldofgeese:one.ems.host
I swapped hy = { git = "https://github.com/hylang/hy.git", python = ">=3.9,<3.11" } for hy = {version = "1.0a4", allow-prereleases = true, python = ">=3.9,<3.11"}, did a poetry update and now mkPoetryEnv returns Hy 1.04a, which is the latest pre-release. It would be nice to get the tip of the master branch but this works fine for my purposes now

i'm trying to build a package that depends on cryptography 36.0.2, and it fails with:

error: hash mismatch in fixed-output derivation '/nix/store/cb7576730h5ny4x6177dcxy3gl2qvfvl-cryptography-36.0.2-vendor.tar.gz.drv':
         specified: sha256-kozYXkqt1Wpqyo9GYCwN08J+zV92ZWFJY/f+rulxmeQ=
            got:    sha256-6C4N445h4Xf2nCc9rJWpSZaNPilR9GfgbmKvNlSIFqg=

this is because the hash is hard-coded here, and it's now wrong.

what's the idea here? how do we keep that hash updated? should i just override on my end?

In reply to @sephi:matrix.org
Is there a way to use the environment of a derivation to add more files to it right before the Python package is created? I’m creating a derivation for a Django project, and I’d like to collect static files to a directory that’s inside my package. I’m currently doing this by using mkPoetryApplication to create the package, and then have a second mkPoetryApplication with ${appWithoutStatic}/bin/django-admin collectstatic in configurePhase. This works but I was wondering if this is achievable without creating 2 derivations.

In reply to @mou_bugtracker:matrix.org
i'm newbie with nix, but as far as i can understand, proper way to achieve desired, is to make override with custom build paramaters. poetry2nix uses nixpkgs.buildPythonPackage. So i believe there are plenty of post* hooks, which you can use to add aditional step to your build. You only need to figure out proper way to override resulting derivation.