Type annotations for boto3.CloudWatchLogs 1.35.54 service generated with mypy-boto3-builder 8.1.4
Type annotations for boto3.CloudWatchLogs 1.35.54 service compatible with VSCode, PyCharm, Emacs, Sublime Text, mypy, pyright and other tools.
Generated by mypy-boto3-builder 8.1.4.
More information can be found on boto3-stubs page and in mypy-boto3-logs docs.
See how it helps to find and fix potential bugs:
Add
AWS Boto3
extension to your VSCode and run AWS boto3: Quick Start command.
Click Modify and select boto3 common and CloudWatchLogs.
Install boto3-stubs for CloudWatchLogs service.
# install with boto3 type annotations
python -m pip install 'boto3-stubs[logs]'
# Lite version does not provide session.client/resource overloads
# it is more RAM-friendly, but requires explicit type annotations
python -m pip install 'boto3-stubs-lite[logs]'
# standalone installation
python -m pip install mypy-boto3-logs
python -m pip uninstall -y mypy-boto3-logs
Pylance as your Python Language Serverboto3-stubs[logs] in your environment:python -m pip install 'boto3-stubs[logs]'
Both type checking and code completion should now work. No explicit type
annotations required, write your boto3 code as usual.
Install boto3-stubs-lite[logs] in your environment:
python -m pip install 'boto3-stubs-lite[logs]'
Both type checking and code completion should now work. Explicit type annotations are required.
Use boto3-stubs package instead for implicit type discovery.
boto3-stubs with services you use in your environment:python -m pip install 'boto3-stubs[logs]'
(use-package lsp-pyright
:ensure t
:hook (python-mode . (lambda ()
(require 'lsp-pyright)
(lsp))) ; or lsp-deferred
:init (when (executable-find "python3")
(setq lsp-pyright-python-executable-cmd "python3"))
)
boto3-stubsType checking should now work. No explicit type annotations required, write
your boto3 code as usual.
boto3-stubs[logs] with services you use in your environment:python -m pip install 'boto3-stubs[logs]'
Type checking should now work. No explicit type annotations required, write
your boto3 code as usual.
Not tested, but as long as your IDE supports mypy or pyright, everything
should work.
mypy: python -m pip install mypyboto3-stubs[logs] in your environment:python -m pip install 'boto3-stubs[logs]'
Type checking should now work. No explicit type annotations required, write
your boto3 code as usual.
pyright: npm i -g pyrightboto3-stubs[logs] in your environment:python -m pip install 'boto3-stubs[logs]'
Optionally, you can install boto3-stubs to typings directory.
Type checking should now work. No explicit type annotations required, write
your boto3 code as usual.
CloudWatchLogsClient provides annotations for boto3.client("logs").
from boto3.session import Session
from mypy_boto3_logs import CloudWatchLogsClient
client: CloudWatchLogsClient = Session().client("logs")
# now client usage is checked by mypy and IDE should provide code completion
mypy_boto3_logs.paginator module contains type annotations for all
paginators.
from boto3.session import Session
from mypy_boto3_logs import CloudWatchLogsClient
from mypy_boto3_logs.paginator import (
DescribeConfigurationTemplatesPaginator,
DescribeDeliveriesPaginator,
DescribeDeliveryDestinationsPaginator,
DescribeDeliverySourcesPaginator,
DescribeDestinationsPaginator,
DescribeExportTasksPaginator,
DescribeLogGroupsPaginator,
DescribeLogStreamsPaginator,
DescribeMetricFiltersPaginator,
DescribeQueriesPaginator,
DescribeResourcePoliciesPaginator,
DescribeSubscriptionFiltersPaginator,
FilterLogEventsPaginator,
ListAnomaliesPaginator,
ListLogAnomalyDetectorsPaginator,
)
client: CloudWatchLogsClient = Session().client("logs")
# Explicit type annotations are optional here
# Types should be correctly discovered by mypy and IDEs
describe_configuration_templates_paginator: DescribeConfigurationTemplatesPaginator = (
client.get_paginator("describe_configuration_templates")
)
describe_deliveries_paginator: DescribeDeliveriesPaginator = client.get_paginator(
"describe_deliveries"
)
describe_delivery_destinations_paginator: DescribeDeliveryDestinationsPaginator = (
client.get_paginator("describe_delivery_destinations")
)
describe_delivery_sources_paginator: DescribeDeliverySourcesPaginator = client.get_paginator(
"describe_delivery_sources"
)
describe_destinations_paginator: DescribeDestinationsPaginator = client.get_paginator(
"describe_destinations"
)
describe_export_tasks_paginator: DescribeExportTasksPaginator = client.get_paginator(
"describe_export_tasks"
)
describe_log_groups_paginator: DescribeLogGroupsPaginator = client.get_paginator(
"describe_log_groups"
)
describe_log_streams_paginator: DescribeLogStreamsPaginator = client.get_paginator(
"describe_log_streams"
)
describe_metric_filters_paginator: DescribeMetricFiltersPaginator = client.get_paginator(
"describe_metric_filters"
)
describe_queries_paginator: DescribeQueriesPaginator = client.get_paginator("describe_queries")
describe_resource_policies_paginator: DescribeResourcePoliciesPaginator = client.get_paginator(
"describe_resource_policies"
)
describe_subscription_filters_paginator: DescribeSubscriptionFiltersPaginator = (
client.get_paginator("describe_subscription_filters")
)
filter_log_events_paginator: FilterLogEventsPaginator = client.get_paginator("filter_log_events")
list_anomalies_paginator: ListAnomaliesPaginator = client.get_paginator("list_anomalies")
list_log_anomaly_detectors_paginator: ListLogAnomalyDetectorsPaginator = client.get_paginator(
"list_log_anomaly_detectors"
)
mypy_boto3_logs.literals module contains literals extracted from shapes that
can be used in user code for type checking.
Full list of CloudWatchLogs Literals can be found in
docs.
from mypy_boto3_logs.literals import AnomalyDetectorStatusType
def check_value(value: AnomalyDetectorStatusType) -> bool: ...
mypy_boto3_logs.type_defs module contains structures and shapes assembled to
typed dictionaries and unions for additional type checking.
Full list of CloudWatchLogs TypeDefs can be found in
docs.
from mypy_boto3_logs.type_defs import AccountPolicyTypeDef
def get_value() -> AccountPolicyTypeDef:
return {...}
Fully automated
mypy-boto3-builder carefully
generates type annotations for each service, patiently waiting for boto3
updates. It delivers drop-in type annotations for you and makes sure that:
boto3 services are covered.boto3 service gets valid type
annotations extracted from botocore schemas.boto3, botocore, aiobotocore and aioboto3
librariesmypy, pyright, VSCode, PyCharm, Sublime Text and Emacs
compatibilityClient, ServiceResource, Resource, Waiter Paginator type
annotations for each serviceTypeDefs for each serviceLiterals for each serviceboto3.client and boto3.resource callssession.client and session.resource callsclient.get_waiter and client.get_paginator
callsServiceResource and Resource collectionsaiobotocore.Session.create_client callsBuilder changelog can be found in Releases.
mypy-boto3-logs version is the same as related boto3 version and follows
PEP 440 format.
All services type annotations can be found in boto3 docs
This package is auto-generated. Please reports any bugs or request new features in mypy-boto3-builder repository.
FAQs
Type annotations for boto3.CloudWatchLogs 1.35.54 service generated with mypy-boto3-builder 8.1.4
We found that mypy-boto3-logs demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
A malicious npm package disguised as a WhatsApp client is exploiting authentication flows with a remote kill switch to exfiltrate data and destroy files.
Security News
PyPI now supports digital attestations, enhancing security and trust by allowing package maintainers to verify the authenticity of Python packages.
Security News
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.