[Bug]: Installation fails if binary distributions are prohibited
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 42/100
Direzione di ricerca
Start by reading the Python package installation and Node.js driver selection paths; the issue links to the Playwright core package metadata and the Arch Linux package recipe as examples. Check how installation behaves when binary distributions are prohibited and how the system Node.js version is selected. Done means the package can install without its bundled executable and use a compatible system Node.js.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Version
1.58.0
Steps to reproduce
- Prohibit binary distributions by setting installer.no-binary to
:all:ortrue. - Run
$ poetry add playwright.
Expected behavior
Installing playwright package succeeds.
Actual behavior
$ poetry add playwright
Using version ^1.58.0 for playwright
Updating dependencies
Resolving dependencies... (2.5s)
Package operations: 3 installs, 0 updates, 0 removals
- Installing greenlet (3.3.2)
- Installing pyee (13.0.1)
- Installing playwright (1.58.0): Failed
| Unable to find installation candidates for playwright (1.58.0)
|
| This is likely not a Poetry issue.
|
| - 8 candidate(s) were identified for the package
| - 8 wheel(s) were skipped due to your installer.no-binary policy
|
| Solutions:
| Make sure the lockfile is up-to-date. You can try one of the following;
|
| 1. Regenerate lockfile: poetry lock --no-cache --regenerate
| 2. Update package : poetry update --no-cache playwright
|
| If any of those solutions worked, you will have to clear your caches using (poetry cache clear --all).
|
| If neither works, please first check to verify that the playwright has published wheels available from your configured source that are compatible with your environment- ie. operating system, architecture (x86_64, arm64 etc.), python interpreter.
Additional context
Seems like no platform-independent distribution is available on PyPI. After investigating the package, it seems like the only reason for this is driver/node, which seems to be Node.js executable. I already do have Node.js installed on my system and I checked the version compatibility here.
So, I'd like to not be forced to have this executable on my system and have Playwright use the system Node.js. And that's exactly what the Arch Linux package has been doing.
Created from https://github.com/microsoft/playwright-python/issues/3036.
Environment
- Operating System: Arch Linux
- CPU: x86_64
- Browser: All
- Python Version: 3.14.3
- Other info:
- Poetry version: 2.3.2
- Lingua principale
- TypeScript
- Stelle
- 98.5k
- Fork
- 6.7k
- Merge medio
- 15h 43m
- PR unite (30g)
- 279
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di microsoft/playwright
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 70/100
microsoft/playwright#43640 ·
I maintainer di solito rispondono entro 1 giorno
-
[Bug]: `playwright install` hangs silently for ~8 minutes when PLAYWRIGHT_BROWSERS_PATH is not writableForse già presa @dcrousso l’ha presa 2 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
microsoft/playwright#43606 ·
I maintainer di solito rispondono entro 1 giorno
-
[Feature]: Set `this.name` in `TargetClosedError` constructorForse di nuovo libera @LeonxLJX l’ha presa 52 giorni fa e non c’è nessuna pull request aperta. ApertaP3-collecting-feedback
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 86/100
microsoft/playwright#42522 · 7 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
[Bug]: connectOverCDP kills the process with an uncaught assertion when an attached target has no browserContextIdForse già presa Una pull request collegata a questa issue è aperta o già unita. Aperta
Difficoltà 3/5 1-2 giorni Idoneità per principianti 68/100
microsoft/playwright#43638 ·
I maintainer di solito rispondono entro 1 giorno
-
needs-triage-win
Difficoltà 3/5 1-2 giorni Idoneità per principianti 58/100
microsoft/playwright#43632 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di microsoft/playwright
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
grafana/profiles-drilldown#1212 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
grafana/traces-drilldown#980 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
openremote/openremote#3487 · 1 commento ·
-
triage:needs-human
Difficoltà 2/5 1-3 ore Idoneità per principianti 67/100
garrytan/gbrain#7635 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
coollabsio/jean#867 ·
I maintainer di solito rispondono entro 1 giorno