Registry /
type-stubs / mypy-boto3-codeartifact
Install & Compatibility
Where this runs
tested against v1.43.0 · pip install
no network on importno background threads
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
muslpy 3.10–3.95 runs
installs and imports cleanly · install 0.0s · import 0.614s · 52.1MB
glibcpy 3.10–3.95 runs
installs and imports cleanly · install 3.9s · import 0.580s · 53MB
50MB installed
● package 50MB
Code
Verified usage
Verified import paths — ran on the pinned version, not inferred.
CodeArtifactClient
✓ from mypy_boto3_codeartifact.client import CodeArtifactClient
For explicit type hints for the CodeArtifact client.
Service Resource, Paginator, Waiter
✓ from mypy_boto3_codeartifact import CodeArtifactClient, CodeArtifactServiceResource, Paginator, Waiter
Access to all top-level types provided by the stub package.
This quickstart demonstrates how to use `mypy-boto3-codeartifact` with `boto3`. You typically import `boto3` as usual, and `mypy` automatically picks up the provided type stubs. For explicit type annotations, you can import specific types like `CodeArtifactClient` from the stub package.
import boto3
from mypy_boto3_codeartifact.client import CodeArtifactClient
from typing import TYPE_CHECKING
# For runtime, you use boto3 as usual
client = boto3.client("codeartifact")
# For type checking, mypy will infer types based on the stubs
# You can also explicitly annotate:
if TYPE_CHECKING:
typed_client: CodeArtifactClient = boto3.client("codeartifact")
# Example of a typed call (won't run without AWS credentials & region)
# try:
# domain_response = typed_client.list_domains()
# print(domain_response['domains'][0]['name'])
# except Exception as e:
# print(f"Could not list domains: {e}")
print("CodeArtifact client initialized. Type checking will use mypy-boto3-codeartifact stubs.")
Debug
Known issues
breakingSupport for Python 3.8 was removed in `mypy-boto3-builder` version 8.12.0, affecting all generated stub packages including `mypy-boto3-codeartifact`. Users on Python 3.8 will not receive type stubs for versions generated with this builder or newer.fixUpgrade your Python environment to 3.9 or newer to continue receiving type stubs for `boto3` services.
affects: >=1.42.3 (packages generated by builder >=8.12.0)
breakingType Definition naming conventions changed in `mypy-boto3-builder` version 8.9.0. This might affect explicit type hints using `TypeDef` suffixes, for example, `CreateDistributionRequestRequestTypeDef` became `CreateDistributionRequestTypeDef`.fixReview and update explicit `TypedDict` annotations in your codebase if you were relying on the older naming patterns.
affects: >=1.39.0 (packages generated by builder >=8.9.0)
gotcha`mypy-boto3-codeartifact` only provides type stubs, not the actual `boto3` library. You must install `boto3` separately for your code to run.fixEnsure both `boto3` and `mypy-boto3-codeartifact` are installed via `pip install boto3 mypy-boto3-codeartifact`.
affects: All versions
gotchaFor best compatibility, the version of `mypy-boto3-codeartifact` should ideally match the major and minor version of your installed `boto3` library.fixWhen upgrading `boto3`, also upgrade `mypy-boto3-codeartifact` to a matching version (e.g., `pip install boto3==X.Y.Z mypy-boto3-codeartifact==X.Y.Z`).
affects: All versions
gotchaThe builder migrated to PEP 561 compliant packages in version 8.12.0. While this improves type checker compatibility, ensure your type checker is up-to-date and configured correctly to pick up the stubs.fixUpdate your type checker (e.g., `mypy`) to its latest version. No direct code changes are typically needed, but be aware of how your environment resolves type stubs.
affects: >=1.42.3 (packages generated by builder >=8.12.0)
Upgrade
Version history
1.43.0latest on PyPI · released Apr 29, 2026
Audit
Dependencies
boto3requiredThis package provides type stubs for boto3; boto3 itself must be installed to use it.