poetry install: Differences from poetry export --format requirements.txt w/ pip install -r requirements.txt?

[tony]

Hi there!

When this happens, what's different from poetry install?

poetry export --dev --format requirements.txt --without-hashes > prod-requirements.txt

# Assume a virtualenv is being managed and already source'd into the shell
pip install -r prod-requirements.txt

• Technically, behind the hood, what's the difference?

• With hashes? Without hashes?

• Does poetry install use pip? In what ways?

• Caching differences?

• Security differences?

• Is any "detail" lost when doing poetry export and installing via pip? e.g. deep dependencies?

• How can poetry install be made to perform faster?

  A year or so back: I originally got into the pattern of using requirements.txt in CI due to performance and bugs in poetry 1.0. Related: Document docker poetry best practices #1879

If we get good feedback on this, it may be a good idea to add a table or page to the Documentation on the Poetry website for us.