I'm currenlty exporting requirements in a package using a script based on poetry and the lock information.
I think this plugin would be a good place to add that functionality using --format wheel to create a package which depends on all lock versions. Often I get asked why not just use requirements.txt: python packages are more easily distributed though existing channels and my use-case requires me to ignore (not pin down) some parts of the depenency tree.
As this is the official export plugin, I would love to help integrate the logic from poetry-lock-packge into this plugin.
My current plugin implementation can be tracked here: bneijt/poetry-lock-package#13
I'm currenlty exporting requirements in a package using a script based on poetry and the lock information.
I think this plugin would be a good place to add that functionality using
--format wheelto create a package which depends on all lock versions. Often I get asked why not just userequirements.txt: python packages are more easily distributed though existing channels and my use-case requires me to ignore (not pin down) some parts of the depenency tree.As this is the official export plugin, I would love to help integrate the logic from
poetry-lock-packgeinto this plugin.My current plugin implementation can be tracked here: bneijt/poetry-lock-package#13