Playwright for Python
https://github.com/microsoft/playwright-python- Category
- Developer Tools
- Rank
- No. 168Tools index
- Pricing
- Open Source
- Type
- TOOL
- Builder
- microsoft
- GitHub
- 15.0k stars
- Latest release
- v1.62.0
- Date
About
Python bindings for Playwright — Microsoft's cross-browser end-to-end testing framework with auto-wait and tracing.
What it does
It lets Python programs open real browser engines, create pages, navigate websites, evaluate page code, and capture screenshots. Developers can choose synchronous control for straightforward scripts or asynchronous control for event-driven programs, while keeping a similar model across Chromium, Firefox, and WebKit.
Why it's ranked here
A strong pick for Python browser automation because one library exposes three major engines on Linux, macOS, and Windows. Separate synchronous and asynchronous interfaces widen its practical fit. Typed generated APIs, assertions, network controls, tracing, video, and browser interaction primitives show substantial coverage beyond simple page loading.
What's good
The cross-browser model is concrete: the same workflow launches Chromium, Firefox, or WebKit. Both synchronous and asynchronous examples perform equivalent work, which reduces conceptual switching between script styles. The package also includes typed interfaces for pages, contexts, requests, responses, locators, input devices, downloads, dialogs, WebSockets, tracing, and assertions.
Tradeoffs
Python 3.10 or newer is required. Distribution is platform-specific because each wheel contains a matching driver assembled from a pinned browser-control package and Node.js binary. That makes packaging more involved than a pure Python library. The synchronous and asynchronous surfaces are generated separately, so contributors must understand the generation pipeline rather than treating both as independent handwritten APIs.
How to use it well
Use it when a Python team needs repeatable browser workflows across multiple rendering engines. Choose the synchronous interface for compact scripts and the asynchronous interface when browser work belongs inside an async application. It fits navigation, interaction, evaluation, screenshots, network handling, and assertions. It does not replace broader test organization or non-browser application tooling.
Technical notes+
pyproject.toml defines the playwright distribution, Python 3.10 minimum, pyee and greenlet dependencies, a playwright CLI entry point, and sync, async, implementation, and PyInstaller packages. playwright/__main__.py forwards CLI arguments to the computed bundled driver executable. setup.py builds platform-specific wheels and inserts a driver archive. scripts/build_driver.py assembles that archive from pinned playwright-core and official Node.js artifacts for macOS, Linux, and Windows architectures. scripts/generate_sync_api.py and scripts/generate_async_api.py derive public wrappers from implementation types, while scripts/generate_api.py centralizes signatures, type conversion, object mapping, and generated documentation.
Observed
- License
- Apache License 2.0
- Primary language
- Python
- Install surface
- PyPI package named playwright with platform-specific wheels
- Interfaces
- Python library with synchronous API, asynchronous API, and a CLI entry point
- Browser support
- Chromium, Firefox, and WebKit
- Operating systems
- Linux, macOS, and Windows
- Python requirement
- Python 3.10 or newer
- Runtime dependencies
- pyee and greenlet
Read from README.md, setup.py, setup.cfg, pyproject.toml, requirements.txt, playwright/__init__.py, playwright/__main__.py, scripts/build_driver.py, scripts/example_sync.py, scripts/generate_api.py, scripts/example_async.py, scripts/update_versions.py, scripts/generate_sync_api.py, scripts/generate_async_api.py, scripts/update_node_version.py.
What it can do
Automate web browser interactions
Python test scripts with browser commands → Executed browser actions (clicks, form fills, navigation)
Run cross-browser tests
Test suite and browser specifications → Test results across multiple browsers (Chrome, Firefox, Safari)
Capture screenshots and videos
Web pages during test execution → Screenshot images and video recordings
Generate execution traces
Test runs and browser interactions → Detailed trace files for debugging
Wait for page elements automatically
Element selectors and page state conditions → Synchronized test execution without manual waits
Extract data from web pages
Web pages and element selectors → Scraped text, attributes, and content data
Simulate mobile device testing
Device specifications and test scripts → Mobile browser simulation results
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.