-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Option to support poetry export packages only specified in pyproject.toml, but no related upstreams #177
Comments
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? |
yes, the locked versions of top level deps. Keep simple and concise of requirements.txt for reading |
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: