In reply to @elonsroadster:matrix.org
I feel like I'm probably missing something obvious, but I'm curious about what the easiest way to support a dependency that is not in nixpkgs or pypi is. Should I just use the built in nixpkgs tooling to define a nix build for that package and then add an override

Hi all,

I'm trying to build scikit-learn 1.5.0, and their changelog says they've switched to meson: https://scikit-learn.org/stable/whats_new/v1.5.html#version-1-5-0. When I add meson-python to nativeBuildInputs, metadata generation fails when running this file: https://github.com/scikit-learn/scikit-learn/blob/5491dc695dbe2c9bec3452be5f3c409706ff7ee7/sklearn/_build_utils/version.py

This seems like an opportunity to learn more about poetry2nix and submit a PR. Are there any good resources people can recommend on translating a meson build to a poetry2nix override?

Thanks!

I'm trying to patch the cython version used by a package:

peewee = super.peewee.overridePythonAttrs (old: let
            old_buildInputs = old.buildInputs or [];
            old_cython_filter = input: (builtins.substring 0 7 input.name) != "cython-";
          in {
            buildInputs =
              (builtins.filter old_cython_filter old_buildInputs);
              ++ [super.cython_0];
          });

But all I get is " error: value is a list while a set was expected" ...

Can anybody spot what I'm doing wrong?

Hello all - I have a question about editable packages. I'll try to keep it brief but can expand as needed.

We're looking into using nix and poetry to manage a python monorepo. For a client project to depend on a local utils library, we have this dependency in the utils pyproject.toml:

[tool.poetry.dependencies]
python = "^3.11"
utils = { path = "../utils/", develop = true }

We'd also like to have utils as an editable installation in the nix development shell for client. I was able to accomplish this by redundantly stating this by using mkPoetryEditablePackage:

          devShells = {
            explicit = pkgs.mkShell {
              buildInputs = [
                (mkPoetryEditablePackage {
                  projectDir = ./.;
                  editablePackageSources = {
                    utils = ../utils;
                  };
                })
              ];
            };
          };

We'd also like to have utils as an editable installation in the nix development shell for client. I was able to accomplish this by redundantly stating this by using mkPoetryEditablePackage in the clients flake.nix:

          devShells = {
            explicit = pkgs.mkShell {
              buildInputs = [
                (mkPoetryEditablePackage {
                  projectDir = ./.;
                  editablePackageSources = {
                    utils = ../utils;
                  };
                })
              ];
            };
          };

We'd also like to have utils as an editable installation in the nix development shell for client. I was able to accomplish this by redundantly stating this intention using mkPoetryEditablePackage in the clients flake.nix:

          devShells = {
            explicit = pkgs.mkShell {
              buildInputs = [
                (mkPoetryEditablePackage {
                  projectDir = ./.;
                  editablePackageSources = {
                    utils = ../utils;
                  };
                })
              ];
            };
          };