This doesn't work:

poetry2nix.mkPoetryEnv {
    projectDir = ./.;
    editablePackageSources = {
        my-app = ./src;
    };
}

because my-app resolves to a store path

In reply to @adis:blad.is
The behaviour of editable together with flakes is kinda terrible..

error: builder for '/nix/store/54prvc1413an75zb70asbd19kq8zh5va-python3.11-dbus-python-1.3.2.drv' failed with exit code 2;
       last 10 log lines:
       >           ^^^^^^^^^^^^^^^^^^^^^^^
       >   File "/nix/store/ffll6glz3gwx342z0ch8wx30p5cnqz1z-python3-3.11.5/lib/python3.11/importlib/__init__.py", line 126, in import_module
       >     return _bootstrap._gcd_import(name[level:], package, level)
       >            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
       >   File "<frozen importlib._bootstrap>", line 1204, in _gcd_import
       >   File "<frozen importlib._bootstrap>", line 1176, in _find_and_load
       >   File "<frozen importlib._bootstrap>", line 1140, in _find_and_load_unlocked
       > ModuleNotFoundError: No module named 'mesonpy'
       >
       >
       For full logs, run 'nix log /nix/store/54prvc1413an75zb70asbd19kq8zh5va-python3.11-dbus-python-1.3.2.drv'

In reply to @gaivs:matrix.org
Hello! I'm having some odd problems with the cattrs package.

To reproduce, I use `nix flake init --template github:nix-community/poetry2nix`, then `poetry add cattrs`. When I build, I get the `No module named 'hatchling'` error, so I add an override for cattrs with the hatchling package.

When I try to build after this, I get this error:

```
hatchling.plugin.exceptions.UnknownPluginError: Unknown version source: vcs
error: subprocess-exited-with-error
```

Have anyone had this, or a similar, issue before?

It seems to me that poetry2nix doesn't properly support scripts at the top level? I'm wondering if that's known/reported/irrelevant/a bad idea/…

Say I've got a project set up like this:

nix flake init --template github:nix-community/poetry2nix
echo 'def main(): print("foo")' >foo.py
echo -e '\n[tool.poetry.scripts]\nbar = "foo:main"' >>pyproject.toml
poetry install

Then I can execute

poetry run bar

and it'll print foo.
But If I execute

nix shell -c bar

That fails with ModuleNotFoundError: No module named 'foo'.
Looking around, foo.py isn't included in result for nix build ., but it does appear in a -source folder in the store. Can I somehow execute top level scripts?

1. whether the current flake structure is "best practice" for this case (notably defining the repo's package attr xls2latex via callPackage in let .. in and directly refering to it for the different flake outputs),

2. secondly I get a strange errorr message in a consuming flake (see next)