bowmark-web-stubs
PEP 561 type stubs for
bowmark-web — the whole
Bowmark capability surface, typed.
pip install bowmark-web bowmark-web-stubs
async with session() as bm:
found = await bm.providers.gymshark.search({"query": "hoodie"})
# ^ your editor knows every provider, every
# function, every argument and every field
Why it is a separate distribution
PEP 561 is explicit: "The name of the stub package MUST follow the scheme
foopkg-stubs." So this is mandated rather than chosen, and PyPI has no rename, alias
or redirect mechanism to undo it with.
bowmark-web still ships py.typed, so installing only the client keeps the client's
own types and loses only the catalog.
This distribution is marked partial, which matters: without that marker a checker
resolving bowmark_web-stubs stops looking at bowmark_web altogether, and every
private submodule becomes unresolvable to anyone who imports one.
What is in it, and where it comes from
bowmark_web-stubs/__init__.pyi is generated — from the same LibraryManifest that
produces the TypeScript declarations in
@bowmark/web. One manifest, one refusal
rule, two languages, so the two clients cannot come to disagree about what the library
offers. A gate in the source repo asserts the parity on every change.
Everything the library can do is in CAPABILITIES.md and PROVIDERS.md, regenerated daily.
What it deliberately does NOT type
Some functions are absent, on purpose. A function whose declared argument is a bare
destructuring pattern with no field types, or whose signature names a type its own
documentation never defines, gets a comment in place of a signature naming it and saying
why. Those functions are real and callable at runtime — the stub withholds only the
compile-time claim, because we have none to make. A (*args: Any) -> Any stand-in would
pass every check and tell you nothing.
Family members are not enumerated. bowmark.providers.gymshark.search(…) works and is
not in these stubs: there are half a million Shopify storefronts and no manifest carries
one. Type checkers will not complete them; the client sends them happily.
Everything leans toward accepting. An argument-position list is Sequence[T], a
number is float (so an int is fine), and anything the schema could not model is Any.
A stub that refuses a correct argument is a red squiggle you cannot turn off, and that is
a worse failure than one round trip.
Versioning
bowmark-web, bowmark-web-stubs and @bowmark/web on npm are released together and
always carry the same version. A skew would mean one ecosystem is on an older contract.
1 maintainer
Metadata
1 maintainer
Release files for bowmark-web-stubs 1.25.8
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 | |
|---|---|---|---|---|
| bowmark_web_stubs-1.25.8.tar.gz | 595.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bowmark_web_stubs-1.25.8-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.2 MB
Release files / bowmark_web_stubs-1.25.8.tar.gz
| Download URL | bowmark_web_stubs-1.25.8.tar.gz |
|---|---|
| Size | 595.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e93e95cb02f0979314a7c109d25d852da07df31ff9fe6c4a50f66f2b6038bb65
|
|
BLAKE2b-256 checksum How to use checksums |
7c906cdcd321f49d0288d5bcbdaef3436a53f81c10d4b279dbb93150138a5031
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / bowmark_web_stubs-1.25.8-py3-none-any.whl
| Download URL | bowmark_web_stubs-1.25.8-py3-none-any.whl |
|---|---|
| Size | 598.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f7058d52fa230fb1dc3aaf2f120cebea5be82a49d2dd4b923dbe5b848475915d
|
|
BLAKE2b-256 checksum How to use checksums |
f8d8eb61bd0b45cae7c4e71668767fcb4e9f21b1f3cd72f72347113194d0a43e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for bowmark-web-stubs 1.25.8
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.
