In reply to @jmgilman:matrix.org
Anyone available to help troubleshoot a failing build?

In reply to @vengmark2:matrix.org
How should I expose the Poetry executable itself when using mkPoetryEnv? I need to be able to run things like poetry add while in the Nix shell. Using mkShell with buildInputs = [ pkgs.poetry ]; seems wrong. And using extraPackages = ps: [ ps.poetry ]; fails with a collision message.

i use this approach (snippet taken from flake.nix)

        devShell = (pkgs.poetry2nix.mkPoetryEnv {
          projectDir = ./.;
          editablePackageSources = {
            whateverpackagenames = ./.;
          };
        }).env.overrideAttrs (oldAttrs: {
          buildInputs = [ pkgs.poetry ];
        });

In reply to @tompurl:destrocodpiece.wtf
Hello! I went through the tutorial on Youtube for packaging a Flask app. I would love to do the same thing with a Django app but I assume that I would need to figure out how to start my app from the tool.poetry.scripts command in pyproject.toml. However, I can't find any resource on how exactly to do that. Currently I run python manage.py runserver. How can I specify that command from poetry?

In reply to @mou_bugtracker:matrix.org
Sorry for late reply, but this question is about poetry itself, not about it integration with nix nor the poetry2nix. So i'm afraid you should try to search answer in diffrerent community. At least i'm not aware about soulution.

Thank you mou . I appreciate the help, and there's no reason to apologize :-)

Now that I've thought about the question a bit more, I think what I meant to ask was how does one package a Python app that is a server that has some sort of startup command?

It appears to me that poetry2nix will support the "startup command" only if it can be wrapped by the tools.poetry.scripts param in a pyproject.tompl file. Do you know if this is correct?

In reply to @tompurl:destrocodpiece.wtf

Thank you mou . I appreciate the help, and there's no reason to apologize :-)

Now that I've thought about the question a bit more, I think what I meant to ask was how does one package a Python app that is a server that has some sort of startup command?

It appears to me that poetry2nix will support the "startup command" only if it can be wrapped by the tools.poetry.scripts param in a pyproject.tompl file. Do you know if this is correct?

In reply to @mou_bugtracker:matrix.org
i do not know anything about startup scripts, but as i'm aware, scripts declared in tools.poetry.scripts will be installed as part of package installation. Look at my snippet two message earlier (about devShell). I use it with direnv integration and it grants me environment there such scripts are in PATH.

In reply to @tompurl:destrocodpiece.wtf
Thank you!

In reply to @mou_bugtracker:matrix.org

i use this approach (snippet taken from flake.nix)

        devShell = (pkgs.poetry2nix.mkPoetryEnv {
          projectDir = ./.;
          editablePackageSources = {
            whateverpackagenames = ./.;
          };
        }).env.overrideAttrs (oldAttrs: {
          buildInputs = [ pkgs.poetry ];
        });

In reply to @mou_bugtracker:matrix.org

i use this approach (snippet taken from flake.nix)

        devShell = (pkgs.poetry2nix.mkPoetryEnv {
          projectDir = ./.;
          editablePackageSources = {
            whateverpackagenames = ./.;
          };
        }).env.overrideAttrs (oldAttrs: {
          buildInputs = [ pkgs.poetry ];
        });

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

{ pkgs ? import
    (
      fetchTarball
        {
          name = "21.11-2022-03-08";
          url = "https://github.com/NixOS/nixpkgs/archive/bb3dee861440695ce6d8f43d0dd3a97622cb08c4.tar.gz";
          sha256 = "0j94fz656a0xf3s7kvi8p16p52186ks6r3m1gv8i2zmiinlvv5v3";
        })
    { }
}:
let
  python = pkgs.python38;
  poetryEnv = pkgs.poetry2nix.mkPoetryEnv {
    inherit python;
    projectDir = builtins.path { path = ./.; name = "geostore"; };
    extraPackages = ps: [ ps.pip ];
  };
in
pkgs.mkShell {
  buildInputs = [
    (pkgs.poetry.override {
      inherit python;
    })
    poetryEnv
  ];

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

{ pkgs ? import
    (
      fetchTarball
        {
          name = "21.11-2022-03-08";
          url = "https://github.com/NixOS/nixpkgs/archive/bb3dee861440695ce6d8f43d0dd3a97622cb08c4.tar.gz";
          sha256 = "0j94fz656a0xf3s7kvi8p16p52186ks6r3m1gv8i2zmiinlvv5v3";
        })
    { }
}:
let
  python = pkgs.python38;
  poetryEnv = pkgs.poetry2nix.mkPoetryEnv {
    inherit python;
    projectDir = builtins.path { path = ./.; name = "geostore"; };
    extraPackages = ps: [ ps.pip ];
  };
in
pkgs.mkShell {
  buildInputs = [
    (pkgs.poetry.override {
      inherit python;
    })
    poetryEnv
  ];
}```

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

{ pkgs ? import
    (
      fetchTarball
        {
          name = "21.11-2022-03-08";
          url = "https://github.com/NixOS/nixpkgs/archive/bb3dee861440695ce6d8f43d0dd3a97622cb08c4.tar.gz";
          sha256 = "0j94fz656a0xf3s7kvi8p16p52186ks6r3m1gv8i2zmiinlvv5v3";
        })
    { }
}:
let
  python = pkgs.python38;
  poetryEnv = pkgs.poetry2nix.mkPoetryEnv {
    inherit python;
    projectDir = builtins.path { path = ./.; name = "geostore"; };
    extraPackages = ps: [ ps.pip ];
  };
in
pkgs.mkShell {
  buildInputs = [
    (pkgs.poetry.override {
      inherit python;
    })
    poetryEnv
  ];
}

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

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.