In reply to @x10an14:matrix.org
That fixed my issue with prospector, thanks mou! =D Now I gotta figure out how to fix the next error...

In reply to @x10an14:matrix.org
https://paste.sr.ht/~x10an14/8b83382fa0c3a0352ed79f9757b7ae7ff7249263 <-- A python egg a different dependency tries to create. I'ma be busy searching the poetry2nix repo's issues =P

In reply to @x10an14:matrix.org
https://paste.sr.ht/~x10an14/8b83382fa0c3a0352ed79f9757b7ae7ff7249263 <-- A python egg a different dependency tries to create. I'ma be busy searching the poetry2nix repo's issues =P

In reply to @mou_bugtracker:matrix.org
my guess: fiass-logging needs pytest-runner, but does not specify so, or trying to download it during build (but this is prohibited)

Hello, while building a derivation with poetry2nix, I get this error:

error: unsupported build system requirement poetry-dynamic-versioning

I guess it comes from this part of the pyproject.toml file:

[build-system]
requires = ["poetry-core>=1.0.0", "poetry-dynamic-versioning"]
build-backend = "poetry.core.masonry.api"

Any clues on how to fix that problem?

Hello, on nix build of a flake with poetry2nix, I get this error:

error: unsupported build system requirement poetry-dynamic-versioning

I guess it comes from this part of the pyproject.toml file:

[build-system]
requires = ["poetry-core>=1.0.0", "poetry-dynamic-versioning"]
build-backend = "poetry.core.masonry.api"

Any clues on how to fix that problem?

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?