[Bug]: Playwright 1.63.0 Module Not Found on Windows (conda-forge) - playwright not playing nicely with conda and Python 3.12 and later...
Maintainer antworten meist innerhalb von 5 Tagen
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 45/100
- Issue-Typ
- Bug
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- python
- Bereich
- build-system, testing-qa
Rechercherichtung
Start by reproducing the reported failure with the conda create command on Windows, then compare the result with environment.yml and the linked conda-forge playwright-feedstock package. Verify whether the 1.63.0 build places the Python module in site-packages; done means a fresh conda environment can run the reported import successfully.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Version
1.63.0
Steps to reproduce
Bug Report: Playwright 1.63.0 Module Not Found on Windows (conda-forge)
Date: 2026-09-25
Environment: Windows 11, Python 3.13.15, conda-forge
Issue: ModuleNotFoundError: No module named 'playwright' despite successful conda installation
Summary
Playwright 1.63.0 installs successfully via conda-forge but fails to import in Python, causing ModuleNotFoundError. The package appears in conda list but the Python module is not discoverable.
Environment Details
OS: Windows 11
Python: 3.13.15 (conda-forge)
Conda Version: 24.x (current)
Channel: conda-forge (exclusive)
Playwright: 1.63.0 (h8fff0a6_1)
Build Package: playwright-1.63.0-h8fff0a6_1.conda
Reproduction Steps
-
Create conda environment with Python 3.13 and playwright from conda-forge:
conda create -n test_pw python=3.13 playwright -c conda-forge -
Activate environment:
conda activate test_pw -
Attempt to import:
python -c "import playwright; print('✓ OK')"
Expected Result
✓ OK
Actual Result
Traceback (most recent call last):
File "<string>", line 1, in <module>
import playwright
^^^^^^^^^^^^^^^^^
ModuleNotFoundError: No module named 'playwright'
Verification
Package Installed:
conda list | grep playwright
# playwright 1.63.0 h8fff0a6_1 conda-forge
Package Contents Check:
ls "C:\ProgramData\Anaconda3\envs\topss_tools\Lib\site-packages" | findstr -i playwright
# (no results)
Hypothesis
The conda-forge build of playwright (1.63.0-h8fff0a6_1) on Windows appears to:
- Package the binary/compiled files correctly (installs without error)
- Fail to expose the Python module entry point
- Possibly missing
__init__.pyor site-packages registration
Related Information
- Official Playwright Python: v1.63.0 (supports Python 3.8+)
- Official Installation: Works via
pip install playwright==1.63.0 - conda-forge Feedstock: playwright-feedstock
- Workaround: Using pip instead of conda resolves the issue immediately
Files
- Conda environment spec:
environment.yml(Python 3.13, playwright via conda-forge) - Test location: Windows, C:\Users\PowerUser\Desktop\tosapps\00000_Projects_Catalog_Builder
Requested Action: Investigate Windows packaging in conda-forge playwright build 1.63.0-h8fff0a6_1
Expected behavior
The "conda install -c conda-forge playwright" should just work on all versions of Windows where current versions of Python v3 can be installed.
Actual behavior
See above...
Additional context
No response
Environment
- Operating System: [Ubuntu 22.04]
- CPU: [Intel x64]
- Browser: [All, Chromium, Firefox, WebKit]
- Python Version: [3.12 or later]
- Other info:
- Vorherrschende Sprache
- Python
- Sterne
- 15k
- Forks
- 1.2k
- Ø Merge
- 4 T. 20 Std.
- Gemergte PRs (30 T.)
- 24
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Keine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus microsoft/playwright-python
-
[Bug]: Exception raised by a signal handler kills the sync dispatcher fiber, every later sync call spins at 100% CPUEvtl. vergeben @pavelfeldman hat das vor 1 Tag übernommen. Offen
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 48/100
microsoft/playwright-python#3222 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 5 Tagen
-
[Feature]: Official APIs to resolve/map ephemeral aria-refs to stable locators for LLM automationOffen
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 35/100
microsoft/playwright-python#3207 ·
Maintainer antworten meist innerhalb von 5 Tagen
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 1/100
microsoft/playwright-python#3172 ·
Maintainer antworten meist innerhalb von 5 Tagen
Alle Issues in microsoft/playwright-python
Ähnliche Issues
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 85/100
Deepak3699/Ai_Mentor#244 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
btclib-org/btclib-node#1880 ·
Maintainer antworten meist innerhalb von 1 Tag
-
CONTRIBUTING.md: say how ticketless bug fixes and feature PRs are handledEvtl. vergeben @khuisman hat das heute übernommen. Offenv0.9.2
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 84/100
khuisman/mcp-gee-sweet#941 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
pyjanitor-devs/pyjanitor#1758 ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug ready for review
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 86/100
odysseus-dev/odysseus#6641 ·
Maintainer antworten meist innerhalb von 1 Tag