At it’s simplest it allows you to send mouse and keyboard actions to windows dialogs and controls, but It has support for more complex controls also.
Recommended usage: 64-bit Python is for 64-bit applications; 32-bit Python is for 32-bit ones.
Installation
(Python 2.7 and 3.x)
Just run pip install pywinauto (pypiwin32 will be installed automatically)
(Python 2.6)
Install pyWin32 extensions manually: http://sourceforge.net/projects/pywin32/files/pywin32/ (no need for ActivePython)
Unzip pywinauto archive and run python setup.py install
(Python 2.5 and before is not supported)
Useful links
Home page: http://pywinauto.github.io/
Docs (table of contents): http://pywinauto.github.io/docs/contents.html
Examples: https://gist.github.com/vasily-v-ryabov
Mailing list subscription: https://sourceforge.net/p/pywinauto/mailman/
Metadata
Release files for pywinauto 0.5.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pywinauto-0.5.4.zip | 399.5 kB | Without provenance | Details |
Release files / pywinauto-0.5.4.zip
| Download URL | pywinauto-0.5.4.zip |
|---|---|
| Size | 399.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bde9f590025dfd9503a544c137ebd6799f8c8f86e21afcb33c84cb8b8fc41a03
|
|
BLAKE2b-256 checksum How to use checksums |
692a3cbf939ddae83ae2ad89620aa9cb2d08b0d2266627eb3907578156dc3fcd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pywinauto 0.5.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.