This release is a pre-release and may not be stable for production use.
cleverweb
1. OVERVIEW
A collection of methods used by CleverSession for accessing common sites using selenium.
2. INSTALLATION
pip install cleverweb
3. BASIC USE
>>> import cleverweb
4. UNDER THE BONNET
5. CONTRIBUTING
Contact Peter Fison peter@southwestlondon.tv or feel free to raise Pull Requests / Issue in the normal Github way.
6. CREDITS
7. PAYING IT FORWARD
If cleverweb helps you save time and focus on more important things, please feel free to to show your appreciation by starring the repository on Github.
I'd also be delighted if you wanted to:
1 maintainer
Metadata
1 maintainer
Release files for cleverweb 0.0.1a1
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 | |
|---|---|---|---|---|
| cleverweb-0.0.1a1.tar.gz | 3.9 kB | Without provenance | Details |
Release files / cleverweb-0.0.1a1.tar.gz
| Download URL | cleverweb-0.0.1a1.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8e3efb9f1466a62e09cc98ef7a0d3e4b41196b74039cac8e14035c8c5bc57754
|
|
BLAKE2b-256 checksum How to use checksums |
e73dd5198b50ac127becb6ce4d4ad3eb9b6f70a695d057a3e635db5ca551f918
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.0 setuptools/50.3.2 requests-toolbelt/0.9.1 tqdm/4.50.0 CPython/3.9.0
|
Security for cleverweb 0.0.1a1
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.
