avlm / pre-commit-poetry-export Goto Github PK

First off, thanks for creating this pre-commit hook, it's what I was looking for to be able to simplify installation of an application via pip while developing with poetry and not ending up with the requirements out of sync.

That said, my preference would be that development requirements would not be included in the exported requirements.txt file. In the use case I'm envisioning, a developer/contributor should be using poetry and the requirements.txt file is just there for ease of installation for deployment.

Is that something you'd be willing to change the default on? What if poetry-export accepted a --dev option similar to poetry export?

Edit: I just noticed that there is an inconsistency between when the requirements file is first created without --dev on line 18 and when it is recreated/checked on line 26 with --dev on line 26. Which explains why when I tried running it back-to-back without a requirements.txt it failed both times. I'm going to see about writing some tests.