[BUG] Requirements conflicts
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1k
- Forks
- 85
- PR merge metrics
- No merged PRs in 30d
Description
2024-03-20 14:14:33.383 [info] INFO: pip is looking at multiple versions of undetected-playwright-patch to determine which version is compatible with other requirements. This could take a while.
2024-03-20 14:14:33.419 [info] ERROR: Cannot install -r /Users/xxx/Desktop/dev/repos/Botright/requirements.txt (line 4) and -r /Users/xxx/Desktop/dev/repos/Botright/requirements.txt (line 5) because these package versions have conflicting dependencies.
2024-03-20 14:14:33.419 [info]
The conflict is caused by:
playwright 1.42.0 depends on greenlet==3.0.3
undetected-playwright-patch 1.40.0.post1700587210000 depends on greenlet==3.0.1
There's a conflict between playwright and undetected-playwright-patch regarding greenlet.
This is caused by https://github.com/kaliiiiiiiiii/undetected-playwright-python/blob/8886a371b5758dc59026c5fc0e8735ef8b754427/setup.py#L228
install_requires=[
"greenlet==3.0.1",
"pyee==11.0.1",
"typing-extensions;python_version<='3.8'",
],
I don't really know where to address this issue as it comes from kaliiiiiiiiii repo, but your requirements are then, triggering the conflict.
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
Inspect requirements.txt lines 4 and 5, then compare the dependency declaration at setup.py line 228 in the linked undetected-playwright-python revision. Reproduce the pip resolver failure and determine whether the project requirements can be made compatible; done means a clean installation no longer reports the greenlet conflict.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- playwright, python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100