feat: support pyproject.toml in compile_pip_requirements#1519
feat: support pyproject.toml in compile_pip_requirements#1519rickeylev merged 7 commits intobazel-contrib:mainfrom
Conversation
8454c1c to
dff8198
Compare
groodt
left a comment
There was a problem hiding this comment.
LGTM
I think in the description, could be worth clarifying that it's support PEP-621 project.dependencies https://packaging.python.org/en/latest/specifications/declaring-project-metadata/#declaring-project-metadata only. It shouldn't imply support of any other TOML tables that may exist, or tool specific tables such as tool.black or tool.poetry etc
|
LGTM. I pushed a small update to the The only comment, more question, I have is: should src default to |
e31955a to
b746642
Compare
|
I have changed the code to default to If you are OK with the changes, explanation, feel free to merge it during your working hours. |
With this PR we can also use
pyproject.tomlin additionto
requirements.inwhich helps in making the requirementsin a more structured form. For example, we could parse the
toml itself and create aliases in the hub repos only for the
packages outlined in the
pyproject.tomlfile. The same forgazelle, we could restrictgazelle_python.yamlcontentsto only the dependencies listed in
pyproject.toml.Examples can be migrated once we agree on the interface.
Summary: