In reply to @graf_blutwurst:matrix.org
Good Morning everyone. I am currently working on a little showcase workbench/projects for python based friends that don't know nix. They work fairly extensively with numpy and pandas so i tried adding those to poetry and so also to my environment. but it seems that that causes pandas and numpy to fully recompile them locally. i also tried pinning the versions to ones specifically available on nix. does anyone have some insight into this?

In reply to @graf_blutwurst:matrix.org
hm it seems i have to better understand build closures better. i assumed a dependency like that would be "low" enough that it could be picked up from the store/nixpkgs. thanks though! how do people deal with the long resulting build times? push the result from mkPoetryEnv to a binary cache?

In reply to @adis:blad.is
Typically, yes.

In reply to @graf_blutwurst:matrix.org
ok then i was on the right track for that. do you happen to have any resources that'd help me understand what causes the recompile of pandas etc? mostly so i can predict when it happens since those take a significant chunk of time to crunch through

When some of the build inputs changes, or some parameters are different.
poetry2nix tries as much as possible to ignore nixpkgs python packages which will cause the derivations to be different from nixpkgs ~all of the time.

Practially this means that you will have to rebuild when:

• You update nixpkgs
• Any of the python packages that pandas/numpy depends on changes in your poetry.lock

Hello!
I'm suffering from a problem that seems to have been already detected and fixed...

I get this failure even for the Flask exaple from the Tweag blogpost and the video. I get the message about an infinite recursion and when I use the verbose switch it get to read that flint-core is detected as missing. Adding the package as a dependendency does not stop this from failing.

In reply to @mou_bugtracker:matrix.org
Octavio, could you provide details about your environment? Error message, pyproject.toml, your nix expression will help anyone to better identify root cause.

  outputs = { self, nixpkgs, poetry2nix }:
    let
      name = "foo";
      system = "x86_64-linux";

      pkgs = import nixpkgs {
        inherit system;
        overlays = [ poetry2nix.overlay ];
      };

      poetryAttrs = {
        projectDir = ./.;
        python = pkgs.python39;

        checkPhase = ''
          py.test tests/
        '';

        overrides = pkgs.poetry2nix.overrides.withDefaults (final: prev: {
          lmdb = prev.lmdb.overrideAttrs
            (
              old: {
                # we need to patch the hard-coded path to patch,
                # see https://github.com/jnwatson/py-lmdb/blob/80d7ce6fd5531a2b2f586d9ec871fe60126f8aba/setup.py#L117
                patchPhase = ''
                  substituteInPlace ./setup.py --replace /usr/bin/patch ${pkgs.patch}/bin/patch
                '';
              }
            );
        });
      };
    in
    {
      packages.${system} = {
        ${name} = pkgs.poetry2nix.mkPoetryApplication poetryAttrs;
      };

      devShell.${system} =
        (pkgs.poetry2nix.mkPoetryEnv poetryAttrs).env;

    };
...
}