here's my default.nix

{ pkgs ? import <nixpkgs> { } }:
let
  poetry2nix = pkgs.callPackage (builtins.fetchTarball
    "https://github.com/nix-community/poetry2nix/archive/master.tar.gz") { };
  python312 = pkgs.python312;
  keyrings = pkgs.python312Packages.keyrings-google-artifactregistry-auth;
  gexEnv = poetry2nix.mkPoetryEnv {
    projectDir = ./.;
    editablePackageSources = { gex = ./gex; };
    python = python312;
    pyproject = ./pyproject.toml;
    poetrylock = ./poetry.lock;
    preferWheels = true;
  };
in pkgs.mkShell {
  buildInputs = [ gexEnv pkgs.google-cloud-sdk keyrings ];
  shellHook = ''
    # keyrings are available here and I'm authenticated in google cloud
  '';
}

In reply to @elonsroadster:matrix.org
Does anyone have any what is going on with libcst?

seems like its not extracting a tar archive that it should be:

error: opening file '/nix/store/201zc10pdd4ls1gmpsmbl710lm0q6ai7-libcst-1.1.0.tar.gz/native/Cargo.lock': Not a directory

that looks like the override is broken. I encountered something similar recently trying to wrap polaris.

But the nixpkgs libcst module - at least in master - uses fetchFromGitHub, so it really shouldn't have a tarball. And I don't see an override in poetry2nix Hm.

In reply to @julius:mtx.liftm.de
How much of a sin is overrides = defaultPoetryOverrides.extend (_: _: pkgs.python311Packages);?

I'm getting

➜ LD_LIBRARY_PATH='' nix build '.?submodules=1#railbird-api' --dry-run --impure --show-trace
warning: Git tree '/home/imalison/Projects/railbird' is dirty
trace: warning: pythonForBuild (from python*) has been renamed to pythonOnBuildForHost
trace: warning: pythonForBuild (from python*) has been renamed to pythonOnBuildForHost
trace: warning: pythonForBuild (from python*) has been renamed to pythonOnBuildForHost
evaluating derivation 'git+file:///home/imalison/Projects/railbird#railbird-api'error: stack overflow (possible infinite recursion)

after updating the nixpkgs and poetry2nix versions in my flake.

sort of at a loss as to how to try to even ascertain which package is causing this because why depends and dry run are failing with the same issue.

the only thing I can think of is to start putting traces in the poetry2nix code itself. Does anyone have any idea how I can debug this?

In reply to @tyberius_prime:matrix.org
adisbladis: Hi, are you still working on poetry2nix?

For various reasons I haven't worked on anything Nix related for a bit.

The reasons are many-fold:

• Personal (I don't want to get into details here, not relevant to the overall community regardless)

• I don't exactly enjoy the maintenance aspect
  Overrides et al was something I always saw as a stop gap, but now takes up the brunt of maintenance time. This is not what I enjoy working on.

• Ongoing political conflicts in Nix
  I have extremely low patience for social BS at the best of times, this is too much to handle.

I have some pretty large changes that I want to do to how Nixpkgs deals with Python in general that would break things drastically for some people. Dealing with any sort of social fallout in this climate is something I see as untenable.

• I barely even use Python myself any more

• Companies make money off poetry2nix, I make none
  This reality makes me question how much unpaid time I should put into the project.

In reply to @tyberius_prime:matrix.org
adisbladis: Hi, are you still working on poetry2nix?

For various reasons I haven't worked on anything Nix related for a bit.

The reasons are many-fold:

• Personal (I don't want to get into details here, not relevant to the overall community regardless)
• I don't exactly enjoy the maintenance aspect
  Overrides et al was something I always saw as a stop gap, but now takes up the brunt of maintenance time. This is not what I enjoy working on. I want to work on fundamentals, not what I consider to be a "software janitor".
• Ongoing political conflicts in Nix
  I have extremely low patience for social BS at the best of times, this is too much to handle.

I have some pretty large changes that I want to do to how Nixpkgs deals with Python in general that would break things drastically for some people. Dealing with any sort of social fallout in this climate is something I see as untenable.

• I barely even use Python myself any more
• Companies make money off poetry2nix, I make none
  This reality makes me question how much unpaid time I should put into the project.

In reply to @FRidh:matrix.org
It would be great if this PR could be merged adding a cargo hash https://github.com/nix-community/poetry2nix/pull/1726

In reply to @truh:matrix.org
I'm trying to investigate why opencv is no longer building (probably the same as https://github.com/nix-community/poetry2nix/issues/1715).

Do the opencv packages in poetry2nix rely on the instructions from https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/libraries/opencv/4.x.nix ?