We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This cannot currently be parsed by lock_repo_model_poetry:
lock_repo_model_poetry
[tool.poetry] name = "foobar" version = "0.0.1" description = "Foo Bar" authors = ["Engineering <[email protected]>"] readme = "README.md" [tool.poetry.dependencies] python = "3.9.16" abc = { path = "../abc", develop = false } [build-system] requires = ["poetry-core"] build-backend = "poetry.core.masonry.api"
Perhaps path dependencies should be skipped, rather than throw an error? The usual Bazel approach is to include these in deps.
path
deps
The current work-around is to maintain two project files: one for rules_pycross and one for regular Python tooling.
rules_pycross
This could be put behind a flag - skip_path_dependencies = True?
skip_path_dependencies = True
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
This cannot currently be parsed by
lock_repo_model_poetry
:Perhaps
path
dependencies should be skipped, rather than throw an error?The usual Bazel approach is to include these in
deps
.The current work-around is to maintain two project files: one for
rules_pycross
and one for regular Python tooling.This could be put behind a flag -
skip_path_dependencies = True
?The text was updated successfully, but these errors were encountered: