Getting the Appium Flutter Finder
There are three ways to install and use the Appium Flutter Finder. Supported Python version follows appium python client.
-
Install from PyPi, as 'Appium-Flutter-Finder'.
pip install Appium-Flutter-Finder
-
Install from source, via PyPi. From 'Appium-Flutter-Finder', download and unarchive the source tarball (
appium_flutter_finder-X.X.tar.gz).tar -xvf appium_flutter_finder-X.X.tar.gz cd appium_flutter_finder-X.X python -m pip install .
-
Install from source via GitHub.
git clone git@github.com:appium/appium-flutter-driver.git cd appium-flutter-driver/finder/python python -m pip install .
How to use
Examples can be found out here.
Release
python -m pip install --upgrade build twine
python -m build
python -m twine check dist/*
python -m twine upload dist/appium_flutter_finder-*
Changelog
- 0.8.2
- Migrate package metadata and builds to
pyproject.toml
- Migrate package metadata and builds to
- 0.8.1
- Relax the Appium-Python-Client upper version to accept v6
- 0.8.0
- Update the limit of python appium client version
- 0.7.0
- Update the limit of python appium client version
- 0.6.1
- Fix package
- 0.6.0
- Fix type of
match_rootandfirst_match_onlyinby_ancestorand `by_descendant
- Fix type of
- 0.5.0
- Allow Appium-Python-Client to be v3
- 0.4.0
- Bump base Appium-Python-Client to v2
- 0.3.1
- Use Appium-Python-Client 1.x
- 0.3.0
- Add
first_match_onlyoption inby_ancestorandby_descendant
- Add
- 0.2.0
- Support over Python 3.6
- 0.1.5
- Fix
by_ancestorandby_descendant
- Fix
- 0.1.4
- Remove whitespaces from the decoded JSON
- Fix
by_ancestorandby_descendant
- 0.1.3
- Allow
from appium_flutter_finder import FlutterElement, FlutterFinder
- Allow
- 0.1.2
- Fix b64encode error in Python 3
- 0.1.1
- Initial release
Metadata
Release files for Appium-Flutter-Finder 0.8.2
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 | Actions |
|---|---|---|---|---|
| appium_flutter_finder-0.8.2.tar.gz | 3.2 kB | Without provenance | Details for appium_flutter_finder-0.8.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| appium_flutter_finder-0.8.2-py3-none-any.whl | Python 3 | none | any | Details for appium_flutter_finder-0.8.2-py3-none-any.whl |
Total release size: 6.8 kB
Release files / appium_flutter_finder-0.8.2.tar.gz
| Download URL | appium_flutter_finder-0.8.2.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5a3879b5c556ebef1a1fec7cf2b78906560b48048906eb0c5e38916f76b9048b
|
|
BLAKE2b-256 checksum How to use checksums |
89c1d6436bd2cebc6e71684b2057fef2020da71c4cd2bf99dab2d6f61e278077
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.6
|
Release files / appium_flutter_finder-0.8.2-py3-none-any.whl
| Download URL | appium_flutter_finder-0.8.2-py3-none-any.whl |
|---|---|
| Size | 3.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bea551347a80a75c2f5e641f0acc604c9f0ae384736e1df8f3de68ef7637667a
|
|
BLAKE2b-256 checksum How to use checksums |
a405bfa72f4e24313b5a7792fe738a98b664104ab5085d8f27c9edde576e0322
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.6
|
Security for Appium-Flutter-Finder 0.8.2
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.