You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having the ability to run poetry add requirements.txt would greatly improve developer experience.
I use poetry for all my projects but when working on other people's projects, I've found that it's a little bit cumbersome to have to wangle poetry add command to pass the requirements file.
Impact
Developer Experience.
Workarounds
cat requirements.txt | xargs poetry add
OR
poetry add $(cat requirements.txt)
The text was updated successfully, but these errors were encountered:
I'm afraid I agree that the workarounds might be the right solution here :)
As stated in #8837, this (if it actually needs to be done) might be a case for a plugin more so than poetry itself.
The maintenance burden for a feature like this does not make much sense at the moment. While the feature itself might be trivial (#famouslastwords), the ongoing support of it might trigger more nuanced fixes and improvements that deter time from areas already requiring maintenance. This is the reason we eventually spun out the export command to a plugin.
In any case, I'm closing this for now as this won't be implemented as things stand.
Issue Kind
Brand new capability
Description
Having the ability to run
poetry add requirements.txt
would greatly improve developer experience.I use poetry for all my projects but when working on other people's projects, I've found that it's a little bit cumbersome to have to wangle
poetry add
command to pass the requirements file.Impact
Developer Experience.
Workarounds
cat requirements.txt | xargs poetry add
OR
poetry add $(cat requirements.txt)
The text was updated successfully, but these errors were encountered: