TFGNN can not be includes as dependency to a project that uses poetry for dependency management
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 204
- Avg merge
- 13m
- Merged PRs (30d)
- 1
Description
poetry is a very popular dependency manager for python applications. Currently, we can not include tensorflow-gnn as a dependency because we see error message:
Package 'tensorflow-macos' is listed as a dependency of itself.
Searching GitHub confirms that nobody is able to include tensorflow-gnn as a dependency in a poetry project.
To recreate this error, create an empty directory with a file named pyproject.toml:
[project]
name = "test"
version = "0.1.0"
requires-python = ">=3.9,<4"
[tool.poetry.dependencies]
tensorflow-gnn = "^1.0.3"
[build-system]
requires = ["poetry-core>=2.0.0,<3.0.0"]
build-backend = "poetry.core.masonry.api"
Install poetry and run:
poetry lock
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with the provided pyproject.toml and run poetry lock. Then inspect the repository's packaging metadata to find why tensorflow-macos is listed as its own dependency. Done means tensorflow-gnn can be added to a Poetry project and poetry lock completes without the self-dependency error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, tensorflow
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 56/100