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
I feel this is mostly a duplicate of python-poetry/roadmap#3 -- you want to get top-level dependency information, and PEP 621 metadata will be the best way for Poetry to expose that, as it will require no special tools to extract.
What use case do you have for locked versions/hashes of top-level deps? Or do you just want the information exposed in PEP 621?
I prefer the requirements.txt of vcs to build docker image, i think it will easy to use cache and read if export simple. If use pyproject.toml, any change will break docker cache strategy, such as version updated which not affect depends.
pyproject.toml:
now
poetry export
output:Maybe we can support option to output top packages that only specified by pyproject.toml directly(the example above is just
httpx
)Expected export:
The text was updated successfully, but these errors were encountered: