Closed bast closed 4 years ago
I guess the pyproject.toml
is wrong? I might not have tested thoroughly enough... I think we can have both poetry and flit, with the caveat that the latter will need a requirements.txt
file too.
Of course the above problem can wait, did not want to distract.
I kind of like the separation into pyproject.toml and requirements.txt and this may not even be best practice but just plays well with my alias that can set up a venv based on requirements.txt. And really the only thing that needs to go into requirements.txt is flit.
I'm moving to Flit (agreed, it's much nicer... I was blinded by Nix) But still the entry point doesn't work. It installs the package, but the console script won't work :thinking:
I can look at that. You can open a draft-PR and I can add to that and perhaps I see the problem.
See #93
This is what I tried:
Then (not knowing poetry well enough) I created a new folder, new venv and pip installed from the source folder, then: