vercel-internal-core-bundle
This is a version of vercel-internal-core with third-party dependencies bundled. For normal use, install the unbundled vercel-internal-core package instead: https://pypi.org/project/vercel-internal-core/
Internal Core
vercel._internal.core provides the shared runtime used by Vercel Python service
packages. It is installed as their dependency and is not intended for direct
installation or direct end-user imports.
The distribution contributes service-neutral namespace portions. Import the
public session context from vercel.api and shared exceptions from
vercel.errors:
from vercel.api import session
from vercel.errors import VercelError
Legacy HTTPX client migration
HTTPX2 is the default HTTP implementation and the only HTTPX family installed
by the SDK. As a temporary runtime-only migration path, applications that
explicitly install legacy httpx may return a complete httpx.Client or
httpx.AsyncClient from session(httpx_client_factory=...). Static annotations
remain HTTPX2-based, so type-checked applications need a targeted cast(Any, ...).
Legacy transport objects must remain inside a legacy client; an
httpx.HTTPTransport cannot be mounted in an httpx2.Client.
Metadata
Release files for vercel-internal-core-bundle 0.2.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 |
|---|---|---|---|---|
| vercel_internal_core_bundle-0.2.2.tar.gz | 20.0 kB | Without provenance | Details for vercel_internal_core_bundle-0.2.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| vercel_internal_core_bundle-0.2.2-py3-none-any.whl | Python 3 | none | any | Details for vercel_internal_core_bundle-0.2.2-py3-none-any.whl |
Total release size: 45.4 kB
Release files / vercel_internal_core_bundle-0.2.2.tar.gz
| Download URL | vercel_internal_core_bundle-0.2.2.tar.gz |
|---|---|
| Size | 20.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ae732e294a618fcacb0a67a06193b8eaee1adae8474fcafa7215899353300f25
|
|
BLAKE2b-256 checksum How to use checksums |
e223bec6e5d3357db5961d80867582f064128f3c7a36e2e543048f3fedb8e857
|
| 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 / vercel_internal_core_bundle-0.2.2-py3-none-any.whl
| Download URL | vercel_internal_core_bundle-0.2.2-py3-none-any.whl |
|---|---|
| Size | 25.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6eb4a740fca128d20d27f750a23ddb5b2af4098a424b9592476bb92e21bc04cf
|
|
BLAKE2b-256 checksum How to use checksums |
46ed588e31abcaba9df877ae760ec155420cb6a897ccca4b9002ca46bb48df43
|
| 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 vercel-internal-core-bundle 0.2.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.
