Mock Version: 6.0 Mock Version: 6.0 Mock Version: 6.0 ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --noclean --target noarch --nodeps /builddir/build/SPECS/python-botocore.spec'], chrootPath='/var/lib/mock/dist-an23-build-530887-80588/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=86400uid=982gid=135user='mockbuild'unshare_net=TrueprintOutput=Falsenspawn_args=['--capability=cap_ipc_lock']) Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --noclean --target noarch --nodeps /builddir/build/SPECS/python-botocore.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'} and shell False Building target platforms: noarch Building for target noarch setting SOURCE_DATE_EPOCH=1777420800 Wrote: /builddir/build/SRPMS/python-botocore-1.42.97-1.an23.src.rpm Child return code was: 0 ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -br --noclean --target noarch --nodeps /builddir/build/SPECS/python-botocore.spec'], chrootPath='/var/lib/mock/dist-an23-build-530887-80588/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=86400uid=982gid=135user='mockbuild'unshare_net=TrueraiseExc=FalseprintOutput=Falsenspawn_args=['--capability=cap_ipc_lock']) Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -br --noclean --target noarch --nodeps /builddir/build/SPECS/python-botocore.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'} and shell False Building target platforms: noarch Building for target noarch setting SOURCE_DATE_EPOCH=1777420800 Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.lhUbLw + umask 022 + cd /builddir/build/BUILD + cd /builddir/build/BUILD + rm -rf botocore-1.42.97 + /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/botocore-1.42.97.tar.gz + STATUS=0 + '[' 0 -ne 0 ']' + cd botocore-1.42.97 + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + rm -vr tests/integration removed 'tests/integration/__init__.py' removed 'tests/integration/test-credentials' removed 'tests/integration/test_apigateway.py' removed 'tests/integration/test_client.py' removed 'tests/integration/test_client_http.py' removed 'tests/integration/test_cloudformation.py' removed 'tests/integration/test_cloudwatch.py' removed 'tests/integration/test_cognito_identity.py' removed 'tests/integration/test_credentials.py' removed 'tests/integration/test_ec2.py' removed 'tests/integration/test_emr.py' removed 'tests/integration/test_loaders.py' removed 'tests/integration/test_rds.py' removed 'tests/integration/test_route53.py' removed 'tests/integration/test_s3.py' removed 'tests/integration/test_session.py' removed 'tests/integration/test_smoke.py' removed 'tests/integration/test_sts.py' removed 'tests/integration/test_utils.py' removed 'tests/integration/test_waiters.py' removed directory 'tests/integration' + rm -vr tests/functional/leak removed 'tests/functional/leak/__init__.py' removed 'tests/functional/leak/test_resource_leaks.py' removed directory 'tests/functional/leak' + RPM_EC=0 ++ jobs -p + exit 0 Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.QsDvm4 + umask 022 + cd /builddir/build/BUILD + cd botocore-1.42.97 + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/gfortran/modules' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/gfortran/modules' + export FCFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/anolis/anolis-hardened-ld -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -Wl,--build-id=sha1 ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + echo pyproject-rpm-macros + echo python3-devel + echo 'python3dist(pip) >= 19' + echo 'python3dist(packaging)' + '[' -f pyproject.toml ']' + echo '(python3dist(tomli) if python3-devel < 3.11)' + rm -rfv '*.dist-info/' + '[' -f /usr/bin/python3 ']' + mkdir -p /builddir/build/BUILD/botocore-1.42.97/.pyproject-builddir + echo -n + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/anolis/anolis-hardened-ld -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -Wl,--build-id=sha1 ' + TMPDIR=/builddir/build/BUILD/botocore-1.42.97/.pyproject-builddir + RPM_TOXENV=py311 + HOSTNAME=rpmbuild + /usr/bin/python3 -Bs /usr/lib/rpm/anolis/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /builddir/build/BUILD/botocore-1.42.97/pyproject-wheeldir --output /builddir/build/BUILD/python-botocore-1.42.97-1.an23.noarch-pyproject-buildrequires Handling setuptools >= 40.8 from default build backend Requirement satisfied: setuptools >= 40.8 (installed: setuptools 68.0.0) Handling wheel from default build backend Requirement satisfied: wheel (installed: wheel 0.38.4) running egg_info creating botocore.egg-info writing botocore.egg-info/PKG-INFO writing dependency_links to botocore.egg-info/dependency_links.txt writing requirements to botocore.egg-info/requires.txt writing top-level names to botocore.egg-info/top_level.txt writing manifest file 'botocore.egg-info/SOURCES.txt' reading manifest file 'botocore.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching 'botocore/vendored/requests/cacert.pem' warning: no files found matching '*.json.gz' under directory 'botocore/data' no previously-included directories found matching 'docs/build' adding license file 'LICENSE.txt' adding license file 'NOTICE' writing manifest file 'botocore.egg-info/SOURCES.txt' Handling wheel from get_requires_for_build_wheel Requirement satisfied: wheel (installed: wheel 0.38.4) running dist_info writing botocore.egg-info/PKG-INFO writing dependency_links to botocore.egg-info/dependency_links.txt writing requirements to botocore.egg-info/requires.txt writing top-level names to botocore.egg-info/top_level.txt reading manifest file 'botocore.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching 'botocore/vendored/requests/cacert.pem' warning: no files found matching '*.json.gz' under directory 'botocore/data' no previously-included directories found matching 'docs/build' adding license file 'LICENSE.txt' adding license file 'NOTICE' writing manifest file 'botocore.egg-info/SOURCES.txt' creating '/builddir/build/BUILD/botocore-1.42.97/botocore-1.42.97.dist-info' Handling jmespath (<2.0.0,>=0.7.1) from hook generated metadata: Requires-Dist (botocore) Requirement not satisfied: jmespath (<2.0.0,>=0.7.1) Handling python-dateutil (<3.0.0,>=2.1) from hook generated metadata: Requires-Dist (botocore) Requirement not satisfied: python-dateutil (<3.0.0,>=2.1) Handling urllib3 (<1.27,>=1.25.4) ; python_version < "3.10" from hook generated metadata: Requires-Dist (botocore) Ignoring alien requirement: urllib3 (<1.27,>=1.25.4) ; python_version < "3.10" Handling urllib3 (!=2.2.0,<3,>=1.25.4) ; python_version >= "3.10" from hook generated metadata: Requires-Dist (botocore) Requirement not satisfied: urllib3 (!=2.2.0,<3,>=1.25.4) ; python_version >= "3.10" Handling awscrt (==0.31.2) ; extra == 'crt' from hook generated metadata: Requires-Dist (botocore) Ignoring alien requirement: awscrt (==0.31.2) ; extra == 'crt' + cat /builddir/build/BUILD/python-botocore-1.42.97-1.an23.noarch-pyproject-buildrequires + rm -rfv botocore-1.42.97.dist-info/ removed 'botocore-1.42.97.dist-info/top_level.txt' removed 'botocore-1.42.97.dist-info/METADATA' removed 'botocore-1.42.97.dist-info/LICENSE.txt' removed 'botocore-1.42.97.dist-info/NOTICE' removed directory 'botocore-1.42.97.dist-info/' + RPM_EC=0 ++ jobs -p + exit 0 Wrote: /builddir/build/SRPMS/python-botocore-1.42.97-1.an23.buildreqs.nosrc.rpm Child return code was: 11 Dynamic buildrequires detected Going to install missing buildrequires. See root.log for details. ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -br --noprep --noclean --target noarch --nodeps /builddir/build/SPECS/python-botocore.spec'], chrootPath='/var/lib/mock/dist-an23-build-530887-80588/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=86400uid=982gid=135user='mockbuild'unshare_net=TrueraiseExc=FalseprintOutput=Falsenspawn_args=['--capability=cap_ipc_lock']) Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -br --noprep --noclean --target noarch --nodeps /builddir/build/SPECS/python-botocore.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'} and shell False Building target platforms: noarch Building for target noarch setting SOURCE_DATE_EPOCH=1777420800 Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.7CvKt6 + umask 022 + cd /builddir/build/BUILD + cd botocore-1.42.97 + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/gfortran/modules' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/gfortran/modules' + export FCFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/anolis/anolis-hardened-ld -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -Wl,--build-id=sha1 ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + echo pyproject-rpm-macros + echo python3-devel + echo 'python3dist(pip) >= 19' + echo 'python3dist(packaging)' + '[' -f pyproject.toml ']' + echo '(python3dist(tomli) if python3-devel < 3.11)' + rm -rfv '*.dist-info/' + '[' -f /usr/bin/python3 ']' + mkdir -p /builddir/build/BUILD/botocore-1.42.97/.pyproject-builddir + echo -n + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/anolis/anolis-hardened-ld -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -Wl,--build-id=sha1 ' + TMPDIR=/builddir/build/BUILD/botocore-1.42.97/.pyproject-builddir + RPM_TOXENV=py311 + HOSTNAME=rpmbuild + /usr/bin/python3 -Bs /usr/lib/rpm/anolis/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /builddir/build/BUILD/botocore-1.42.97/pyproject-wheeldir --output /builddir/build/BUILD/python-botocore-1.42.97-1.an23.noarch-pyproject-buildrequires Handling setuptools >= 40.8 from default build backend Requirement satisfied: setuptools >= 40.8 (installed: setuptools 68.0.0) Handling wheel from default build backend Requirement satisfied: wheel (installed: wheel 0.38.4) running egg_info writing botocore.egg-info/PKG-INFO writing dependency_links to botocore.egg-info/dependency_links.txt writing requirements to botocore.egg-info/requires.txt writing top-level names to botocore.egg-info/top_level.txt reading manifest file 'botocore.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching 'botocore/vendored/requests/cacert.pem' warning: no files found matching '*.json.gz' under directory 'botocore/data' no previously-included directories found matching 'docs/build' adding license file 'LICENSE.txt' adding license file 'NOTICE' writing manifest file 'botocore.egg-info/SOURCES.txt' Handling wheel from get_requires_for_build_wheel Requirement satisfied: wheel (installed: wheel 0.38.4) running dist_info writing botocore.egg-info/PKG-INFO writing dependency_links to botocore.egg-info/dependency_links.txt writing requirements to botocore.egg-info/requires.txt writing top-level names to botocore.egg-info/top_level.txt reading manifest file 'botocore.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching 'botocore/vendored/requests/cacert.pem' warning: no files found matching '*.json.gz' under directory 'botocore/data' no previously-included directories found matching 'docs/build' adding license file 'LICENSE.txt' adding license file 'NOTICE' writing manifest file 'botocore.egg-info/SOURCES.txt' creating '/builddir/build/BUILD/botocore-1.42.97/botocore-1.42.97.dist-info' Handling jmespath (<2.0.0,>=0.7.1) from hook generated metadata: Requires-Dist (botocore) Requirement satisfied: jmespath (<2.0.0,>=0.7.1) (installed: jmespath 0.10.0) Handling python-dateutil (<3.0.0,>=2.1) from hook generated metadata: Requires-Dist (botocore) Requirement satisfied: python-dateutil (<3.0.0,>=2.1) (installed: python-dateutil 2.8.2) Handling urllib3 (<1.27,>=1.25.4) ; python_version < "3.10" from hook generated metadata: Requires-Dist (botocore) Ignoring alien requirement: urllib3 (<1.27,>=1.25.4) ; python_version < "3.10" Handling urllib3 (!=2.2.0,<3,>=1.25.4) ; python_version >= "3.10" from hook generated metadata: Requires-Dist (botocore) Requirement satisfied: urllib3 (!=2.2.0,<3,>=1.25.4) ; python_version >= "3.10" (installed: urllib3 1.26.19) Handling awscrt (==0.31.2) ; extra == 'crt' from hook generated metadata: Requires-Dist (botocore) Ignoring alien requirement: awscrt (==0.31.2) ; extra == 'crt' + cat /builddir/build/BUILD/python-botocore-1.42.97-1.an23.noarch-pyproject-buildrequires + rm -rfv botocore-1.42.97.dist-info/ removed 'botocore-1.42.97.dist-info/top_level.txt' removed 'botocore-1.42.97.dist-info/METADATA' removed 'botocore-1.42.97.dist-info/LICENSE.txt' removed 'botocore-1.42.97.dist-info/NOTICE' removed directory 'botocore-1.42.97.dist-info/' + RPM_EC=0 ++ jobs -p + exit 0 Wrote: /builddir/build/SRPMS/python-botocore-1.42.97-1.an23.buildreqs.nosrc.rpm Child return code was: 11 Dynamic buildrequires detected Going to install missing buildrequires. See root.log for details. ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -ba --noprep --noclean --target noarch /builddir/build/SPECS/python-botocore.spec'], chrootPath='/var/lib/mock/dist-an23-build-530887-80588/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=86400uid=982gid=135user='mockbuild'unshare_net=TrueprintOutput=Falsenspawn_args=['--capability=cap_ipc_lock']) Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -ba --noprep --noclean --target noarch /builddir/build/SPECS/python-botocore.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'} and shell False Building target platforms: noarch Building for target noarch setting SOURCE_DATE_EPOCH=1777420800 Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.k0JEcb + umask 022 + cd /builddir/build/BUILD + cd botocore-1.42.97 + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/gfortran/modules' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/gfortran/modules' + export FCFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/anolis/anolis-hardened-ld -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -Wl,--build-id=sha1 ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + echo pyproject-rpm-macros + echo python3-devel + echo 'python3dist(pip) >= 19' + echo 'python3dist(packaging)' + '[' -f pyproject.toml ']' + echo '(python3dist(tomli) if python3-devel < 3.11)' + rm -rfv '*.dist-info/' + '[' -f /usr/bin/python3 ']' + mkdir -p /builddir/build/BUILD/botocore-1.42.97/.pyproject-builddir + echo -n + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/anolis/anolis-hardened-ld -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -Wl,--build-id=sha1 ' + TMPDIR=/builddir/build/BUILD/botocore-1.42.97/.pyproject-builddir + RPM_TOXENV=py311 + HOSTNAME=rpmbuild + /usr/bin/python3 -Bs /usr/lib/rpm/anolis/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /builddir/build/BUILD/botocore-1.42.97/pyproject-wheeldir --output /builddir/build/BUILD/python-botocore-1.42.97-1.an23.noarch-pyproject-buildrequires Handling setuptools >= 40.8 from default build backend Requirement satisfied: setuptools >= 40.8 (installed: setuptools 68.0.0) Handling wheel from default build backend Requirement satisfied: wheel (installed: wheel 0.38.4) running egg_info writing botocore.egg-info/PKG-INFO writing dependency_links to botocore.egg-info/dependency_links.txt writing requirements to botocore.egg-info/requires.txt writing top-level names to botocore.egg-info/top_level.txt reading manifest file 'botocore.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching 'botocore/vendored/requests/cacert.pem' warning: no files found matching '*.json.gz' under directory 'botocore/data' no previously-included directories found matching 'docs/build' adding license file 'LICENSE.txt' adding license file 'NOTICE' writing manifest file 'botocore.egg-info/SOURCES.txt' Handling wheel from get_requires_for_build_wheel Requirement satisfied: wheel (installed: wheel 0.38.4) running dist_info writing botocore.egg-info/PKG-INFO writing dependency_links to botocore.egg-info/dependency_links.txt writing requirements to botocore.egg-info/requires.txt writing top-level names to botocore.egg-info/top_level.txt reading manifest file 'botocore.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching 'botocore/vendored/requests/cacert.pem' warning: no files found matching '*.json.gz' under directory 'botocore/data' no previously-included directories found matching 'docs/build' adding license file 'LICENSE.txt' adding license file 'NOTICE' writing manifest file 'botocore.egg-info/SOURCES.txt' creating '/builddir/build/BUILD/botocore-1.42.97/botocore-1.42.97.dist-info' Handling jmespath (<2.0.0,>=0.7.1) from hook generated metadata: Requires-Dist (botocore) Requirement satisfied: jmespath (<2.0.0,>=0.7.1) (installed: jmespath 0.10.0) Handling python-dateutil (<3.0.0,>=2.1) from hook generated metadata: Requires-Dist (botocore) Requirement satisfied: python-dateutil (<3.0.0,>=2.1) (installed: python-dateutil 2.8.2) Handling urllib3 (<1.27,>=1.25.4) ; python_version < "3.10" from hook generated metadata: Requires-Dist (botocore) Ignoring alien requirement: urllib3 (<1.27,>=1.25.4) ; python_version < "3.10" Handling urllib3 (!=2.2.0,<3,>=1.25.4) ; python_version >= "3.10" from hook generated metadata: Requires-Dist (botocore) Requirement satisfied: urllib3 (!=2.2.0,<3,>=1.25.4) ; python_version >= "3.10" (installed: urllib3 1.26.19) Handling awscrt (==0.31.2) ; extra == 'crt' from hook generated metadata: Requires-Dist (botocore) Ignoring alien requirement: awscrt (==0.31.2) ; extra == 'crt' + cat /builddir/build/BUILD/python-botocore-1.42.97-1.an23.noarch-pyproject-buildrequires + rm -rfv botocore-1.42.97.dist-info/ removed 'botocore-1.42.97.dist-info/top_level.txt' removed 'botocore-1.42.97.dist-info/METADATA' removed 'botocore-1.42.97.dist-info/LICENSE.txt' removed 'botocore-1.42.97.dist-info/NOTICE' removed directory 'botocore-1.42.97.dist-info/' + RPM_EC=0 ++ jobs -p + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.Pvuc2W + umask 022 + cd /builddir/build/BUILD + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/gfortran/modules' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/gfortran/modules' + export FCFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/anolis/anolis-hardened-ld -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -Wl,--build-id=sha1 ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd botocore-1.42.97 + mkdir -p /builddir/build/BUILD/botocore-1.42.97/.pyproject-builddir + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/anolis/anolis-hardened-ld -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -Wl,--build-id=sha1 ' + TMPDIR=/builddir/build/BUILD/botocore-1.42.97/.pyproject-builddir + /usr/bin/python3 -Bs /usr/lib/rpm/anolis/pyproject_wheel.py /builddir/build/BUILD/botocore-1.42.97/pyproject-wheeldir Looking in indexes: https://mirrors.aliyun.com/pypi/simple/ Processing /builddir/build/BUILD/botocore-1.42.97 Preparing metadata (pyproject.toml): started Running command Preparing metadata (pyproject.toml) running dist_info creating /builddir/build/BUILD/botocore-1.42.97/.pyproject-builddir/pip-modern-metadata-g6mlqpca/botocore.egg-info writing /builddir/build/BUILD/botocore-1.42.97/.pyproject-builddir/pip-modern-metadata-g6mlqpca/botocore.egg-info/PKG-INFO writing dependency_links to /builddir/build/BUILD/botocore-1.42.97/.pyproject-builddir/pip-modern-metadata-g6mlqpca/botocore.egg-info/dependency_links.txt writing requirements to /builddir/build/BUILD/botocore-1.42.97/.pyproject-builddir/pip-modern-metadata-g6mlqpca/botocore.egg-info/requires.txt writing top-level names to /builddir/build/BUILD/botocore-1.42.97/.pyproject-builddir/pip-modern-metadata-g6mlqpca/botocore.egg-info/top_level.txt writing manifest file '/builddir/build/BUILD/botocore-1.42.97/.pyproject-builddir/pip-modern-metadata-g6mlqpca/botocore.egg-info/SOURCES.txt' reading manifest file '/builddir/build/BUILD/botocore-1.42.97/.pyproject-builddir/pip-modern-metadata-g6mlqpca/botocore.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching 'botocore/vendored/requests/cacert.pem' warning: no files found matching '*.json.gz' under directory 'botocore/data' no previously-included directories found matching 'docs/build' adding license file 'LICENSE.txt' adding license file 'NOTICE' writing manifest file '/builddir/build/BUILD/botocore-1.42.97/.pyproject-builddir/pip-modern-metadata-g6mlqpca/botocore.egg-info/SOURCES.txt' creating '/builddir/build/BUILD/botocore-1.42.97/.pyproject-builddir/pip-modern-metadata-g6mlqpca/botocore-1.42.97.dist-info' Preparing metadata (pyproject.toml): finished with status 'done' Building wheels for collected packages: botocore Building wheel for botocore (pyproject.toml): started Running command Building wheel for botocore (pyproject.toml) running bdist_wheel running build running build_py creating build creating build/lib creating build/lib/botocore copying botocore/__init__.py -> build/lib/botocore copying botocore/args.py -> build/lib/botocore copying botocore/auth.py -> build/lib/botocore copying botocore/awsrequest.py -> build/lib/botocore copying botocore/client.py -> build/lib/botocore copying botocore/compat.py -> build/lib/botocore copying botocore/compress.py -> build/lib/botocore copying botocore/config.py -> build/lib/botocore copying botocore/configloader.py -> build/lib/botocore copying botocore/configprovider.py -> build/lib/botocore copying botocore/context.py -> build/lib/botocore copying botocore/credentials.py -> build/lib/botocore copying botocore/discovery.py -> build/lib/botocore copying botocore/endpoint.py -> build/lib/botocore copying botocore/endpoint_provider.py -> build/lib/botocore copying botocore/errorfactory.py -> build/lib/botocore copying botocore/eventstream.py -> build/lib/botocore copying botocore/exceptions.py -> build/lib/botocore copying botocore/handlers.py -> build/lib/botocore copying botocore/history.py -> build/lib/botocore copying botocore/hooks.py -> build/lib/botocore copying botocore/httpchecksum.py -> build/lib/botocore copying botocore/httpsession.py -> build/lib/botocore copying botocore/loaders.py -> build/lib/botocore copying botocore/model.py -> build/lib/botocore copying botocore/monitoring.py -> build/lib/botocore copying botocore/paginate.py -> build/lib/botocore copying botocore/parsers.py -> build/lib/botocore copying botocore/plugin.py -> build/lib/botocore copying botocore/regions.py -> build/lib/botocore copying botocore/response.py -> build/lib/botocore copying botocore/retryhandler.py -> build/lib/botocore copying botocore/serialize.py -> build/lib/botocore copying botocore/session.py -> build/lib/botocore copying botocore/signers.py -> build/lib/botocore copying botocore/stub.py -> build/lib/botocore copying botocore/tokens.py -> build/lib/botocore copying botocore/translate.py -> build/lib/botocore copying botocore/useragent.py -> build/lib/botocore copying botocore/utils.py -> build/lib/botocore copying botocore/validate.py -> build/lib/botocore copying botocore/waiter.py -> build/lib/botocore creating build/lib/botocore/crt copying botocore/crt/__init__.py -> build/lib/botocore/crt copying botocore/crt/auth.py -> build/lib/botocore/crt creating build/lib/botocore/docs copying botocore/docs/__init__.py -> build/lib/botocore/docs copying botocore/docs/client.py -> build/lib/botocore/docs copying botocore/docs/docstring.py -> build/lib/botocore/docs copying botocore/docs/example.py -> build/lib/botocore/docs copying botocore/docs/method.py -> build/lib/botocore/docs copying botocore/docs/paginator.py -> build/lib/botocore/docs copying botocore/docs/params.py -> build/lib/botocore/docs copying botocore/docs/service.py -> build/lib/botocore/docs copying botocore/docs/shape.py -> build/lib/botocore/docs copying botocore/docs/sharedexample.py -> build/lib/botocore/docs copying botocore/docs/translator.py -> build/lib/botocore/docs copying botocore/docs/utils.py -> build/lib/botocore/docs copying botocore/docs/waiter.py -> build/lib/botocore/docs creating build/lib/botocore/retries copying botocore/retries/__init__.py -> build/lib/botocore/retries copying botocore/retries/adaptive.py -> build/lib/botocore/retries copying botocore/retries/base.py -> build/lib/botocore/retries copying botocore/retries/bucket.py -> build/lib/botocore/retries copying botocore/retries/quota.py -> build/lib/botocore/retries copying botocore/retries/special.py -> build/lib/botocore/retries copying botocore/retries/standard.py -> build/lib/botocore/retries copying botocore/retries/throttling.py -> build/lib/botocore/retries creating build/lib/botocore/vendored copying botocore/vendored/__init__.py -> build/lib/botocore/vendored copying botocore/vendored/six.py -> build/lib/botocore/vendored creating build/lib/botocore/docs/bcdoc copying botocore/docs/bcdoc/__init__.py -> build/lib/botocore/docs/bcdoc copying botocore/docs/bcdoc/docstringparser.py -> build/lib/botocore/docs/bcdoc copying botocore/docs/bcdoc/restdoc.py -> build/lib/botocore/docs/bcdoc copying botocore/docs/bcdoc/style.py -> build/lib/botocore/docs/bcdoc creating build/lib/botocore/vendored/requests copying botocore/vendored/requests/__init__.py -> build/lib/botocore/vendored/requests copying botocore/vendored/requests/exceptions.py -> build/lib/botocore/vendored/requests creating build/lib/botocore/vendored/requests/packages copying botocore/vendored/requests/packages/__init__.py -> build/lib/botocore/vendored/requests/packages creating build/lib/botocore/vendored/requests/packages/urllib3 copying botocore/vendored/requests/packages/urllib3/__init__.py -> build/lib/botocore/vendored/requests/packages/urllib3 copying botocore/vendored/requests/packages/urllib3/exceptions.py -> build/lib/botocore/vendored/requests/packages/urllib3 running egg_info writing botocore.egg-info/PKG-INFO writing dependency_links to botocore.egg-info/dependency_links.txt writing requirements to botocore.egg-info/requires.txt writing top-level names to botocore.egg-info/top_level.txt reading manifest file 'botocore.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching 'botocore/vendored/requests/cacert.pem' warning: no files found matching '*.json.gz' under directory 'botocore/data' no previously-included directories found matching 'docs/build' adding license file 'LICENSE.txt' adding license file 'NOTICE' writing manifest file 'botocore.egg-info/SOURCES.txt' /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data' to be distributed and are already explicitly excluding 'botocore.data' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.accessanalyzer' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.accessanalyzer' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.accessanalyzer' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.accessanalyzer' to be distributed and are already explicitly excluding 'botocore.data.accessanalyzer' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.account' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.account' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.account' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.account' to be distributed and are already explicitly excluding 'botocore.data.account' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.acm' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.acm' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.acm' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.acm' to be distributed and are already explicitly excluding 'botocore.data.acm' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.aiops' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.aiops' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.aiops' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.aiops' to be distributed and are already explicitly excluding 'botocore.data.aiops' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.amp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.amp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.amp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.amp' to be distributed and are already explicitly excluding 'botocore.data.amp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.amplify' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.amplify' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.amplify' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.amplify' to be distributed and are already explicitly excluding 'botocore.data.amplify' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.amplifybackend' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.amplifybackend' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.amplifybackend' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.amplifybackend' to be distributed and are already explicitly excluding 'botocore.data.amplifybackend' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.amplifyuibuilder' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.amplifyuibuilder' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.amplifyuibuilder' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.amplifyuibuilder' to be distributed and are already explicitly excluding 'botocore.data.amplifyuibuilder' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.apigateway' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.apigateway' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.apigateway' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.apigateway' to be distributed and are already explicitly excluding 'botocore.data.apigateway' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.apigatewaymanagementapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.apigatewaymanagementapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.apigatewaymanagementapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.apigatewaymanagementapi' to be distributed and are already explicitly excluding 'botocore.data.apigatewaymanagementapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.apigatewayv2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.apigatewayv2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.apigatewayv2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.apigatewayv2' to be distributed and are already explicitly excluding 'botocore.data.apigatewayv2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.appconfig' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.appconfig' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.appconfig' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.appconfig' to be distributed and are already explicitly excluding 'botocore.data.appconfig' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.appconfigdata' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.appconfigdata' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.appconfigdata' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.appconfigdata' to be distributed and are already explicitly excluding 'botocore.data.appconfigdata' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.appfabric' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.appfabric' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.appfabric' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.appfabric' to be distributed and are already explicitly excluding 'botocore.data.appfabric' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.appflow' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.appflow' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.appflow' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.appflow' to be distributed and are already explicitly excluding 'botocore.data.appflow' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.appintegrations' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.appintegrations' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.appintegrations' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.appintegrations' to be distributed and are already explicitly excluding 'botocore.data.appintegrations' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.applicationcostprofiler' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.applicationcostprofiler' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.applicationcostprofiler' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.applicationcostprofiler' to be distributed and are already explicitly excluding 'botocore.data.applicationcostprofiler' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.appmesh' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.appmesh' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.appmesh' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.appmesh' to be distributed and are already explicitly excluding 'botocore.data.appmesh' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.apprunner' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.apprunner' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.apprunner' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.apprunner' to be distributed and are already explicitly excluding 'botocore.data.apprunner' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.appstream' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.appstream' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.appstream' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.appstream' to be distributed and are already explicitly excluding 'botocore.data.appstream' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.appsync' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.appsync' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.appsync' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.appsync' to be distributed and are already explicitly excluding 'botocore.data.appsync' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.artifact' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.artifact' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.artifact' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.artifact' to be distributed and are already explicitly excluding 'botocore.data.artifact' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.athena' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.athena' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.athena' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.athena' to be distributed and are already explicitly excluding 'botocore.data.athena' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.auditmanager' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.auditmanager' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.auditmanager' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.auditmanager' to be distributed and are already explicitly excluding 'botocore.data.auditmanager' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.autoscaling' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.autoscaling' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.autoscaling' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.autoscaling' to be distributed and are already explicitly excluding 'botocore.data.autoscaling' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.b2bi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.b2bi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.b2bi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.b2bi' to be distributed and are already explicitly excluding 'botocore.data.b2bi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.backup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.backup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.backup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.backup' to be distributed and are already explicitly excluding 'botocore.data.backup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.backupsearch' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.backupsearch' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.backupsearch' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.backupsearch' to be distributed and are already explicitly excluding 'botocore.data.backupsearch' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.batch' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.batch' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.batch' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.batch' to be distributed and are already explicitly excluding 'botocore.data.batch' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.bedrock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.bedrock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.bedrock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.bedrock' to be distributed and are already explicitly excluding 'botocore.data.bedrock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.billing' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.billing' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.billing' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.billing' to be distributed and are already explicitly excluding 'botocore.data.billing' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.billingconductor' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.billingconductor' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.billingconductor' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.billingconductor' to be distributed and are already explicitly excluding 'botocore.data.billingconductor' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.braket' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.braket' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.braket' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.braket' to be distributed and are already explicitly excluding 'botocore.data.braket' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.budgets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.budgets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.budgets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.budgets' to be distributed and are already explicitly excluding 'botocore.data.budgets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.ce' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.ce' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.ce' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.ce' to be distributed and are already explicitly excluding 'botocore.data.ce' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.chatbot' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.chatbot' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.chatbot' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.chatbot' to be distributed and are already explicitly excluding 'botocore.data.chatbot' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.chime' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.chime' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.chime' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.chime' to be distributed and are already explicitly excluding 'botocore.data.chime' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.cleanrooms' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.cleanrooms' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.cleanrooms' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.cleanrooms' to be distributed and are already explicitly excluding 'botocore.data.cleanrooms' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.cleanroomsml' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.cleanroomsml' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.cleanroomsml' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.cleanroomsml' to be distributed and are already explicitly excluding 'botocore.data.cleanroomsml' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.cloud9' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.cloud9' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.cloud9' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.cloud9' to be distributed and are already explicitly excluding 'botocore.data.cloud9' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.cloudcontrol' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.cloudcontrol' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.cloudcontrol' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.cloudcontrol' to be distributed and are already explicitly excluding 'botocore.data.cloudcontrol' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.clouddirectory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.clouddirectory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.clouddirectory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.clouddirectory' to be distributed and are already explicitly excluding 'botocore.data.clouddirectory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.cloudformation' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.cloudformation' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.cloudformation' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.cloudformation' to be distributed and are already explicitly excluding 'botocore.data.cloudformation' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.cloudfront' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.cloudfront' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.cloudfront' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.cloudfront' to be distributed and are already explicitly excluding 'botocore.data.cloudfront' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.cloudhsm' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.cloudhsm' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.cloudhsm' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.cloudhsm' to be distributed and are already explicitly excluding 'botocore.data.cloudhsm' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.cloudhsmv2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.cloudhsmv2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.cloudhsmv2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.cloudhsmv2' to be distributed and are already explicitly excluding 'botocore.data.cloudhsmv2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.cloudsearch' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.cloudsearch' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.cloudsearch' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.cloudsearch' to be distributed and are already explicitly excluding 'botocore.data.cloudsearch' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.cloudsearchdomain' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.cloudsearchdomain' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.cloudsearchdomain' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.cloudsearchdomain' to be distributed and are already explicitly excluding 'botocore.data.cloudsearchdomain' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.cloudtrail' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.cloudtrail' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.cloudtrail' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.cloudtrail' to be distributed and are already explicitly excluding 'botocore.data.cloudtrail' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.cloudwatch' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.cloudwatch' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.cloudwatch' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.cloudwatch' to be distributed and are already explicitly excluding 'botocore.data.cloudwatch' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.codeartifact' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.codeartifact' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.codeartifact' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.codeartifact' to be distributed and are already explicitly excluding 'botocore.data.codeartifact' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.codebuild' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.codebuild' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.codebuild' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.codebuild' to be distributed and are already explicitly excluding 'botocore.data.codebuild' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.codecatalyst' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.codecatalyst' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.codecatalyst' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.codecatalyst' to be distributed and are already explicitly excluding 'botocore.data.codecatalyst' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.codecommit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.codecommit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.codecommit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.codecommit' to be distributed and are already explicitly excluding 'botocore.data.codecommit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.codeconnections' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.codeconnections' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.codeconnections' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.codeconnections' to be distributed and are already explicitly excluding 'botocore.data.codeconnections' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.codedeploy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.codedeploy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.codedeploy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.codedeploy' to be distributed and are already explicitly excluding 'botocore.data.codedeploy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.codeguruprofiler' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.codeguruprofiler' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.codeguruprofiler' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.codeguruprofiler' to be distributed and are already explicitly excluding 'botocore.data.codeguruprofiler' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.codepipeline' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.codepipeline' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.codepipeline' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.codepipeline' to be distributed and are already explicitly excluding 'botocore.data.codepipeline' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.comprehend' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.comprehend' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.comprehend' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.comprehend' to be distributed and are already explicitly excluding 'botocore.data.comprehend' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.comprehendmedical' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.comprehendmedical' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.comprehendmedical' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.comprehendmedical' to be distributed and are already explicitly excluding 'botocore.data.comprehendmedical' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.config' to be distributed and are already explicitly excluding 'botocore.data.config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.connect' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.connect' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.connect' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.connect' to be distributed and are already explicitly excluding 'botocore.data.connect' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.connectcampaigns' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.connectcampaigns' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.connectcampaigns' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.connectcampaigns' to be distributed and are already explicitly excluding 'botocore.data.connectcampaigns' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.connectcampaignsv2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.connectcampaignsv2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.connectcampaignsv2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.connectcampaignsv2' to be distributed and are already explicitly excluding 'botocore.data.connectcampaignsv2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.connectcases' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.connectcases' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.connectcases' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.connectcases' to be distributed and are already explicitly excluding 'botocore.data.connectcases' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.connecthealth' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.connecthealth' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.connecthealth' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.connecthealth' to be distributed and are already explicitly excluding 'botocore.data.connecthealth' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.connectparticipant' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.connectparticipant' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.connectparticipant' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.connectparticipant' to be distributed and are already explicitly excluding 'botocore.data.connectparticipant' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.controlcatalog' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.controlcatalog' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.controlcatalog' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.controlcatalog' to be distributed and are already explicitly excluding 'botocore.data.controlcatalog' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.controltower' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.controltower' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.controltower' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.controltower' to be distributed and are already explicitly excluding 'botocore.data.controltower' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.cur' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.cur' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.cur' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.cur' to be distributed and are already explicitly excluding 'botocore.data.cur' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.databrew' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.databrew' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.databrew' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.databrew' to be distributed and are already explicitly excluding 'botocore.data.databrew' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.dataexchange' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.dataexchange' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.dataexchange' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.dataexchange' to be distributed and are already explicitly excluding 'botocore.data.dataexchange' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.datapipeline' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.datapipeline' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.datapipeline' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.datapipeline' to be distributed and are already explicitly excluding 'botocore.data.datapipeline' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.datasync' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.datasync' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.datasync' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.datasync' to be distributed and are already explicitly excluding 'botocore.data.datasync' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.datazone' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.datazone' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.datazone' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.datazone' to be distributed and are already explicitly excluding 'botocore.data.datazone' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.dax' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.dax' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.dax' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.dax' to be distributed and are already explicitly excluding 'botocore.data.dax' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.deadline' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.deadline' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.deadline' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.deadline' to be distributed and are already explicitly excluding 'botocore.data.deadline' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.detective' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.detective' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.detective' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.detective' to be distributed and are already explicitly excluding 'botocore.data.detective' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.devicefarm' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.devicefarm' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.devicefarm' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.devicefarm' to be distributed and are already explicitly excluding 'botocore.data.devicefarm' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.directconnect' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.directconnect' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.directconnect' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.directconnect' to be distributed and are already explicitly excluding 'botocore.data.directconnect' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.discovery' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.discovery' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.discovery' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.discovery' to be distributed and are already explicitly excluding 'botocore.data.discovery' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.dlm' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.dlm' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.dlm' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.dlm' to be distributed and are already explicitly excluding 'botocore.data.dlm' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.dms' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.dms' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.dms' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.dms' to be distributed and are already explicitly excluding 'botocore.data.dms' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.docdb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.docdb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.docdb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.docdb' to be distributed and are already explicitly excluding 'botocore.data.docdb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.drs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.drs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.drs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.drs' to be distributed and are already explicitly excluding 'botocore.data.drs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.ds' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.ds' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.ds' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.ds' to be distributed and are already explicitly excluding 'botocore.data.ds' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.dsql' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.dsql' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.dsql' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.dsql' to be distributed and are already explicitly excluding 'botocore.data.dsql' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.dynamodb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.dynamodb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.dynamodb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.dynamodb' to be distributed and are already explicitly excluding 'botocore.data.dynamodb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.dynamodbstreams' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.dynamodbstreams' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.dynamodbstreams' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.dynamodbstreams' to be distributed and are already explicitly excluding 'botocore.data.dynamodbstreams' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.ebs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.ebs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.ebs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.ebs' to be distributed and are already explicitly excluding 'botocore.data.ebs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.ec2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.ec2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.ec2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.ec2' to be distributed and are already explicitly excluding 'botocore.data.ec2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.ecr' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.ecr' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.ecr' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.ecr' to be distributed and are already explicitly excluding 'botocore.data.ecr' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.ecs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.ecs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.ecs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.ecs' to be distributed and are already explicitly excluding 'botocore.data.ecs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.efs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.efs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.efs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.efs' to be distributed and are already explicitly excluding 'botocore.data.efs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.eks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.eks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.eks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.eks' to be distributed and are already explicitly excluding 'botocore.data.eks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.elasticache' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.elasticache' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.elasticache' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.elasticache' to be distributed and are already explicitly excluding 'botocore.data.elasticache' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.elasticbeanstalk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.elasticbeanstalk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.elasticbeanstalk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.elasticbeanstalk' to be distributed and are already explicitly excluding 'botocore.data.elasticbeanstalk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.elb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.elb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.elb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.elb' to be distributed and are already explicitly excluding 'botocore.data.elb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.elbv2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.elbv2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.elbv2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.elbv2' to be distributed and are already explicitly excluding 'botocore.data.elbv2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.elementalinference' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.elementalinference' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.elementalinference' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.elementalinference' to be distributed and are already explicitly excluding 'botocore.data.elementalinference' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.emr' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.emr' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.emr' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.emr' to be distributed and are already explicitly excluding 'botocore.data.emr' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.entityresolution' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.entityresolution' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.entityresolution' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.entityresolution' to be distributed and are already explicitly excluding 'botocore.data.entityresolution' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.es' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.es' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.es' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.es' to be distributed and are already explicitly excluding 'botocore.data.es' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.events' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.events' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.events' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.events' to be distributed and are already explicitly excluding 'botocore.data.events' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.evs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.evs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.evs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.evs' to be distributed and are already explicitly excluding 'botocore.data.evs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.finspace' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.finspace' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.finspace' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.finspace' to be distributed and are already explicitly excluding 'botocore.data.finspace' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.firehose' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.firehose' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.firehose' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.firehose' to be distributed and are already explicitly excluding 'botocore.data.firehose' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.fis' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.fis' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.fis' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.fis' to be distributed and are already explicitly excluding 'botocore.data.fis' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.fms' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.fms' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.fms' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.fms' to be distributed and are already explicitly excluding 'botocore.data.fms' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.forecast' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.forecast' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.forecast' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.forecast' to be distributed and are already explicitly excluding 'botocore.data.forecast' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.forecastquery' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.forecastquery' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.forecastquery' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.forecastquery' to be distributed and are already explicitly excluding 'botocore.data.forecastquery' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.frauddetector' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.frauddetector' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.frauddetector' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.frauddetector' to be distributed and are already explicitly excluding 'botocore.data.frauddetector' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.freetier' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.freetier' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.freetier' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.freetier' to be distributed and are already explicitly excluding 'botocore.data.freetier' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.fsx' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.fsx' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.fsx' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.fsx' to be distributed and are already explicitly excluding 'botocore.data.fsx' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.gamelift' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.gamelift' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.gamelift' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.gamelift' to be distributed and are already explicitly excluding 'botocore.data.gamelift' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.gameliftstreams' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.gameliftstreams' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.gameliftstreams' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.gameliftstreams' to be distributed and are already explicitly excluding 'botocore.data.gameliftstreams' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.glacier' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.glacier' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.glacier' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.glacier' to be distributed and are already explicitly excluding 'botocore.data.glacier' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.globalaccelerator' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.globalaccelerator' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.globalaccelerator' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.globalaccelerator' to be distributed and are already explicitly excluding 'botocore.data.globalaccelerator' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.glue' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.glue' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.glue' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.glue' to be distributed and are already explicitly excluding 'botocore.data.glue' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.grafana' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.grafana' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.grafana' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.grafana' to be distributed and are already explicitly excluding 'botocore.data.grafana' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.greengrass' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.greengrass' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.greengrass' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.greengrass' to be distributed and are already explicitly excluding 'botocore.data.greengrass' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.greengrassv2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.greengrassv2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.greengrassv2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.greengrassv2' to be distributed and are already explicitly excluding 'botocore.data.greengrassv2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.groundstation' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.groundstation' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.groundstation' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.groundstation' to be distributed and are already explicitly excluding 'botocore.data.groundstation' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.guardduty' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.guardduty' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.guardduty' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.guardduty' to be distributed and are already explicitly excluding 'botocore.data.guardduty' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.health' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.health' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.health' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.health' to be distributed and are already explicitly excluding 'botocore.data.health' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.healthlake' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.healthlake' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.healthlake' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.healthlake' to be distributed and are already explicitly excluding 'botocore.data.healthlake' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.iam' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.iam' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.iam' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.iam' to be distributed and are already explicitly excluding 'botocore.data.iam' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.identitystore' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.identitystore' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.identitystore' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.identitystore' to be distributed and are already explicitly excluding 'botocore.data.identitystore' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.imagebuilder' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.imagebuilder' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.imagebuilder' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.imagebuilder' to be distributed and are already explicitly excluding 'botocore.data.imagebuilder' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.importexport' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.importexport' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.importexport' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.importexport' to be distributed and are already explicitly excluding 'botocore.data.importexport' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.inspector' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.inspector' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.inspector' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.inspector' to be distributed and are already explicitly excluding 'botocore.data.inspector' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.inspector2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.inspector2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.inspector2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.inspector2' to be distributed and are already explicitly excluding 'botocore.data.inspector2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.interconnect' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.interconnect' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.interconnect' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.interconnect' to be distributed and are already explicitly excluding 'botocore.data.interconnect' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.internetmonitor' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.internetmonitor' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.internetmonitor' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.internetmonitor' to be distributed and are already explicitly excluding 'botocore.data.internetmonitor' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.invoicing' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.invoicing' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.invoicing' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.invoicing' to be distributed and are already explicitly excluding 'botocore.data.invoicing' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.iot' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.iot' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.iot' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.iot' to be distributed and are already explicitly excluding 'botocore.data.iot' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.iotdeviceadvisor' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.iotdeviceadvisor' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.iotdeviceadvisor' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.iotdeviceadvisor' to be distributed and are already explicitly excluding 'botocore.data.iotdeviceadvisor' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.iotevents' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.iotevents' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.iotevents' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.iotevents' to be distributed and are already explicitly excluding 'botocore.data.iotevents' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.iotfleetwise' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.iotfleetwise' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.iotfleetwise' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.iotfleetwise' to be distributed and are already explicitly excluding 'botocore.data.iotfleetwise' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.iotsecuretunneling' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.iotsecuretunneling' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.iotsecuretunneling' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.iotsecuretunneling' to be distributed and are already explicitly excluding 'botocore.data.iotsecuretunneling' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.iotsitewise' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.iotsitewise' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.iotsitewise' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.iotsitewise' to be distributed and are already explicitly excluding 'botocore.data.iotsitewise' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.iotthingsgraph' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.iotthingsgraph' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.iotthingsgraph' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.iotthingsgraph' to be distributed and are already explicitly excluding 'botocore.data.iotthingsgraph' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.iottwinmaker' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.iottwinmaker' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.iottwinmaker' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.iottwinmaker' to be distributed and are already explicitly excluding 'botocore.data.iottwinmaker' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.iotwireless' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.iotwireless' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.iotwireless' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.iotwireless' to be distributed and are already explicitly excluding 'botocore.data.iotwireless' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.ivs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.ivs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.ivs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.ivs' to be distributed and are already explicitly excluding 'botocore.data.ivs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.ivschat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.ivschat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.ivschat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.ivschat' to be distributed and are already explicitly excluding 'botocore.data.ivschat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.kafka' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.kafka' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.kafka' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.kafka' to be distributed and are already explicitly excluding 'botocore.data.kafka' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.kafkaconnect' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.kafkaconnect' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.kafkaconnect' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.kafkaconnect' to be distributed and are already explicitly excluding 'botocore.data.kafkaconnect' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.kendra' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.kendra' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.kendra' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.kendra' to be distributed and are already explicitly excluding 'botocore.data.kendra' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.keyspaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.keyspaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.keyspaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.keyspaces' to be distributed and are already explicitly excluding 'botocore.data.keyspaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.keyspacesstreams' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.keyspacesstreams' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.keyspacesstreams' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.keyspacesstreams' to be distributed and are already explicitly excluding 'botocore.data.keyspacesstreams' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.kinesis' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.kinesis' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.kinesis' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.kinesis' to be distributed and are already explicitly excluding 'botocore.data.kinesis' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.kinesisanalytics' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.kinesisanalytics' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.kinesisanalytics' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.kinesisanalytics' to be distributed and are already explicitly excluding 'botocore.data.kinesisanalytics' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.kinesisanalyticsv2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.kinesisanalyticsv2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.kinesisanalyticsv2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.kinesisanalyticsv2' to be distributed and are already explicitly excluding 'botocore.data.kinesisanalyticsv2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.kinesisvideo' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.kinesisvideo' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.kinesisvideo' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.kinesisvideo' to be distributed and are already explicitly excluding 'botocore.data.kinesisvideo' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.kms' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.kms' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.kms' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.kms' to be distributed and are already explicitly excluding 'botocore.data.kms' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.lakeformation' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.lakeformation' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.lakeformation' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.lakeformation' to be distributed and are already explicitly excluding 'botocore.data.lakeformation' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.lambda' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.lambda' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.lambda' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.lambda' to be distributed and are already explicitly excluding 'botocore.data.lambda' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.lightsail' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.lightsail' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.lightsail' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.lightsail' to be distributed and are already explicitly excluding 'botocore.data.lightsail' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.location' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.location' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.location' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.location' to be distributed and are already explicitly excluding 'botocore.data.location' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.logs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.logs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.logs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.logs' to be distributed and are already explicitly excluding 'botocore.data.logs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.lookoutequipment' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.lookoutequipment' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.lookoutequipment' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.lookoutequipment' to be distributed and are already explicitly excluding 'botocore.data.lookoutequipment' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.m2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.m2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.m2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.m2' to be distributed and are already explicitly excluding 'botocore.data.m2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.machinelearning' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.machinelearning' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.machinelearning' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.machinelearning' to be distributed and are already explicitly excluding 'botocore.data.machinelearning' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.macie2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.macie2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.macie2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.macie2' to be distributed and are already explicitly excluding 'botocore.data.macie2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.mailmanager' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.mailmanager' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.mailmanager' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.mailmanager' to be distributed and are already explicitly excluding 'botocore.data.mailmanager' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.managedblockchain' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.managedblockchain' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.managedblockchain' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.managedblockchain' to be distributed and are already explicitly excluding 'botocore.data.managedblockchain' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.marketplacecommerceanalytics' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.marketplacecommerceanalytics' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.marketplacecommerceanalytics' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.marketplacecommerceanalytics' to be distributed and are already explicitly excluding 'botocore.data.marketplacecommerceanalytics' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.mediaconnect' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.mediaconnect' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.mediaconnect' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.mediaconnect' to be distributed and are already explicitly excluding 'botocore.data.mediaconnect' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.mediaconvert' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.mediaconvert' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.mediaconvert' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.mediaconvert' to be distributed and are already explicitly excluding 'botocore.data.mediaconvert' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.medialive' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.medialive' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.medialive' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.medialive' to be distributed and are already explicitly excluding 'botocore.data.medialive' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.mediapackage' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.mediapackage' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.mediapackage' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.mediapackage' to be distributed and are already explicitly excluding 'botocore.data.mediapackage' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.mediapackagev2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.mediapackagev2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.mediapackagev2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.mediapackagev2' to be distributed and are already explicitly excluding 'botocore.data.mediapackagev2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.mediastore' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.mediastore' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.mediastore' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.mediastore' to be distributed and are already explicitly excluding 'botocore.data.mediastore' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.mediatailor' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.mediatailor' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.mediatailor' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.mediatailor' to be distributed and are already explicitly excluding 'botocore.data.mediatailor' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.memorydb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.memorydb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.memorydb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.memorydb' to be distributed and are already explicitly excluding 'botocore.data.memorydb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.meteringmarketplace' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.meteringmarketplace' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.meteringmarketplace' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.meteringmarketplace' to be distributed and are already explicitly excluding 'botocore.data.meteringmarketplace' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.mgh' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.mgh' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.mgh' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.mgh' to be distributed and are already explicitly excluding 'botocore.data.mgh' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.mgn' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.mgn' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.mgn' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.mgn' to be distributed and are already explicitly excluding 'botocore.data.mgn' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.migrationhuborchestrator' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.migrationhuborchestrator' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.migrationhuborchestrator' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.migrationhuborchestrator' to be distributed and are already explicitly excluding 'botocore.data.migrationhuborchestrator' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.migrationhubstrategy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.migrationhubstrategy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.migrationhubstrategy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.migrationhubstrategy' to be distributed and are already explicitly excluding 'botocore.data.migrationhubstrategy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.mpa' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.mpa' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.mpa' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.mpa' to be distributed and are already explicitly excluding 'botocore.data.mpa' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.mq' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.mq' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.mq' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.mq' to be distributed and are already explicitly excluding 'botocore.data.mq' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.mturk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.mturk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.mturk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.mturk' to be distributed and are already explicitly excluding 'botocore.data.mturk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.mwaa' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.mwaa' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.mwaa' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.mwaa' to be distributed and are already explicitly excluding 'botocore.data.mwaa' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.neptune' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.neptune' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.neptune' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.neptune' to be distributed and are already explicitly excluding 'botocore.data.neptune' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.neptunedata' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.neptunedata' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.neptunedata' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.neptunedata' to be distributed and are already explicitly excluding 'botocore.data.neptunedata' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.networkflowmonitor' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.networkflowmonitor' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.networkflowmonitor' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.networkflowmonitor' to be distributed and are already explicitly excluding 'botocore.data.networkflowmonitor' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.networkmanager' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.networkmanager' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.networkmanager' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.networkmanager' to be distributed and are already explicitly excluding 'botocore.data.networkmanager' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.networkmonitor' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.networkmonitor' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.networkmonitor' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.networkmonitor' to be distributed and are already explicitly excluding 'botocore.data.networkmonitor' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.notifications' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.notifications' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.notifications' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.notifications' to be distributed and are already explicitly excluding 'botocore.data.notifications' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.notificationscontacts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.notificationscontacts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.notificationscontacts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.notificationscontacts' to be distributed and are already explicitly excluding 'botocore.data.notificationscontacts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.oam' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.oam' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.oam' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.oam' to be distributed and are already explicitly excluding 'botocore.data.oam' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.observabilityadmin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.observabilityadmin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.observabilityadmin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.observabilityadmin' to be distributed and are already explicitly excluding 'botocore.data.observabilityadmin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.odb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.odb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.odb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.odb' to be distributed and are already explicitly excluding 'botocore.data.odb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.omics' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.omics' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.omics' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.omics' to be distributed and are already explicitly excluding 'botocore.data.omics' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.opensearch' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.opensearch' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.opensearch' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.opensearch' to be distributed and are already explicitly excluding 'botocore.data.opensearch' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.opensearchserverless' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.opensearchserverless' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.opensearchserverless' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.opensearchserverless' to be distributed and are already explicitly excluding 'botocore.data.opensearchserverless' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.organizations' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.organizations' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.organizations' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.organizations' to be distributed and are already explicitly excluding 'botocore.data.organizations' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.osis' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.osis' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.osis' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.osis' to be distributed and are already explicitly excluding 'botocore.data.osis' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.outposts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.outposts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.outposts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.outposts' to be distributed and are already explicitly excluding 'botocore.data.outposts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.panorama' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.panorama' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.panorama' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.panorama' to be distributed and are already explicitly excluding 'botocore.data.panorama' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.pcs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.pcs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.pcs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.pcs' to be distributed and are already explicitly excluding 'botocore.data.pcs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.personalize' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.personalize' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.personalize' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.personalize' to be distributed and are already explicitly excluding 'botocore.data.personalize' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.pi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.pi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.pi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.pi' to be distributed and are already explicitly excluding 'botocore.data.pi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.pinpoint' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.pinpoint' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.pinpoint' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.pinpoint' to be distributed and are already explicitly excluding 'botocore.data.pinpoint' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.pipes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.pipes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.pipes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.pipes' to be distributed and are already explicitly excluding 'botocore.data.pipes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.polly' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.polly' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.polly' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.polly' to be distributed and are already explicitly excluding 'botocore.data.polly' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.pricing' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.pricing' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.pricing' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.pricing' to be distributed and are already explicitly excluding 'botocore.data.pricing' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.proton' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.proton' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.proton' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.proton' to be distributed and are already explicitly excluding 'botocore.data.proton' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.qapps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.qapps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.qapps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.qapps' to be distributed and are already explicitly excluding 'botocore.data.qapps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.qbusiness' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.qbusiness' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.qbusiness' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.qbusiness' to be distributed and are already explicitly excluding 'botocore.data.qbusiness' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.qconnect' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.qconnect' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.qconnect' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.qconnect' to be distributed and are already explicitly excluding 'botocore.data.qconnect' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.quicksight' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.quicksight' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.quicksight' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.quicksight' to be distributed and are already explicitly excluding 'botocore.data.quicksight' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.ram' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.ram' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.ram' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.ram' to be distributed and are already explicitly excluding 'botocore.data.ram' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.rbin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.rbin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.rbin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.rbin' to be distributed and are already explicitly excluding 'botocore.data.rbin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.rds' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.rds' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.rds' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.rds' to be distributed and are already explicitly excluding 'botocore.data.rds' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.redshift' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.redshift' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.redshift' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.redshift' to be distributed and are already explicitly excluding 'botocore.data.redshift' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.rekognition' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.rekognition' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.rekognition' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.rekognition' to be distributed and are already explicitly excluding 'botocore.data.rekognition' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.repostspace' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.repostspace' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.repostspace' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.repostspace' to be distributed and are already explicitly excluding 'botocore.data.repostspace' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.resiliencehub' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.resiliencehub' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.resiliencehub' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.resiliencehub' to be distributed and are already explicitly excluding 'botocore.data.resiliencehub' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.resourcegroupstaggingapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.resourcegroupstaggingapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.resourcegroupstaggingapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.resourcegroupstaggingapi' to be distributed and are already explicitly excluding 'botocore.data.resourcegroupstaggingapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.rolesanywhere' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.rolesanywhere' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.rolesanywhere' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.rolesanywhere' to be distributed and are already explicitly excluding 'botocore.data.rolesanywhere' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.route53' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.route53' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.route53' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.route53' to be distributed and are already explicitly excluding 'botocore.data.route53' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.route53domains' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.route53domains' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.route53domains' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.route53domains' to be distributed and are already explicitly excluding 'botocore.data.route53domains' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.route53globalresolver' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.route53globalresolver' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.route53globalresolver' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.route53globalresolver' to be distributed and are already explicitly excluding 'botocore.data.route53globalresolver' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.route53profiles' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.route53profiles' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.route53profiles' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.route53profiles' to be distributed and are already explicitly excluding 'botocore.data.route53profiles' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.route53resolver' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.route53resolver' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.route53resolver' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.route53resolver' to be distributed and are already explicitly excluding 'botocore.data.route53resolver' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.rtbfabric' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.rtbfabric' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.rtbfabric' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.rtbfabric' to be distributed and are already explicitly excluding 'botocore.data.rtbfabric' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.rum' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.rum' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.rum' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.rum' to be distributed and are already explicitly excluding 'botocore.data.rum' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.s3' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.s3' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.s3' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.s3' to be distributed and are already explicitly excluding 'botocore.data.s3' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.s3control' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.s3control' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.s3control' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.s3control' to be distributed and are already explicitly excluding 'botocore.data.s3control' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.s3files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.s3files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.s3files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.s3files' to be distributed and are already explicitly excluding 'botocore.data.s3files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.s3outposts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.s3outposts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.s3outposts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.s3outposts' to be distributed and are already explicitly excluding 'botocore.data.s3outposts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.s3tables' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.s3tables' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.s3tables' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.s3tables' to be distributed and are already explicitly excluding 'botocore.data.s3tables' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.s3vectors' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.s3vectors' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.s3vectors' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.s3vectors' to be distributed and are already explicitly excluding 'botocore.data.s3vectors' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.sagemaker' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.sagemaker' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.sagemaker' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.sagemaker' to be distributed and are already explicitly excluding 'botocore.data.sagemaker' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.savingsplans' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.savingsplans' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.savingsplans' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.savingsplans' to be distributed and are already explicitly excluding 'botocore.data.savingsplans' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.scheduler' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.scheduler' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.scheduler' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.scheduler' to be distributed and are already explicitly excluding 'botocore.data.scheduler' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.schemas' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.schemas' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.schemas' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.schemas' to be distributed and are already explicitly excluding 'botocore.data.schemas' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.sdb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.sdb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.sdb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.sdb' to be distributed and are already explicitly excluding 'botocore.data.sdb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.secretsmanager' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.secretsmanager' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.secretsmanager' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.secretsmanager' to be distributed and are already explicitly excluding 'botocore.data.secretsmanager' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.securityagent' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.securityagent' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.securityagent' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.securityagent' to be distributed and are already explicitly excluding 'botocore.data.securityagent' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.securityhub' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.securityhub' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.securityhub' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.securityhub' to be distributed and are already explicitly excluding 'botocore.data.securityhub' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.securitylake' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.securitylake' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.securitylake' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.securitylake' to be distributed and are already explicitly excluding 'botocore.data.securitylake' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.serverlessrepo' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.serverlessrepo' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.serverlessrepo' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.serverlessrepo' to be distributed and are already explicitly excluding 'botocore.data.serverlessrepo' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.servicecatalog' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.servicecatalog' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.servicecatalog' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.servicecatalog' to be distributed and are already explicitly excluding 'botocore.data.servicecatalog' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.servicediscovery' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.servicediscovery' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.servicediscovery' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.servicediscovery' to be distributed and are already explicitly excluding 'botocore.data.servicediscovery' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.ses' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.ses' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.ses' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.ses' to be distributed and are already explicitly excluding 'botocore.data.ses' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.sesv2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.sesv2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.sesv2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.sesv2' to be distributed and are already explicitly excluding 'botocore.data.sesv2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.shield' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.shield' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.shield' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.shield' to be distributed and are already explicitly excluding 'botocore.data.shield' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.signer' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.signer' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.signer' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.signer' to be distributed and are already explicitly excluding 'botocore.data.signer' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.signin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.signin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.signin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.signin' to be distributed and are already explicitly excluding 'botocore.data.signin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.simpledbv2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.simpledbv2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.simpledbv2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.simpledbv2' to be distributed and are already explicitly excluding 'botocore.data.simpledbv2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.simspaceweaver' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.simspaceweaver' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.simspaceweaver' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.simspaceweaver' to be distributed and are already explicitly excluding 'botocore.data.simspaceweaver' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.snowball' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.snowball' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.snowball' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.snowball' to be distributed and are already explicitly excluding 'botocore.data.snowball' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.sns' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.sns' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.sns' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.sns' to be distributed and are already explicitly excluding 'botocore.data.sns' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.socialmessaging' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.socialmessaging' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.socialmessaging' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.socialmessaging' to be distributed and are already explicitly excluding 'botocore.data.socialmessaging' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.sqs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.sqs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.sqs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.sqs' to be distributed and are already explicitly excluding 'botocore.data.sqs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.ssm' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.ssm' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.ssm' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.ssm' to be distributed and are already explicitly excluding 'botocore.data.ssm' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.sso' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.sso' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.sso' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.sso' to be distributed and are already explicitly excluding 'botocore.data.sso' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.stepfunctions' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.stepfunctions' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.stepfunctions' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.stepfunctions' to be distributed and are already explicitly excluding 'botocore.data.stepfunctions' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.storagegateway' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.storagegateway' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.storagegateway' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.storagegateway' to be distributed and are already explicitly excluding 'botocore.data.storagegateway' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.sts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.sts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.sts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.sts' to be distributed and are already explicitly excluding 'botocore.data.sts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.supplychain' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.supplychain' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.supplychain' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.supplychain' to be distributed and are already explicitly excluding 'botocore.data.supplychain' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.support' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.support' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.support' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.support' to be distributed and are already explicitly excluding 'botocore.data.support' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.sustainability' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.sustainability' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.sustainability' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.sustainability' to be distributed and are already explicitly excluding 'botocore.data.sustainability' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.swf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.swf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.swf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.swf' to be distributed and are already explicitly excluding 'botocore.data.swf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.synthetics' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.synthetics' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.synthetics' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.synthetics' to be distributed and are already explicitly excluding 'botocore.data.synthetics' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.taxsettings' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.taxsettings' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.taxsettings' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.taxsettings' to be distributed and are already explicitly excluding 'botocore.data.taxsettings' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.textract' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.textract' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.textract' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.textract' to be distributed and are already explicitly excluding 'botocore.data.textract' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.tnb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.tnb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.tnb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.tnb' to be distributed and are already explicitly excluding 'botocore.data.tnb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.transcribe' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.transcribe' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.transcribe' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.transcribe' to be distributed and are already explicitly excluding 'botocore.data.transcribe' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.transfer' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.transfer' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.transfer' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.transfer' to be distributed and are already explicitly excluding 'botocore.data.transfer' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.translate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.translate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.translate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.translate' to be distributed and are already explicitly excluding 'botocore.data.translate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.trustedadvisor' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.trustedadvisor' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.trustedadvisor' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.trustedadvisor' to be distributed and are already explicitly excluding 'botocore.data.trustedadvisor' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.uxc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.uxc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.uxc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.uxc' to be distributed and are already explicitly excluding 'botocore.data.uxc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.verifiedpermissions' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.verifiedpermissions' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.verifiedpermissions' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.verifiedpermissions' to be distributed and are already explicitly excluding 'botocore.data.verifiedpermissions' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.waf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.waf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.waf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.waf' to be distributed and are already explicitly excluding 'botocore.data.waf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.wafv2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.wafv2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.wafv2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.wafv2' to be distributed and are already explicitly excluding 'botocore.data.wafv2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.wellarchitected' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.wellarchitected' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.wellarchitected' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.wellarchitected' to be distributed and are already explicitly excluding 'botocore.data.wellarchitected' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.wickr' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.wickr' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.wickr' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.wickr' to be distributed and are already explicitly excluding 'botocore.data.wickr' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.wisdom' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.wisdom' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.wisdom' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.wisdom' to be distributed and are already explicitly excluding 'botocore.data.wisdom' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.workdocs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.workdocs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.workdocs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.workdocs' to be distributed and are already explicitly excluding 'botocore.data.workdocs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.workmail' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.workmail' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.workmail' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.workmail' to be distributed and are already explicitly excluding 'botocore.data.workmail' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.workmailmessageflow' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.workmailmessageflow' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.workmailmessageflow' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.workmailmessageflow' to be distributed and are already explicitly excluding 'botocore.data.workmailmessageflow' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.workspaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.workspaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.workspaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.workspaces' to be distributed and are already explicitly excluding 'botocore.data.workspaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.xray' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.xray' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.xray' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.xray' to be distributed and are already explicitly excluding 'botocore.data.xray' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) copying botocore/cacert.pem -> build/lib/botocore creating build/lib/botocore/data copying botocore/data/_retry.json -> build/lib/botocore/data copying botocore/data/endpoints.json -> build/lib/botocore/data copying botocore/data/partitions.json -> build/lib/botocore/data copying botocore/data/sdk-default-configuration.json -> build/lib/botocore/data creating build/lib/botocore/data/accessanalyzer creating build/lib/botocore/data/accessanalyzer/2019-11-01 copying botocore/data/accessanalyzer/2019-11-01/endpoint-rule-set-1.json -> build/lib/botocore/data/accessanalyzer/2019-11-01 copying botocore/data/accessanalyzer/2019-11-01/examples-1.json -> build/lib/botocore/data/accessanalyzer/2019-11-01 copying botocore/data/accessanalyzer/2019-11-01/paginators-1.json -> build/lib/botocore/data/accessanalyzer/2019-11-01 copying botocore/data/accessanalyzer/2019-11-01/paginators-1.sdk-extras.json -> build/lib/botocore/data/accessanalyzer/2019-11-01 copying botocore/data/accessanalyzer/2019-11-01/service-2.json -> build/lib/botocore/data/accessanalyzer/2019-11-01 creating build/lib/botocore/data/account creating build/lib/botocore/data/account/2021-02-01 copying botocore/data/account/2021-02-01/endpoint-rule-set-1.json -> build/lib/botocore/data/account/2021-02-01 copying botocore/data/account/2021-02-01/examples-1.json -> build/lib/botocore/data/account/2021-02-01 copying botocore/data/account/2021-02-01/paginators-1.json -> build/lib/botocore/data/account/2021-02-01 copying botocore/data/account/2021-02-01/service-2.json -> build/lib/botocore/data/account/2021-02-01 creating build/lib/botocore/data/acm-pca creating build/lib/botocore/data/acm-pca/2017-08-22 copying botocore/data/acm-pca/2017-08-22/endpoint-rule-set-1.json -> build/lib/botocore/data/acm-pca/2017-08-22 copying botocore/data/acm-pca/2017-08-22/examples-1.json -> build/lib/botocore/data/acm-pca/2017-08-22 copying botocore/data/acm-pca/2017-08-22/paginators-1.json -> build/lib/botocore/data/acm-pca/2017-08-22 copying botocore/data/acm-pca/2017-08-22/service-2.json -> build/lib/botocore/data/acm-pca/2017-08-22 copying botocore/data/acm-pca/2017-08-22/waiters-2.json -> build/lib/botocore/data/acm-pca/2017-08-22 creating build/lib/botocore/data/acm creating build/lib/botocore/data/acm/2015-12-08 copying botocore/data/acm/2015-12-08/endpoint-rule-set-1.json -> build/lib/botocore/data/acm/2015-12-08 copying botocore/data/acm/2015-12-08/examples-1.json -> build/lib/botocore/data/acm/2015-12-08 copying botocore/data/acm/2015-12-08/paginators-1.json -> build/lib/botocore/data/acm/2015-12-08 copying botocore/data/acm/2015-12-08/service-2.json -> build/lib/botocore/data/acm/2015-12-08 copying botocore/data/acm/2015-12-08/waiters-2.json -> build/lib/botocore/data/acm/2015-12-08 creating build/lib/botocore/data/aiops creating build/lib/botocore/data/aiops/2018-05-10 copying botocore/data/aiops/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/aiops/2018-05-10 copying botocore/data/aiops/2018-05-10/paginators-1.json -> build/lib/botocore/data/aiops/2018-05-10 copying botocore/data/aiops/2018-05-10/service-2.json -> build/lib/botocore/data/aiops/2018-05-10 copying botocore/data/aiops/2018-05-10/waiters-2.json -> build/lib/botocore/data/aiops/2018-05-10 creating build/lib/botocore/data/amp creating build/lib/botocore/data/amp/2020-08-01 copying botocore/data/amp/2020-08-01/endpoint-rule-set-1.json -> build/lib/botocore/data/amp/2020-08-01 copying botocore/data/amp/2020-08-01/examples-1.json -> build/lib/botocore/data/amp/2020-08-01 copying botocore/data/amp/2020-08-01/paginators-1.json -> build/lib/botocore/data/amp/2020-08-01 copying botocore/data/amp/2020-08-01/service-2.json -> build/lib/botocore/data/amp/2020-08-01 copying botocore/data/amp/2020-08-01/waiters-2.json -> build/lib/botocore/data/amp/2020-08-01 creating build/lib/botocore/data/amplify creating build/lib/botocore/data/amplify/2017-07-25 copying botocore/data/amplify/2017-07-25/endpoint-rule-set-1.json -> build/lib/botocore/data/amplify/2017-07-25 copying botocore/data/amplify/2017-07-25/examples-1.json -> build/lib/botocore/data/amplify/2017-07-25 copying botocore/data/amplify/2017-07-25/paginators-1.json -> build/lib/botocore/data/amplify/2017-07-25 copying botocore/data/amplify/2017-07-25/service-2.json -> build/lib/botocore/data/amplify/2017-07-25 creating build/lib/botocore/data/amplifybackend creating build/lib/botocore/data/amplifybackend/2020-08-11 copying botocore/data/amplifybackend/2020-08-11/endpoint-rule-set-1.json -> build/lib/botocore/data/amplifybackend/2020-08-11 copying botocore/data/amplifybackend/2020-08-11/paginators-1.json -> build/lib/botocore/data/amplifybackend/2020-08-11 copying botocore/data/amplifybackend/2020-08-11/service-2.json -> build/lib/botocore/data/amplifybackend/2020-08-11 creating build/lib/botocore/data/amplifyuibuilder creating build/lib/botocore/data/amplifyuibuilder/2021-08-11 copying botocore/data/amplifyuibuilder/2021-08-11/endpoint-rule-set-1.json -> build/lib/botocore/data/amplifyuibuilder/2021-08-11 copying botocore/data/amplifyuibuilder/2021-08-11/examples-1.json -> build/lib/botocore/data/amplifyuibuilder/2021-08-11 copying botocore/data/amplifyuibuilder/2021-08-11/paginators-1.json -> build/lib/botocore/data/amplifyuibuilder/2021-08-11 copying botocore/data/amplifyuibuilder/2021-08-11/service-2.json -> build/lib/botocore/data/amplifyuibuilder/2021-08-11 copying botocore/data/amplifyuibuilder/2021-08-11/waiters-2.json -> build/lib/botocore/data/amplifyuibuilder/2021-08-11 creating build/lib/botocore/data/apigateway creating build/lib/botocore/data/apigateway/2015-07-09 copying botocore/data/apigateway/2015-07-09/endpoint-rule-set-1.json -> build/lib/botocore/data/apigateway/2015-07-09 copying botocore/data/apigateway/2015-07-09/examples-1.json -> build/lib/botocore/data/apigateway/2015-07-09 copying botocore/data/apigateway/2015-07-09/paginators-1.json -> build/lib/botocore/data/apigateway/2015-07-09 copying botocore/data/apigateway/2015-07-09/service-2.json -> build/lib/botocore/data/apigateway/2015-07-09 creating build/lib/botocore/data/apigatewaymanagementapi creating build/lib/botocore/data/apigatewaymanagementapi/2018-11-29 copying botocore/data/apigatewaymanagementapi/2018-11-29/endpoint-rule-set-1.json -> build/lib/botocore/data/apigatewaymanagementapi/2018-11-29 copying botocore/data/apigatewaymanagementapi/2018-11-29/paginators-1.json -> build/lib/botocore/data/apigatewaymanagementapi/2018-11-29 copying botocore/data/apigatewaymanagementapi/2018-11-29/service-2.json -> build/lib/botocore/data/apigatewaymanagementapi/2018-11-29 creating build/lib/botocore/data/apigatewayv2 creating build/lib/botocore/data/apigatewayv2/2018-11-29 copying botocore/data/apigatewayv2/2018-11-29/endpoint-rule-set-1.json -> build/lib/botocore/data/apigatewayv2/2018-11-29 copying botocore/data/apigatewayv2/2018-11-29/paginators-1.json -> build/lib/botocore/data/apigatewayv2/2018-11-29 copying botocore/data/apigatewayv2/2018-11-29/service-2.json -> build/lib/botocore/data/apigatewayv2/2018-11-29 creating build/lib/botocore/data/appconfig creating build/lib/botocore/data/appconfig/2019-10-09 copying botocore/data/appconfig/2019-10-09/endpoint-rule-set-1.json -> build/lib/botocore/data/appconfig/2019-10-09 copying botocore/data/appconfig/2019-10-09/examples-1.json -> build/lib/botocore/data/appconfig/2019-10-09 copying botocore/data/appconfig/2019-10-09/paginators-1.json -> build/lib/botocore/data/appconfig/2019-10-09 copying botocore/data/appconfig/2019-10-09/service-2.json -> build/lib/botocore/data/appconfig/2019-10-09 copying botocore/data/appconfig/2019-10-09/waiters-2.json -> build/lib/botocore/data/appconfig/2019-10-09 creating build/lib/botocore/data/appconfigdata creating build/lib/botocore/data/appconfigdata/2021-11-11 copying botocore/data/appconfigdata/2021-11-11/endpoint-rule-set-1.json -> build/lib/botocore/data/appconfigdata/2021-11-11 copying botocore/data/appconfigdata/2021-11-11/examples-1.json -> build/lib/botocore/data/appconfigdata/2021-11-11 copying botocore/data/appconfigdata/2021-11-11/paginators-1.json -> build/lib/botocore/data/appconfigdata/2021-11-11 copying botocore/data/appconfigdata/2021-11-11/service-2.json -> build/lib/botocore/data/appconfigdata/2021-11-11 creating build/lib/botocore/data/appfabric creating build/lib/botocore/data/appfabric/2023-05-19 copying botocore/data/appfabric/2023-05-19/endpoint-rule-set-1.json -> build/lib/botocore/data/appfabric/2023-05-19 copying botocore/data/appfabric/2023-05-19/paginators-1.json -> build/lib/botocore/data/appfabric/2023-05-19 copying botocore/data/appfabric/2023-05-19/service-2.json -> build/lib/botocore/data/appfabric/2023-05-19 copying botocore/data/appfabric/2023-05-19/waiters-2.json -> build/lib/botocore/data/appfabric/2023-05-19 creating build/lib/botocore/data/appflow creating build/lib/botocore/data/appflow/2020-08-23 copying botocore/data/appflow/2020-08-23/endpoint-rule-set-1.json -> build/lib/botocore/data/appflow/2020-08-23 copying botocore/data/appflow/2020-08-23/examples-1.json -> build/lib/botocore/data/appflow/2020-08-23 copying botocore/data/appflow/2020-08-23/paginators-1.json -> build/lib/botocore/data/appflow/2020-08-23 copying botocore/data/appflow/2020-08-23/service-2.json -> build/lib/botocore/data/appflow/2020-08-23 creating build/lib/botocore/data/appintegrations creating build/lib/botocore/data/appintegrations/2020-07-29 copying botocore/data/appintegrations/2020-07-29/endpoint-rule-set-1.json -> build/lib/botocore/data/appintegrations/2020-07-29 copying botocore/data/appintegrations/2020-07-29/examples-1.json -> build/lib/botocore/data/appintegrations/2020-07-29 copying botocore/data/appintegrations/2020-07-29/paginators-1.json -> build/lib/botocore/data/appintegrations/2020-07-29 copying botocore/data/appintegrations/2020-07-29/service-2.json -> build/lib/botocore/data/appintegrations/2020-07-29 creating build/lib/botocore/data/application-autoscaling creating build/lib/botocore/data/application-autoscaling/2016-02-06 copying botocore/data/application-autoscaling/2016-02-06/endpoint-rule-set-1.json -> build/lib/botocore/data/application-autoscaling/2016-02-06 copying botocore/data/application-autoscaling/2016-02-06/examples-1.json -> build/lib/botocore/data/application-autoscaling/2016-02-06 copying botocore/data/application-autoscaling/2016-02-06/paginators-1.json -> build/lib/botocore/data/application-autoscaling/2016-02-06 copying botocore/data/application-autoscaling/2016-02-06/service-2.json -> build/lib/botocore/data/application-autoscaling/2016-02-06 creating build/lib/botocore/data/application-insights creating build/lib/botocore/data/application-insights/2018-11-25 copying botocore/data/application-insights/2018-11-25/endpoint-rule-set-1.json -> build/lib/botocore/data/application-insights/2018-11-25 copying botocore/data/application-insights/2018-11-25/examples-1.json -> build/lib/botocore/data/application-insights/2018-11-25 copying botocore/data/application-insights/2018-11-25/paginators-1.json -> build/lib/botocore/data/application-insights/2018-11-25 copying botocore/data/application-insights/2018-11-25/service-2.json -> build/lib/botocore/data/application-insights/2018-11-25 creating build/lib/botocore/data/application-signals creating build/lib/botocore/data/application-signals/2024-04-15 copying botocore/data/application-signals/2024-04-15/endpoint-rule-set-1.json -> build/lib/botocore/data/application-signals/2024-04-15 copying botocore/data/application-signals/2024-04-15/paginators-1.json -> build/lib/botocore/data/application-signals/2024-04-15 copying botocore/data/application-signals/2024-04-15/paginators-1.sdk-extras.json -> build/lib/botocore/data/application-signals/2024-04-15 copying botocore/data/application-signals/2024-04-15/service-2.json -> build/lib/botocore/data/application-signals/2024-04-15 copying botocore/data/application-signals/2024-04-15/waiters-2.json -> build/lib/botocore/data/application-signals/2024-04-15 creating build/lib/botocore/data/applicationcostprofiler creating build/lib/botocore/data/applicationcostprofiler/2020-09-10 copying botocore/data/applicationcostprofiler/2020-09-10/endpoint-rule-set-1.json -> build/lib/botocore/data/applicationcostprofiler/2020-09-10 copying botocore/data/applicationcostprofiler/2020-09-10/examples-1.json -> build/lib/botocore/data/applicationcostprofiler/2020-09-10 copying botocore/data/applicationcostprofiler/2020-09-10/paginators-1.json -> build/lib/botocore/data/applicationcostprofiler/2020-09-10 copying botocore/data/applicationcostprofiler/2020-09-10/service-2.json -> build/lib/botocore/data/applicationcostprofiler/2020-09-10 creating build/lib/botocore/data/appmesh creating build/lib/botocore/data/appmesh/2018-10-01 copying botocore/data/appmesh/2018-10-01/endpoint-rule-set-1.json -> build/lib/botocore/data/appmesh/2018-10-01 copying botocore/data/appmesh/2018-10-01/examples-1.json -> build/lib/botocore/data/appmesh/2018-10-01 copying botocore/data/appmesh/2018-10-01/paginators-1.json -> build/lib/botocore/data/appmesh/2018-10-01 copying botocore/data/appmesh/2018-10-01/service-2.json -> build/lib/botocore/data/appmesh/2018-10-01 creating build/lib/botocore/data/appmesh/2019-01-25 copying botocore/data/appmesh/2019-01-25/endpoint-rule-set-1.json -> build/lib/botocore/data/appmesh/2019-01-25 copying botocore/data/appmesh/2019-01-25/examples-1.json -> build/lib/botocore/data/appmesh/2019-01-25 copying botocore/data/appmesh/2019-01-25/paginators-1.json -> build/lib/botocore/data/appmesh/2019-01-25 copying botocore/data/appmesh/2019-01-25/service-2.json -> build/lib/botocore/data/appmesh/2019-01-25 creating build/lib/botocore/data/apprunner creating build/lib/botocore/data/apprunner/2020-05-15 copying botocore/data/apprunner/2020-05-15/endpoint-rule-set-1.json -> build/lib/botocore/data/apprunner/2020-05-15 copying botocore/data/apprunner/2020-05-15/examples-1.json -> build/lib/botocore/data/apprunner/2020-05-15 copying botocore/data/apprunner/2020-05-15/paginators-1.json -> build/lib/botocore/data/apprunner/2020-05-15 copying botocore/data/apprunner/2020-05-15/service-2.json -> build/lib/botocore/data/apprunner/2020-05-15 creating build/lib/botocore/data/appstream creating build/lib/botocore/data/appstream/2016-12-01 copying botocore/data/appstream/2016-12-01/endpoint-rule-set-1.json -> build/lib/botocore/data/appstream/2016-12-01 copying botocore/data/appstream/2016-12-01/examples-1.json -> build/lib/botocore/data/appstream/2016-12-01 copying botocore/data/appstream/2016-12-01/paginators-1.json -> build/lib/botocore/data/appstream/2016-12-01 copying botocore/data/appstream/2016-12-01/service-2.json -> build/lib/botocore/data/appstream/2016-12-01 copying botocore/data/appstream/2016-12-01/waiters-2.json -> build/lib/botocore/data/appstream/2016-12-01 creating build/lib/botocore/data/appsync creating build/lib/botocore/data/appsync/2017-07-25 copying botocore/data/appsync/2017-07-25/endpoint-rule-set-1.json -> build/lib/botocore/data/appsync/2017-07-25 copying botocore/data/appsync/2017-07-25/examples-1.json -> build/lib/botocore/data/appsync/2017-07-25 copying botocore/data/appsync/2017-07-25/paginators-1.json -> build/lib/botocore/data/appsync/2017-07-25 copying botocore/data/appsync/2017-07-25/service-2.json -> build/lib/botocore/data/appsync/2017-07-25 creating build/lib/botocore/data/arc-region-switch creating build/lib/botocore/data/arc-region-switch/2022-07-26 copying botocore/data/arc-region-switch/2022-07-26/endpoint-rule-set-1.json -> build/lib/botocore/data/arc-region-switch/2022-07-26 copying botocore/data/arc-region-switch/2022-07-26/paginators-1.json -> build/lib/botocore/data/arc-region-switch/2022-07-26 copying botocore/data/arc-region-switch/2022-07-26/paginators-1.sdk-extras.json -> build/lib/botocore/data/arc-region-switch/2022-07-26 copying botocore/data/arc-region-switch/2022-07-26/service-2.json -> build/lib/botocore/data/arc-region-switch/2022-07-26 copying botocore/data/arc-region-switch/2022-07-26/waiters-2.json -> build/lib/botocore/data/arc-region-switch/2022-07-26 creating build/lib/botocore/data/arc-zonal-shift creating build/lib/botocore/data/arc-zonal-shift/2022-10-30 copying botocore/data/arc-zonal-shift/2022-10-30/endpoint-rule-set-1.json -> build/lib/botocore/data/arc-zonal-shift/2022-10-30 copying botocore/data/arc-zonal-shift/2022-10-30/paginators-1.json -> build/lib/botocore/data/arc-zonal-shift/2022-10-30 copying botocore/data/arc-zonal-shift/2022-10-30/service-2.json -> build/lib/botocore/data/arc-zonal-shift/2022-10-30 copying botocore/data/arc-zonal-shift/2022-10-30/waiters-2.json -> build/lib/botocore/data/arc-zonal-shift/2022-10-30 creating build/lib/botocore/data/artifact creating build/lib/botocore/data/artifact/2018-05-10 copying botocore/data/artifact/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/artifact/2018-05-10 copying botocore/data/artifact/2018-05-10/paginators-1.json -> build/lib/botocore/data/artifact/2018-05-10 copying botocore/data/artifact/2018-05-10/service-2.json -> build/lib/botocore/data/artifact/2018-05-10 copying botocore/data/artifact/2018-05-10/waiters-2.json -> build/lib/botocore/data/artifact/2018-05-10 creating build/lib/botocore/data/athena creating build/lib/botocore/data/athena/2017-05-18 copying botocore/data/athena/2017-05-18/endpoint-rule-set-1.json -> build/lib/botocore/data/athena/2017-05-18 copying botocore/data/athena/2017-05-18/examples-1.json -> build/lib/botocore/data/athena/2017-05-18 copying botocore/data/athena/2017-05-18/paginators-1.json -> build/lib/botocore/data/athena/2017-05-18 copying botocore/data/athena/2017-05-18/service-2.json -> build/lib/botocore/data/athena/2017-05-18 creating build/lib/botocore/data/auditmanager creating build/lib/botocore/data/auditmanager/2017-07-25 copying botocore/data/auditmanager/2017-07-25/endpoint-rule-set-1.json -> build/lib/botocore/data/auditmanager/2017-07-25 copying botocore/data/auditmanager/2017-07-25/examples-1.json -> build/lib/botocore/data/auditmanager/2017-07-25 copying botocore/data/auditmanager/2017-07-25/paginators-1.json -> build/lib/botocore/data/auditmanager/2017-07-25 copying botocore/data/auditmanager/2017-07-25/service-2.json -> build/lib/botocore/data/auditmanager/2017-07-25 creating build/lib/botocore/data/autoscaling-plans creating build/lib/botocore/data/autoscaling-plans/2018-01-06 copying botocore/data/autoscaling-plans/2018-01-06/endpoint-rule-set-1.json -> build/lib/botocore/data/autoscaling-plans/2018-01-06 copying botocore/data/autoscaling-plans/2018-01-06/examples-1.json -> build/lib/botocore/data/autoscaling-plans/2018-01-06 copying botocore/data/autoscaling-plans/2018-01-06/paginators-1.json -> build/lib/botocore/data/autoscaling-plans/2018-01-06 copying botocore/data/autoscaling-plans/2018-01-06/service-2.json -> build/lib/botocore/data/autoscaling-plans/2018-01-06 creating build/lib/botocore/data/autoscaling creating build/lib/botocore/data/autoscaling/2011-01-01 copying botocore/data/autoscaling/2011-01-01/endpoint-rule-set-1.json -> build/lib/botocore/data/autoscaling/2011-01-01 copying botocore/data/autoscaling/2011-01-01/examples-1.json -> build/lib/botocore/data/autoscaling/2011-01-01 copying botocore/data/autoscaling/2011-01-01/paginators-1.json -> build/lib/botocore/data/autoscaling/2011-01-01 copying botocore/data/autoscaling/2011-01-01/paginators-1.sdk-extras.json -> build/lib/botocore/data/autoscaling/2011-01-01 copying botocore/data/autoscaling/2011-01-01/service-2.json -> build/lib/botocore/data/autoscaling/2011-01-01 creating build/lib/botocore/data/b2bi creating build/lib/botocore/data/b2bi/2022-06-23 copying botocore/data/b2bi/2022-06-23/endpoint-rule-set-1.json -> build/lib/botocore/data/b2bi/2022-06-23 copying botocore/data/b2bi/2022-06-23/paginators-1.json -> build/lib/botocore/data/b2bi/2022-06-23 copying botocore/data/b2bi/2022-06-23/service-2.json -> build/lib/botocore/data/b2bi/2022-06-23 copying botocore/data/b2bi/2022-06-23/waiters-2.json -> build/lib/botocore/data/b2bi/2022-06-23 creating build/lib/botocore/data/backup-gateway creating build/lib/botocore/data/backup-gateway/2021-01-01 copying botocore/data/backup-gateway/2021-01-01/endpoint-rule-set-1.json -> build/lib/botocore/data/backup-gateway/2021-01-01 copying botocore/data/backup-gateway/2021-01-01/examples-1.json -> build/lib/botocore/data/backup-gateway/2021-01-01 copying botocore/data/backup-gateway/2021-01-01/paginators-1.json -> build/lib/botocore/data/backup-gateway/2021-01-01 copying botocore/data/backup-gateway/2021-01-01/service-2.json -> build/lib/botocore/data/backup-gateway/2021-01-01 creating build/lib/botocore/data/backup creating build/lib/botocore/data/backup/2018-11-15 copying botocore/data/backup/2018-11-15/endpoint-rule-set-1.json -> build/lib/botocore/data/backup/2018-11-15 copying botocore/data/backup/2018-11-15/examples-1.json -> build/lib/botocore/data/backup/2018-11-15 copying botocore/data/backup/2018-11-15/paginators-1.json -> build/lib/botocore/data/backup/2018-11-15 copying botocore/data/backup/2018-11-15/paginators-1.sdk-extras.json -> build/lib/botocore/data/backup/2018-11-15 copying botocore/data/backup/2018-11-15/service-2.json -> build/lib/botocore/data/backup/2018-11-15 creating build/lib/botocore/data/backupsearch creating build/lib/botocore/data/backupsearch/2018-05-10 copying botocore/data/backupsearch/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/backupsearch/2018-05-10 copying botocore/data/backupsearch/2018-05-10/paginators-1.json -> build/lib/botocore/data/backupsearch/2018-05-10 copying botocore/data/backupsearch/2018-05-10/service-2.json -> build/lib/botocore/data/backupsearch/2018-05-10 copying botocore/data/backupsearch/2018-05-10/waiters-2.json -> build/lib/botocore/data/backupsearch/2018-05-10 creating build/lib/botocore/data/batch creating build/lib/botocore/data/batch/2016-08-10 copying botocore/data/batch/2016-08-10/endpoint-rule-set-1.json -> build/lib/botocore/data/batch/2016-08-10 copying botocore/data/batch/2016-08-10/examples-1.json -> build/lib/botocore/data/batch/2016-08-10 copying botocore/data/batch/2016-08-10/paginators-1.json -> build/lib/botocore/data/batch/2016-08-10 copying botocore/data/batch/2016-08-10/service-2.json -> build/lib/botocore/data/batch/2016-08-10 creating build/lib/botocore/data/bcm-dashboards creating build/lib/botocore/data/bcm-dashboards/2025-08-18 copying botocore/data/bcm-dashboards/2025-08-18/endpoint-rule-set-1.json -> build/lib/botocore/data/bcm-dashboards/2025-08-18 copying botocore/data/bcm-dashboards/2025-08-18/paginators-1.json -> build/lib/botocore/data/bcm-dashboards/2025-08-18 copying botocore/data/bcm-dashboards/2025-08-18/service-2.json -> build/lib/botocore/data/bcm-dashboards/2025-08-18 copying botocore/data/bcm-dashboards/2025-08-18/waiters-2.json -> build/lib/botocore/data/bcm-dashboards/2025-08-18 creating build/lib/botocore/data/bcm-data-exports creating build/lib/botocore/data/bcm-data-exports/2023-11-26 copying botocore/data/bcm-data-exports/2023-11-26/endpoint-rule-set-1.json -> build/lib/botocore/data/bcm-data-exports/2023-11-26 copying botocore/data/bcm-data-exports/2023-11-26/paginators-1.json -> build/lib/botocore/data/bcm-data-exports/2023-11-26 copying botocore/data/bcm-data-exports/2023-11-26/service-2.json -> build/lib/botocore/data/bcm-data-exports/2023-11-26 creating build/lib/botocore/data/bcm-pricing-calculator creating build/lib/botocore/data/bcm-pricing-calculator/2024-06-19 copying botocore/data/bcm-pricing-calculator/2024-06-19/endpoint-rule-set-1.json -> build/lib/botocore/data/bcm-pricing-calculator/2024-06-19 copying botocore/data/bcm-pricing-calculator/2024-06-19/paginators-1.json -> build/lib/botocore/data/bcm-pricing-calculator/2024-06-19 copying botocore/data/bcm-pricing-calculator/2024-06-19/service-2.json -> build/lib/botocore/data/bcm-pricing-calculator/2024-06-19 copying botocore/data/bcm-pricing-calculator/2024-06-19/waiters-2.json -> build/lib/botocore/data/bcm-pricing-calculator/2024-06-19 creating build/lib/botocore/data/bcm-recommended-actions creating build/lib/botocore/data/bcm-recommended-actions/2024-11-14 copying botocore/data/bcm-recommended-actions/2024-11-14/endpoint-rule-set-1.json -> build/lib/botocore/data/bcm-recommended-actions/2024-11-14 copying botocore/data/bcm-recommended-actions/2024-11-14/paginators-1.json -> build/lib/botocore/data/bcm-recommended-actions/2024-11-14 copying botocore/data/bcm-recommended-actions/2024-11-14/service-2.json -> build/lib/botocore/data/bcm-recommended-actions/2024-11-14 copying botocore/data/bcm-recommended-actions/2024-11-14/waiters-2.json -> build/lib/botocore/data/bcm-recommended-actions/2024-11-14 creating build/lib/botocore/data/bedrock-agent-runtime creating build/lib/botocore/data/bedrock-agent-runtime/2023-07-26 copying botocore/data/bedrock-agent-runtime/2023-07-26/endpoint-rule-set-1.json -> build/lib/botocore/data/bedrock-agent-runtime/2023-07-26 copying botocore/data/bedrock-agent-runtime/2023-07-26/paginators-1.json -> build/lib/botocore/data/bedrock-agent-runtime/2023-07-26 copying botocore/data/bedrock-agent-runtime/2023-07-26/paginators-1.sdk-extras.json -> build/lib/botocore/data/bedrock-agent-runtime/2023-07-26 copying botocore/data/bedrock-agent-runtime/2023-07-26/service-2.json -> build/lib/botocore/data/bedrock-agent-runtime/2023-07-26 copying botocore/data/bedrock-agent-runtime/2023-07-26/waiters-2.json -> build/lib/botocore/data/bedrock-agent-runtime/2023-07-26 creating build/lib/botocore/data/bedrock-agent creating build/lib/botocore/data/bedrock-agent/2023-06-05 copying botocore/data/bedrock-agent/2023-06-05/endpoint-rule-set-1.json -> build/lib/botocore/data/bedrock-agent/2023-06-05 copying botocore/data/bedrock-agent/2023-06-05/paginators-1.json -> build/lib/botocore/data/bedrock-agent/2023-06-05 copying botocore/data/bedrock-agent/2023-06-05/service-2.json -> build/lib/botocore/data/bedrock-agent/2023-06-05 copying botocore/data/bedrock-agent/2023-06-05/waiters-2.json -> build/lib/botocore/data/bedrock-agent/2023-06-05 creating build/lib/botocore/data/bedrock-agentcore-control creating build/lib/botocore/data/bedrock-agentcore-control/2023-06-05 copying botocore/data/bedrock-agentcore-control/2023-06-05/endpoint-rule-set-1.json -> build/lib/botocore/data/bedrock-agentcore-control/2023-06-05 copying botocore/data/bedrock-agentcore-control/2023-06-05/paginators-1.json -> build/lib/botocore/data/bedrock-agentcore-control/2023-06-05 copying botocore/data/bedrock-agentcore-control/2023-06-05/service-2.json -> build/lib/botocore/data/bedrock-agentcore-control/2023-06-05 copying botocore/data/bedrock-agentcore-control/2023-06-05/waiters-2.json -> build/lib/botocore/data/bedrock-agentcore-control/2023-06-05 creating build/lib/botocore/data/bedrock-agentcore creating build/lib/botocore/data/bedrock-agentcore/2024-02-28 copying botocore/data/bedrock-agentcore/2024-02-28/endpoint-rule-set-1.json -> build/lib/botocore/data/bedrock-agentcore/2024-02-28 copying botocore/data/bedrock-agentcore/2024-02-28/paginators-1.json -> build/lib/botocore/data/bedrock-agentcore/2024-02-28 copying botocore/data/bedrock-agentcore/2024-02-28/service-2.json -> build/lib/botocore/data/bedrock-agentcore/2024-02-28 copying botocore/data/bedrock-agentcore/2024-02-28/waiters-2.json -> build/lib/botocore/data/bedrock-agentcore/2024-02-28 creating build/lib/botocore/data/bedrock-data-automation-runtime creating build/lib/botocore/data/bedrock-data-automation-runtime/2024-06-13 copying botocore/data/bedrock-data-automation-runtime/2024-06-13/endpoint-rule-set-1.json -> build/lib/botocore/data/bedrock-data-automation-runtime/2024-06-13 copying botocore/data/bedrock-data-automation-runtime/2024-06-13/paginators-1.json -> build/lib/botocore/data/bedrock-data-automation-runtime/2024-06-13 copying botocore/data/bedrock-data-automation-runtime/2024-06-13/service-2.json -> build/lib/botocore/data/bedrock-data-automation-runtime/2024-06-13 creating build/lib/botocore/data/bedrock-data-automation creating build/lib/botocore/data/bedrock-data-automation/2023-07-26 copying botocore/data/bedrock-data-automation/2023-07-26/endpoint-rule-set-1.json -> build/lib/botocore/data/bedrock-data-automation/2023-07-26 copying botocore/data/bedrock-data-automation/2023-07-26/paginators-1.json -> build/lib/botocore/data/bedrock-data-automation/2023-07-26 copying botocore/data/bedrock-data-automation/2023-07-26/service-2.json -> build/lib/botocore/data/bedrock-data-automation/2023-07-26 creating build/lib/botocore/data/bedrock-runtime creating build/lib/botocore/data/bedrock-runtime/2023-09-30 copying botocore/data/bedrock-runtime/2023-09-30/endpoint-rule-set-1.json -> build/lib/botocore/data/bedrock-runtime/2023-09-30 copying botocore/data/bedrock-runtime/2023-09-30/paginators-1.json -> build/lib/botocore/data/bedrock-runtime/2023-09-30 copying botocore/data/bedrock-runtime/2023-09-30/service-2.json -> build/lib/botocore/data/bedrock-runtime/2023-09-30 copying botocore/data/bedrock-runtime/2023-09-30/waiters-2.json -> build/lib/botocore/data/bedrock-runtime/2023-09-30 creating build/lib/botocore/data/bedrock creating build/lib/botocore/data/bedrock/2023-04-20 copying botocore/data/bedrock/2023-04-20/endpoint-rule-set-1.json -> build/lib/botocore/data/bedrock/2023-04-20 copying botocore/data/bedrock/2023-04-20/paginators-1.json -> build/lib/botocore/data/bedrock/2023-04-20 copying botocore/data/bedrock/2023-04-20/service-2.json -> build/lib/botocore/data/bedrock/2023-04-20 copying botocore/data/bedrock/2023-04-20/waiters-2.json -> build/lib/botocore/data/bedrock/2023-04-20 creating build/lib/botocore/data/billing creating build/lib/botocore/data/billing/2023-09-07 copying botocore/data/billing/2023-09-07/endpoint-rule-set-1.json -> build/lib/botocore/data/billing/2023-09-07 copying botocore/data/billing/2023-09-07/paginators-1.json -> build/lib/botocore/data/billing/2023-09-07 copying botocore/data/billing/2023-09-07/service-2.json -> build/lib/botocore/data/billing/2023-09-07 copying botocore/data/billing/2023-09-07/waiters-2.json -> build/lib/botocore/data/billing/2023-09-07 creating build/lib/botocore/data/billingconductor creating build/lib/botocore/data/billingconductor/2021-07-30 copying botocore/data/billingconductor/2021-07-30/endpoint-rule-set-1.json -> build/lib/botocore/data/billingconductor/2021-07-30 copying botocore/data/billingconductor/2021-07-30/examples-1.json -> build/lib/botocore/data/billingconductor/2021-07-30 copying botocore/data/billingconductor/2021-07-30/paginators-1.json -> build/lib/botocore/data/billingconductor/2021-07-30 copying botocore/data/billingconductor/2021-07-30/service-2.json -> build/lib/botocore/data/billingconductor/2021-07-30 copying botocore/data/billingconductor/2021-07-30/waiters-2.json -> build/lib/botocore/data/billingconductor/2021-07-30 creating build/lib/botocore/data/braket creating build/lib/botocore/data/braket/2019-09-01 copying botocore/data/braket/2019-09-01/endpoint-rule-set-1.json -> build/lib/botocore/data/braket/2019-09-01 copying botocore/data/braket/2019-09-01/examples-1.json -> build/lib/botocore/data/braket/2019-09-01 copying botocore/data/braket/2019-09-01/paginators-1.json -> build/lib/botocore/data/braket/2019-09-01 copying botocore/data/braket/2019-09-01/service-2.json -> build/lib/botocore/data/braket/2019-09-01 creating build/lib/botocore/data/budgets creating build/lib/botocore/data/budgets/2016-10-20 copying botocore/data/budgets/2016-10-20/endpoint-rule-set-1.json -> build/lib/botocore/data/budgets/2016-10-20 copying botocore/data/budgets/2016-10-20/examples-1.json -> build/lib/botocore/data/budgets/2016-10-20 copying botocore/data/budgets/2016-10-20/paginators-1.json -> build/lib/botocore/data/budgets/2016-10-20 copying botocore/data/budgets/2016-10-20/service-2.json -> build/lib/botocore/data/budgets/2016-10-20 creating build/lib/botocore/data/ce creating build/lib/botocore/data/ce/2017-10-25 copying botocore/data/ce/2017-10-25/endpoint-rule-set-1.json -> build/lib/botocore/data/ce/2017-10-25 copying botocore/data/ce/2017-10-25/examples-1.json -> build/lib/botocore/data/ce/2017-10-25 copying botocore/data/ce/2017-10-25/paginators-1.json -> build/lib/botocore/data/ce/2017-10-25 copying botocore/data/ce/2017-10-25/paginators-1.sdk-extras.json -> build/lib/botocore/data/ce/2017-10-25 copying botocore/data/ce/2017-10-25/service-2.json -> build/lib/botocore/data/ce/2017-10-25 creating build/lib/botocore/data/chatbot creating build/lib/botocore/data/chatbot/2017-10-11 copying botocore/data/chatbot/2017-10-11/endpoint-rule-set-1.json -> build/lib/botocore/data/chatbot/2017-10-11 copying botocore/data/chatbot/2017-10-11/paginators-1.json -> build/lib/botocore/data/chatbot/2017-10-11 copying botocore/data/chatbot/2017-10-11/service-2.json -> build/lib/botocore/data/chatbot/2017-10-11 creating build/lib/botocore/data/chime-sdk-identity creating build/lib/botocore/data/chime-sdk-identity/2021-04-20 copying botocore/data/chime-sdk-identity/2021-04-20/endpoint-rule-set-1.json -> build/lib/botocore/data/chime-sdk-identity/2021-04-20 copying botocore/data/chime-sdk-identity/2021-04-20/examples-1.json -> build/lib/botocore/data/chime-sdk-identity/2021-04-20 copying botocore/data/chime-sdk-identity/2021-04-20/paginators-1.json -> build/lib/botocore/data/chime-sdk-identity/2021-04-20 copying botocore/data/chime-sdk-identity/2021-04-20/service-2.json -> build/lib/botocore/data/chime-sdk-identity/2021-04-20 creating build/lib/botocore/data/chime-sdk-media-pipelines creating build/lib/botocore/data/chime-sdk-media-pipelines/2021-07-15 copying botocore/data/chime-sdk-media-pipelines/2021-07-15/endpoint-rule-set-1.json -> build/lib/botocore/data/chime-sdk-media-pipelines/2021-07-15 copying botocore/data/chime-sdk-media-pipelines/2021-07-15/paginators-1.json -> build/lib/botocore/data/chime-sdk-media-pipelines/2021-07-15 copying botocore/data/chime-sdk-media-pipelines/2021-07-15/service-2.json -> build/lib/botocore/data/chime-sdk-media-pipelines/2021-07-15 creating build/lib/botocore/data/chime-sdk-meetings creating build/lib/botocore/data/chime-sdk-meetings/2021-07-15 copying botocore/data/chime-sdk-meetings/2021-07-15/endpoint-rule-set-1.json -> build/lib/botocore/data/chime-sdk-meetings/2021-07-15 copying botocore/data/chime-sdk-meetings/2021-07-15/examples-1.json -> build/lib/botocore/data/chime-sdk-meetings/2021-07-15 copying botocore/data/chime-sdk-meetings/2021-07-15/paginators-1.json -> build/lib/botocore/data/chime-sdk-meetings/2021-07-15 copying botocore/data/chime-sdk-meetings/2021-07-15/service-2.json -> build/lib/botocore/data/chime-sdk-meetings/2021-07-15 creating build/lib/botocore/data/chime-sdk-messaging creating build/lib/botocore/data/chime-sdk-messaging/2021-05-15 copying botocore/data/chime-sdk-messaging/2021-05-15/endpoint-rule-set-1.json -> build/lib/botocore/data/chime-sdk-messaging/2021-05-15 copying botocore/data/chime-sdk-messaging/2021-05-15/examples-1.json -> build/lib/botocore/data/chime-sdk-messaging/2021-05-15 copying botocore/data/chime-sdk-messaging/2021-05-15/paginators-1.json -> build/lib/botocore/data/chime-sdk-messaging/2021-05-15 copying botocore/data/chime-sdk-messaging/2021-05-15/service-2.json -> build/lib/botocore/data/chime-sdk-messaging/2021-05-15 creating build/lib/botocore/data/chime-sdk-voice creating build/lib/botocore/data/chime-sdk-voice/2022-08-03 copying botocore/data/chime-sdk-voice/2022-08-03/endpoint-rule-set-1.json -> build/lib/botocore/data/chime-sdk-voice/2022-08-03 copying botocore/data/chime-sdk-voice/2022-08-03/paginators-1.json -> build/lib/botocore/data/chime-sdk-voice/2022-08-03 copying botocore/data/chime-sdk-voice/2022-08-03/service-2.json -> build/lib/botocore/data/chime-sdk-voice/2022-08-03 creating build/lib/botocore/data/chime creating build/lib/botocore/data/chime/2018-05-01 copying botocore/data/chime/2018-05-01/endpoint-rule-set-1.json -> build/lib/botocore/data/chime/2018-05-01 copying botocore/data/chime/2018-05-01/examples-1.json -> build/lib/botocore/data/chime/2018-05-01 copying botocore/data/chime/2018-05-01/paginators-1.json -> build/lib/botocore/data/chime/2018-05-01 copying botocore/data/chime/2018-05-01/service-2.json -> build/lib/botocore/data/chime/2018-05-01 creating build/lib/botocore/data/cleanrooms creating build/lib/botocore/data/cleanrooms/2022-02-17 copying botocore/data/cleanrooms/2022-02-17/endpoint-rule-set-1.json -> build/lib/botocore/data/cleanrooms/2022-02-17 copying botocore/data/cleanrooms/2022-02-17/paginators-1.json -> build/lib/botocore/data/cleanrooms/2022-02-17 copying botocore/data/cleanrooms/2022-02-17/service-2.json -> build/lib/botocore/data/cleanrooms/2022-02-17 copying botocore/data/cleanrooms/2022-02-17/waiters-2.json -> build/lib/botocore/data/cleanrooms/2022-02-17 creating build/lib/botocore/data/cleanroomsml creating build/lib/botocore/data/cleanroomsml/2023-09-06 copying botocore/data/cleanroomsml/2023-09-06/endpoint-rule-set-1.json -> build/lib/botocore/data/cleanroomsml/2023-09-06 copying botocore/data/cleanroomsml/2023-09-06/paginators-1.json -> build/lib/botocore/data/cleanroomsml/2023-09-06 copying botocore/data/cleanroomsml/2023-09-06/service-2.json -> build/lib/botocore/data/cleanroomsml/2023-09-06 copying botocore/data/cleanroomsml/2023-09-06/waiters-2.json -> build/lib/botocore/data/cleanroomsml/2023-09-06 creating build/lib/botocore/data/cloud9 creating build/lib/botocore/data/cloud9/2017-09-23 copying botocore/data/cloud9/2017-09-23/endpoint-rule-set-1.json -> build/lib/botocore/data/cloud9/2017-09-23 copying botocore/data/cloud9/2017-09-23/examples-1.json -> build/lib/botocore/data/cloud9/2017-09-23 copying botocore/data/cloud9/2017-09-23/paginators-1.json -> build/lib/botocore/data/cloud9/2017-09-23 copying botocore/data/cloud9/2017-09-23/service-2.json -> build/lib/botocore/data/cloud9/2017-09-23 creating build/lib/botocore/data/cloudcontrol creating build/lib/botocore/data/cloudcontrol/2021-09-30 copying botocore/data/cloudcontrol/2021-09-30/endpoint-rule-set-1.json -> build/lib/botocore/data/cloudcontrol/2021-09-30 copying botocore/data/cloudcontrol/2021-09-30/examples-1.json -> build/lib/botocore/data/cloudcontrol/2021-09-30 copying botocore/data/cloudcontrol/2021-09-30/paginators-1.json -> build/lib/botocore/data/cloudcontrol/2021-09-30 copying botocore/data/cloudcontrol/2021-09-30/paginators-1.sdk-extras.json -> build/lib/botocore/data/cloudcontrol/2021-09-30 copying botocore/data/cloudcontrol/2021-09-30/service-2.json -> build/lib/botocore/data/cloudcontrol/2021-09-30 copying botocore/data/cloudcontrol/2021-09-30/waiters-2.json -> build/lib/botocore/data/cloudcontrol/2021-09-30 creating build/lib/botocore/data/clouddirectory creating build/lib/botocore/data/clouddirectory/2016-05-10 copying botocore/data/clouddirectory/2016-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/clouddirectory/2016-05-10 copying botocore/data/clouddirectory/2016-05-10/examples-1.json -> build/lib/botocore/data/clouddirectory/2016-05-10 copying botocore/data/clouddirectory/2016-05-10/paginators-1.json -> build/lib/botocore/data/clouddirectory/2016-05-10 copying botocore/data/clouddirectory/2016-05-10/service-2.json -> build/lib/botocore/data/clouddirectory/2016-05-10 creating build/lib/botocore/data/clouddirectory/2017-01-11 copying botocore/data/clouddirectory/2017-01-11/endpoint-rule-set-1.json -> build/lib/botocore/data/clouddirectory/2017-01-11 copying botocore/data/clouddirectory/2017-01-11/examples-1.json -> build/lib/botocore/data/clouddirectory/2017-01-11 copying botocore/data/clouddirectory/2017-01-11/paginators-1.json -> build/lib/botocore/data/clouddirectory/2017-01-11 copying botocore/data/clouddirectory/2017-01-11/service-2.json -> build/lib/botocore/data/clouddirectory/2017-01-11 creating build/lib/botocore/data/cloudformation creating build/lib/botocore/data/cloudformation/2010-05-15 copying botocore/data/cloudformation/2010-05-15/endpoint-rule-set-1.json -> build/lib/botocore/data/cloudformation/2010-05-15 copying botocore/data/cloudformation/2010-05-15/examples-1.json -> build/lib/botocore/data/cloudformation/2010-05-15 copying botocore/data/cloudformation/2010-05-15/paginators-1.json -> build/lib/botocore/data/cloudformation/2010-05-15 copying botocore/data/cloudformation/2010-05-15/service-2.json -> build/lib/botocore/data/cloudformation/2010-05-15 copying botocore/data/cloudformation/2010-05-15/waiters-2.json -> build/lib/botocore/data/cloudformation/2010-05-15 creating build/lib/botocore/data/cloudfront-keyvaluestore creating build/lib/botocore/data/cloudfront-keyvaluestore/2022-07-26 copying botocore/data/cloudfront-keyvaluestore/2022-07-26/endpoint-rule-set-1.json -> build/lib/botocore/data/cloudfront-keyvaluestore/2022-07-26 copying botocore/data/cloudfront-keyvaluestore/2022-07-26/paginators-1.json -> build/lib/botocore/data/cloudfront-keyvaluestore/2022-07-26 copying botocore/data/cloudfront-keyvaluestore/2022-07-26/service-2.json -> build/lib/botocore/data/cloudfront-keyvaluestore/2022-07-26 creating build/lib/botocore/data/cloudfront creating build/lib/botocore/data/cloudfront/2014-05-31 copying botocore/data/cloudfront/2014-05-31/endpoint-rule-set-1.json -> build/lib/botocore/data/cloudfront/2014-05-31 copying botocore/data/cloudfront/2014-05-31/paginators-1.json -> build/lib/botocore/data/cloudfront/2014-05-31 copying botocore/data/cloudfront/2014-05-31/service-2.json -> build/lib/botocore/data/cloudfront/2014-05-31 copying botocore/data/cloudfront/2014-05-31/waiters-2.json -> build/lib/botocore/data/cloudfront/2014-05-31 creating build/lib/botocore/data/cloudfront/2014-10-21 copying botocore/data/cloudfront/2014-10-21/endpoint-rule-set-1.json -> build/lib/botocore/data/cloudfront/2014-10-21 copying botocore/data/cloudfront/2014-10-21/paginators-1.json -> build/lib/botocore/data/cloudfront/2014-10-21 copying botocore/data/cloudfront/2014-10-21/service-2.json -> build/lib/botocore/data/cloudfront/2014-10-21 copying botocore/data/cloudfront/2014-10-21/waiters-2.json -> build/lib/botocore/data/cloudfront/2014-10-21 creating build/lib/botocore/data/cloudfront/2014-11-06 copying botocore/data/cloudfront/2014-11-06/endpoint-rule-set-1.json -> build/lib/botocore/data/cloudfront/2014-11-06 copying botocore/data/cloudfront/2014-11-06/paginators-1.json -> build/lib/botocore/data/cloudfront/2014-11-06 copying botocore/data/cloudfront/2014-11-06/service-2.json -> build/lib/botocore/data/cloudfront/2014-11-06 copying botocore/data/cloudfront/2014-11-06/waiters-2.json -> build/lib/botocore/data/cloudfront/2014-11-06 creating build/lib/botocore/data/cloudfront/2015-04-17 copying botocore/data/cloudfront/2015-04-17/endpoint-rule-set-1.json -> build/lib/botocore/data/cloudfront/2015-04-17 copying botocore/data/cloudfront/2015-04-17/paginators-1.json -> build/lib/botocore/data/cloudfront/2015-04-17 copying botocore/data/cloudfront/2015-04-17/service-2.json -> build/lib/botocore/data/cloudfront/2015-04-17 copying botocore/data/cloudfront/2015-04-17/waiters-2.json -> build/lib/botocore/data/cloudfront/2015-04-17 creating build/lib/botocore/data/cloudfront/2015-07-27 copying botocore/data/cloudfront/2015-07-27/endpoint-rule-set-1.json -> build/lib/botocore/data/cloudfront/2015-07-27 copying botocore/data/cloudfront/2015-07-27/paginators-1.json -> build/lib/botocore/data/cloudfront/2015-07-27 copying botocore/data/cloudfront/2015-07-27/service-2.json -> build/lib/botocore/data/cloudfront/2015-07-27 copying botocore/data/cloudfront/2015-07-27/waiters-2.json -> build/lib/botocore/data/cloudfront/2015-07-27 creating build/lib/botocore/data/cloudfront/2015-09-17 copying botocore/data/cloudfront/2015-09-17/endpoint-rule-set-1.json -> build/lib/botocore/data/cloudfront/2015-09-17 copying botocore/data/cloudfront/2015-09-17/paginators-1.json -> build/lib/botocore/data/cloudfront/2015-09-17 copying botocore/data/cloudfront/2015-09-17/service-2.json -> build/lib/botocore/data/cloudfront/2015-09-17 copying botocore/data/cloudfront/2015-09-17/waiters-2.json -> build/lib/botocore/data/cloudfront/2015-09-17 creating build/lib/botocore/data/cloudfront/2016-01-13 copying botocore/data/cloudfront/2016-01-13/endpoint-rule-set-1.json -> build/lib/botocore/data/cloudfront/2016-01-13 copying botocore/data/cloudfront/2016-01-13/paginators-1.json -> build/lib/botocore/data/cloudfront/2016-01-13 copying botocore/data/cloudfront/2016-01-13/service-2.json -> build/lib/botocore/data/cloudfront/2016-01-13 copying botocore/data/cloudfront/2016-01-13/waiters-2.json -> build/lib/botocore/data/cloudfront/2016-01-13 creating build/lib/botocore/data/cloudfront/2016-01-28 copying botocore/data/cloudfront/2016-01-28/endpoint-rule-set-1.json -> build/lib/botocore/data/cloudfront/2016-01-28 copying botocore/data/cloudfront/2016-01-28/examples-1.json -> build/lib/botocore/data/cloudfront/2016-01-28 copying botocore/data/cloudfront/2016-01-28/paginators-1.json -> build/lib/botocore/data/cloudfront/2016-01-28 copying botocore/data/cloudfront/2016-01-28/service-2.json -> build/lib/botocore/data/cloudfront/2016-01-28 copying botocore/data/cloudfront/2016-01-28/waiters-2.json -> build/lib/botocore/data/cloudfront/2016-01-28 creating build/lib/botocore/data/cloudfront/2016-08-01 copying botocore/data/cloudfront/2016-08-01/endpoint-rule-set-1.json -> build/lib/botocore/data/cloudfront/2016-08-01 copying botocore/data/cloudfront/2016-08-01/examples-1.json -> build/lib/botocore/data/cloudfront/2016-08-01 copying botocore/data/cloudfront/2016-08-01/paginators-1.json -> build/lib/botocore/data/cloudfront/2016-08-01 copying botocore/data/cloudfront/2016-08-01/service-2.json -> build/lib/botocore/data/cloudfront/2016-08-01 copying botocore/data/cloudfront/2016-08-01/waiters-2.json -> build/lib/botocore/data/cloudfront/2016-08-01 creating build/lib/botocore/data/cloudfront/2016-08-20 copying botocore/data/cloudfront/2016-08-20/endpoint-rule-set-1.json -> build/lib/botocore/data/cloudfront/2016-08-20 copying botocore/data/cloudfront/2016-08-20/paginators-1.json -> build/lib/botocore/data/cloudfront/2016-08-20 copying botocore/data/cloudfront/2016-08-20/service-2.json -> build/lib/botocore/data/cloudfront/2016-08-20 copying botocore/data/cloudfront/2016-08-20/waiters-2.json -> build/lib/botocore/data/cloudfront/2016-08-20 creating build/lib/botocore/data/cloudfront/2016-09-07 copying botocore/data/cloudfront/2016-09-07/endpoint-rule-set-1.json -> build/lib/botocore/data/cloudfront/2016-09-07 copying botocore/data/cloudfront/2016-09-07/examples-1.json -> build/lib/botocore/data/cloudfront/2016-09-07 copying botocore/data/cloudfront/2016-09-07/paginators-1.json -> build/lib/botocore/data/cloudfront/2016-09-07 copying botocore/data/cloudfront/2016-09-07/service-2.json -> build/lib/botocore/data/cloudfront/2016-09-07 copying botocore/data/cloudfront/2016-09-07/waiters-2.json -> build/lib/botocore/data/cloudfront/2016-09-07 creating build/lib/botocore/data/cloudfront/2016-09-29 copying botocore/data/cloudfront/2016-09-29/endpoint-rule-set-1.json -> build/lib/botocore/data/cloudfront/2016-09-29 copying botocore/data/cloudfront/2016-09-29/examples-1.json -> build/lib/botocore/data/cloudfront/2016-09-29 copying botocore/data/cloudfront/2016-09-29/paginators-1.json -> build/lib/botocore/data/cloudfront/2016-09-29 copying botocore/data/cloudfront/2016-09-29/service-2.json -> build/lib/botocore/data/cloudfront/2016-09-29 copying botocore/data/cloudfront/2016-09-29/waiters-2.json -> build/lib/botocore/data/cloudfront/2016-09-29 creating build/lib/botocore/data/cloudfront/2016-11-25 copying botocore/data/cloudfront/2016-11-25/endpoint-rule-set-1.json -> build/lib/botocore/data/cloudfront/2016-11-25 copying botocore/data/cloudfront/2016-11-25/examples-1.json -> build/lib/botocore/data/cloudfront/2016-11-25 copying botocore/data/cloudfront/2016-11-25/paginators-1.json -> build/lib/botocore/data/cloudfront/2016-11-25 copying botocore/data/cloudfront/2016-11-25/service-2.json -> build/lib/botocore/data/cloudfront/2016-11-25 copying botocore/data/cloudfront/2016-11-25/waiters-2.json -> build/lib/botocore/data/cloudfront/2016-11-25 creating build/lib/botocore/data/cloudfront/2017-03-25 copying botocore/data/cloudfront/2017-03-25/endpoint-rule-set-1.json -> build/lib/botocore/data/cloudfront/2017-03-25 copying botocore/data/cloudfront/2017-03-25/paginators-1.json -> build/lib/botocore/data/cloudfront/2017-03-25 copying botocore/data/cloudfront/2017-03-25/service-2.json -> build/lib/botocore/data/cloudfront/2017-03-25 copying botocore/data/cloudfront/2017-03-25/waiters-2.json -> build/lib/botocore/data/cloudfront/2017-03-25 creating build/lib/botocore/data/cloudfront/2017-10-30 copying botocore/data/cloudfront/2017-10-30/endpoint-rule-set-1.json -> build/lib/botocore/data/cloudfront/2017-10-30 copying botocore/data/cloudfront/2017-10-30/examples-1.json -> build/lib/botocore/data/cloudfront/2017-10-30 copying botocore/data/cloudfront/2017-10-30/paginators-1.json -> build/lib/botocore/data/cloudfront/2017-10-30 copying botocore/data/cloudfront/2017-10-30/service-2.json -> build/lib/botocore/data/cloudfront/2017-10-30 copying botocore/data/cloudfront/2017-10-30/waiters-2.json -> build/lib/botocore/data/cloudfront/2017-10-30 creating build/lib/botocore/data/cloudfront/2018-06-18 copying botocore/data/cloudfront/2018-06-18/endpoint-rule-set-1.json -> build/lib/botocore/data/cloudfront/2018-06-18 copying botocore/data/cloudfront/2018-06-18/examples-1.json -> build/lib/botocore/data/cloudfront/2018-06-18 copying botocore/data/cloudfront/2018-06-18/paginators-1.json -> build/lib/botocore/data/cloudfront/2018-06-18 copying botocore/data/cloudfront/2018-06-18/service-2.json -> build/lib/botocore/data/cloudfront/2018-06-18 copying botocore/data/cloudfront/2018-06-18/waiters-2.json -> build/lib/botocore/data/cloudfront/2018-06-18 creating build/lib/botocore/data/cloudfront/2018-11-05 copying botocore/data/cloudfront/2018-11-05/endpoint-rule-set-1.json -> build/lib/botocore/data/cloudfront/2018-11-05 copying botocore/data/cloudfront/2018-11-05/examples-1.json -> build/lib/botocore/data/cloudfront/2018-11-05 copying botocore/data/cloudfront/2018-11-05/paginators-1.json -> build/lib/botocore/data/cloudfront/2018-11-05 copying botocore/data/cloudfront/2018-11-05/service-2.json -> build/lib/botocore/data/cloudfront/2018-11-05 copying botocore/data/cloudfront/2018-11-05/waiters-2.json -> build/lib/botocore/data/cloudfront/2018-11-05 creating build/lib/botocore/data/cloudfront/2019-03-26 copying botocore/data/cloudfront/2019-03-26/endpoint-rule-set-1.json -> build/lib/botocore/data/cloudfront/2019-03-26 copying botocore/data/cloudfront/2019-03-26/examples-1.json -> build/lib/botocore/data/cloudfront/2019-03-26 copying botocore/data/cloudfront/2019-03-26/paginators-1.json -> build/lib/botocore/data/cloudfront/2019-03-26 copying botocore/data/cloudfront/2019-03-26/service-2.json -> build/lib/botocore/data/cloudfront/2019-03-26 copying botocore/data/cloudfront/2019-03-26/waiters-2.json -> build/lib/botocore/data/cloudfront/2019-03-26 creating build/lib/botocore/data/cloudfront/2020-05-31 copying botocore/data/cloudfront/2020-05-31/endpoint-rule-set-1.json -> build/lib/botocore/data/cloudfront/2020-05-31 copying botocore/data/cloudfront/2020-05-31/examples-1.json -> build/lib/botocore/data/cloudfront/2020-05-31 copying botocore/data/cloudfront/2020-05-31/paginators-1.json -> build/lib/botocore/data/cloudfront/2020-05-31 copying botocore/data/cloudfront/2020-05-31/service-2.json -> build/lib/botocore/data/cloudfront/2020-05-31 copying botocore/data/cloudfront/2020-05-31/waiters-2.json -> build/lib/botocore/data/cloudfront/2020-05-31 creating build/lib/botocore/data/cloudhsm creating build/lib/botocore/data/cloudhsm/2014-05-30 copying botocore/data/cloudhsm/2014-05-30/endpoint-rule-set-1.json -> build/lib/botocore/data/cloudhsm/2014-05-30 copying botocore/data/cloudhsm/2014-05-30/examples-1.json -> build/lib/botocore/data/cloudhsm/2014-05-30 copying botocore/data/cloudhsm/2014-05-30/paginators-1.json -> build/lib/botocore/data/cloudhsm/2014-05-30 copying botocore/data/cloudhsm/2014-05-30/service-2.json -> build/lib/botocore/data/cloudhsm/2014-05-30 creating build/lib/botocore/data/cloudhsmv2 creating build/lib/botocore/data/cloudhsmv2/2017-04-28 copying botocore/data/cloudhsmv2/2017-04-28/endpoint-rule-set-1.json -> build/lib/botocore/data/cloudhsmv2/2017-04-28 copying botocore/data/cloudhsmv2/2017-04-28/examples-1.json -> build/lib/botocore/data/cloudhsmv2/2017-04-28 copying botocore/data/cloudhsmv2/2017-04-28/paginators-1.json -> build/lib/botocore/data/cloudhsmv2/2017-04-28 copying botocore/data/cloudhsmv2/2017-04-28/service-2.json -> build/lib/botocore/data/cloudhsmv2/2017-04-28 creating build/lib/botocore/data/cloudsearch creating build/lib/botocore/data/cloudsearch/2011-02-01 copying botocore/data/cloudsearch/2011-02-01/endpoint-rule-set-1.json -> build/lib/botocore/data/cloudsearch/2011-02-01 copying botocore/data/cloudsearch/2011-02-01/service-2.json -> build/lib/botocore/data/cloudsearch/2011-02-01 creating build/lib/botocore/data/cloudsearch/2013-01-01 copying botocore/data/cloudsearch/2013-01-01/endpoint-rule-set-1.json -> build/lib/botocore/data/cloudsearch/2013-01-01 copying botocore/data/cloudsearch/2013-01-01/examples-1.json -> build/lib/botocore/data/cloudsearch/2013-01-01 copying botocore/data/cloudsearch/2013-01-01/paginators-1.json -> build/lib/botocore/data/cloudsearch/2013-01-01 copying botocore/data/cloudsearch/2013-01-01/service-2.json -> build/lib/botocore/data/cloudsearch/2013-01-01 creating build/lib/botocore/data/cloudsearchdomain creating build/lib/botocore/data/cloudsearchdomain/2013-01-01 copying botocore/data/cloudsearchdomain/2013-01-01/endpoint-rule-set-1.json -> build/lib/botocore/data/cloudsearchdomain/2013-01-01 copying botocore/data/cloudsearchdomain/2013-01-01/examples-1.json -> build/lib/botocore/data/cloudsearchdomain/2013-01-01 copying botocore/data/cloudsearchdomain/2013-01-01/paginators-1.json -> build/lib/botocore/data/cloudsearchdomain/2013-01-01 copying botocore/data/cloudsearchdomain/2013-01-01/service-2.json -> build/lib/botocore/data/cloudsearchdomain/2013-01-01 creating build/lib/botocore/data/cloudtrail-data creating build/lib/botocore/data/cloudtrail-data/2021-08-11 copying botocore/data/cloudtrail-data/2021-08-11/endpoint-rule-set-1.json -> build/lib/botocore/data/cloudtrail-data/2021-08-11 copying botocore/data/cloudtrail-data/2021-08-11/paginators-1.json -> build/lib/botocore/data/cloudtrail-data/2021-08-11 copying botocore/data/cloudtrail-data/2021-08-11/service-2.json -> build/lib/botocore/data/cloudtrail-data/2021-08-11 creating build/lib/botocore/data/cloudtrail creating build/lib/botocore/data/cloudtrail/2013-11-01 copying botocore/data/cloudtrail/2013-11-01/endpoint-rule-set-1.json -> build/lib/botocore/data/cloudtrail/2013-11-01 copying botocore/data/cloudtrail/2013-11-01/examples-1.json -> build/lib/botocore/data/cloudtrail/2013-11-01 copying botocore/data/cloudtrail/2013-11-01/paginators-1.json -> build/lib/botocore/data/cloudtrail/2013-11-01 copying botocore/data/cloudtrail/2013-11-01/service-2.json -> build/lib/botocore/data/cloudtrail/2013-11-01 creating build/lib/botocore/data/cloudwatch creating build/lib/botocore/data/cloudwatch/2010-08-01 copying botocore/data/cloudwatch/2010-08-01/endpoint-rule-set-1.json -> build/lib/botocore/data/cloudwatch/2010-08-01 copying botocore/data/cloudwatch/2010-08-01/examples-1.json -> build/lib/botocore/data/cloudwatch/2010-08-01 copying botocore/data/cloudwatch/2010-08-01/paginators-1.json -> build/lib/botocore/data/cloudwatch/2010-08-01 copying botocore/data/cloudwatch/2010-08-01/service-2.json -> build/lib/botocore/data/cloudwatch/2010-08-01 copying botocore/data/cloudwatch/2010-08-01/waiters-2.json -> build/lib/botocore/data/cloudwatch/2010-08-01 creating build/lib/botocore/data/codeartifact creating build/lib/botocore/data/codeartifact/2018-09-22 copying botocore/data/codeartifact/2018-09-22/endpoint-rule-set-1.json -> build/lib/botocore/data/codeartifact/2018-09-22 copying botocore/data/codeartifact/2018-09-22/examples-1.json -> build/lib/botocore/data/codeartifact/2018-09-22 copying botocore/data/codeartifact/2018-09-22/paginators-1.json -> build/lib/botocore/data/codeartifact/2018-09-22 copying botocore/data/codeartifact/2018-09-22/paginators-1.sdk-extras.json -> build/lib/botocore/data/codeartifact/2018-09-22 copying botocore/data/codeartifact/2018-09-22/service-2.json -> build/lib/botocore/data/codeartifact/2018-09-22 creating build/lib/botocore/data/codebuild creating build/lib/botocore/data/codebuild/2016-10-06 copying botocore/data/codebuild/2016-10-06/endpoint-rule-set-1.json -> build/lib/botocore/data/codebuild/2016-10-06 copying botocore/data/codebuild/2016-10-06/examples-1.json -> build/lib/botocore/data/codebuild/2016-10-06 copying botocore/data/codebuild/2016-10-06/paginators-1.json -> build/lib/botocore/data/codebuild/2016-10-06 copying botocore/data/codebuild/2016-10-06/service-2.json -> build/lib/botocore/data/codebuild/2016-10-06 creating build/lib/botocore/data/codecatalyst creating build/lib/botocore/data/codecatalyst/2022-09-28 copying botocore/data/codecatalyst/2022-09-28/endpoint-rule-set-1.json -> build/lib/botocore/data/codecatalyst/2022-09-28 copying botocore/data/codecatalyst/2022-09-28/paginators-1.json -> build/lib/botocore/data/codecatalyst/2022-09-28 copying botocore/data/codecatalyst/2022-09-28/service-2.json -> build/lib/botocore/data/codecatalyst/2022-09-28 copying botocore/data/codecatalyst/2022-09-28/waiters-2.json -> build/lib/botocore/data/codecatalyst/2022-09-28 creating build/lib/botocore/data/codecommit creating build/lib/botocore/data/codecommit/2015-04-13 copying botocore/data/codecommit/2015-04-13/endpoint-rule-set-1.json -> build/lib/botocore/data/codecommit/2015-04-13 copying botocore/data/codecommit/2015-04-13/examples-1.json -> build/lib/botocore/data/codecommit/2015-04-13 copying botocore/data/codecommit/2015-04-13/paginators-1.json -> build/lib/botocore/data/codecommit/2015-04-13 copying botocore/data/codecommit/2015-04-13/service-2.json -> build/lib/botocore/data/codecommit/2015-04-13 creating build/lib/botocore/data/codeconnections creating build/lib/botocore/data/codeconnections/2023-12-01 copying botocore/data/codeconnections/2023-12-01/endpoint-rule-set-1.json -> build/lib/botocore/data/codeconnections/2023-12-01 copying botocore/data/codeconnections/2023-12-01/paginators-1.json -> build/lib/botocore/data/codeconnections/2023-12-01 copying botocore/data/codeconnections/2023-12-01/service-2.json -> build/lib/botocore/data/codeconnections/2023-12-01 creating build/lib/botocore/data/codedeploy creating build/lib/botocore/data/codedeploy/2014-10-06 copying botocore/data/codedeploy/2014-10-06/endpoint-rule-set-1.json -> build/lib/botocore/data/codedeploy/2014-10-06 copying botocore/data/codedeploy/2014-10-06/examples-1.json -> build/lib/botocore/data/codedeploy/2014-10-06 copying botocore/data/codedeploy/2014-10-06/paginators-1.json -> build/lib/botocore/data/codedeploy/2014-10-06 copying botocore/data/codedeploy/2014-10-06/service-2.json -> build/lib/botocore/data/codedeploy/2014-10-06 copying botocore/data/codedeploy/2014-10-06/waiters-2.json -> build/lib/botocore/data/codedeploy/2014-10-06 creating build/lib/botocore/data/codeguru-reviewer creating build/lib/botocore/data/codeguru-reviewer/2019-09-19 copying botocore/data/codeguru-reviewer/2019-09-19/endpoint-rule-set-1.json -> build/lib/botocore/data/codeguru-reviewer/2019-09-19 copying botocore/data/codeguru-reviewer/2019-09-19/examples-1.json -> build/lib/botocore/data/codeguru-reviewer/2019-09-19 copying botocore/data/codeguru-reviewer/2019-09-19/paginators-1.json -> build/lib/botocore/data/codeguru-reviewer/2019-09-19 copying botocore/data/codeguru-reviewer/2019-09-19/service-2.json -> build/lib/botocore/data/codeguru-reviewer/2019-09-19 copying botocore/data/codeguru-reviewer/2019-09-19/waiters-2.json -> build/lib/botocore/data/codeguru-reviewer/2019-09-19 creating build/lib/botocore/data/codeguru-security creating build/lib/botocore/data/codeguru-security/2018-05-10 copying botocore/data/codeguru-security/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/codeguru-security/2018-05-10 copying botocore/data/codeguru-security/2018-05-10/paginators-1.json -> build/lib/botocore/data/codeguru-security/2018-05-10 copying botocore/data/codeguru-security/2018-05-10/service-2.json -> build/lib/botocore/data/codeguru-security/2018-05-10 copying botocore/data/codeguru-security/2018-05-10/waiters-2.json -> build/lib/botocore/data/codeguru-security/2018-05-10 creating build/lib/botocore/data/codeguruprofiler creating build/lib/botocore/data/codeguruprofiler/2019-07-18 copying botocore/data/codeguruprofiler/2019-07-18/endpoint-rule-set-1.json -> build/lib/botocore/data/codeguruprofiler/2019-07-18 copying botocore/data/codeguruprofiler/2019-07-18/examples-1.json -> build/lib/botocore/data/codeguruprofiler/2019-07-18 copying botocore/data/codeguruprofiler/2019-07-18/paginators-1.json -> build/lib/botocore/data/codeguruprofiler/2019-07-18 copying botocore/data/codeguruprofiler/2019-07-18/service-2.json -> build/lib/botocore/data/codeguruprofiler/2019-07-18 creating build/lib/botocore/data/codepipeline creating build/lib/botocore/data/codepipeline/2015-07-09 copying botocore/data/codepipeline/2015-07-09/endpoint-rule-set-1.json -> build/lib/botocore/data/codepipeline/2015-07-09 copying botocore/data/codepipeline/2015-07-09/examples-1.json -> build/lib/botocore/data/codepipeline/2015-07-09 copying botocore/data/codepipeline/2015-07-09/paginators-1.json -> build/lib/botocore/data/codepipeline/2015-07-09 copying botocore/data/codepipeline/2015-07-09/service-2.json -> build/lib/botocore/data/codepipeline/2015-07-09 creating build/lib/botocore/data/codestar-connections creating build/lib/botocore/data/codestar-connections/2019-12-01 copying botocore/data/codestar-connections/2019-12-01/endpoint-rule-set-1.json -> build/lib/botocore/data/codestar-connections/2019-12-01 copying botocore/data/codestar-connections/2019-12-01/examples-1.json -> build/lib/botocore/data/codestar-connections/2019-12-01 copying botocore/data/codestar-connections/2019-12-01/paginators-1.json -> build/lib/botocore/data/codestar-connections/2019-12-01 copying botocore/data/codestar-connections/2019-12-01/service-2.json -> build/lib/botocore/data/codestar-connections/2019-12-01 creating build/lib/botocore/data/codestar-notifications creating build/lib/botocore/data/codestar-notifications/2019-10-15 copying botocore/data/codestar-notifications/2019-10-15/endpoint-rule-set-1.json -> build/lib/botocore/data/codestar-notifications/2019-10-15 copying botocore/data/codestar-notifications/2019-10-15/examples-1.json -> build/lib/botocore/data/codestar-notifications/2019-10-15 copying botocore/data/codestar-notifications/2019-10-15/paginators-1.json -> build/lib/botocore/data/codestar-notifications/2019-10-15 copying botocore/data/codestar-notifications/2019-10-15/service-2.json -> build/lib/botocore/data/codestar-notifications/2019-10-15 creating build/lib/botocore/data/cognito-identity creating build/lib/botocore/data/cognito-identity/2014-06-30 copying botocore/data/cognito-identity/2014-06-30/endpoint-rule-set-1.json -> build/lib/botocore/data/cognito-identity/2014-06-30 copying botocore/data/cognito-identity/2014-06-30/examples-1.json -> build/lib/botocore/data/cognito-identity/2014-06-30 copying botocore/data/cognito-identity/2014-06-30/paginators-1.json -> build/lib/botocore/data/cognito-identity/2014-06-30 copying botocore/data/cognito-identity/2014-06-30/service-2.json -> build/lib/botocore/data/cognito-identity/2014-06-30 creating build/lib/botocore/data/cognito-idp creating build/lib/botocore/data/cognito-idp/2016-04-18 copying botocore/data/cognito-idp/2016-04-18/endpoint-rule-set-1.json -> build/lib/botocore/data/cognito-idp/2016-04-18 copying botocore/data/cognito-idp/2016-04-18/examples-1.json -> build/lib/botocore/data/cognito-idp/2016-04-18 copying botocore/data/cognito-idp/2016-04-18/paginators-1.json -> build/lib/botocore/data/cognito-idp/2016-04-18 copying botocore/data/cognito-idp/2016-04-18/service-2.json -> build/lib/botocore/data/cognito-idp/2016-04-18 creating build/lib/botocore/data/cognito-sync creating build/lib/botocore/data/cognito-sync/2014-06-30 copying botocore/data/cognito-sync/2014-06-30/endpoint-rule-set-1.json -> build/lib/botocore/data/cognito-sync/2014-06-30 copying botocore/data/cognito-sync/2014-06-30/examples-1.json -> build/lib/botocore/data/cognito-sync/2014-06-30 copying botocore/data/cognito-sync/2014-06-30/paginators-1.json -> build/lib/botocore/data/cognito-sync/2014-06-30 copying botocore/data/cognito-sync/2014-06-30/service-2.json -> build/lib/botocore/data/cognito-sync/2014-06-30 creating build/lib/botocore/data/comprehend creating build/lib/botocore/data/comprehend/2017-11-27 copying botocore/data/comprehend/2017-11-27/endpoint-rule-set-1.json -> build/lib/botocore/data/comprehend/2017-11-27 copying botocore/data/comprehend/2017-11-27/examples-1.json -> build/lib/botocore/data/comprehend/2017-11-27 copying botocore/data/comprehend/2017-11-27/paginators-1.json -> build/lib/botocore/data/comprehend/2017-11-27 copying botocore/data/comprehend/2017-11-27/service-2.json -> build/lib/botocore/data/comprehend/2017-11-27 creating build/lib/botocore/data/comprehendmedical creating build/lib/botocore/data/comprehendmedical/2018-10-30 copying botocore/data/comprehendmedical/2018-10-30/endpoint-rule-set-1.json -> build/lib/botocore/data/comprehendmedical/2018-10-30 copying botocore/data/comprehendmedical/2018-10-30/examples-1.json -> build/lib/botocore/data/comprehendmedical/2018-10-30 copying botocore/data/comprehendmedical/2018-10-30/paginators-1.json -> build/lib/botocore/data/comprehendmedical/2018-10-30 copying botocore/data/comprehendmedical/2018-10-30/service-2.json -> build/lib/botocore/data/comprehendmedical/2018-10-30 creating build/lib/botocore/data/compute-optimizer-automation creating build/lib/botocore/data/compute-optimizer-automation/2025-09-22 copying botocore/data/compute-optimizer-automation/2025-09-22/endpoint-rule-set-1.json -> build/lib/botocore/data/compute-optimizer-automation/2025-09-22 copying botocore/data/compute-optimizer-automation/2025-09-22/paginators-1.json -> build/lib/botocore/data/compute-optimizer-automation/2025-09-22 copying botocore/data/compute-optimizer-automation/2025-09-22/service-2.json -> build/lib/botocore/data/compute-optimizer-automation/2025-09-22 copying botocore/data/compute-optimizer-automation/2025-09-22/waiters-2.json -> build/lib/botocore/data/compute-optimizer-automation/2025-09-22 creating build/lib/botocore/data/compute-optimizer creating build/lib/botocore/data/compute-optimizer/2019-11-01 copying botocore/data/compute-optimizer/2019-11-01/endpoint-rule-set-1.json -> build/lib/botocore/data/compute-optimizer/2019-11-01 copying botocore/data/compute-optimizer/2019-11-01/examples-1.json -> build/lib/botocore/data/compute-optimizer/2019-11-01 copying botocore/data/compute-optimizer/2019-11-01/paginators-1.json -> build/lib/botocore/data/compute-optimizer/2019-11-01 copying botocore/data/compute-optimizer/2019-11-01/service-2.json -> build/lib/botocore/data/compute-optimizer/2019-11-01 creating build/lib/botocore/data/config creating build/lib/botocore/data/config/2014-11-12 copying botocore/data/config/2014-11-12/endpoint-rule-set-1.json -> build/lib/botocore/data/config/2014-11-12 copying botocore/data/config/2014-11-12/examples-1.json -> build/lib/botocore/data/config/2014-11-12 copying botocore/data/config/2014-11-12/paginators-1.json -> build/lib/botocore/data/config/2014-11-12 copying botocore/data/config/2014-11-12/service-2.json -> build/lib/botocore/data/config/2014-11-12 creating build/lib/botocore/data/connect-contact-lens creating build/lib/botocore/data/connect-contact-lens/2020-08-21 copying botocore/data/connect-contact-lens/2020-08-21/endpoint-rule-set-1.json -> build/lib/botocore/data/connect-contact-lens/2020-08-21 copying botocore/data/connect-contact-lens/2020-08-21/examples-1.json -> build/lib/botocore/data/connect-contact-lens/2020-08-21 copying botocore/data/connect-contact-lens/2020-08-21/paginators-1.json -> build/lib/botocore/data/connect-contact-lens/2020-08-21 copying botocore/data/connect-contact-lens/2020-08-21/service-2.json -> build/lib/botocore/data/connect-contact-lens/2020-08-21 creating build/lib/botocore/data/connect creating build/lib/botocore/data/connect/2017-08-08 copying botocore/data/connect/2017-08-08/endpoint-rule-set-1.json -> build/lib/botocore/data/connect/2017-08-08 copying botocore/data/connect/2017-08-08/examples-1.json -> build/lib/botocore/data/connect/2017-08-08 copying botocore/data/connect/2017-08-08/paginators-1.json -> build/lib/botocore/data/connect/2017-08-08 copying botocore/data/connect/2017-08-08/service-2.json -> build/lib/botocore/data/connect/2017-08-08 creating build/lib/botocore/data/connectcampaigns creating build/lib/botocore/data/connectcampaigns/2021-01-30 copying botocore/data/connectcampaigns/2021-01-30/endpoint-rule-set-1.json -> build/lib/botocore/data/connectcampaigns/2021-01-30 copying botocore/data/connectcampaigns/2021-01-30/paginators-1.json -> build/lib/botocore/data/connectcampaigns/2021-01-30 copying botocore/data/connectcampaigns/2021-01-30/service-2.json -> build/lib/botocore/data/connectcampaigns/2021-01-30 creating build/lib/botocore/data/connectcampaignsv2 creating build/lib/botocore/data/connectcampaignsv2/2024-04-23 copying botocore/data/connectcampaignsv2/2024-04-23/endpoint-rule-set-1.json -> build/lib/botocore/data/connectcampaignsv2/2024-04-23 copying botocore/data/connectcampaignsv2/2024-04-23/paginators-1.json -> build/lib/botocore/data/connectcampaignsv2/2024-04-23 copying botocore/data/connectcampaignsv2/2024-04-23/service-2.json -> build/lib/botocore/data/connectcampaignsv2/2024-04-23 creating build/lib/botocore/data/connectcases creating build/lib/botocore/data/connectcases/2022-10-03 copying botocore/data/connectcases/2022-10-03/endpoint-rule-set-1.json -> build/lib/botocore/data/connectcases/2022-10-03 copying botocore/data/connectcases/2022-10-03/paginators-1.json -> build/lib/botocore/data/connectcases/2022-10-03 copying botocore/data/connectcases/2022-10-03/paginators-1.sdk-extras.json -> build/lib/botocore/data/connectcases/2022-10-03 copying botocore/data/connectcases/2022-10-03/service-2.json -> build/lib/botocore/data/connectcases/2022-10-03 copying botocore/data/connectcases/2022-10-03/waiters-2.json -> build/lib/botocore/data/connectcases/2022-10-03 creating build/lib/botocore/data/connecthealth creating build/lib/botocore/data/connecthealth/2025-01-29 copying botocore/data/connecthealth/2025-01-29/endpoint-rule-set-1.json -> build/lib/botocore/data/connecthealth/2025-01-29 copying botocore/data/connecthealth/2025-01-29/paginators-1.json -> build/lib/botocore/data/connecthealth/2025-01-29 copying botocore/data/connecthealth/2025-01-29/service-2.json -> build/lib/botocore/data/connecthealth/2025-01-29 copying botocore/data/connecthealth/2025-01-29/waiters-2.json -> build/lib/botocore/data/connecthealth/2025-01-29 creating build/lib/botocore/data/connectparticipant creating build/lib/botocore/data/connectparticipant/2018-09-07 copying botocore/data/connectparticipant/2018-09-07/endpoint-rule-set-1.json -> build/lib/botocore/data/connectparticipant/2018-09-07 copying botocore/data/connectparticipant/2018-09-07/examples-1.json -> build/lib/botocore/data/connectparticipant/2018-09-07 copying botocore/data/connectparticipant/2018-09-07/paginators-1.json -> build/lib/botocore/data/connectparticipant/2018-09-07 copying botocore/data/connectparticipant/2018-09-07/service-2.json -> build/lib/botocore/data/connectparticipant/2018-09-07 creating build/lib/botocore/data/controlcatalog creating build/lib/botocore/data/controlcatalog/2018-05-10 copying botocore/data/controlcatalog/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/controlcatalog/2018-05-10 copying botocore/data/controlcatalog/2018-05-10/paginators-1.json -> build/lib/botocore/data/controlcatalog/2018-05-10 copying botocore/data/controlcatalog/2018-05-10/service-2.json -> build/lib/botocore/data/controlcatalog/2018-05-10 copying botocore/data/controlcatalog/2018-05-10/waiters-2.json -> build/lib/botocore/data/controlcatalog/2018-05-10 creating build/lib/botocore/data/controltower creating build/lib/botocore/data/controltower/2018-05-10 copying botocore/data/controltower/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/controltower/2018-05-10 copying botocore/data/controltower/2018-05-10/paginators-1.json -> build/lib/botocore/data/controltower/2018-05-10 copying botocore/data/controltower/2018-05-10/service-2.json -> build/lib/botocore/data/controltower/2018-05-10 copying botocore/data/controltower/2018-05-10/waiters-2.json -> build/lib/botocore/data/controltower/2018-05-10 creating build/lib/botocore/data/cost-optimization-hub creating build/lib/botocore/data/cost-optimization-hub/2022-07-26 copying botocore/data/cost-optimization-hub/2022-07-26/endpoint-rule-set-1.json -> build/lib/botocore/data/cost-optimization-hub/2022-07-26 copying botocore/data/cost-optimization-hub/2022-07-26/paginators-1.json -> build/lib/botocore/data/cost-optimization-hub/2022-07-26 copying botocore/data/cost-optimization-hub/2022-07-26/paginators-1.sdk-extras.json -> build/lib/botocore/data/cost-optimization-hub/2022-07-26 copying botocore/data/cost-optimization-hub/2022-07-26/service-2.json -> build/lib/botocore/data/cost-optimization-hub/2022-07-26 copying botocore/data/cost-optimization-hub/2022-07-26/waiters-2.json -> build/lib/botocore/data/cost-optimization-hub/2022-07-26 creating build/lib/botocore/data/cur creating build/lib/botocore/data/cur/2017-01-06 copying botocore/data/cur/2017-01-06/endpoint-rule-set-1.json -> build/lib/botocore/data/cur/2017-01-06 copying botocore/data/cur/2017-01-06/examples-1.json -> build/lib/botocore/data/cur/2017-01-06 copying botocore/data/cur/2017-01-06/paginators-1.json -> build/lib/botocore/data/cur/2017-01-06 copying botocore/data/cur/2017-01-06/service-2.json -> build/lib/botocore/data/cur/2017-01-06 creating build/lib/botocore/data/customer-profiles creating build/lib/botocore/data/customer-profiles/2020-08-15 copying botocore/data/customer-profiles/2020-08-15/endpoint-rule-set-1.json -> build/lib/botocore/data/customer-profiles/2020-08-15 copying botocore/data/customer-profiles/2020-08-15/examples-1.json -> build/lib/botocore/data/customer-profiles/2020-08-15 copying botocore/data/customer-profiles/2020-08-15/paginators-1.json -> build/lib/botocore/data/customer-profiles/2020-08-15 copying botocore/data/customer-profiles/2020-08-15/paginators-1.sdk-extras.json -> build/lib/botocore/data/customer-profiles/2020-08-15 copying botocore/data/customer-profiles/2020-08-15/service-2.json -> build/lib/botocore/data/customer-profiles/2020-08-15 creating build/lib/botocore/data/databrew creating build/lib/botocore/data/databrew/2017-07-25 copying botocore/data/databrew/2017-07-25/endpoint-rule-set-1.json -> build/lib/botocore/data/databrew/2017-07-25 copying botocore/data/databrew/2017-07-25/examples-1.json -> build/lib/botocore/data/databrew/2017-07-25 copying botocore/data/databrew/2017-07-25/paginators-1.json -> build/lib/botocore/data/databrew/2017-07-25 copying botocore/data/databrew/2017-07-25/service-2.json -> build/lib/botocore/data/databrew/2017-07-25 creating build/lib/botocore/data/dataexchange creating build/lib/botocore/data/dataexchange/2017-07-25 copying botocore/data/dataexchange/2017-07-25/endpoint-rule-set-1.json -> build/lib/botocore/data/dataexchange/2017-07-25 copying botocore/data/dataexchange/2017-07-25/paginators-1.json -> build/lib/botocore/data/dataexchange/2017-07-25 copying botocore/data/dataexchange/2017-07-25/service-2.json -> build/lib/botocore/data/dataexchange/2017-07-25 copying botocore/data/dataexchange/2017-07-25/waiters-2.json -> build/lib/botocore/data/dataexchange/2017-07-25 creating build/lib/botocore/data/datapipeline creating build/lib/botocore/data/datapipeline/2012-10-29 copying botocore/data/datapipeline/2012-10-29/endpoint-rule-set-1.json -> build/lib/botocore/data/datapipeline/2012-10-29 copying botocore/data/datapipeline/2012-10-29/examples-1.json -> build/lib/botocore/data/datapipeline/2012-10-29 copying botocore/data/datapipeline/2012-10-29/paginators-1.json -> build/lib/botocore/data/datapipeline/2012-10-29 copying botocore/data/datapipeline/2012-10-29/service-2.json -> build/lib/botocore/data/datapipeline/2012-10-29 creating build/lib/botocore/data/datasync creating build/lib/botocore/data/datasync/2018-11-09 copying botocore/data/datasync/2018-11-09/endpoint-rule-set-1.json -> build/lib/botocore/data/datasync/2018-11-09 copying botocore/data/datasync/2018-11-09/examples-1.json -> build/lib/botocore/data/datasync/2018-11-09 copying botocore/data/datasync/2018-11-09/paginators-1.json -> build/lib/botocore/data/datasync/2018-11-09 copying botocore/data/datasync/2018-11-09/service-2.json -> build/lib/botocore/data/datasync/2018-11-09 creating build/lib/botocore/data/datazone creating build/lib/botocore/data/datazone/2018-05-10 copying botocore/data/datazone/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/datazone/2018-05-10 copying botocore/data/datazone/2018-05-10/paginators-1.json -> build/lib/botocore/data/datazone/2018-05-10 copying botocore/data/datazone/2018-05-10/paginators-1.sdk-extras.json -> build/lib/botocore/data/datazone/2018-05-10 copying botocore/data/datazone/2018-05-10/service-2.json -> build/lib/botocore/data/datazone/2018-05-10 copying botocore/data/datazone/2018-05-10/waiters-2.json -> build/lib/botocore/data/datazone/2018-05-10 creating build/lib/botocore/data/dax creating build/lib/botocore/data/dax/2017-04-19 copying botocore/data/dax/2017-04-19/endpoint-rule-set-1.json -> build/lib/botocore/data/dax/2017-04-19 copying botocore/data/dax/2017-04-19/examples-1.json -> build/lib/botocore/data/dax/2017-04-19 copying botocore/data/dax/2017-04-19/paginators-1.json -> build/lib/botocore/data/dax/2017-04-19 copying botocore/data/dax/2017-04-19/service-2.json -> build/lib/botocore/data/dax/2017-04-19 creating build/lib/botocore/data/deadline creating build/lib/botocore/data/deadline/2023-10-12 copying botocore/data/deadline/2023-10-12/endpoint-rule-set-1.json -> build/lib/botocore/data/deadline/2023-10-12 copying botocore/data/deadline/2023-10-12/paginators-1.json -> build/lib/botocore/data/deadline/2023-10-12 copying botocore/data/deadline/2023-10-12/paginators-1.sdk-extras.json -> build/lib/botocore/data/deadline/2023-10-12 copying botocore/data/deadline/2023-10-12/service-2.json -> build/lib/botocore/data/deadline/2023-10-12 copying botocore/data/deadline/2023-10-12/waiters-2.json -> build/lib/botocore/data/deadline/2023-10-12 creating build/lib/botocore/data/detective creating build/lib/botocore/data/detective/2018-10-26 copying botocore/data/detective/2018-10-26/endpoint-rule-set-1.json -> build/lib/botocore/data/detective/2018-10-26 copying botocore/data/detective/2018-10-26/examples-1.json -> build/lib/botocore/data/detective/2018-10-26 copying botocore/data/detective/2018-10-26/paginators-1.json -> build/lib/botocore/data/detective/2018-10-26 copying botocore/data/detective/2018-10-26/service-2.json -> build/lib/botocore/data/detective/2018-10-26 creating build/lib/botocore/data/devicefarm creating build/lib/botocore/data/devicefarm/2015-06-23 copying botocore/data/devicefarm/2015-06-23/endpoint-rule-set-1.json -> build/lib/botocore/data/devicefarm/2015-06-23 copying botocore/data/devicefarm/2015-06-23/examples-1.json -> build/lib/botocore/data/devicefarm/2015-06-23 copying botocore/data/devicefarm/2015-06-23/paginators-1.json -> build/lib/botocore/data/devicefarm/2015-06-23 copying botocore/data/devicefarm/2015-06-23/service-2.json -> build/lib/botocore/data/devicefarm/2015-06-23 creating build/lib/botocore/data/devops-agent creating build/lib/botocore/data/devops-agent/2026-01-01 copying botocore/data/devops-agent/2026-01-01/endpoint-rule-set-1.json -> build/lib/botocore/data/devops-agent/2026-01-01 copying botocore/data/devops-agent/2026-01-01/paginators-1.json -> build/lib/botocore/data/devops-agent/2026-01-01 copying botocore/data/devops-agent/2026-01-01/service-2.json -> build/lib/botocore/data/devops-agent/2026-01-01 creating build/lib/botocore/data/devops-guru creating build/lib/botocore/data/devops-guru/2020-12-01 copying botocore/data/devops-guru/2020-12-01/endpoint-rule-set-1.json -> build/lib/botocore/data/devops-guru/2020-12-01 copying botocore/data/devops-guru/2020-12-01/examples-1.json -> build/lib/botocore/data/devops-guru/2020-12-01 copying botocore/data/devops-guru/2020-12-01/paginators-1.json -> build/lib/botocore/data/devops-guru/2020-12-01 copying botocore/data/devops-guru/2020-12-01/service-2.json -> build/lib/botocore/data/devops-guru/2020-12-01 creating build/lib/botocore/data/directconnect creating build/lib/botocore/data/directconnect/2012-10-25 copying botocore/data/directconnect/2012-10-25/endpoint-rule-set-1.json -> build/lib/botocore/data/directconnect/2012-10-25 copying botocore/data/directconnect/2012-10-25/examples-1.json -> build/lib/botocore/data/directconnect/2012-10-25 copying botocore/data/directconnect/2012-10-25/paginators-1.json -> build/lib/botocore/data/directconnect/2012-10-25 copying botocore/data/directconnect/2012-10-25/service-2.json -> build/lib/botocore/data/directconnect/2012-10-25 creating build/lib/botocore/data/discovery creating build/lib/botocore/data/discovery/2015-11-01 copying botocore/data/discovery/2015-11-01/endpoint-rule-set-1.json -> build/lib/botocore/data/discovery/2015-11-01 copying botocore/data/discovery/2015-11-01/examples-1.json -> build/lib/botocore/data/discovery/2015-11-01 copying botocore/data/discovery/2015-11-01/paginators-1.json -> build/lib/botocore/data/discovery/2015-11-01 copying botocore/data/discovery/2015-11-01/service-2.json -> build/lib/botocore/data/discovery/2015-11-01 creating build/lib/botocore/data/dlm creating build/lib/botocore/data/dlm/2018-01-12 copying botocore/data/dlm/2018-01-12/endpoint-rule-set-1.json -> build/lib/botocore/data/dlm/2018-01-12 copying botocore/data/dlm/2018-01-12/examples-1.json -> build/lib/botocore/data/dlm/2018-01-12 copying botocore/data/dlm/2018-01-12/paginators-1.json -> build/lib/botocore/data/dlm/2018-01-12 copying botocore/data/dlm/2018-01-12/service-2.json -> build/lib/botocore/data/dlm/2018-01-12 creating build/lib/botocore/data/dms creating build/lib/botocore/data/dms/2016-01-01 copying botocore/data/dms/2016-01-01/endpoint-rule-set-1.json -> build/lib/botocore/data/dms/2016-01-01 copying botocore/data/dms/2016-01-01/examples-1.json -> build/lib/botocore/data/dms/2016-01-01 copying botocore/data/dms/2016-01-01/paginators-1.json -> build/lib/botocore/data/dms/2016-01-01 copying botocore/data/dms/2016-01-01/service-2.json -> build/lib/botocore/data/dms/2016-01-01 copying botocore/data/dms/2016-01-01/waiters-2.json -> build/lib/botocore/data/dms/2016-01-01 creating build/lib/botocore/data/docdb-elastic creating build/lib/botocore/data/docdb-elastic/2022-11-28 copying botocore/data/docdb-elastic/2022-11-28/endpoint-rule-set-1.json -> build/lib/botocore/data/docdb-elastic/2022-11-28 copying botocore/data/docdb-elastic/2022-11-28/paginators-1.json -> build/lib/botocore/data/docdb-elastic/2022-11-28 copying botocore/data/docdb-elastic/2022-11-28/service-2.json -> build/lib/botocore/data/docdb-elastic/2022-11-28 creating build/lib/botocore/data/docdb creating build/lib/botocore/data/docdb/2014-10-31 copying botocore/data/docdb/2014-10-31/endpoint-rule-set-1.json -> build/lib/botocore/data/docdb/2014-10-31 copying botocore/data/docdb/2014-10-31/examples-1.json -> build/lib/botocore/data/docdb/2014-10-31 copying botocore/data/docdb/2014-10-31/paginators-1.json -> build/lib/botocore/data/docdb/2014-10-31 copying botocore/data/docdb/2014-10-31/service-2.json -> build/lib/botocore/data/docdb/2014-10-31 copying botocore/data/docdb/2014-10-31/service-2.sdk-extras.json -> build/lib/botocore/data/docdb/2014-10-31 copying botocore/data/docdb/2014-10-31/waiters-2.json -> build/lib/botocore/data/docdb/2014-10-31 creating build/lib/botocore/data/drs creating build/lib/botocore/data/drs/2020-02-26 copying botocore/data/drs/2020-02-26/endpoint-rule-set-1.json -> build/lib/botocore/data/drs/2020-02-26 copying botocore/data/drs/2020-02-26/examples-1.json -> build/lib/botocore/data/drs/2020-02-26 copying botocore/data/drs/2020-02-26/paginators-1.json -> build/lib/botocore/data/drs/2020-02-26 copying botocore/data/drs/2020-02-26/service-2.json -> build/lib/botocore/data/drs/2020-02-26 creating build/lib/botocore/data/ds-data creating build/lib/botocore/data/ds-data/2023-05-31 copying botocore/data/ds-data/2023-05-31/endpoint-rule-set-1.json -> build/lib/botocore/data/ds-data/2023-05-31 copying botocore/data/ds-data/2023-05-31/paginators-1.json -> build/lib/botocore/data/ds-data/2023-05-31 copying botocore/data/ds-data/2023-05-31/paginators-1.sdk-extras.json -> build/lib/botocore/data/ds-data/2023-05-31 copying botocore/data/ds-data/2023-05-31/service-2.json -> build/lib/botocore/data/ds-data/2023-05-31 creating build/lib/botocore/data/ds creating build/lib/botocore/data/ds/2015-04-16 copying botocore/data/ds/2015-04-16/endpoint-rule-set-1.json -> build/lib/botocore/data/ds/2015-04-16 copying botocore/data/ds/2015-04-16/examples-1.json -> build/lib/botocore/data/ds/2015-04-16 copying botocore/data/ds/2015-04-16/paginators-1.json -> build/lib/botocore/data/ds/2015-04-16 copying botocore/data/ds/2015-04-16/service-2.json -> build/lib/botocore/data/ds/2015-04-16 copying botocore/data/ds/2015-04-16/waiters-2.json -> build/lib/botocore/data/ds/2015-04-16 creating build/lib/botocore/data/dsql creating build/lib/botocore/data/dsql/2018-05-10 copying botocore/data/dsql/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/dsql/2018-05-10 copying botocore/data/dsql/2018-05-10/paginators-1.json -> build/lib/botocore/data/dsql/2018-05-10 copying botocore/data/dsql/2018-05-10/service-2.json -> build/lib/botocore/data/dsql/2018-05-10 copying botocore/data/dsql/2018-05-10/waiters-2.json -> build/lib/botocore/data/dsql/2018-05-10 creating build/lib/botocore/data/dynamodb creating build/lib/botocore/data/dynamodb/2011-12-05 copying botocore/data/dynamodb/2011-12-05/endpoint-rule-set-1.json -> build/lib/botocore/data/dynamodb/2011-12-05 copying botocore/data/dynamodb/2011-12-05/examples-1.json -> build/lib/botocore/data/dynamodb/2011-12-05 creating build/lib/botocore/data/dynamodb/2012-08-10 copying botocore/data/dynamodb/2012-08-10/endpoint-rule-set-1.json -> build/lib/botocore/data/dynamodb/2012-08-10 copying botocore/data/dynamodb/2012-08-10/examples-1.json -> build/lib/botocore/data/dynamodb/2012-08-10 copying botocore/data/dynamodb/2012-08-10/paginators-1.json -> build/lib/botocore/data/dynamodb/2012-08-10 copying botocore/data/dynamodb/2012-08-10/service-2.json -> build/lib/botocore/data/dynamodb/2012-08-10 copying botocore/data/dynamodb/2012-08-10/waiters-2.json -> build/lib/botocore/data/dynamodb/2012-08-10 creating build/lib/botocore/data/dynamodbstreams creating build/lib/botocore/data/dynamodbstreams/2012-08-10 copying botocore/data/dynamodbstreams/2012-08-10/endpoint-rule-set-1.json -> build/lib/botocore/data/dynamodbstreams/2012-08-10 copying botocore/data/dynamodbstreams/2012-08-10/examples-1.json -> build/lib/botocore/data/dynamodbstreams/2012-08-10 copying botocore/data/dynamodbstreams/2012-08-10/paginators-1.json -> build/lib/botocore/data/dynamodbstreams/2012-08-10 copying botocore/data/dynamodbstreams/2012-08-10/service-2.json -> build/lib/botocore/data/dynamodbstreams/2012-08-10 creating build/lib/botocore/data/ebs creating build/lib/botocore/data/ebs/2019-11-02 copying botocore/data/ebs/2019-11-02/endpoint-rule-set-1.json -> build/lib/botocore/data/ebs/2019-11-02 copying botocore/data/ebs/2019-11-02/examples-1.json -> build/lib/botocore/data/ebs/2019-11-02 copying botocore/data/ebs/2019-11-02/paginators-1.json -> build/lib/botocore/data/ebs/2019-11-02 copying botocore/data/ebs/2019-11-02/service-2.json -> build/lib/botocore/data/ebs/2019-11-02 creating build/lib/botocore/data/ec2-instance-connect creating build/lib/botocore/data/ec2-instance-connect/2018-04-02 copying botocore/data/ec2-instance-connect/2018-04-02/endpoint-rule-set-1.json -> build/lib/botocore/data/ec2-instance-connect/2018-04-02 copying botocore/data/ec2-instance-connect/2018-04-02/examples-1.json -> build/lib/botocore/data/ec2-instance-connect/2018-04-02 copying botocore/data/ec2-instance-connect/2018-04-02/paginators-1.json -> build/lib/botocore/data/ec2-instance-connect/2018-04-02 copying botocore/data/ec2-instance-connect/2018-04-02/service-2.json -> build/lib/botocore/data/ec2-instance-connect/2018-04-02 creating build/lib/botocore/data/ec2 creating build/lib/botocore/data/ec2/2014-09-01 copying botocore/data/ec2/2014-09-01/endpoint-rule-set-1.json -> build/lib/botocore/data/ec2/2014-09-01 copying botocore/data/ec2/2014-09-01/paginators-1.json -> build/lib/botocore/data/ec2/2014-09-01 copying botocore/data/ec2/2014-09-01/service-2.json -> build/lib/botocore/data/ec2/2014-09-01 copying botocore/data/ec2/2014-09-01/waiters-2.json -> build/lib/botocore/data/ec2/2014-09-01 creating build/lib/botocore/data/ec2/2014-10-01 copying botocore/data/ec2/2014-10-01/endpoint-rule-set-1.json -> build/lib/botocore/data/ec2/2014-10-01 copying botocore/data/ec2/2014-10-01/paginators-1.json -> build/lib/botocore/data/ec2/2014-10-01 copying botocore/data/ec2/2014-10-01/service-2.json -> build/lib/botocore/data/ec2/2014-10-01 copying botocore/data/ec2/2014-10-01/waiters-2.json -> build/lib/botocore/data/ec2/2014-10-01 creating build/lib/botocore/data/ec2/2015-03-01 copying botocore/data/ec2/2015-03-01/endpoint-rule-set-1.json -> build/lib/botocore/data/ec2/2015-03-01 copying botocore/data/ec2/2015-03-01/paginators-1.json -> build/lib/botocore/data/ec2/2015-03-01 copying botocore/data/ec2/2015-03-01/service-2.json -> build/lib/botocore/data/ec2/2015-03-01 copying botocore/data/ec2/2015-03-01/waiters-2.json -> build/lib/botocore/data/ec2/2015-03-01 creating build/lib/botocore/data/ec2/2015-04-15 copying botocore/data/ec2/2015-04-15/endpoint-rule-set-1.json -> build/lib/botocore/data/ec2/2015-04-15 copying botocore/data/ec2/2015-04-15/paginators-1.json -> build/lib/botocore/data/ec2/2015-04-15 copying botocore/data/ec2/2015-04-15/service-2.json -> build/lib/botocore/data/ec2/2015-04-15 copying botocore/data/ec2/2015-04-15/waiters-2.json -> build/lib/botocore/data/ec2/2015-04-15 creating build/lib/botocore/data/ec2/2015-10-01 copying botocore/data/ec2/2015-10-01/endpoint-rule-set-1.json -> build/lib/botocore/data/ec2/2015-10-01 copying botocore/data/ec2/2015-10-01/examples-1.json -> build/lib/botocore/data/ec2/2015-10-01 copying botocore/data/ec2/2015-10-01/paginators-1.json -> build/lib/botocore/data/ec2/2015-10-01 copying botocore/data/ec2/2015-10-01/service-2.json -> build/lib/botocore/data/ec2/2015-10-01 copying botocore/data/ec2/2015-10-01/waiters-2.json -> build/lib/botocore/data/ec2/2015-10-01 creating build/lib/botocore/data/ec2/2016-04-01 copying botocore/data/ec2/2016-04-01/endpoint-rule-set-1.json -> build/lib/botocore/data/ec2/2016-04-01 copying botocore/data/ec2/2016-04-01/examples-1.json -> build/lib/botocore/data/ec2/2016-04-01 copying botocore/data/ec2/2016-04-01/paginators-1.json -> build/lib/botocore/data/ec2/2016-04-01 copying botocore/data/ec2/2016-04-01/service-2.json -> build/lib/botocore/data/ec2/2016-04-01 copying botocore/data/ec2/2016-04-01/waiters-2.json -> build/lib/botocore/data/ec2/2016-04-01 creating build/lib/botocore/data/ec2/2016-09-15 copying botocore/data/ec2/2016-09-15/endpoint-rule-set-1.json -> build/lib/botocore/data/ec2/2016-09-15 copying botocore/data/ec2/2016-09-15/examples-1.json -> build/lib/botocore/data/ec2/2016-09-15 copying botocore/data/ec2/2016-09-15/paginators-1.json -> build/lib/botocore/data/ec2/2016-09-15 copying botocore/data/ec2/2016-09-15/service-2.json -> build/lib/botocore/data/ec2/2016-09-15 copying botocore/data/ec2/2016-09-15/waiters-2.json -> build/lib/botocore/data/ec2/2016-09-15 creating build/lib/botocore/data/ec2/2016-11-15 copying botocore/data/ec2/2016-11-15/endpoint-rule-set-1.json -> build/lib/botocore/data/ec2/2016-11-15 copying botocore/data/ec2/2016-11-15/examples-1.json -> build/lib/botocore/data/ec2/2016-11-15 copying botocore/data/ec2/2016-11-15/paginators-1.json -> build/lib/botocore/data/ec2/2016-11-15 copying botocore/data/ec2/2016-11-15/paginators-1.sdk-extras.json -> build/lib/botocore/data/ec2/2016-11-15 copying botocore/data/ec2/2016-11-15/service-2.json -> build/lib/botocore/data/ec2/2016-11-15 copying botocore/data/ec2/2016-11-15/waiters-2.json -> build/lib/botocore/data/ec2/2016-11-15 creating build/lib/botocore/data/ecr-public creating build/lib/botocore/data/ecr-public/2020-10-30 copying botocore/data/ecr-public/2020-10-30/endpoint-rule-set-1.json -> build/lib/botocore/data/ecr-public/2020-10-30 copying botocore/data/ecr-public/2020-10-30/examples-1.json -> build/lib/botocore/data/ecr-public/2020-10-30 copying botocore/data/ecr-public/2020-10-30/paginators-1.json -> build/lib/botocore/data/ecr-public/2020-10-30 copying botocore/data/ecr-public/2020-10-30/service-2.json -> build/lib/botocore/data/ecr-public/2020-10-30 creating build/lib/botocore/data/ecr creating build/lib/botocore/data/ecr/2015-09-21 copying botocore/data/ecr/2015-09-21/endpoint-rule-set-1.json -> build/lib/botocore/data/ecr/2015-09-21 copying botocore/data/ecr/2015-09-21/examples-1.json -> build/lib/botocore/data/ecr/2015-09-21 copying botocore/data/ecr/2015-09-21/paginators-1.json -> build/lib/botocore/data/ecr/2015-09-21 copying botocore/data/ecr/2015-09-21/service-2.json -> build/lib/botocore/data/ecr/2015-09-21 copying botocore/data/ecr/2015-09-21/waiters-2.json -> build/lib/botocore/data/ecr/2015-09-21 creating build/lib/botocore/data/ecs creating build/lib/botocore/data/ecs/2014-11-13 copying botocore/data/ecs/2014-11-13/endpoint-rule-set-1.json -> build/lib/botocore/data/ecs/2014-11-13 copying botocore/data/ecs/2014-11-13/examples-1.json -> build/lib/botocore/data/ecs/2014-11-13 copying botocore/data/ecs/2014-11-13/paginators-1.json -> build/lib/botocore/data/ecs/2014-11-13 copying botocore/data/ecs/2014-11-13/service-2.json -> build/lib/botocore/data/ecs/2014-11-13 copying botocore/data/ecs/2014-11-13/waiters-2.json -> build/lib/botocore/data/ecs/2014-11-13 creating build/lib/botocore/data/efs creating build/lib/botocore/data/efs/2015-02-01 copying botocore/data/efs/2015-02-01/endpoint-rule-set-1.json -> build/lib/botocore/data/efs/2015-02-01 copying botocore/data/efs/2015-02-01/examples-1.json -> build/lib/botocore/data/efs/2015-02-01 copying botocore/data/efs/2015-02-01/paginators-1.json -> build/lib/botocore/data/efs/2015-02-01 copying botocore/data/efs/2015-02-01/service-2.json -> build/lib/botocore/data/efs/2015-02-01 creating build/lib/botocore/data/eks-auth creating build/lib/botocore/data/eks-auth/2023-11-26 copying botocore/data/eks-auth/2023-11-26/endpoint-rule-set-1.json -> build/lib/botocore/data/eks-auth/2023-11-26 copying botocore/data/eks-auth/2023-11-26/paginators-1.json -> build/lib/botocore/data/eks-auth/2023-11-26 copying botocore/data/eks-auth/2023-11-26/service-2.json -> build/lib/botocore/data/eks-auth/2023-11-26 copying botocore/data/eks-auth/2023-11-26/waiters-2.json -> build/lib/botocore/data/eks-auth/2023-11-26 creating build/lib/botocore/data/eks creating build/lib/botocore/data/eks/2017-11-01 copying botocore/data/eks/2017-11-01/endpoint-rule-set-1.json -> build/lib/botocore/data/eks/2017-11-01 copying botocore/data/eks/2017-11-01/examples-1.json -> build/lib/botocore/data/eks/2017-11-01 copying botocore/data/eks/2017-11-01/paginators-1.json -> build/lib/botocore/data/eks/2017-11-01 copying botocore/data/eks/2017-11-01/service-2.json -> build/lib/botocore/data/eks/2017-11-01 copying botocore/data/eks/2017-11-01/service-2.sdk-extras.json -> build/lib/botocore/data/eks/2017-11-01 copying botocore/data/eks/2017-11-01/waiters-2.json -> build/lib/botocore/data/eks/2017-11-01 creating build/lib/botocore/data/elasticache creating build/lib/botocore/data/elasticache/2014-09-30 copying botocore/data/elasticache/2014-09-30/endpoint-rule-set-1.json -> build/lib/botocore/data/elasticache/2014-09-30 copying botocore/data/elasticache/2014-09-30/paginators-1.json -> build/lib/botocore/data/elasticache/2014-09-30 copying botocore/data/elasticache/2014-09-30/service-2.json -> build/lib/botocore/data/elasticache/2014-09-30 copying botocore/data/elasticache/2014-09-30/waiters-2.json -> build/lib/botocore/data/elasticache/2014-09-30 creating build/lib/botocore/data/elasticache/2015-02-02 copying botocore/data/elasticache/2015-02-02/endpoint-rule-set-1.json -> build/lib/botocore/data/elasticache/2015-02-02 copying botocore/data/elasticache/2015-02-02/examples-1.json -> build/lib/botocore/data/elasticache/2015-02-02 copying botocore/data/elasticache/2015-02-02/paginators-1.json -> build/lib/botocore/data/elasticache/2015-02-02 copying botocore/data/elasticache/2015-02-02/service-2.json -> build/lib/botocore/data/elasticache/2015-02-02 copying botocore/data/elasticache/2015-02-02/waiters-2.json -> build/lib/botocore/data/elasticache/2015-02-02 creating build/lib/botocore/data/elasticbeanstalk creating build/lib/botocore/data/elasticbeanstalk/2010-12-01 copying botocore/data/elasticbeanstalk/2010-12-01/endpoint-rule-set-1.json -> build/lib/botocore/data/elasticbeanstalk/2010-12-01 copying botocore/data/elasticbeanstalk/2010-12-01/examples-1.json -> build/lib/botocore/data/elasticbeanstalk/2010-12-01 copying botocore/data/elasticbeanstalk/2010-12-01/paginators-1.json -> build/lib/botocore/data/elasticbeanstalk/2010-12-01 copying botocore/data/elasticbeanstalk/2010-12-01/service-2.json -> build/lib/botocore/data/elasticbeanstalk/2010-12-01 copying botocore/data/elasticbeanstalk/2010-12-01/waiters-2.json -> build/lib/botocore/data/elasticbeanstalk/2010-12-01 creating build/lib/botocore/data/elb creating build/lib/botocore/data/elb/2012-06-01 copying botocore/data/elb/2012-06-01/endpoint-rule-set-1.json -> build/lib/botocore/data/elb/2012-06-01 copying botocore/data/elb/2012-06-01/examples-1.json -> build/lib/botocore/data/elb/2012-06-01 copying botocore/data/elb/2012-06-01/paginators-1.json -> build/lib/botocore/data/elb/2012-06-01 copying botocore/data/elb/2012-06-01/service-2.json -> build/lib/botocore/data/elb/2012-06-01 copying botocore/data/elb/2012-06-01/waiters-2.json -> build/lib/botocore/data/elb/2012-06-01 creating build/lib/botocore/data/elbv2 creating build/lib/botocore/data/elbv2/2015-12-01 copying botocore/data/elbv2/2015-12-01/endpoint-rule-set-1.json -> build/lib/botocore/data/elbv2/2015-12-01 copying botocore/data/elbv2/2015-12-01/examples-1.json -> build/lib/botocore/data/elbv2/2015-12-01 copying botocore/data/elbv2/2015-12-01/paginators-1.json -> build/lib/botocore/data/elbv2/2015-12-01 copying botocore/data/elbv2/2015-12-01/service-2.json -> build/lib/botocore/data/elbv2/2015-12-01 copying botocore/data/elbv2/2015-12-01/waiters-2.json -> build/lib/botocore/data/elbv2/2015-12-01 creating build/lib/botocore/data/elementalinference creating build/lib/botocore/data/elementalinference/2018-11-14 copying botocore/data/elementalinference/2018-11-14/endpoint-rule-set-1.json -> build/lib/botocore/data/elementalinference/2018-11-14 copying botocore/data/elementalinference/2018-11-14/paginators-1.json -> build/lib/botocore/data/elementalinference/2018-11-14 copying botocore/data/elementalinference/2018-11-14/service-2.json -> build/lib/botocore/data/elementalinference/2018-11-14 copying botocore/data/elementalinference/2018-11-14/waiters-2.json -> build/lib/botocore/data/elementalinference/2018-11-14 creating build/lib/botocore/data/emr-containers creating build/lib/botocore/data/emr-containers/2020-10-01 copying botocore/data/emr-containers/2020-10-01/endpoint-rule-set-1.json -> build/lib/botocore/data/emr-containers/2020-10-01 copying botocore/data/emr-containers/2020-10-01/examples-1.json -> build/lib/botocore/data/emr-containers/2020-10-01 copying botocore/data/emr-containers/2020-10-01/paginators-1.json -> build/lib/botocore/data/emr-containers/2020-10-01 copying botocore/data/emr-containers/2020-10-01/service-2.json -> build/lib/botocore/data/emr-containers/2020-10-01 creating build/lib/botocore/data/emr-serverless creating build/lib/botocore/data/emr-serverless/2021-07-13 copying botocore/data/emr-serverless/2021-07-13/endpoint-rule-set-1.json -> build/lib/botocore/data/emr-serverless/2021-07-13 copying botocore/data/emr-serverless/2021-07-13/paginators-1.json -> build/lib/botocore/data/emr-serverless/2021-07-13 copying botocore/data/emr-serverless/2021-07-13/service-2.json -> build/lib/botocore/data/emr-serverless/2021-07-13 creating build/lib/botocore/data/emr creating build/lib/botocore/data/emr/2009-03-31 copying botocore/data/emr/2009-03-31/endpoint-rule-set-1.json -> build/lib/botocore/data/emr/2009-03-31 copying botocore/data/emr/2009-03-31/examples-1.json -> build/lib/botocore/data/emr/2009-03-31 copying botocore/data/emr/2009-03-31/paginators-1.json -> build/lib/botocore/data/emr/2009-03-31 copying botocore/data/emr/2009-03-31/service-2.json -> build/lib/botocore/data/emr/2009-03-31 copying botocore/data/emr/2009-03-31/waiters-2.json -> build/lib/botocore/data/emr/2009-03-31 creating build/lib/botocore/data/entityresolution creating build/lib/botocore/data/entityresolution/2018-05-10 copying botocore/data/entityresolution/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/entityresolution/2018-05-10 copying botocore/data/entityresolution/2018-05-10/paginators-1.json -> build/lib/botocore/data/entityresolution/2018-05-10 copying botocore/data/entityresolution/2018-05-10/service-2.json -> build/lib/botocore/data/entityresolution/2018-05-10 creating build/lib/botocore/data/es creating build/lib/botocore/data/es/2015-01-01 copying botocore/data/es/2015-01-01/endpoint-rule-set-1.json -> build/lib/botocore/data/es/2015-01-01 copying botocore/data/es/2015-01-01/examples-1.json -> build/lib/botocore/data/es/2015-01-01 copying botocore/data/es/2015-01-01/paginators-1.json -> build/lib/botocore/data/es/2015-01-01 copying botocore/data/es/2015-01-01/service-2.json -> build/lib/botocore/data/es/2015-01-01 creating build/lib/botocore/data/events creating build/lib/botocore/data/events/2014-02-03 copying botocore/data/events/2014-02-03/endpoint-rule-set-1.json -> build/lib/botocore/data/events/2014-02-03 copying botocore/data/events/2014-02-03/service-2.json -> build/lib/botocore/data/events/2014-02-03 creating build/lib/botocore/data/events/2015-10-07 copying botocore/data/events/2015-10-07/endpoint-rule-set-1.json -> build/lib/botocore/data/events/2015-10-07 copying botocore/data/events/2015-10-07/examples-1.json -> build/lib/botocore/data/events/2015-10-07 copying botocore/data/events/2015-10-07/paginators-1.json -> build/lib/botocore/data/events/2015-10-07 copying botocore/data/events/2015-10-07/service-2.json -> build/lib/botocore/data/events/2015-10-07 creating build/lib/botocore/data/evs creating build/lib/botocore/data/evs/2023-07-27 copying botocore/data/evs/2023-07-27/endpoint-rule-set-1.json -> build/lib/botocore/data/evs/2023-07-27 copying botocore/data/evs/2023-07-27/paginators-1.json -> build/lib/botocore/data/evs/2023-07-27 copying botocore/data/evs/2023-07-27/service-2.json -> build/lib/botocore/data/evs/2023-07-27 copying botocore/data/evs/2023-07-27/waiters-2.json -> build/lib/botocore/data/evs/2023-07-27 creating build/lib/botocore/data/finspace-data creating build/lib/botocore/data/finspace-data/2020-07-13 copying botocore/data/finspace-data/2020-07-13/endpoint-rule-set-1.json -> build/lib/botocore/data/finspace-data/2020-07-13 copying botocore/data/finspace-data/2020-07-13/examples-1.json -> build/lib/botocore/data/finspace-data/2020-07-13 copying botocore/data/finspace-data/2020-07-13/paginators-1.json -> build/lib/botocore/data/finspace-data/2020-07-13 copying botocore/data/finspace-data/2020-07-13/service-2.json -> build/lib/botocore/data/finspace-data/2020-07-13 creating build/lib/botocore/data/finspace creating build/lib/botocore/data/finspace/2021-03-12 copying botocore/data/finspace/2021-03-12/endpoint-rule-set-1.json -> build/lib/botocore/data/finspace/2021-03-12 copying botocore/data/finspace/2021-03-12/examples-1.json -> build/lib/botocore/data/finspace/2021-03-12 copying botocore/data/finspace/2021-03-12/paginators-1.json -> build/lib/botocore/data/finspace/2021-03-12 copying botocore/data/finspace/2021-03-12/service-2.json -> build/lib/botocore/data/finspace/2021-03-12 creating build/lib/botocore/data/firehose creating build/lib/botocore/data/firehose/2015-08-04 copying botocore/data/firehose/2015-08-04/endpoint-rule-set-1.json -> build/lib/botocore/data/firehose/2015-08-04 copying botocore/data/firehose/2015-08-04/examples-1.json -> build/lib/botocore/data/firehose/2015-08-04 copying botocore/data/firehose/2015-08-04/paginators-1.json -> build/lib/botocore/data/firehose/2015-08-04 copying botocore/data/firehose/2015-08-04/service-2.json -> build/lib/botocore/data/firehose/2015-08-04 creating build/lib/botocore/data/fis creating build/lib/botocore/data/fis/2020-12-01 copying botocore/data/fis/2020-12-01/endpoint-rule-set-1.json -> build/lib/botocore/data/fis/2020-12-01 copying botocore/data/fis/2020-12-01/examples-1.json -> build/lib/botocore/data/fis/2020-12-01 copying botocore/data/fis/2020-12-01/paginators-1.json -> build/lib/botocore/data/fis/2020-12-01 copying botocore/data/fis/2020-12-01/service-2.json -> build/lib/botocore/data/fis/2020-12-01 creating build/lib/botocore/data/fms creating build/lib/botocore/data/fms/2018-01-01 copying botocore/data/fms/2018-01-01/endpoint-rule-set-1.json -> build/lib/botocore/data/fms/2018-01-01 copying botocore/data/fms/2018-01-01/examples-1.json -> build/lib/botocore/data/fms/2018-01-01 copying botocore/data/fms/2018-01-01/paginators-1.json -> build/lib/botocore/data/fms/2018-01-01 copying botocore/data/fms/2018-01-01/service-2.json -> build/lib/botocore/data/fms/2018-01-01 creating build/lib/botocore/data/forecast creating build/lib/botocore/data/forecast/2018-06-26 copying botocore/data/forecast/2018-06-26/endpoint-rule-set-1.json -> build/lib/botocore/data/forecast/2018-06-26 copying botocore/data/forecast/2018-06-26/examples-1.json -> build/lib/botocore/data/forecast/2018-06-26 copying botocore/data/forecast/2018-06-26/paginators-1.json -> build/lib/botocore/data/forecast/2018-06-26 copying botocore/data/forecast/2018-06-26/service-2.json -> build/lib/botocore/data/forecast/2018-06-26 creating build/lib/botocore/data/forecastquery creating build/lib/botocore/data/forecastquery/2018-06-26 copying botocore/data/forecastquery/2018-06-26/endpoint-rule-set-1.json -> build/lib/botocore/data/forecastquery/2018-06-26 copying botocore/data/forecastquery/2018-06-26/examples-1.json -> build/lib/botocore/data/forecastquery/2018-06-26 copying botocore/data/forecastquery/2018-06-26/paginators-1.json -> build/lib/botocore/data/forecastquery/2018-06-26 copying botocore/data/forecastquery/2018-06-26/service-2.json -> build/lib/botocore/data/forecastquery/2018-06-26 creating build/lib/botocore/data/frauddetector creating build/lib/botocore/data/frauddetector/2019-11-15 copying botocore/data/frauddetector/2019-11-15/endpoint-rule-set-1.json -> build/lib/botocore/data/frauddetector/2019-11-15 copying botocore/data/frauddetector/2019-11-15/examples-1.json -> build/lib/botocore/data/frauddetector/2019-11-15 copying botocore/data/frauddetector/2019-11-15/paginators-1.json -> build/lib/botocore/data/frauddetector/2019-11-15 copying botocore/data/frauddetector/2019-11-15/service-2.json -> build/lib/botocore/data/frauddetector/2019-11-15 creating build/lib/botocore/data/freetier creating build/lib/botocore/data/freetier/2023-09-07 copying botocore/data/freetier/2023-09-07/endpoint-rule-set-1.json -> build/lib/botocore/data/freetier/2023-09-07 copying botocore/data/freetier/2023-09-07/paginators-1.json -> build/lib/botocore/data/freetier/2023-09-07 copying botocore/data/freetier/2023-09-07/service-2.json -> build/lib/botocore/data/freetier/2023-09-07 copying botocore/data/freetier/2023-09-07/waiters-2.json -> build/lib/botocore/data/freetier/2023-09-07 creating build/lib/botocore/data/fsx creating build/lib/botocore/data/fsx/2018-03-01 copying botocore/data/fsx/2018-03-01/endpoint-rule-set-1.json -> build/lib/botocore/data/fsx/2018-03-01 copying botocore/data/fsx/2018-03-01/examples-1.json -> build/lib/botocore/data/fsx/2018-03-01 copying botocore/data/fsx/2018-03-01/paginators-1.json -> build/lib/botocore/data/fsx/2018-03-01 copying botocore/data/fsx/2018-03-01/service-2.json -> build/lib/botocore/data/fsx/2018-03-01 creating build/lib/botocore/data/gamelift creating build/lib/botocore/data/gamelift/2015-10-01 copying botocore/data/gamelift/2015-10-01/endpoint-rule-set-1.json -> build/lib/botocore/data/gamelift/2015-10-01 copying botocore/data/gamelift/2015-10-01/examples-1.json -> build/lib/botocore/data/gamelift/2015-10-01 copying botocore/data/gamelift/2015-10-01/paginators-1.json -> build/lib/botocore/data/gamelift/2015-10-01 copying botocore/data/gamelift/2015-10-01/service-2.json -> build/lib/botocore/data/gamelift/2015-10-01 creating build/lib/botocore/data/gameliftstreams creating build/lib/botocore/data/gameliftstreams/2018-05-10 copying botocore/data/gameliftstreams/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/gameliftstreams/2018-05-10 copying botocore/data/gameliftstreams/2018-05-10/paginators-1.json -> build/lib/botocore/data/gameliftstreams/2018-05-10 copying botocore/data/gameliftstreams/2018-05-10/service-2.json -> build/lib/botocore/data/gameliftstreams/2018-05-10 copying botocore/data/gameliftstreams/2018-05-10/waiters-2.json -> build/lib/botocore/data/gameliftstreams/2018-05-10 creating build/lib/botocore/data/geo-maps creating build/lib/botocore/data/geo-maps/2020-11-19 copying botocore/data/geo-maps/2020-11-19/endpoint-rule-set-1.json -> build/lib/botocore/data/geo-maps/2020-11-19 copying botocore/data/geo-maps/2020-11-19/paginators-1.json -> build/lib/botocore/data/geo-maps/2020-11-19 copying botocore/data/geo-maps/2020-11-19/service-2.json -> build/lib/botocore/data/geo-maps/2020-11-19 copying botocore/data/geo-maps/2020-11-19/waiters-2.json -> build/lib/botocore/data/geo-maps/2020-11-19 creating build/lib/botocore/data/geo-places creating build/lib/botocore/data/geo-places/2020-11-19 copying botocore/data/geo-places/2020-11-19/endpoint-rule-set-1.json -> build/lib/botocore/data/geo-places/2020-11-19 copying botocore/data/geo-places/2020-11-19/paginators-1.json -> build/lib/botocore/data/geo-places/2020-11-19 copying botocore/data/geo-places/2020-11-19/service-2.json -> build/lib/botocore/data/geo-places/2020-11-19 copying botocore/data/geo-places/2020-11-19/waiters-2.json -> build/lib/botocore/data/geo-places/2020-11-19 creating build/lib/botocore/data/geo-routes creating build/lib/botocore/data/geo-routes/2020-11-19 copying botocore/data/geo-routes/2020-11-19/endpoint-rule-set-1.json -> build/lib/botocore/data/geo-routes/2020-11-19 copying botocore/data/geo-routes/2020-11-19/paginators-1.json -> build/lib/botocore/data/geo-routes/2020-11-19 copying botocore/data/geo-routes/2020-11-19/service-2.json -> build/lib/botocore/data/geo-routes/2020-11-19 copying botocore/data/geo-routes/2020-11-19/waiters-2.json -> build/lib/botocore/data/geo-routes/2020-11-19 creating build/lib/botocore/data/glacier creating build/lib/botocore/data/glacier/2012-06-01 copying botocore/data/glacier/2012-06-01/endpoint-rule-set-1.json -> build/lib/botocore/data/glacier/2012-06-01 copying botocore/data/glacier/2012-06-01/examples-1.json -> build/lib/botocore/data/glacier/2012-06-01 copying botocore/data/glacier/2012-06-01/paginators-1.json -> build/lib/botocore/data/glacier/2012-06-01 copying botocore/data/glacier/2012-06-01/service-2.json -> build/lib/botocore/data/glacier/2012-06-01 copying botocore/data/glacier/2012-06-01/waiters-2.json -> build/lib/botocore/data/glacier/2012-06-01 creating build/lib/botocore/data/globalaccelerator creating build/lib/botocore/data/globalaccelerator/2018-08-08 copying botocore/data/globalaccelerator/2018-08-08/endpoint-rule-set-1.json -> build/lib/botocore/data/globalaccelerator/2018-08-08 copying botocore/data/globalaccelerator/2018-08-08/examples-1.json -> build/lib/botocore/data/globalaccelerator/2018-08-08 copying botocore/data/globalaccelerator/2018-08-08/paginators-1.json -> build/lib/botocore/data/globalaccelerator/2018-08-08 copying botocore/data/globalaccelerator/2018-08-08/service-2.json -> build/lib/botocore/data/globalaccelerator/2018-08-08 creating build/lib/botocore/data/glue creating build/lib/botocore/data/glue/2017-03-31 copying botocore/data/glue/2017-03-31/endpoint-rule-set-1.json -> build/lib/botocore/data/glue/2017-03-31 copying botocore/data/glue/2017-03-31/examples-1.json -> build/lib/botocore/data/glue/2017-03-31 copying botocore/data/glue/2017-03-31/paginators-1.json -> build/lib/botocore/data/glue/2017-03-31 copying botocore/data/glue/2017-03-31/paginators-1.sdk-extras.json -> build/lib/botocore/data/glue/2017-03-31 copying botocore/data/glue/2017-03-31/service-2.json -> build/lib/botocore/data/glue/2017-03-31 creating build/lib/botocore/data/grafana creating build/lib/botocore/data/grafana/2020-08-18 copying botocore/data/grafana/2020-08-18/endpoint-rule-set-1.json -> build/lib/botocore/data/grafana/2020-08-18 copying botocore/data/grafana/2020-08-18/examples-1.json -> build/lib/botocore/data/grafana/2020-08-18 copying botocore/data/grafana/2020-08-18/paginators-1.json -> build/lib/botocore/data/grafana/2020-08-18 copying botocore/data/grafana/2020-08-18/paginators-1.sdk-extras.json -> build/lib/botocore/data/grafana/2020-08-18 copying botocore/data/grafana/2020-08-18/service-2.json -> build/lib/botocore/data/grafana/2020-08-18 copying botocore/data/grafana/2020-08-18/waiters-2.json -> build/lib/botocore/data/grafana/2020-08-18 creating build/lib/botocore/data/greengrass creating build/lib/botocore/data/greengrass/2017-06-07 copying botocore/data/greengrass/2017-06-07/endpoint-rule-set-1.json -> build/lib/botocore/data/greengrass/2017-06-07 copying botocore/data/greengrass/2017-06-07/paginators-1.json -> build/lib/botocore/data/greengrass/2017-06-07 copying botocore/data/greengrass/2017-06-07/service-2.json -> build/lib/botocore/data/greengrass/2017-06-07 creating build/lib/botocore/data/greengrassv2 creating build/lib/botocore/data/greengrassv2/2020-11-30 copying botocore/data/greengrassv2/2020-11-30/endpoint-rule-set-1.json -> build/lib/botocore/data/greengrassv2/2020-11-30 copying botocore/data/greengrassv2/2020-11-30/examples-1.json -> build/lib/botocore/data/greengrassv2/2020-11-30 copying botocore/data/greengrassv2/2020-11-30/paginators-1.json -> build/lib/botocore/data/greengrassv2/2020-11-30 copying botocore/data/greengrassv2/2020-11-30/service-2.json -> build/lib/botocore/data/greengrassv2/2020-11-30 creating build/lib/botocore/data/groundstation creating build/lib/botocore/data/groundstation/2019-05-23 copying botocore/data/groundstation/2019-05-23/endpoint-rule-set-1.json -> build/lib/botocore/data/groundstation/2019-05-23 copying botocore/data/groundstation/2019-05-23/examples-1.json -> build/lib/botocore/data/groundstation/2019-05-23 copying botocore/data/groundstation/2019-05-23/paginators-1.json -> build/lib/botocore/data/groundstation/2019-05-23 copying botocore/data/groundstation/2019-05-23/service-2.json -> build/lib/botocore/data/groundstation/2019-05-23 copying botocore/data/groundstation/2019-05-23/waiters-2.json -> build/lib/botocore/data/groundstation/2019-05-23 creating build/lib/botocore/data/guardduty creating build/lib/botocore/data/guardduty/2017-11-28 copying botocore/data/guardduty/2017-11-28/endpoint-rule-set-1.json -> build/lib/botocore/data/guardduty/2017-11-28 copying botocore/data/guardduty/2017-11-28/examples-1.json -> build/lib/botocore/data/guardduty/2017-11-28 copying botocore/data/guardduty/2017-11-28/paginators-1.json -> build/lib/botocore/data/guardduty/2017-11-28 copying botocore/data/guardduty/2017-11-28/service-2.json -> build/lib/botocore/data/guardduty/2017-11-28 creating build/lib/botocore/data/health creating build/lib/botocore/data/health/2016-08-04 copying botocore/data/health/2016-08-04/endpoint-rule-set-1.json -> build/lib/botocore/data/health/2016-08-04 copying botocore/data/health/2016-08-04/examples-1.json -> build/lib/botocore/data/health/2016-08-04 copying botocore/data/health/2016-08-04/paginators-1.json -> build/lib/botocore/data/health/2016-08-04 copying botocore/data/health/2016-08-04/service-2.json -> build/lib/botocore/data/health/2016-08-04 creating build/lib/botocore/data/healthlake creating build/lib/botocore/data/healthlake/2017-07-01 copying botocore/data/healthlake/2017-07-01/endpoint-rule-set-1.json -> build/lib/botocore/data/healthlake/2017-07-01 copying botocore/data/healthlake/2017-07-01/examples-1.json -> build/lib/botocore/data/healthlake/2017-07-01 copying botocore/data/healthlake/2017-07-01/paginators-1.json -> build/lib/botocore/data/healthlake/2017-07-01 copying botocore/data/healthlake/2017-07-01/service-2.json -> build/lib/botocore/data/healthlake/2017-07-01 copying botocore/data/healthlake/2017-07-01/waiters-2.json -> build/lib/botocore/data/healthlake/2017-07-01 creating build/lib/botocore/data/iam creating build/lib/botocore/data/iam/2010-05-08 copying botocore/data/iam/2010-05-08/endpoint-rule-set-1.json -> build/lib/botocore/data/iam/2010-05-08 copying botocore/data/iam/2010-05-08/examples-1.json -> build/lib/botocore/data/iam/2010-05-08 copying botocore/data/iam/2010-05-08/paginators-1.json -> build/lib/botocore/data/iam/2010-05-08 copying botocore/data/iam/2010-05-08/service-2.json -> build/lib/botocore/data/iam/2010-05-08 copying botocore/data/iam/2010-05-08/waiters-2.json -> build/lib/botocore/data/iam/2010-05-08 creating build/lib/botocore/data/identitystore creating build/lib/botocore/data/identitystore/2020-06-15 copying botocore/data/identitystore/2020-06-15/endpoint-rule-set-1.json -> build/lib/botocore/data/identitystore/2020-06-15 copying botocore/data/identitystore/2020-06-15/examples-1.json -> build/lib/botocore/data/identitystore/2020-06-15 copying botocore/data/identitystore/2020-06-15/paginators-1.json -> build/lib/botocore/data/identitystore/2020-06-15 copying botocore/data/identitystore/2020-06-15/service-2.json -> build/lib/botocore/data/identitystore/2020-06-15 creating build/lib/botocore/data/imagebuilder creating build/lib/botocore/data/imagebuilder/2019-12-02 copying botocore/data/imagebuilder/2019-12-02/endpoint-rule-set-1.json -> build/lib/botocore/data/imagebuilder/2019-12-02 copying botocore/data/imagebuilder/2019-12-02/examples-1.json -> build/lib/botocore/data/imagebuilder/2019-12-02 copying botocore/data/imagebuilder/2019-12-02/paginators-1.json -> build/lib/botocore/data/imagebuilder/2019-12-02 copying botocore/data/imagebuilder/2019-12-02/paginators-1.sdk-extras.json -> build/lib/botocore/data/imagebuilder/2019-12-02 copying botocore/data/imagebuilder/2019-12-02/service-2.json -> build/lib/botocore/data/imagebuilder/2019-12-02 creating build/lib/botocore/data/importexport creating build/lib/botocore/data/importexport/2010-06-01 copying botocore/data/importexport/2010-06-01/endpoint-rule-set-1.json -> build/lib/botocore/data/importexport/2010-06-01 copying botocore/data/importexport/2010-06-01/paginators-1.json -> build/lib/botocore/data/importexport/2010-06-01 copying botocore/data/importexport/2010-06-01/service-2.json -> build/lib/botocore/data/importexport/2010-06-01 creating build/lib/botocore/data/inspector-scan creating build/lib/botocore/data/inspector-scan/2023-08-08 copying botocore/data/inspector-scan/2023-08-08/endpoint-rule-set-1.json -> build/lib/botocore/data/inspector-scan/2023-08-08 copying botocore/data/inspector-scan/2023-08-08/paginators-1.json -> build/lib/botocore/data/inspector-scan/2023-08-08 copying botocore/data/inspector-scan/2023-08-08/service-2.json -> build/lib/botocore/data/inspector-scan/2023-08-08 creating build/lib/botocore/data/inspector creating build/lib/botocore/data/inspector/2015-08-18 copying botocore/data/inspector/2015-08-18/endpoint-rule-set-1.json -> build/lib/botocore/data/inspector/2015-08-18 copying botocore/data/inspector/2015-08-18/service-2.json -> build/lib/botocore/data/inspector/2015-08-18 creating build/lib/botocore/data/inspector/2016-02-16 copying botocore/data/inspector/2016-02-16/endpoint-rule-set-1.json -> build/lib/botocore/data/inspector/2016-02-16 copying botocore/data/inspector/2016-02-16/examples-1.json -> build/lib/botocore/data/inspector/2016-02-16 copying botocore/data/inspector/2016-02-16/paginators-1.json -> build/lib/botocore/data/inspector/2016-02-16 copying botocore/data/inspector/2016-02-16/service-2.json -> build/lib/botocore/data/inspector/2016-02-16 creating build/lib/botocore/data/inspector2 creating build/lib/botocore/data/inspector2/2020-06-08 copying botocore/data/inspector2/2020-06-08/endpoint-rule-set-1.json -> build/lib/botocore/data/inspector2/2020-06-08 copying botocore/data/inspector2/2020-06-08/examples-1.json -> build/lib/botocore/data/inspector2/2020-06-08 copying botocore/data/inspector2/2020-06-08/paginators-1.json -> build/lib/botocore/data/inspector2/2020-06-08 copying botocore/data/inspector2/2020-06-08/paginators-1.sdk-extras.json -> build/lib/botocore/data/inspector2/2020-06-08 copying botocore/data/inspector2/2020-06-08/service-2.json -> build/lib/botocore/data/inspector2/2020-06-08 creating build/lib/botocore/data/interconnect creating build/lib/botocore/data/interconnect/2022-07-26 copying botocore/data/interconnect/2022-07-26/endpoint-rule-set-1.json -> build/lib/botocore/data/interconnect/2022-07-26 copying botocore/data/interconnect/2022-07-26/paginators-1.json -> build/lib/botocore/data/interconnect/2022-07-26 copying botocore/data/interconnect/2022-07-26/service-2.json -> build/lib/botocore/data/interconnect/2022-07-26 copying botocore/data/interconnect/2022-07-26/waiters-2.json -> build/lib/botocore/data/interconnect/2022-07-26 creating build/lib/botocore/data/internetmonitor creating build/lib/botocore/data/internetmonitor/2021-06-03 copying botocore/data/internetmonitor/2021-06-03/endpoint-rule-set-1.json -> build/lib/botocore/data/internetmonitor/2021-06-03 copying botocore/data/internetmonitor/2021-06-03/paginators-1.json -> build/lib/botocore/data/internetmonitor/2021-06-03 copying botocore/data/internetmonitor/2021-06-03/service-2.json -> build/lib/botocore/data/internetmonitor/2021-06-03 copying botocore/data/internetmonitor/2021-06-03/waiters-2.json -> build/lib/botocore/data/internetmonitor/2021-06-03 creating build/lib/botocore/data/invoicing creating build/lib/botocore/data/invoicing/2024-12-01 copying botocore/data/invoicing/2024-12-01/endpoint-rule-set-1.json -> build/lib/botocore/data/invoicing/2024-12-01 copying botocore/data/invoicing/2024-12-01/paginators-1.json -> build/lib/botocore/data/invoicing/2024-12-01 copying botocore/data/invoicing/2024-12-01/service-2.json -> build/lib/botocore/data/invoicing/2024-12-01 copying botocore/data/invoicing/2024-12-01/waiters-2.json -> build/lib/botocore/data/invoicing/2024-12-01 creating build/lib/botocore/data/iot-data creating build/lib/botocore/data/iot-data/2015-05-28 copying botocore/data/iot-data/2015-05-28/endpoint-rule-set-1.json -> build/lib/botocore/data/iot-data/2015-05-28 copying botocore/data/iot-data/2015-05-28/examples-1.json -> build/lib/botocore/data/iot-data/2015-05-28 copying botocore/data/iot-data/2015-05-28/paginators-1.json -> build/lib/botocore/data/iot-data/2015-05-28 copying botocore/data/iot-data/2015-05-28/service-2.json -> build/lib/botocore/data/iot-data/2015-05-28 creating build/lib/botocore/data/iot-jobs-data creating build/lib/botocore/data/iot-jobs-data/2017-09-29 copying botocore/data/iot-jobs-data/2017-09-29/endpoint-rule-set-1.json -> build/lib/botocore/data/iot-jobs-data/2017-09-29 copying botocore/data/iot-jobs-data/2017-09-29/examples-1.json -> build/lib/botocore/data/iot-jobs-data/2017-09-29 copying botocore/data/iot-jobs-data/2017-09-29/paginators-1.json -> build/lib/botocore/data/iot-jobs-data/2017-09-29 copying botocore/data/iot-jobs-data/2017-09-29/service-2.json -> build/lib/botocore/data/iot-jobs-data/2017-09-29 creating build/lib/botocore/data/iot-managed-integrations creating build/lib/botocore/data/iot-managed-integrations/2025-03-03 copying botocore/data/iot-managed-integrations/2025-03-03/endpoint-rule-set-1.json -> build/lib/botocore/data/iot-managed-integrations/2025-03-03 copying botocore/data/iot-managed-integrations/2025-03-03/paginators-1.json -> build/lib/botocore/data/iot-managed-integrations/2025-03-03 copying botocore/data/iot-managed-integrations/2025-03-03/service-2.json -> build/lib/botocore/data/iot-managed-integrations/2025-03-03 creating build/lib/botocore/data/iot creating build/lib/botocore/data/iot/2015-05-28 copying botocore/data/iot/2015-05-28/endpoint-rule-set-1.json -> build/lib/botocore/data/iot/2015-05-28 copying botocore/data/iot/2015-05-28/examples-1.json -> build/lib/botocore/data/iot/2015-05-28 copying botocore/data/iot/2015-05-28/paginators-1.json -> build/lib/botocore/data/iot/2015-05-28 copying botocore/data/iot/2015-05-28/service-2.json -> build/lib/botocore/data/iot/2015-05-28 creating build/lib/botocore/data/iotdeviceadvisor creating build/lib/botocore/data/iotdeviceadvisor/2020-09-18 copying botocore/data/iotdeviceadvisor/2020-09-18/endpoint-rule-set-1.json -> build/lib/botocore/data/iotdeviceadvisor/2020-09-18 copying botocore/data/iotdeviceadvisor/2020-09-18/examples-1.json -> build/lib/botocore/data/iotdeviceadvisor/2020-09-18 copying botocore/data/iotdeviceadvisor/2020-09-18/paginators-1.json -> build/lib/botocore/data/iotdeviceadvisor/2020-09-18 copying botocore/data/iotdeviceadvisor/2020-09-18/service-2.json -> build/lib/botocore/data/iotdeviceadvisor/2020-09-18 creating build/lib/botocore/data/iotevents-data creating build/lib/botocore/data/iotevents-data/2018-10-23 copying botocore/data/iotevents-data/2018-10-23/endpoint-rule-set-1.json -> build/lib/botocore/data/iotevents-data/2018-10-23 copying botocore/data/iotevents-data/2018-10-23/examples-1.json -> build/lib/botocore/data/iotevents-data/2018-10-23 copying botocore/data/iotevents-data/2018-10-23/paginators-1.json -> build/lib/botocore/data/iotevents-data/2018-10-23 copying botocore/data/iotevents-data/2018-10-23/service-2.json -> build/lib/botocore/data/iotevents-data/2018-10-23 creating build/lib/botocore/data/iotevents creating build/lib/botocore/data/iotevents/2018-07-27 copying botocore/data/iotevents/2018-07-27/endpoint-rule-set-1.json -> build/lib/botocore/data/iotevents/2018-07-27 copying botocore/data/iotevents/2018-07-27/examples-1.json -> build/lib/botocore/data/iotevents/2018-07-27 copying botocore/data/iotevents/2018-07-27/paginators-1.json -> build/lib/botocore/data/iotevents/2018-07-27 copying botocore/data/iotevents/2018-07-27/service-2.json -> build/lib/botocore/data/iotevents/2018-07-27 creating build/lib/botocore/data/iotfleetwise creating build/lib/botocore/data/iotfleetwise/2021-06-17 copying botocore/data/iotfleetwise/2021-06-17/endpoint-rule-set-1.json -> build/lib/botocore/data/iotfleetwise/2021-06-17 copying botocore/data/iotfleetwise/2021-06-17/paginators-1.json -> build/lib/botocore/data/iotfleetwise/2021-06-17 copying botocore/data/iotfleetwise/2021-06-17/service-2.json -> build/lib/botocore/data/iotfleetwise/2021-06-17 copying botocore/data/iotfleetwise/2021-06-17/waiters-2.json -> build/lib/botocore/data/iotfleetwise/2021-06-17 creating build/lib/botocore/data/iotsecuretunneling creating build/lib/botocore/data/iotsecuretunneling/2018-10-05 copying botocore/data/iotsecuretunneling/2018-10-05/endpoint-rule-set-1.json -> build/lib/botocore/data/iotsecuretunneling/2018-10-05 copying botocore/data/iotsecuretunneling/2018-10-05/examples-1.json -> build/lib/botocore/data/iotsecuretunneling/2018-10-05 copying botocore/data/iotsecuretunneling/2018-10-05/paginators-1.json -> build/lib/botocore/data/iotsecuretunneling/2018-10-05 copying botocore/data/iotsecuretunneling/2018-10-05/service-2.json -> build/lib/botocore/data/iotsecuretunneling/2018-10-05 creating build/lib/botocore/data/iotsitewise creating build/lib/botocore/data/iotsitewise/2019-12-02 copying botocore/data/iotsitewise/2019-12-02/endpoint-rule-set-1.json -> build/lib/botocore/data/iotsitewise/2019-12-02 copying botocore/data/iotsitewise/2019-12-02/examples-1.json -> build/lib/botocore/data/iotsitewise/2019-12-02 copying botocore/data/iotsitewise/2019-12-02/paginators-1.json -> build/lib/botocore/data/iotsitewise/2019-12-02 copying botocore/data/iotsitewise/2019-12-02/paginators-1.sdk-extras.json -> build/lib/botocore/data/iotsitewise/2019-12-02 copying botocore/data/iotsitewise/2019-12-02/service-2.json -> build/lib/botocore/data/iotsitewise/2019-12-02 copying botocore/data/iotsitewise/2019-12-02/waiters-2.json -> build/lib/botocore/data/iotsitewise/2019-12-02 creating build/lib/botocore/data/iotthingsgraph creating build/lib/botocore/data/iotthingsgraph/2018-09-06 copying botocore/data/iotthingsgraph/2018-09-06/endpoint-rule-set-1.json -> build/lib/botocore/data/iotthingsgraph/2018-09-06 copying botocore/data/iotthingsgraph/2018-09-06/examples-1.json -> build/lib/botocore/data/iotthingsgraph/2018-09-06 copying botocore/data/iotthingsgraph/2018-09-06/paginators-1.json -> build/lib/botocore/data/iotthingsgraph/2018-09-06 copying botocore/data/iotthingsgraph/2018-09-06/service-2.json -> build/lib/botocore/data/iotthingsgraph/2018-09-06 creating build/lib/botocore/data/iottwinmaker creating build/lib/botocore/data/iottwinmaker/2021-11-29 copying botocore/data/iottwinmaker/2021-11-29/endpoint-rule-set-1.json -> build/lib/botocore/data/iottwinmaker/2021-11-29 copying botocore/data/iottwinmaker/2021-11-29/examples-1.json -> build/lib/botocore/data/iottwinmaker/2021-11-29 copying botocore/data/iottwinmaker/2021-11-29/paginators-1.json -> build/lib/botocore/data/iottwinmaker/2021-11-29 copying botocore/data/iottwinmaker/2021-11-29/service-2.json -> build/lib/botocore/data/iottwinmaker/2021-11-29 copying botocore/data/iottwinmaker/2021-11-29/waiters-2.json -> build/lib/botocore/data/iottwinmaker/2021-11-29 creating build/lib/botocore/data/iotwireless creating build/lib/botocore/data/iotwireless/2020-11-22 copying botocore/data/iotwireless/2020-11-22/endpoint-rule-set-1.json -> build/lib/botocore/data/iotwireless/2020-11-22 copying botocore/data/iotwireless/2020-11-22/examples-1.json -> build/lib/botocore/data/iotwireless/2020-11-22 copying botocore/data/iotwireless/2020-11-22/paginators-1.json -> build/lib/botocore/data/iotwireless/2020-11-22 copying botocore/data/iotwireless/2020-11-22/service-2.json -> build/lib/botocore/data/iotwireless/2020-11-22 creating build/lib/botocore/data/ivs-realtime creating build/lib/botocore/data/ivs-realtime/2020-07-14 copying botocore/data/ivs-realtime/2020-07-14/endpoint-rule-set-1.json -> build/lib/botocore/data/ivs-realtime/2020-07-14 copying botocore/data/ivs-realtime/2020-07-14/paginators-1.json -> build/lib/botocore/data/ivs-realtime/2020-07-14 copying botocore/data/ivs-realtime/2020-07-14/service-2.json -> build/lib/botocore/data/ivs-realtime/2020-07-14 copying botocore/data/ivs-realtime/2020-07-14/waiters-2.json -> build/lib/botocore/data/ivs-realtime/2020-07-14 creating build/lib/botocore/data/ivs creating build/lib/botocore/data/ivs/2020-07-14 copying botocore/data/ivs/2020-07-14/endpoint-rule-set-1.json -> build/lib/botocore/data/ivs/2020-07-14 copying botocore/data/ivs/2020-07-14/examples-1.json -> build/lib/botocore/data/ivs/2020-07-14 copying botocore/data/ivs/2020-07-14/paginators-1.json -> build/lib/botocore/data/ivs/2020-07-14 copying botocore/data/ivs/2020-07-14/service-2.json -> build/lib/botocore/data/ivs/2020-07-14 creating build/lib/botocore/data/ivschat creating build/lib/botocore/data/ivschat/2020-07-14 copying botocore/data/ivschat/2020-07-14/endpoint-rule-set-1.json -> build/lib/botocore/data/ivschat/2020-07-14 copying botocore/data/ivschat/2020-07-14/examples-1.json -> build/lib/botocore/data/ivschat/2020-07-14 copying botocore/data/ivschat/2020-07-14/paginators-1.json -> build/lib/botocore/data/ivschat/2020-07-14 copying botocore/data/ivschat/2020-07-14/service-2.json -> build/lib/botocore/data/ivschat/2020-07-14 copying botocore/data/ivschat/2020-07-14/waiters-2.json -> build/lib/botocore/data/ivschat/2020-07-14 creating build/lib/botocore/data/kafka creating build/lib/botocore/data/kafka/2018-11-14 copying botocore/data/kafka/2018-11-14/endpoint-rule-set-1.json -> build/lib/botocore/data/kafka/2018-11-14 copying botocore/data/kafka/2018-11-14/paginators-1.json -> build/lib/botocore/data/kafka/2018-11-14 copying botocore/data/kafka/2018-11-14/service-2.json -> build/lib/botocore/data/kafka/2018-11-14 creating build/lib/botocore/data/kafkaconnect creating build/lib/botocore/data/kafkaconnect/2021-09-14 copying botocore/data/kafkaconnect/2021-09-14/endpoint-rule-set-1.json -> build/lib/botocore/data/kafkaconnect/2021-09-14 copying botocore/data/kafkaconnect/2021-09-14/examples-1.json -> build/lib/botocore/data/kafkaconnect/2021-09-14 copying botocore/data/kafkaconnect/2021-09-14/paginators-1.json -> build/lib/botocore/data/kafkaconnect/2021-09-14 copying botocore/data/kafkaconnect/2021-09-14/service-2.json -> build/lib/botocore/data/kafkaconnect/2021-09-14 copying botocore/data/kafkaconnect/2021-09-14/waiters-2.json -> build/lib/botocore/data/kafkaconnect/2021-09-14 creating build/lib/botocore/data/kendra-ranking creating build/lib/botocore/data/kendra-ranking/2022-10-19 copying botocore/data/kendra-ranking/2022-10-19/endpoint-rule-set-1.json -> build/lib/botocore/data/kendra-ranking/2022-10-19 copying botocore/data/kendra-ranking/2022-10-19/paginators-1.json -> build/lib/botocore/data/kendra-ranking/2022-10-19 copying botocore/data/kendra-ranking/2022-10-19/service-2.json -> build/lib/botocore/data/kendra-ranking/2022-10-19 creating build/lib/botocore/data/kendra creating build/lib/botocore/data/kendra/2019-02-03 copying botocore/data/kendra/2019-02-03/endpoint-rule-set-1.json -> build/lib/botocore/data/kendra/2019-02-03 copying botocore/data/kendra/2019-02-03/examples-1.json -> build/lib/botocore/data/kendra/2019-02-03 copying botocore/data/kendra/2019-02-03/paginators-1.json -> build/lib/botocore/data/kendra/2019-02-03 copying botocore/data/kendra/2019-02-03/service-2.json -> build/lib/botocore/data/kendra/2019-02-03 creating build/lib/botocore/data/keyspaces creating build/lib/botocore/data/keyspaces/2022-02-10 copying botocore/data/keyspaces/2022-02-10/endpoint-rule-set-1.json -> build/lib/botocore/data/keyspaces/2022-02-10 copying botocore/data/keyspaces/2022-02-10/examples-1.json -> build/lib/botocore/data/keyspaces/2022-02-10 copying botocore/data/keyspaces/2022-02-10/paginators-1.json -> build/lib/botocore/data/keyspaces/2022-02-10 copying botocore/data/keyspaces/2022-02-10/service-2.json -> build/lib/botocore/data/keyspaces/2022-02-10 copying botocore/data/keyspaces/2022-02-10/waiters-2.json -> build/lib/botocore/data/keyspaces/2022-02-10 creating build/lib/botocore/data/keyspacesstreams creating build/lib/botocore/data/keyspacesstreams/2024-09-09 copying botocore/data/keyspacesstreams/2024-09-09/endpoint-rule-set-1.json -> build/lib/botocore/data/keyspacesstreams/2024-09-09 copying botocore/data/keyspacesstreams/2024-09-09/paginators-1.json -> build/lib/botocore/data/keyspacesstreams/2024-09-09 copying botocore/data/keyspacesstreams/2024-09-09/paginators-1.sdk-extras.json -> build/lib/botocore/data/keyspacesstreams/2024-09-09 copying botocore/data/keyspacesstreams/2024-09-09/service-2.json -> build/lib/botocore/data/keyspacesstreams/2024-09-09 creating build/lib/botocore/data/kinesis-video-archived-media creating build/lib/botocore/data/kinesis-video-archived-media/2017-09-30 copying botocore/data/kinesis-video-archived-media/2017-09-30/endpoint-rule-set-1.json -> build/lib/botocore/data/kinesis-video-archived-media/2017-09-30 copying botocore/data/kinesis-video-archived-media/2017-09-30/examples-1.json -> build/lib/botocore/data/kinesis-video-archived-media/2017-09-30 copying botocore/data/kinesis-video-archived-media/2017-09-30/paginators-1.json -> build/lib/botocore/data/kinesis-video-archived-media/2017-09-30 copying botocore/data/kinesis-video-archived-media/2017-09-30/service-2.json -> build/lib/botocore/data/kinesis-video-archived-media/2017-09-30 creating build/lib/botocore/data/kinesis-video-media creating build/lib/botocore/data/kinesis-video-media/2017-09-30 copying botocore/data/kinesis-video-media/2017-09-30/endpoint-rule-set-1.json -> build/lib/botocore/data/kinesis-video-media/2017-09-30 copying botocore/data/kinesis-video-media/2017-09-30/examples-1.json -> build/lib/botocore/data/kinesis-video-media/2017-09-30 copying botocore/data/kinesis-video-media/2017-09-30/paginators-1.json -> build/lib/botocore/data/kinesis-video-media/2017-09-30 copying botocore/data/kinesis-video-media/2017-09-30/service-2.json -> build/lib/botocore/data/kinesis-video-media/2017-09-30 creating build/lib/botocore/data/kinesis-video-signaling creating build/lib/botocore/data/kinesis-video-signaling/2019-12-04 copying botocore/data/kinesis-video-signaling/2019-12-04/endpoint-rule-set-1.json -> build/lib/botocore/data/kinesis-video-signaling/2019-12-04 copying botocore/data/kinesis-video-signaling/2019-12-04/examples-1.json -> build/lib/botocore/data/kinesis-video-signaling/2019-12-04 copying botocore/data/kinesis-video-signaling/2019-12-04/paginators-1.json -> build/lib/botocore/data/kinesis-video-signaling/2019-12-04 copying botocore/data/kinesis-video-signaling/2019-12-04/service-2.json -> build/lib/botocore/data/kinesis-video-signaling/2019-12-04 creating build/lib/botocore/data/kinesis-video-webrtc-storage creating build/lib/botocore/data/kinesis-video-webrtc-storage/2018-05-10 copying botocore/data/kinesis-video-webrtc-storage/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/kinesis-video-webrtc-storage/2018-05-10 copying botocore/data/kinesis-video-webrtc-storage/2018-05-10/paginators-1.json -> build/lib/botocore/data/kinesis-video-webrtc-storage/2018-05-10 copying botocore/data/kinesis-video-webrtc-storage/2018-05-10/service-2.json -> build/lib/botocore/data/kinesis-video-webrtc-storage/2018-05-10 creating build/lib/botocore/data/kinesis creating build/lib/botocore/data/kinesis/2013-12-02 copying botocore/data/kinesis/2013-12-02/endpoint-rule-set-1.json -> build/lib/botocore/data/kinesis/2013-12-02 copying botocore/data/kinesis/2013-12-02/examples-1.json -> build/lib/botocore/data/kinesis/2013-12-02 copying botocore/data/kinesis/2013-12-02/paginators-1.json -> build/lib/botocore/data/kinesis/2013-12-02 copying botocore/data/kinesis/2013-12-02/service-2.json -> build/lib/botocore/data/kinesis/2013-12-02 copying botocore/data/kinesis/2013-12-02/waiters-2.json -> build/lib/botocore/data/kinesis/2013-12-02 creating build/lib/botocore/data/kinesisanalytics creating build/lib/botocore/data/kinesisanalytics/2015-08-14 copying botocore/data/kinesisanalytics/2015-08-14/endpoint-rule-set-1.json -> build/lib/botocore/data/kinesisanalytics/2015-08-14 copying botocore/data/kinesisanalytics/2015-08-14/examples-1.json -> build/lib/botocore/data/kinesisanalytics/2015-08-14 copying botocore/data/kinesisanalytics/2015-08-14/paginators-1.json -> build/lib/botocore/data/kinesisanalytics/2015-08-14 copying botocore/data/kinesisanalytics/2015-08-14/service-2.json -> build/lib/botocore/data/kinesisanalytics/2015-08-14 creating build/lib/botocore/data/kinesisanalyticsv2 creating build/lib/botocore/data/kinesisanalyticsv2/2018-05-23 copying botocore/data/kinesisanalyticsv2/2018-05-23/endpoint-rule-set-1.json -> build/lib/botocore/data/kinesisanalyticsv2/2018-05-23 copying botocore/data/kinesisanalyticsv2/2018-05-23/examples-1.json -> build/lib/botocore/data/kinesisanalyticsv2/2018-05-23 copying botocore/data/kinesisanalyticsv2/2018-05-23/paginators-1.json -> build/lib/botocore/data/kinesisanalyticsv2/2018-05-23 copying botocore/data/kinesisanalyticsv2/2018-05-23/service-2.json -> build/lib/botocore/data/kinesisanalyticsv2/2018-05-23 creating build/lib/botocore/data/kinesisvideo creating build/lib/botocore/data/kinesisvideo/2017-09-30 copying botocore/data/kinesisvideo/2017-09-30/endpoint-rule-set-1.json -> build/lib/botocore/data/kinesisvideo/2017-09-30 copying botocore/data/kinesisvideo/2017-09-30/examples-1.json -> build/lib/botocore/data/kinesisvideo/2017-09-30 copying botocore/data/kinesisvideo/2017-09-30/paginators-1.json -> build/lib/botocore/data/kinesisvideo/2017-09-30 copying botocore/data/kinesisvideo/2017-09-30/service-2.json -> build/lib/botocore/data/kinesisvideo/2017-09-30 creating build/lib/botocore/data/kms creating build/lib/botocore/data/kms/2014-11-01 copying botocore/data/kms/2014-11-01/endpoint-rule-set-1.json -> build/lib/botocore/data/kms/2014-11-01 copying botocore/data/kms/2014-11-01/examples-1.json -> build/lib/botocore/data/kms/2014-11-01 copying botocore/data/kms/2014-11-01/paginators-1.json -> build/lib/botocore/data/kms/2014-11-01 copying botocore/data/kms/2014-11-01/service-2.json -> build/lib/botocore/data/kms/2014-11-01 creating build/lib/botocore/data/lakeformation creating build/lib/botocore/data/lakeformation/2017-03-31 copying botocore/data/lakeformation/2017-03-31/endpoint-rule-set-1.json -> build/lib/botocore/data/lakeformation/2017-03-31 copying botocore/data/lakeformation/2017-03-31/examples-1.json -> build/lib/botocore/data/lakeformation/2017-03-31 copying botocore/data/lakeformation/2017-03-31/paginators-1.json -> build/lib/botocore/data/lakeformation/2017-03-31 copying botocore/data/lakeformation/2017-03-31/paginators-1.sdk-extras.json -> build/lib/botocore/data/lakeformation/2017-03-31 copying botocore/data/lakeformation/2017-03-31/service-2.json -> build/lib/botocore/data/lakeformation/2017-03-31 creating build/lib/botocore/data/lambda creating build/lib/botocore/data/lambda/2014-11-11 copying botocore/data/lambda/2014-11-11/endpoint-rule-set-1.json -> build/lib/botocore/data/lambda/2014-11-11 copying botocore/data/lambda/2014-11-11/service-2.json -> build/lib/botocore/data/lambda/2014-11-11 creating build/lib/botocore/data/lambda/2015-03-31 copying botocore/data/lambda/2015-03-31/endpoint-rule-set-1.json -> build/lib/botocore/data/lambda/2015-03-31 copying botocore/data/lambda/2015-03-31/examples-1.json -> build/lib/botocore/data/lambda/2015-03-31 copying botocore/data/lambda/2015-03-31/paginators-1.json -> build/lib/botocore/data/lambda/2015-03-31 copying botocore/data/lambda/2015-03-31/paginators-1.sdk-extras.json -> build/lib/botocore/data/lambda/2015-03-31 copying botocore/data/lambda/2015-03-31/service-2.json -> build/lib/botocore/data/lambda/2015-03-31 copying botocore/data/lambda/2015-03-31/waiters-2.json -> build/lib/botocore/data/lambda/2015-03-31 creating build/lib/botocore/data/launch-wizard creating build/lib/botocore/data/launch-wizard/2018-05-10 copying botocore/data/launch-wizard/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/launch-wizard/2018-05-10 copying botocore/data/launch-wizard/2018-05-10/paginators-1.json -> build/lib/botocore/data/launch-wizard/2018-05-10 copying botocore/data/launch-wizard/2018-05-10/service-2.json -> build/lib/botocore/data/launch-wizard/2018-05-10 copying botocore/data/launch-wizard/2018-05-10/waiters-2.json -> build/lib/botocore/data/launch-wizard/2018-05-10 creating build/lib/botocore/data/lex-models creating build/lib/botocore/data/lex-models/2017-04-19 copying botocore/data/lex-models/2017-04-19/endpoint-rule-set-1.json -> build/lib/botocore/data/lex-models/2017-04-19 copying botocore/data/lex-models/2017-04-19/examples-1.json -> build/lib/botocore/data/lex-models/2017-04-19 copying botocore/data/lex-models/2017-04-19/paginators-1.json -> build/lib/botocore/data/lex-models/2017-04-19 copying botocore/data/lex-models/2017-04-19/service-2.json -> build/lib/botocore/data/lex-models/2017-04-19 creating build/lib/botocore/data/lex-runtime creating build/lib/botocore/data/lex-runtime/2016-11-28 copying botocore/data/lex-runtime/2016-11-28/endpoint-rule-set-1.json -> build/lib/botocore/data/lex-runtime/2016-11-28 copying botocore/data/lex-runtime/2016-11-28/examples-1.json -> build/lib/botocore/data/lex-runtime/2016-11-28 copying botocore/data/lex-runtime/2016-11-28/paginators-1.json -> build/lib/botocore/data/lex-runtime/2016-11-28 copying botocore/data/lex-runtime/2016-11-28/service-2.json -> build/lib/botocore/data/lex-runtime/2016-11-28 creating build/lib/botocore/data/lexv2-models creating build/lib/botocore/data/lexv2-models/2020-08-07 copying botocore/data/lexv2-models/2020-08-07/endpoint-rule-set-1.json -> build/lib/botocore/data/lexv2-models/2020-08-07 copying botocore/data/lexv2-models/2020-08-07/examples-1.json -> build/lib/botocore/data/lexv2-models/2020-08-07 copying botocore/data/lexv2-models/2020-08-07/paginators-1.json -> build/lib/botocore/data/lexv2-models/2020-08-07 copying botocore/data/lexv2-models/2020-08-07/service-2.json -> build/lib/botocore/data/lexv2-models/2020-08-07 copying botocore/data/lexv2-models/2020-08-07/waiters-2.json -> build/lib/botocore/data/lexv2-models/2020-08-07 creating build/lib/botocore/data/lexv2-runtime creating build/lib/botocore/data/lexv2-runtime/2020-08-07 copying botocore/data/lexv2-runtime/2020-08-07/endpoint-rule-set-1.json -> build/lib/botocore/data/lexv2-runtime/2020-08-07 copying botocore/data/lexv2-runtime/2020-08-07/examples-1.json -> build/lib/botocore/data/lexv2-runtime/2020-08-07 copying botocore/data/lexv2-runtime/2020-08-07/paginators-1.json -> build/lib/botocore/data/lexv2-runtime/2020-08-07 copying botocore/data/lexv2-runtime/2020-08-07/service-2.json -> build/lib/botocore/data/lexv2-runtime/2020-08-07 creating build/lib/botocore/data/license-manager-linux-subscriptions creating build/lib/botocore/data/license-manager-linux-subscriptions/2018-05-10 copying botocore/data/license-manager-linux-subscriptions/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/license-manager-linux-subscriptions/2018-05-10 copying botocore/data/license-manager-linux-subscriptions/2018-05-10/paginators-1.json -> build/lib/botocore/data/license-manager-linux-subscriptions/2018-05-10 copying botocore/data/license-manager-linux-subscriptions/2018-05-10/service-2.json -> build/lib/botocore/data/license-manager-linux-subscriptions/2018-05-10 creating build/lib/botocore/data/license-manager-user-subscriptions creating build/lib/botocore/data/license-manager-user-subscriptions/2018-05-10 copying botocore/data/license-manager-user-subscriptions/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/license-manager-user-subscriptions/2018-05-10 copying botocore/data/license-manager-user-subscriptions/2018-05-10/paginators-1.json -> build/lib/botocore/data/license-manager-user-subscriptions/2018-05-10 copying botocore/data/license-manager-user-subscriptions/2018-05-10/service-2.json -> build/lib/botocore/data/license-manager-user-subscriptions/2018-05-10 copying botocore/data/license-manager-user-subscriptions/2018-05-10/waiters-2.json -> build/lib/botocore/data/license-manager-user-subscriptions/2018-05-10 creating build/lib/botocore/data/license-manager creating build/lib/botocore/data/license-manager/2018-08-01 copying botocore/data/license-manager/2018-08-01/endpoint-rule-set-1.json -> build/lib/botocore/data/license-manager/2018-08-01 copying botocore/data/license-manager/2018-08-01/examples-1.json -> build/lib/botocore/data/license-manager/2018-08-01 copying botocore/data/license-manager/2018-08-01/paginators-1.json -> build/lib/botocore/data/license-manager/2018-08-01 copying botocore/data/license-manager/2018-08-01/service-2.json -> build/lib/botocore/data/license-manager/2018-08-01 creating build/lib/botocore/data/lightsail creating build/lib/botocore/data/lightsail/2016-11-28 copying botocore/data/lightsail/2016-11-28/endpoint-rule-set-1.json -> build/lib/botocore/data/lightsail/2016-11-28 copying botocore/data/lightsail/2016-11-28/examples-1.json -> build/lib/botocore/data/lightsail/2016-11-28 copying botocore/data/lightsail/2016-11-28/paginators-1.json -> build/lib/botocore/data/lightsail/2016-11-28 copying botocore/data/lightsail/2016-11-28/service-2.json -> build/lib/botocore/data/lightsail/2016-11-28 creating build/lib/botocore/data/location creating build/lib/botocore/data/location/2020-11-19 copying botocore/data/location/2020-11-19/endpoint-rule-set-1.json -> build/lib/botocore/data/location/2020-11-19 copying botocore/data/location/2020-11-19/examples-1.json -> build/lib/botocore/data/location/2020-11-19 copying botocore/data/location/2020-11-19/paginators-1.json -> build/lib/botocore/data/location/2020-11-19 copying botocore/data/location/2020-11-19/paginators-1.sdk-extras.json -> build/lib/botocore/data/location/2020-11-19 copying botocore/data/location/2020-11-19/service-2.json -> build/lib/botocore/data/location/2020-11-19 copying botocore/data/location/2020-11-19/waiters-2.json -> build/lib/botocore/data/location/2020-11-19 creating build/lib/botocore/data/logs creating build/lib/botocore/data/logs/2014-03-28 copying botocore/data/logs/2014-03-28/endpoint-rule-set-1.json -> build/lib/botocore/data/logs/2014-03-28 copying botocore/data/logs/2014-03-28/examples-1.json -> build/lib/botocore/data/logs/2014-03-28 copying botocore/data/logs/2014-03-28/paginators-1.json -> build/lib/botocore/data/logs/2014-03-28 copying botocore/data/logs/2014-03-28/paginators-1.sdk-extras.json -> build/lib/botocore/data/logs/2014-03-28 copying botocore/data/logs/2014-03-28/service-2.json -> build/lib/botocore/data/logs/2014-03-28 creating build/lib/botocore/data/lookoutequipment creating build/lib/botocore/data/lookoutequipment/2020-12-15 copying botocore/data/lookoutequipment/2020-12-15/endpoint-rule-set-1.json -> build/lib/botocore/data/lookoutequipment/2020-12-15 copying botocore/data/lookoutequipment/2020-12-15/examples-1.json -> build/lib/botocore/data/lookoutequipment/2020-12-15 copying botocore/data/lookoutequipment/2020-12-15/paginators-1.json -> build/lib/botocore/data/lookoutequipment/2020-12-15 copying botocore/data/lookoutequipment/2020-12-15/service-2.json -> build/lib/botocore/data/lookoutequipment/2020-12-15 creating build/lib/botocore/data/m2 creating build/lib/botocore/data/m2/2021-04-28 copying botocore/data/m2/2021-04-28/endpoint-rule-set-1.json -> build/lib/botocore/data/m2/2021-04-28 copying botocore/data/m2/2021-04-28/paginators-1.json -> build/lib/botocore/data/m2/2021-04-28 copying botocore/data/m2/2021-04-28/service-2.json -> build/lib/botocore/data/m2/2021-04-28 creating build/lib/botocore/data/machinelearning creating build/lib/botocore/data/machinelearning/2014-12-12 copying botocore/data/machinelearning/2014-12-12/endpoint-rule-set-1.json -> build/lib/botocore/data/machinelearning/2014-12-12 copying botocore/data/machinelearning/2014-12-12/examples-1.json -> build/lib/botocore/data/machinelearning/2014-12-12 copying botocore/data/machinelearning/2014-12-12/paginators-1.json -> build/lib/botocore/data/machinelearning/2014-12-12 copying botocore/data/machinelearning/2014-12-12/service-2.json -> build/lib/botocore/data/machinelearning/2014-12-12 copying botocore/data/machinelearning/2014-12-12/waiters-2.json -> build/lib/botocore/data/machinelearning/2014-12-12 creating build/lib/botocore/data/macie2 creating build/lib/botocore/data/macie2/2020-01-01 copying botocore/data/macie2/2020-01-01/endpoint-rule-set-1.json -> build/lib/botocore/data/macie2/2020-01-01 copying botocore/data/macie2/2020-01-01/paginators-1.json -> build/lib/botocore/data/macie2/2020-01-01 copying botocore/data/macie2/2020-01-01/service-2.json -> build/lib/botocore/data/macie2/2020-01-01 copying botocore/data/macie2/2020-01-01/waiters-2.json -> build/lib/botocore/data/macie2/2020-01-01 creating build/lib/botocore/data/mailmanager creating build/lib/botocore/data/mailmanager/2023-10-17 copying botocore/data/mailmanager/2023-10-17/endpoint-rule-set-1.json -> build/lib/botocore/data/mailmanager/2023-10-17 copying botocore/data/mailmanager/2023-10-17/paginators-1.json -> build/lib/botocore/data/mailmanager/2023-10-17 copying botocore/data/mailmanager/2023-10-17/service-2.json -> build/lib/botocore/data/mailmanager/2023-10-17 copying botocore/data/mailmanager/2023-10-17/waiters-2.json -> build/lib/botocore/data/mailmanager/2023-10-17 creating build/lib/botocore/data/managedblockchain-query creating build/lib/botocore/data/managedblockchain-query/2023-05-04 copying botocore/data/managedblockchain-query/2023-05-04/endpoint-rule-set-1.json -> build/lib/botocore/data/managedblockchain-query/2023-05-04 copying botocore/data/managedblockchain-query/2023-05-04/paginators-1.json -> build/lib/botocore/data/managedblockchain-query/2023-05-04 copying botocore/data/managedblockchain-query/2023-05-04/service-2.json -> build/lib/botocore/data/managedblockchain-query/2023-05-04 copying botocore/data/managedblockchain-query/2023-05-04/waiters-2.json -> build/lib/botocore/data/managedblockchain-query/2023-05-04 creating build/lib/botocore/data/managedblockchain creating build/lib/botocore/data/managedblockchain/2018-09-24 copying botocore/data/managedblockchain/2018-09-24/endpoint-rule-set-1.json -> build/lib/botocore/data/managedblockchain/2018-09-24 copying botocore/data/managedblockchain/2018-09-24/examples-1.json -> build/lib/botocore/data/managedblockchain/2018-09-24 copying botocore/data/managedblockchain/2018-09-24/paginators-1.json -> build/lib/botocore/data/managedblockchain/2018-09-24 copying botocore/data/managedblockchain/2018-09-24/service-2.json -> build/lib/botocore/data/managedblockchain/2018-09-24 creating build/lib/botocore/data/marketplace-agreement creating build/lib/botocore/data/marketplace-agreement/2020-03-01 copying botocore/data/marketplace-agreement/2020-03-01/endpoint-rule-set-1.json -> build/lib/botocore/data/marketplace-agreement/2020-03-01 copying botocore/data/marketplace-agreement/2020-03-01/paginators-1.json -> build/lib/botocore/data/marketplace-agreement/2020-03-01 copying botocore/data/marketplace-agreement/2020-03-01/service-2.json -> build/lib/botocore/data/marketplace-agreement/2020-03-01 copying botocore/data/marketplace-agreement/2020-03-01/waiters-2.json -> build/lib/botocore/data/marketplace-agreement/2020-03-01 creating build/lib/botocore/data/marketplace-catalog creating build/lib/botocore/data/marketplace-catalog/2018-09-17 copying botocore/data/marketplace-catalog/2018-09-17/endpoint-rule-set-1.json -> build/lib/botocore/data/marketplace-catalog/2018-09-17 copying botocore/data/marketplace-catalog/2018-09-17/examples-1.json -> build/lib/botocore/data/marketplace-catalog/2018-09-17 copying botocore/data/marketplace-catalog/2018-09-17/paginators-1.json -> build/lib/botocore/data/marketplace-catalog/2018-09-17 copying botocore/data/marketplace-catalog/2018-09-17/service-2.json -> build/lib/botocore/data/marketplace-catalog/2018-09-17 creating build/lib/botocore/data/marketplace-deployment creating build/lib/botocore/data/marketplace-deployment/2023-01-25 copying botocore/data/marketplace-deployment/2023-01-25/endpoint-rule-set-1.json -> build/lib/botocore/data/marketplace-deployment/2023-01-25 copying botocore/data/marketplace-deployment/2023-01-25/paginators-1.json -> build/lib/botocore/data/marketplace-deployment/2023-01-25 copying botocore/data/marketplace-deployment/2023-01-25/service-2.json -> build/lib/botocore/data/marketplace-deployment/2023-01-25 creating build/lib/botocore/data/marketplace-discovery creating build/lib/botocore/data/marketplace-discovery/2026-02-05 copying botocore/data/marketplace-discovery/2026-02-05/endpoint-rule-set-1.json -> build/lib/botocore/data/marketplace-discovery/2026-02-05 copying botocore/data/marketplace-discovery/2026-02-05/paginators-1.json -> build/lib/botocore/data/marketplace-discovery/2026-02-05 copying botocore/data/marketplace-discovery/2026-02-05/paginators-1.sdk-extras.json -> build/lib/botocore/data/marketplace-discovery/2026-02-05 copying botocore/data/marketplace-discovery/2026-02-05/service-2.json -> build/lib/botocore/data/marketplace-discovery/2026-02-05 copying botocore/data/marketplace-discovery/2026-02-05/waiters-2.json -> build/lib/botocore/data/marketplace-discovery/2026-02-05 creating build/lib/botocore/data/marketplace-entitlement creating build/lib/botocore/data/marketplace-entitlement/2017-01-11 copying botocore/data/marketplace-entitlement/2017-01-11/endpoint-rule-set-1.json -> build/lib/botocore/data/marketplace-entitlement/2017-01-11 copying botocore/data/marketplace-entitlement/2017-01-11/examples-1.json -> build/lib/botocore/data/marketplace-entitlement/2017-01-11 copying botocore/data/marketplace-entitlement/2017-01-11/paginators-1.json -> build/lib/botocore/data/marketplace-entitlement/2017-01-11 copying botocore/data/marketplace-entitlement/2017-01-11/service-2.json -> build/lib/botocore/data/marketplace-entitlement/2017-01-11 creating build/lib/botocore/data/marketplace-reporting creating build/lib/botocore/data/marketplace-reporting/2018-05-10 copying botocore/data/marketplace-reporting/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/marketplace-reporting/2018-05-10 copying botocore/data/marketplace-reporting/2018-05-10/paginators-1.json -> build/lib/botocore/data/marketplace-reporting/2018-05-10 copying botocore/data/marketplace-reporting/2018-05-10/service-2.json -> build/lib/botocore/data/marketplace-reporting/2018-05-10 copying botocore/data/marketplace-reporting/2018-05-10/waiters-2.json -> build/lib/botocore/data/marketplace-reporting/2018-05-10 creating build/lib/botocore/data/marketplacecommerceanalytics creating build/lib/botocore/data/marketplacecommerceanalytics/2015-07-01 copying botocore/data/marketplacecommerceanalytics/2015-07-01/endpoint-rule-set-1.json -> build/lib/botocore/data/marketplacecommerceanalytics/2015-07-01 copying botocore/data/marketplacecommerceanalytics/2015-07-01/examples-1.json -> build/lib/botocore/data/marketplacecommerceanalytics/2015-07-01 copying botocore/data/marketplacecommerceanalytics/2015-07-01/paginators-1.json -> build/lib/botocore/data/marketplacecommerceanalytics/2015-07-01 copying botocore/data/marketplacecommerceanalytics/2015-07-01/service-2.json -> build/lib/botocore/data/marketplacecommerceanalytics/2015-07-01 creating build/lib/botocore/data/mediaconnect creating build/lib/botocore/data/mediaconnect/2018-11-14 copying botocore/data/mediaconnect/2018-11-14/endpoint-rule-set-1.json -> build/lib/botocore/data/mediaconnect/2018-11-14 copying botocore/data/mediaconnect/2018-11-14/paginators-1.json -> build/lib/botocore/data/mediaconnect/2018-11-14 copying botocore/data/mediaconnect/2018-11-14/service-2.json -> build/lib/botocore/data/mediaconnect/2018-11-14 copying botocore/data/mediaconnect/2018-11-14/waiters-2.json -> build/lib/botocore/data/mediaconnect/2018-11-14 creating build/lib/botocore/data/mediaconvert creating build/lib/botocore/data/mediaconvert/2017-08-29 copying botocore/data/mediaconvert/2017-08-29/endpoint-rule-set-1.json -> build/lib/botocore/data/mediaconvert/2017-08-29 copying botocore/data/mediaconvert/2017-08-29/paginators-1.json -> build/lib/botocore/data/mediaconvert/2017-08-29 copying botocore/data/mediaconvert/2017-08-29/paginators-1.sdk-extras.json -> build/lib/botocore/data/mediaconvert/2017-08-29 copying botocore/data/mediaconvert/2017-08-29/service-2.json -> build/lib/botocore/data/mediaconvert/2017-08-29 creating build/lib/botocore/data/medialive creating build/lib/botocore/data/medialive/2017-10-14 copying botocore/data/medialive/2017-10-14/endpoint-rule-set-1.json -> build/lib/botocore/data/medialive/2017-10-14 copying botocore/data/medialive/2017-10-14/paginators-1.json -> build/lib/botocore/data/medialive/2017-10-14 copying botocore/data/medialive/2017-10-14/service-2.json -> build/lib/botocore/data/medialive/2017-10-14 copying botocore/data/medialive/2017-10-14/waiters-2.json -> build/lib/botocore/data/medialive/2017-10-14 creating build/lib/botocore/data/mediapackage-vod creating build/lib/botocore/data/mediapackage-vod/2018-11-07 copying botocore/data/mediapackage-vod/2018-11-07/endpoint-rule-set-1.json -> build/lib/botocore/data/mediapackage-vod/2018-11-07 copying botocore/data/mediapackage-vod/2018-11-07/paginators-1.json -> build/lib/botocore/data/mediapackage-vod/2018-11-07 copying botocore/data/mediapackage-vod/2018-11-07/service-2.json -> build/lib/botocore/data/mediapackage-vod/2018-11-07 creating build/lib/botocore/data/mediapackage creating build/lib/botocore/data/mediapackage/2017-10-12 copying botocore/data/mediapackage/2017-10-12/endpoint-rule-set-1.json -> build/lib/botocore/data/mediapackage/2017-10-12 copying botocore/data/mediapackage/2017-10-12/paginators-1.json -> build/lib/botocore/data/mediapackage/2017-10-12 copying botocore/data/mediapackage/2017-10-12/service-2.json -> build/lib/botocore/data/mediapackage/2017-10-12 creating build/lib/botocore/data/mediapackagev2 creating build/lib/botocore/data/mediapackagev2/2022-12-25 copying botocore/data/mediapackagev2/2022-12-25/endpoint-rule-set-1.json -> build/lib/botocore/data/mediapackagev2/2022-12-25 copying botocore/data/mediapackagev2/2022-12-25/paginators-1.json -> build/lib/botocore/data/mediapackagev2/2022-12-25 copying botocore/data/mediapackagev2/2022-12-25/service-2.json -> build/lib/botocore/data/mediapackagev2/2022-12-25 copying botocore/data/mediapackagev2/2022-12-25/waiters-2.json -> build/lib/botocore/data/mediapackagev2/2022-12-25 creating build/lib/botocore/data/mediastore-data creating build/lib/botocore/data/mediastore-data/2017-09-01 copying botocore/data/mediastore-data/2017-09-01/endpoint-rule-set-1.json -> build/lib/botocore/data/mediastore-data/2017-09-01 copying botocore/data/mediastore-data/2017-09-01/examples-1.json -> build/lib/botocore/data/mediastore-data/2017-09-01 copying botocore/data/mediastore-data/2017-09-01/paginators-1.json -> build/lib/botocore/data/mediastore-data/2017-09-01 copying botocore/data/mediastore-data/2017-09-01/service-2.json -> build/lib/botocore/data/mediastore-data/2017-09-01 creating build/lib/botocore/data/mediastore creating build/lib/botocore/data/mediastore/2017-09-01 copying botocore/data/mediastore/2017-09-01/endpoint-rule-set-1.json -> build/lib/botocore/data/mediastore/2017-09-01 copying botocore/data/mediastore/2017-09-01/examples-1.json -> build/lib/botocore/data/mediastore/2017-09-01 copying botocore/data/mediastore/2017-09-01/paginators-1.json -> build/lib/botocore/data/mediastore/2017-09-01 copying botocore/data/mediastore/2017-09-01/service-2.json -> build/lib/botocore/data/mediastore/2017-09-01 creating build/lib/botocore/data/mediatailor creating build/lib/botocore/data/mediatailor/2018-04-23 copying botocore/data/mediatailor/2018-04-23/endpoint-rule-set-1.json -> build/lib/botocore/data/mediatailor/2018-04-23 copying botocore/data/mediatailor/2018-04-23/paginators-1.json -> build/lib/botocore/data/mediatailor/2018-04-23 copying botocore/data/mediatailor/2018-04-23/service-2.json -> build/lib/botocore/data/mediatailor/2018-04-23 creating build/lib/botocore/data/medical-imaging creating build/lib/botocore/data/medical-imaging/2023-07-19 copying botocore/data/medical-imaging/2023-07-19/endpoint-rule-set-1.json -> build/lib/botocore/data/medical-imaging/2023-07-19 copying botocore/data/medical-imaging/2023-07-19/paginators-1.json -> build/lib/botocore/data/medical-imaging/2023-07-19 copying botocore/data/medical-imaging/2023-07-19/paginators-1.sdk-extras.json -> build/lib/botocore/data/medical-imaging/2023-07-19 copying botocore/data/medical-imaging/2023-07-19/service-2.json -> build/lib/botocore/data/medical-imaging/2023-07-19 copying botocore/data/medical-imaging/2023-07-19/waiters-2.json -> build/lib/botocore/data/medical-imaging/2023-07-19 creating build/lib/botocore/data/memorydb creating build/lib/botocore/data/memorydb/2021-01-01 copying botocore/data/memorydb/2021-01-01/endpoint-rule-set-1.json -> build/lib/botocore/data/memorydb/2021-01-01 copying botocore/data/memorydb/2021-01-01/examples-1.json -> build/lib/botocore/data/memorydb/2021-01-01 copying botocore/data/memorydb/2021-01-01/paginators-1.json -> build/lib/botocore/data/memorydb/2021-01-01 copying botocore/data/memorydb/2021-01-01/service-2.json -> build/lib/botocore/data/memorydb/2021-01-01 creating build/lib/botocore/data/meteringmarketplace creating build/lib/botocore/data/meteringmarketplace/2016-01-14 copying botocore/data/meteringmarketplace/2016-01-14/endpoint-rule-set-1.json -> build/lib/botocore/data/meteringmarketplace/2016-01-14 copying botocore/data/meteringmarketplace/2016-01-14/examples-1.json -> build/lib/botocore/data/meteringmarketplace/2016-01-14 copying botocore/data/meteringmarketplace/2016-01-14/paginators-1.json -> build/lib/botocore/data/meteringmarketplace/2016-01-14 copying botocore/data/meteringmarketplace/2016-01-14/service-2.json -> build/lib/botocore/data/meteringmarketplace/2016-01-14 creating build/lib/botocore/data/mgh creating build/lib/botocore/data/mgh/2017-05-31 copying botocore/data/mgh/2017-05-31/endpoint-rule-set-1.json -> build/lib/botocore/data/mgh/2017-05-31 copying botocore/data/mgh/2017-05-31/examples-1.json -> build/lib/botocore/data/mgh/2017-05-31 copying botocore/data/mgh/2017-05-31/paginators-1.json -> build/lib/botocore/data/mgh/2017-05-31 copying botocore/data/mgh/2017-05-31/service-2.json -> build/lib/botocore/data/mgh/2017-05-31 creating build/lib/botocore/data/mgn creating build/lib/botocore/data/mgn/2020-02-26 copying botocore/data/mgn/2020-02-26/endpoint-rule-set-1.json -> build/lib/botocore/data/mgn/2020-02-26 copying botocore/data/mgn/2020-02-26/examples-1.json -> build/lib/botocore/data/mgn/2020-02-26 copying botocore/data/mgn/2020-02-26/paginators-1.json -> build/lib/botocore/data/mgn/2020-02-26 copying botocore/data/mgn/2020-02-26/service-2.json -> build/lib/botocore/data/mgn/2020-02-26 copying botocore/data/mgn/2020-02-26/waiters-2.json -> build/lib/botocore/data/mgn/2020-02-26 creating build/lib/botocore/data/migration-hub-refactor-spaces creating build/lib/botocore/data/migration-hub-refactor-spaces/2021-10-26 copying botocore/data/migration-hub-refactor-spaces/2021-10-26/endpoint-rule-set-1.json -> build/lib/botocore/data/migration-hub-refactor-spaces/2021-10-26 copying botocore/data/migration-hub-refactor-spaces/2021-10-26/examples-1.json -> build/lib/botocore/data/migration-hub-refactor-spaces/2021-10-26 copying botocore/data/migration-hub-refactor-spaces/2021-10-26/paginators-1.json -> build/lib/botocore/data/migration-hub-refactor-spaces/2021-10-26 copying botocore/data/migration-hub-refactor-spaces/2021-10-26/service-2.json -> build/lib/botocore/data/migration-hub-refactor-spaces/2021-10-26 creating build/lib/botocore/data/migrationhub-config creating build/lib/botocore/data/migrationhub-config/2019-06-30 copying botocore/data/migrationhub-config/2019-06-30/endpoint-rule-set-1.json -> build/lib/botocore/data/migrationhub-config/2019-06-30 copying botocore/data/migrationhub-config/2019-06-30/examples-1.json -> build/lib/botocore/data/migrationhub-config/2019-06-30 copying botocore/data/migrationhub-config/2019-06-30/paginators-1.json -> build/lib/botocore/data/migrationhub-config/2019-06-30 copying botocore/data/migrationhub-config/2019-06-30/service-2.json -> build/lib/botocore/data/migrationhub-config/2019-06-30 creating build/lib/botocore/data/migrationhuborchestrator creating build/lib/botocore/data/migrationhuborchestrator/2021-08-28 copying botocore/data/migrationhuborchestrator/2021-08-28/endpoint-rule-set-1.json -> build/lib/botocore/data/migrationhuborchestrator/2021-08-28 copying botocore/data/migrationhuborchestrator/2021-08-28/paginators-1.json -> build/lib/botocore/data/migrationhuborchestrator/2021-08-28 copying botocore/data/migrationhuborchestrator/2021-08-28/service-2.json -> build/lib/botocore/data/migrationhuborchestrator/2021-08-28 copying botocore/data/migrationhuborchestrator/2021-08-28/waiters-2.json -> build/lib/botocore/data/migrationhuborchestrator/2021-08-28 creating build/lib/botocore/data/migrationhubstrategy creating build/lib/botocore/data/migrationhubstrategy/2020-02-19 copying botocore/data/migrationhubstrategy/2020-02-19/endpoint-rule-set-1.json -> build/lib/botocore/data/migrationhubstrategy/2020-02-19 copying botocore/data/migrationhubstrategy/2020-02-19/examples-1.json -> build/lib/botocore/data/migrationhubstrategy/2020-02-19 copying botocore/data/migrationhubstrategy/2020-02-19/paginators-1.json -> build/lib/botocore/data/migrationhubstrategy/2020-02-19 copying botocore/data/migrationhubstrategy/2020-02-19/paginators-1.sdk-extras.json -> build/lib/botocore/data/migrationhubstrategy/2020-02-19 copying botocore/data/migrationhubstrategy/2020-02-19/service-2.json -> build/lib/botocore/data/migrationhubstrategy/2020-02-19 creating build/lib/botocore/data/mpa creating build/lib/botocore/data/mpa/2022-07-26 copying botocore/data/mpa/2022-07-26/endpoint-rule-set-1.json -> build/lib/botocore/data/mpa/2022-07-26 copying botocore/data/mpa/2022-07-26/paginators-1.json -> build/lib/botocore/data/mpa/2022-07-26 copying botocore/data/mpa/2022-07-26/service-2.json -> build/lib/botocore/data/mpa/2022-07-26 copying botocore/data/mpa/2022-07-26/waiters-2.json -> build/lib/botocore/data/mpa/2022-07-26 creating build/lib/botocore/data/mq creating build/lib/botocore/data/mq/2017-11-27 copying botocore/data/mq/2017-11-27/endpoint-rule-set-1.json -> build/lib/botocore/data/mq/2017-11-27 copying botocore/data/mq/2017-11-27/paginators-1.json -> build/lib/botocore/data/mq/2017-11-27 copying botocore/data/mq/2017-11-27/service-2.json -> build/lib/botocore/data/mq/2017-11-27 creating build/lib/botocore/data/mturk creating build/lib/botocore/data/mturk/2017-01-17 copying botocore/data/mturk/2017-01-17/endpoint-rule-set-1.json -> build/lib/botocore/data/mturk/2017-01-17 copying botocore/data/mturk/2017-01-17/examples-1.json -> build/lib/botocore/data/mturk/2017-01-17 copying botocore/data/mturk/2017-01-17/paginators-1.json -> build/lib/botocore/data/mturk/2017-01-17 copying botocore/data/mturk/2017-01-17/service-2.json -> build/lib/botocore/data/mturk/2017-01-17 creating build/lib/botocore/data/mwaa-serverless creating build/lib/botocore/data/mwaa-serverless/2024-07-26 copying botocore/data/mwaa-serverless/2024-07-26/endpoint-rule-set-1.json -> build/lib/botocore/data/mwaa-serverless/2024-07-26 copying botocore/data/mwaa-serverless/2024-07-26/paginators-1.json -> build/lib/botocore/data/mwaa-serverless/2024-07-26 copying botocore/data/mwaa-serverless/2024-07-26/service-2.json -> build/lib/botocore/data/mwaa-serverless/2024-07-26 copying botocore/data/mwaa-serverless/2024-07-26/waiters-2.json -> build/lib/botocore/data/mwaa-serverless/2024-07-26 creating build/lib/botocore/data/mwaa creating build/lib/botocore/data/mwaa/2020-07-01 copying botocore/data/mwaa/2020-07-01/endpoint-rule-set-1.json -> build/lib/botocore/data/mwaa/2020-07-01 copying botocore/data/mwaa/2020-07-01/examples-1.json -> build/lib/botocore/data/mwaa/2020-07-01 copying botocore/data/mwaa/2020-07-01/paginators-1.json -> build/lib/botocore/data/mwaa/2020-07-01 copying botocore/data/mwaa/2020-07-01/service-2.json -> build/lib/botocore/data/mwaa/2020-07-01 creating build/lib/botocore/data/neptune-graph creating build/lib/botocore/data/neptune-graph/2023-11-29 copying botocore/data/neptune-graph/2023-11-29/endpoint-rule-set-1.json -> build/lib/botocore/data/neptune-graph/2023-11-29 copying botocore/data/neptune-graph/2023-11-29/paginators-1.json -> build/lib/botocore/data/neptune-graph/2023-11-29 copying botocore/data/neptune-graph/2023-11-29/service-2.json -> build/lib/botocore/data/neptune-graph/2023-11-29 copying botocore/data/neptune-graph/2023-11-29/waiters-2.json -> build/lib/botocore/data/neptune-graph/2023-11-29 creating build/lib/botocore/data/neptune creating build/lib/botocore/data/neptune/2014-10-31 copying botocore/data/neptune/2014-10-31/endpoint-rule-set-1.json -> build/lib/botocore/data/neptune/2014-10-31 copying botocore/data/neptune/2014-10-31/examples-1.json -> build/lib/botocore/data/neptune/2014-10-31 copying botocore/data/neptune/2014-10-31/paginators-1.json -> build/lib/botocore/data/neptune/2014-10-31 copying botocore/data/neptune/2014-10-31/service-2.json -> build/lib/botocore/data/neptune/2014-10-31 copying botocore/data/neptune/2014-10-31/service-2.sdk-extras.json -> build/lib/botocore/data/neptune/2014-10-31 copying botocore/data/neptune/2014-10-31/waiters-2.json -> build/lib/botocore/data/neptune/2014-10-31 creating build/lib/botocore/data/neptunedata creating build/lib/botocore/data/neptunedata/2023-08-01 copying botocore/data/neptunedata/2023-08-01/endpoint-rule-set-1.json -> build/lib/botocore/data/neptunedata/2023-08-01 copying botocore/data/neptunedata/2023-08-01/paginators-1.json -> build/lib/botocore/data/neptunedata/2023-08-01 copying botocore/data/neptunedata/2023-08-01/service-2.json -> build/lib/botocore/data/neptunedata/2023-08-01 creating build/lib/botocore/data/network-firewall creating build/lib/botocore/data/network-firewall/2020-11-12 copying botocore/data/network-firewall/2020-11-12/endpoint-rule-set-1.json -> build/lib/botocore/data/network-firewall/2020-11-12 copying botocore/data/network-firewall/2020-11-12/examples-1.json -> build/lib/botocore/data/network-firewall/2020-11-12 copying botocore/data/network-firewall/2020-11-12/paginators-1.json -> build/lib/botocore/data/network-firewall/2020-11-12 copying botocore/data/network-firewall/2020-11-12/paginators-1.sdk-extras.json -> build/lib/botocore/data/network-firewall/2020-11-12 copying botocore/data/network-firewall/2020-11-12/service-2.json -> build/lib/botocore/data/network-firewall/2020-11-12 creating build/lib/botocore/data/networkflowmonitor creating build/lib/botocore/data/networkflowmonitor/2023-04-19 copying botocore/data/networkflowmonitor/2023-04-19/endpoint-rule-set-1.json -> build/lib/botocore/data/networkflowmonitor/2023-04-19 copying botocore/data/networkflowmonitor/2023-04-19/paginators-1.json -> build/lib/botocore/data/networkflowmonitor/2023-04-19 copying botocore/data/networkflowmonitor/2023-04-19/paginators-1.sdk-extras.json -> build/lib/botocore/data/networkflowmonitor/2023-04-19 copying botocore/data/networkflowmonitor/2023-04-19/service-2.json -> build/lib/botocore/data/networkflowmonitor/2023-04-19 copying botocore/data/networkflowmonitor/2023-04-19/waiters-2.json -> build/lib/botocore/data/networkflowmonitor/2023-04-19 creating build/lib/botocore/data/networkmanager creating build/lib/botocore/data/networkmanager/2019-07-05 copying botocore/data/networkmanager/2019-07-05/endpoint-rule-set-1.json -> build/lib/botocore/data/networkmanager/2019-07-05 copying botocore/data/networkmanager/2019-07-05/examples-1.json -> build/lib/botocore/data/networkmanager/2019-07-05 copying botocore/data/networkmanager/2019-07-05/paginators-1.json -> build/lib/botocore/data/networkmanager/2019-07-05 copying botocore/data/networkmanager/2019-07-05/service-2.json -> build/lib/botocore/data/networkmanager/2019-07-05 creating build/lib/botocore/data/networkmonitor creating build/lib/botocore/data/networkmonitor/2023-08-01 copying botocore/data/networkmonitor/2023-08-01/endpoint-rule-set-1.json -> build/lib/botocore/data/networkmonitor/2023-08-01 copying botocore/data/networkmonitor/2023-08-01/paginators-1.json -> build/lib/botocore/data/networkmonitor/2023-08-01 copying botocore/data/networkmonitor/2023-08-01/service-2.json -> build/lib/botocore/data/networkmonitor/2023-08-01 copying botocore/data/networkmonitor/2023-08-01/waiters-2.json -> build/lib/botocore/data/networkmonitor/2023-08-01 creating build/lib/botocore/data/notifications creating build/lib/botocore/data/notifications/2018-05-10 copying botocore/data/notifications/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/notifications/2018-05-10 copying botocore/data/notifications/2018-05-10/paginators-1.json -> build/lib/botocore/data/notifications/2018-05-10 copying botocore/data/notifications/2018-05-10/service-2.json -> build/lib/botocore/data/notifications/2018-05-10 copying botocore/data/notifications/2018-05-10/waiters-2.json -> build/lib/botocore/data/notifications/2018-05-10 creating build/lib/botocore/data/notificationscontacts creating build/lib/botocore/data/notificationscontacts/2018-05-10 copying botocore/data/notificationscontacts/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/notificationscontacts/2018-05-10 copying botocore/data/notificationscontacts/2018-05-10/paginators-1.json -> build/lib/botocore/data/notificationscontacts/2018-05-10 copying botocore/data/notificationscontacts/2018-05-10/service-2.json -> build/lib/botocore/data/notificationscontacts/2018-05-10 copying botocore/data/notificationscontacts/2018-05-10/waiters-2.json -> build/lib/botocore/data/notificationscontacts/2018-05-10 creating build/lib/botocore/data/nova-act creating build/lib/botocore/data/nova-act/2025-08-22 copying botocore/data/nova-act/2025-08-22/endpoint-rule-set-1.json -> build/lib/botocore/data/nova-act/2025-08-22 copying botocore/data/nova-act/2025-08-22/paginators-1.json -> build/lib/botocore/data/nova-act/2025-08-22 copying botocore/data/nova-act/2025-08-22/service-2.json -> build/lib/botocore/data/nova-act/2025-08-22 copying botocore/data/nova-act/2025-08-22/waiters-2.json -> build/lib/botocore/data/nova-act/2025-08-22 creating build/lib/botocore/data/oam creating build/lib/botocore/data/oam/2022-06-10 copying botocore/data/oam/2022-06-10/endpoint-rule-set-1.json -> build/lib/botocore/data/oam/2022-06-10 copying botocore/data/oam/2022-06-10/paginators-1.json -> build/lib/botocore/data/oam/2022-06-10 copying botocore/data/oam/2022-06-10/service-2.json -> build/lib/botocore/data/oam/2022-06-10 creating build/lib/botocore/data/observabilityadmin creating build/lib/botocore/data/observabilityadmin/2018-05-10 copying botocore/data/observabilityadmin/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/observabilityadmin/2018-05-10 copying botocore/data/observabilityadmin/2018-05-10/paginators-1.json -> build/lib/botocore/data/observabilityadmin/2018-05-10 copying botocore/data/observabilityadmin/2018-05-10/service-2.json -> build/lib/botocore/data/observabilityadmin/2018-05-10 copying botocore/data/observabilityadmin/2018-05-10/waiters-2.json -> build/lib/botocore/data/observabilityadmin/2018-05-10 creating build/lib/botocore/data/odb creating build/lib/botocore/data/odb/2024-08-20 copying botocore/data/odb/2024-08-20/endpoint-rule-set-1.json -> build/lib/botocore/data/odb/2024-08-20 copying botocore/data/odb/2024-08-20/paginators-1.json -> build/lib/botocore/data/odb/2024-08-20 copying botocore/data/odb/2024-08-20/service-2.json -> build/lib/botocore/data/odb/2024-08-20 copying botocore/data/odb/2024-08-20/waiters-2.json -> build/lib/botocore/data/odb/2024-08-20 creating build/lib/botocore/data/omics creating build/lib/botocore/data/omics/2022-11-28 copying botocore/data/omics/2022-11-28/endpoint-rule-set-1.json -> build/lib/botocore/data/omics/2022-11-28 copying botocore/data/omics/2022-11-28/paginators-1.json -> build/lib/botocore/data/omics/2022-11-28 copying botocore/data/omics/2022-11-28/service-2.json -> build/lib/botocore/data/omics/2022-11-28 copying botocore/data/omics/2022-11-28/waiters-2.json -> build/lib/botocore/data/omics/2022-11-28 creating build/lib/botocore/data/opensearch creating build/lib/botocore/data/opensearch/2021-01-01 copying botocore/data/opensearch/2021-01-01/endpoint-rule-set-1.json -> build/lib/botocore/data/opensearch/2021-01-01 copying botocore/data/opensearch/2021-01-01/examples-1.json -> build/lib/botocore/data/opensearch/2021-01-01 copying botocore/data/opensearch/2021-01-01/paginators-1.json -> build/lib/botocore/data/opensearch/2021-01-01 copying botocore/data/opensearch/2021-01-01/service-2.json -> build/lib/botocore/data/opensearch/2021-01-01 creating build/lib/botocore/data/opensearchserverless creating build/lib/botocore/data/opensearchserverless/2021-11-01 copying botocore/data/opensearchserverless/2021-11-01/endpoint-rule-set-1.json -> build/lib/botocore/data/opensearchserverless/2021-11-01 copying botocore/data/opensearchserverless/2021-11-01/paginators-1.json -> build/lib/botocore/data/opensearchserverless/2021-11-01 copying botocore/data/opensearchserverless/2021-11-01/service-2.json -> build/lib/botocore/data/opensearchserverless/2021-11-01 copying botocore/data/opensearchserverless/2021-11-01/waiters-2.json -> build/lib/botocore/data/opensearchserverless/2021-11-01 creating build/lib/botocore/data/organizations creating build/lib/botocore/data/organizations/2016-11-28 copying botocore/data/organizations/2016-11-28/endpoint-rule-set-1.json -> build/lib/botocore/data/organizations/2016-11-28 copying botocore/data/organizations/2016-11-28/examples-1.json -> build/lib/botocore/data/organizations/2016-11-28 copying botocore/data/organizations/2016-11-28/paginators-1.json -> build/lib/botocore/data/organizations/2016-11-28 copying botocore/data/organizations/2016-11-28/paginators-1.sdk-extras.json -> build/lib/botocore/data/organizations/2016-11-28 copying botocore/data/organizations/2016-11-28/service-2.json -> build/lib/botocore/data/organizations/2016-11-28 creating build/lib/botocore/data/osis creating build/lib/botocore/data/osis/2022-01-01 copying botocore/data/osis/2022-01-01/endpoint-rule-set-1.json -> build/lib/botocore/data/osis/2022-01-01 copying botocore/data/osis/2022-01-01/paginators-1.json -> build/lib/botocore/data/osis/2022-01-01 copying botocore/data/osis/2022-01-01/service-2.json -> build/lib/botocore/data/osis/2022-01-01 creating build/lib/botocore/data/outposts creating build/lib/botocore/data/outposts/2019-12-03 copying botocore/data/outposts/2019-12-03/endpoint-rule-set-1.json -> build/lib/botocore/data/outposts/2019-12-03 copying botocore/data/outposts/2019-12-03/examples-1.json -> build/lib/botocore/data/outposts/2019-12-03 copying botocore/data/outposts/2019-12-03/paginators-1.json -> build/lib/botocore/data/outposts/2019-12-03 copying botocore/data/outposts/2019-12-03/paginators-1.sdk-extras.json -> build/lib/botocore/data/outposts/2019-12-03 copying botocore/data/outposts/2019-12-03/service-2.json -> build/lib/botocore/data/outposts/2019-12-03 creating build/lib/botocore/data/panorama creating build/lib/botocore/data/panorama/2019-07-24 copying botocore/data/panorama/2019-07-24/endpoint-rule-set-1.json -> build/lib/botocore/data/panorama/2019-07-24 copying botocore/data/panorama/2019-07-24/examples-1.json -> build/lib/botocore/data/panorama/2019-07-24 copying botocore/data/panorama/2019-07-24/paginators-1.json -> build/lib/botocore/data/panorama/2019-07-24 copying botocore/data/panorama/2019-07-24/service-2.json -> build/lib/botocore/data/panorama/2019-07-24 creating build/lib/botocore/data/partnercentral-account creating build/lib/botocore/data/partnercentral-account/2025-04-04 copying botocore/data/partnercentral-account/2025-04-04/endpoint-rule-set-1.json -> build/lib/botocore/data/partnercentral-account/2025-04-04 copying botocore/data/partnercentral-account/2025-04-04/paginators-1.json -> build/lib/botocore/data/partnercentral-account/2025-04-04 copying botocore/data/partnercentral-account/2025-04-04/service-2.json -> build/lib/botocore/data/partnercentral-account/2025-04-04 copying botocore/data/partnercentral-account/2025-04-04/waiters-2.json -> build/lib/botocore/data/partnercentral-account/2025-04-04 creating build/lib/botocore/data/partnercentral-benefits creating build/lib/botocore/data/partnercentral-benefits/2018-05-10 copying botocore/data/partnercentral-benefits/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/partnercentral-benefits/2018-05-10 copying botocore/data/partnercentral-benefits/2018-05-10/paginators-1.json -> build/lib/botocore/data/partnercentral-benefits/2018-05-10 copying botocore/data/partnercentral-benefits/2018-05-10/service-2.json -> build/lib/botocore/data/partnercentral-benefits/2018-05-10 copying botocore/data/partnercentral-benefits/2018-05-10/waiters-2.json -> build/lib/botocore/data/partnercentral-benefits/2018-05-10 creating build/lib/botocore/data/partnercentral-channel creating build/lib/botocore/data/partnercentral-channel/2024-03-18 copying botocore/data/partnercentral-channel/2024-03-18/endpoint-rule-set-1.json -> build/lib/botocore/data/partnercentral-channel/2024-03-18 copying botocore/data/partnercentral-channel/2024-03-18/paginators-1.json -> build/lib/botocore/data/partnercentral-channel/2024-03-18 copying botocore/data/partnercentral-channel/2024-03-18/service-2.json -> build/lib/botocore/data/partnercentral-channel/2024-03-18 copying botocore/data/partnercentral-channel/2024-03-18/waiters-2.json -> build/lib/botocore/data/partnercentral-channel/2024-03-18 creating build/lib/botocore/data/partnercentral-selling creating build/lib/botocore/data/partnercentral-selling/2022-07-26 copying botocore/data/partnercentral-selling/2022-07-26/endpoint-rule-set-1.json -> build/lib/botocore/data/partnercentral-selling/2022-07-26 copying botocore/data/partnercentral-selling/2022-07-26/paginators-1.json -> build/lib/botocore/data/partnercentral-selling/2022-07-26 copying botocore/data/partnercentral-selling/2022-07-26/service-2.json -> build/lib/botocore/data/partnercentral-selling/2022-07-26 copying botocore/data/partnercentral-selling/2022-07-26/waiters-2.json -> build/lib/botocore/data/partnercentral-selling/2022-07-26 creating build/lib/botocore/data/payment-cryptography-data creating build/lib/botocore/data/payment-cryptography-data/2022-02-03 copying botocore/data/payment-cryptography-data/2022-02-03/endpoint-rule-set-1.json -> build/lib/botocore/data/payment-cryptography-data/2022-02-03 copying botocore/data/payment-cryptography-data/2022-02-03/paginators-1.json -> build/lib/botocore/data/payment-cryptography-data/2022-02-03 copying botocore/data/payment-cryptography-data/2022-02-03/service-2.json -> build/lib/botocore/data/payment-cryptography-data/2022-02-03 copying botocore/data/payment-cryptography-data/2022-02-03/waiters-2.json -> build/lib/botocore/data/payment-cryptography-data/2022-02-03 creating build/lib/botocore/data/payment-cryptography creating build/lib/botocore/data/payment-cryptography/2021-09-14 copying botocore/data/payment-cryptography/2021-09-14/endpoint-rule-set-1.json -> build/lib/botocore/data/payment-cryptography/2021-09-14 copying botocore/data/payment-cryptography/2021-09-14/paginators-1.json -> build/lib/botocore/data/payment-cryptography/2021-09-14 copying botocore/data/payment-cryptography/2021-09-14/service-2.json -> build/lib/botocore/data/payment-cryptography/2021-09-14 copying botocore/data/payment-cryptography/2021-09-14/waiters-2.json -> build/lib/botocore/data/payment-cryptography/2021-09-14 creating build/lib/botocore/data/pca-connector-ad creating build/lib/botocore/data/pca-connector-ad/2018-05-10 copying botocore/data/pca-connector-ad/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/pca-connector-ad/2018-05-10 copying botocore/data/pca-connector-ad/2018-05-10/paginators-1.json -> build/lib/botocore/data/pca-connector-ad/2018-05-10 copying botocore/data/pca-connector-ad/2018-05-10/service-2.json -> build/lib/botocore/data/pca-connector-ad/2018-05-10 creating build/lib/botocore/data/pca-connector-scep creating build/lib/botocore/data/pca-connector-scep/2018-05-10 copying botocore/data/pca-connector-scep/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/pca-connector-scep/2018-05-10 copying botocore/data/pca-connector-scep/2018-05-10/paginators-1.json -> build/lib/botocore/data/pca-connector-scep/2018-05-10 copying botocore/data/pca-connector-scep/2018-05-10/service-2.json -> build/lib/botocore/data/pca-connector-scep/2018-05-10 copying botocore/data/pca-connector-scep/2018-05-10/waiters-2.json -> build/lib/botocore/data/pca-connector-scep/2018-05-10 creating build/lib/botocore/data/pcs creating build/lib/botocore/data/pcs/2023-02-10 copying botocore/data/pcs/2023-02-10/endpoint-rule-set-1.json -> build/lib/botocore/data/pcs/2023-02-10 copying botocore/data/pcs/2023-02-10/paginators-1.json -> build/lib/botocore/data/pcs/2023-02-10 copying botocore/data/pcs/2023-02-10/service-2.json -> build/lib/botocore/data/pcs/2023-02-10 copying botocore/data/pcs/2023-02-10/waiters-2.json -> build/lib/botocore/data/pcs/2023-02-10 creating build/lib/botocore/data/personalize-events creating build/lib/botocore/data/personalize-events/2018-03-22 copying botocore/data/personalize-events/2018-03-22/endpoint-rule-set-1.json -> build/lib/botocore/data/personalize-events/2018-03-22 copying botocore/data/personalize-events/2018-03-22/examples-1.json -> build/lib/botocore/data/personalize-events/2018-03-22 copying botocore/data/personalize-events/2018-03-22/paginators-1.json -> build/lib/botocore/data/personalize-events/2018-03-22 copying botocore/data/personalize-events/2018-03-22/service-2.json -> build/lib/botocore/data/personalize-events/2018-03-22 creating build/lib/botocore/data/personalize-runtime creating build/lib/botocore/data/personalize-runtime/2018-05-22 copying botocore/data/personalize-runtime/2018-05-22/endpoint-rule-set-1.json -> build/lib/botocore/data/personalize-runtime/2018-05-22 copying botocore/data/personalize-runtime/2018-05-22/examples-1.json -> build/lib/botocore/data/personalize-runtime/2018-05-22 copying botocore/data/personalize-runtime/2018-05-22/paginators-1.json -> build/lib/botocore/data/personalize-runtime/2018-05-22 copying botocore/data/personalize-runtime/2018-05-22/service-2.json -> build/lib/botocore/data/personalize-runtime/2018-05-22 creating build/lib/botocore/data/personalize creating build/lib/botocore/data/personalize/2018-05-22 copying botocore/data/personalize/2018-05-22/endpoint-rule-set-1.json -> build/lib/botocore/data/personalize/2018-05-22 copying botocore/data/personalize/2018-05-22/examples-1.json -> build/lib/botocore/data/personalize/2018-05-22 copying botocore/data/personalize/2018-05-22/paginators-1.json -> build/lib/botocore/data/personalize/2018-05-22 copying botocore/data/personalize/2018-05-22/service-2.json -> build/lib/botocore/data/personalize/2018-05-22 creating build/lib/botocore/data/pi creating build/lib/botocore/data/pi/2018-02-27 copying botocore/data/pi/2018-02-27/endpoint-rule-set-1.json -> build/lib/botocore/data/pi/2018-02-27 copying botocore/data/pi/2018-02-27/examples-1.json -> build/lib/botocore/data/pi/2018-02-27 copying botocore/data/pi/2018-02-27/paginators-1.json -> build/lib/botocore/data/pi/2018-02-27 copying botocore/data/pi/2018-02-27/service-2.json -> build/lib/botocore/data/pi/2018-02-27 creating build/lib/botocore/data/pinpoint-email creating build/lib/botocore/data/pinpoint-email/2018-07-26 copying botocore/data/pinpoint-email/2018-07-26/endpoint-rule-set-1.json -> build/lib/botocore/data/pinpoint-email/2018-07-26 copying botocore/data/pinpoint-email/2018-07-26/examples-1.json -> build/lib/botocore/data/pinpoint-email/2018-07-26 copying botocore/data/pinpoint-email/2018-07-26/paginators-1.json -> build/lib/botocore/data/pinpoint-email/2018-07-26 copying botocore/data/pinpoint-email/2018-07-26/service-2.json -> build/lib/botocore/data/pinpoint-email/2018-07-26 creating build/lib/botocore/data/pinpoint-sms-voice-v2 creating build/lib/botocore/data/pinpoint-sms-voice-v2/2022-03-31 copying botocore/data/pinpoint-sms-voice-v2/2022-03-31/endpoint-rule-set-1.json -> build/lib/botocore/data/pinpoint-sms-voice-v2/2022-03-31 copying botocore/data/pinpoint-sms-voice-v2/2022-03-31/examples-1.json -> build/lib/botocore/data/pinpoint-sms-voice-v2/2022-03-31 copying botocore/data/pinpoint-sms-voice-v2/2022-03-31/paginators-1.json -> build/lib/botocore/data/pinpoint-sms-voice-v2/2022-03-31 copying botocore/data/pinpoint-sms-voice-v2/2022-03-31/paginators-1.sdk-extras.json -> build/lib/botocore/data/pinpoint-sms-voice-v2/2022-03-31 copying botocore/data/pinpoint-sms-voice-v2/2022-03-31/service-2.json -> build/lib/botocore/data/pinpoint-sms-voice-v2/2022-03-31 copying botocore/data/pinpoint-sms-voice-v2/2022-03-31/waiters-2.json -> build/lib/botocore/data/pinpoint-sms-voice-v2/2022-03-31 creating build/lib/botocore/data/pinpoint-sms-voice creating build/lib/botocore/data/pinpoint-sms-voice/2018-09-05 copying botocore/data/pinpoint-sms-voice/2018-09-05/endpoint-rule-set-1.json -> build/lib/botocore/data/pinpoint-sms-voice/2018-09-05 copying botocore/data/pinpoint-sms-voice/2018-09-05/service-2.json -> build/lib/botocore/data/pinpoint-sms-voice/2018-09-05 creating build/lib/botocore/data/pinpoint creating build/lib/botocore/data/pinpoint/2016-12-01 copying botocore/data/pinpoint/2016-12-01/endpoint-rule-set-1.json -> build/lib/botocore/data/pinpoint/2016-12-01 copying botocore/data/pinpoint/2016-12-01/examples-1.json -> build/lib/botocore/data/pinpoint/2016-12-01 copying botocore/data/pinpoint/2016-12-01/service-2.json -> build/lib/botocore/data/pinpoint/2016-12-01 creating build/lib/botocore/data/pipes creating build/lib/botocore/data/pipes/2015-10-07 copying botocore/data/pipes/2015-10-07/endpoint-rule-set-1.json -> build/lib/botocore/data/pipes/2015-10-07 copying botocore/data/pipes/2015-10-07/paginators-1.json -> build/lib/botocore/data/pipes/2015-10-07 copying botocore/data/pipes/2015-10-07/service-2.json -> build/lib/botocore/data/pipes/2015-10-07 copying botocore/data/pipes/2015-10-07/waiters-2.json -> build/lib/botocore/data/pipes/2015-10-07 creating build/lib/botocore/data/polly creating build/lib/botocore/data/polly/2016-06-10 copying botocore/data/polly/2016-06-10/endpoint-rule-set-1.json -> build/lib/botocore/data/polly/2016-06-10 copying botocore/data/polly/2016-06-10/examples-1.json -> build/lib/botocore/data/polly/2016-06-10 copying botocore/data/polly/2016-06-10/paginators-1.json -> build/lib/botocore/data/polly/2016-06-10 copying botocore/data/polly/2016-06-10/service-2.json -> build/lib/botocore/data/polly/2016-06-10 creating build/lib/botocore/data/pricing creating build/lib/botocore/data/pricing/2017-10-15 copying botocore/data/pricing/2017-10-15/endpoint-rule-set-1.json -> build/lib/botocore/data/pricing/2017-10-15 copying botocore/data/pricing/2017-10-15/examples-1.json -> build/lib/botocore/data/pricing/2017-10-15 copying botocore/data/pricing/2017-10-15/paginators-1.json -> build/lib/botocore/data/pricing/2017-10-15 copying botocore/data/pricing/2017-10-15/service-2.json -> build/lib/botocore/data/pricing/2017-10-15 copying botocore/data/pricing/2017-10-15/waiters-2.json -> build/lib/botocore/data/pricing/2017-10-15 creating build/lib/botocore/data/proton creating build/lib/botocore/data/proton/2020-07-20 copying botocore/data/proton/2020-07-20/endpoint-rule-set-1.json -> build/lib/botocore/data/proton/2020-07-20 copying botocore/data/proton/2020-07-20/examples-1.json -> build/lib/botocore/data/proton/2020-07-20 copying botocore/data/proton/2020-07-20/paginators-1.json -> build/lib/botocore/data/proton/2020-07-20 copying botocore/data/proton/2020-07-20/service-2.json -> build/lib/botocore/data/proton/2020-07-20 copying botocore/data/proton/2020-07-20/waiters-2.json -> build/lib/botocore/data/proton/2020-07-20 creating build/lib/botocore/data/qapps creating build/lib/botocore/data/qapps/2023-11-27 copying botocore/data/qapps/2023-11-27/endpoint-rule-set-1.json -> build/lib/botocore/data/qapps/2023-11-27 copying botocore/data/qapps/2023-11-27/paginators-1.json -> build/lib/botocore/data/qapps/2023-11-27 copying botocore/data/qapps/2023-11-27/service-2.json -> build/lib/botocore/data/qapps/2023-11-27 copying botocore/data/qapps/2023-11-27/waiters-2.json -> build/lib/botocore/data/qapps/2023-11-27 creating build/lib/botocore/data/qbusiness creating build/lib/botocore/data/qbusiness/2023-11-27 copying botocore/data/qbusiness/2023-11-27/endpoint-rule-set-1.json -> build/lib/botocore/data/qbusiness/2023-11-27 copying botocore/data/qbusiness/2023-11-27/paginators-1.json -> build/lib/botocore/data/qbusiness/2023-11-27 copying botocore/data/qbusiness/2023-11-27/paginators-1.sdk-extras.json -> build/lib/botocore/data/qbusiness/2023-11-27 copying botocore/data/qbusiness/2023-11-27/service-2.json -> build/lib/botocore/data/qbusiness/2023-11-27 copying botocore/data/qbusiness/2023-11-27/waiters-2.json -> build/lib/botocore/data/qbusiness/2023-11-27 creating build/lib/botocore/data/qconnect creating build/lib/botocore/data/qconnect/2020-10-19 copying botocore/data/qconnect/2020-10-19/endpoint-rule-set-1.json -> build/lib/botocore/data/qconnect/2020-10-19 copying botocore/data/qconnect/2020-10-19/paginators-1.json -> build/lib/botocore/data/qconnect/2020-10-19 copying botocore/data/qconnect/2020-10-19/service-2.json -> build/lib/botocore/data/qconnect/2020-10-19 copying botocore/data/qconnect/2020-10-19/waiters-2.json -> build/lib/botocore/data/qconnect/2020-10-19 creating build/lib/botocore/data/quicksight creating build/lib/botocore/data/quicksight/2018-04-01 copying botocore/data/quicksight/2018-04-01/endpoint-rule-set-1.json -> build/lib/botocore/data/quicksight/2018-04-01 copying botocore/data/quicksight/2018-04-01/examples-1.json -> build/lib/botocore/data/quicksight/2018-04-01 copying botocore/data/quicksight/2018-04-01/paginators-1.json -> build/lib/botocore/data/quicksight/2018-04-01 copying botocore/data/quicksight/2018-04-01/paginators-1.sdk-extras.json -> build/lib/botocore/data/quicksight/2018-04-01 copying botocore/data/quicksight/2018-04-01/service-2.json -> build/lib/botocore/data/quicksight/2018-04-01 creating build/lib/botocore/data/ram creating build/lib/botocore/data/ram/2018-01-04 copying botocore/data/ram/2018-01-04/endpoint-rule-set-1.json -> build/lib/botocore/data/ram/2018-01-04 copying botocore/data/ram/2018-01-04/examples-1.json -> build/lib/botocore/data/ram/2018-01-04 copying botocore/data/ram/2018-01-04/paginators-1.json -> build/lib/botocore/data/ram/2018-01-04 copying botocore/data/ram/2018-01-04/service-2.json -> build/lib/botocore/data/ram/2018-01-04 creating build/lib/botocore/data/rbin creating build/lib/botocore/data/rbin/2021-06-15 copying botocore/data/rbin/2021-06-15/endpoint-rule-set-1.json -> build/lib/botocore/data/rbin/2021-06-15 copying botocore/data/rbin/2021-06-15/examples-1.json -> build/lib/botocore/data/rbin/2021-06-15 copying botocore/data/rbin/2021-06-15/paginators-1.json -> build/lib/botocore/data/rbin/2021-06-15 copying botocore/data/rbin/2021-06-15/service-2.json -> build/lib/botocore/data/rbin/2021-06-15 creating build/lib/botocore/data/rds-data creating build/lib/botocore/data/rds-data/2018-08-01 copying botocore/data/rds-data/2018-08-01/endpoint-rule-set-1.json -> build/lib/botocore/data/rds-data/2018-08-01 copying botocore/data/rds-data/2018-08-01/examples-1.json -> build/lib/botocore/data/rds-data/2018-08-01 copying botocore/data/rds-data/2018-08-01/paginators-1.json -> build/lib/botocore/data/rds-data/2018-08-01 copying botocore/data/rds-data/2018-08-01/service-2.json -> build/lib/botocore/data/rds-data/2018-08-01 creating build/lib/botocore/data/rds creating build/lib/botocore/data/rds/2014-09-01 copying botocore/data/rds/2014-09-01/endpoint-rule-set-1.json -> build/lib/botocore/data/rds/2014-09-01 copying botocore/data/rds/2014-09-01/paginators-1.json -> build/lib/botocore/data/rds/2014-09-01 copying botocore/data/rds/2014-09-01/service-2.json -> build/lib/botocore/data/rds/2014-09-01 copying botocore/data/rds/2014-09-01/waiters-2.json -> build/lib/botocore/data/rds/2014-09-01 creating build/lib/botocore/data/rds/2014-10-31 copying botocore/data/rds/2014-10-31/endpoint-rule-set-1.json -> build/lib/botocore/data/rds/2014-10-31 copying botocore/data/rds/2014-10-31/examples-1.json -> build/lib/botocore/data/rds/2014-10-31 copying botocore/data/rds/2014-10-31/paginators-1.json -> build/lib/botocore/data/rds/2014-10-31 copying botocore/data/rds/2014-10-31/paginators-1.sdk-extras.json -> build/lib/botocore/data/rds/2014-10-31 copying botocore/data/rds/2014-10-31/service-2.json -> build/lib/botocore/data/rds/2014-10-31 copying botocore/data/rds/2014-10-31/service-2.sdk-extras.json -> build/lib/botocore/data/rds/2014-10-31 copying botocore/data/rds/2014-10-31/waiters-2.json -> build/lib/botocore/data/rds/2014-10-31 creating build/lib/botocore/data/redshift-data creating build/lib/botocore/data/redshift-data/2019-12-20 copying botocore/data/redshift-data/2019-12-20/endpoint-rule-set-1.json -> build/lib/botocore/data/redshift-data/2019-12-20 copying botocore/data/redshift-data/2019-12-20/examples-1.json -> build/lib/botocore/data/redshift-data/2019-12-20 copying botocore/data/redshift-data/2019-12-20/paginators-1.json -> build/lib/botocore/data/redshift-data/2019-12-20 copying botocore/data/redshift-data/2019-12-20/paginators-1.sdk-extras.json -> build/lib/botocore/data/redshift-data/2019-12-20 copying botocore/data/redshift-data/2019-12-20/service-2.json -> build/lib/botocore/data/redshift-data/2019-12-20 creating build/lib/botocore/data/redshift-serverless creating build/lib/botocore/data/redshift-serverless/2021-04-21 copying botocore/data/redshift-serverless/2021-04-21/endpoint-rule-set-1.json -> build/lib/botocore/data/redshift-serverless/2021-04-21 copying botocore/data/redshift-serverless/2021-04-21/paginators-1.json -> build/lib/botocore/data/redshift-serverless/2021-04-21 copying botocore/data/redshift-serverless/2021-04-21/service-2.json -> build/lib/botocore/data/redshift-serverless/2021-04-21 creating build/lib/botocore/data/redshift creating build/lib/botocore/data/redshift/2012-12-01 copying botocore/data/redshift/2012-12-01/endpoint-rule-set-1.json -> build/lib/botocore/data/redshift/2012-12-01 copying botocore/data/redshift/2012-12-01/examples-1.json -> build/lib/botocore/data/redshift/2012-12-01 copying botocore/data/redshift/2012-12-01/paginators-1.json -> build/lib/botocore/data/redshift/2012-12-01 copying botocore/data/redshift/2012-12-01/service-2.json -> build/lib/botocore/data/redshift/2012-12-01 copying botocore/data/redshift/2012-12-01/waiters-2.json -> build/lib/botocore/data/redshift/2012-12-01 creating build/lib/botocore/data/rekognition creating build/lib/botocore/data/rekognition/2016-06-27 copying botocore/data/rekognition/2016-06-27/endpoint-rule-set-1.json -> build/lib/botocore/data/rekognition/2016-06-27 copying botocore/data/rekognition/2016-06-27/examples-1.json -> build/lib/botocore/data/rekognition/2016-06-27 copying botocore/data/rekognition/2016-06-27/paginators-1.json -> build/lib/botocore/data/rekognition/2016-06-27 copying botocore/data/rekognition/2016-06-27/service-2.json -> build/lib/botocore/data/rekognition/2016-06-27 copying botocore/data/rekognition/2016-06-27/waiters-2.json -> build/lib/botocore/data/rekognition/2016-06-27 creating build/lib/botocore/data/repostspace creating build/lib/botocore/data/repostspace/2022-05-13 copying botocore/data/repostspace/2022-05-13/endpoint-rule-set-1.json -> build/lib/botocore/data/repostspace/2022-05-13 copying botocore/data/repostspace/2022-05-13/paginators-1.json -> build/lib/botocore/data/repostspace/2022-05-13 copying botocore/data/repostspace/2022-05-13/service-2.json -> build/lib/botocore/data/repostspace/2022-05-13 copying botocore/data/repostspace/2022-05-13/waiters-2.json -> build/lib/botocore/data/repostspace/2022-05-13 creating build/lib/botocore/data/resiliencehub creating build/lib/botocore/data/resiliencehub/2020-04-30 copying botocore/data/resiliencehub/2020-04-30/endpoint-rule-set-1.json -> build/lib/botocore/data/resiliencehub/2020-04-30 copying botocore/data/resiliencehub/2020-04-30/examples-1.json -> build/lib/botocore/data/resiliencehub/2020-04-30 copying botocore/data/resiliencehub/2020-04-30/paginators-1.json -> build/lib/botocore/data/resiliencehub/2020-04-30 copying botocore/data/resiliencehub/2020-04-30/service-2.json -> build/lib/botocore/data/resiliencehub/2020-04-30 creating build/lib/botocore/data/resource-explorer-2 creating build/lib/botocore/data/resource-explorer-2/2022-07-28 copying botocore/data/resource-explorer-2/2022-07-28/endpoint-rule-set-1.json -> build/lib/botocore/data/resource-explorer-2/2022-07-28 copying botocore/data/resource-explorer-2/2022-07-28/paginators-1.json -> build/lib/botocore/data/resource-explorer-2/2022-07-28 copying botocore/data/resource-explorer-2/2022-07-28/paginators-1.sdk-extras.json -> build/lib/botocore/data/resource-explorer-2/2022-07-28 copying botocore/data/resource-explorer-2/2022-07-28/service-2.json -> build/lib/botocore/data/resource-explorer-2/2022-07-28 copying botocore/data/resource-explorer-2/2022-07-28/waiters-2.json -> build/lib/botocore/data/resource-explorer-2/2022-07-28 creating build/lib/botocore/data/resource-groups creating build/lib/botocore/data/resource-groups/2017-11-27 copying botocore/data/resource-groups/2017-11-27/endpoint-rule-set-1.json -> build/lib/botocore/data/resource-groups/2017-11-27 copying botocore/data/resource-groups/2017-11-27/examples-1.json -> build/lib/botocore/data/resource-groups/2017-11-27 copying botocore/data/resource-groups/2017-11-27/paginators-1.json -> build/lib/botocore/data/resource-groups/2017-11-27 copying botocore/data/resource-groups/2017-11-27/paginators-1.sdk-extras.json -> build/lib/botocore/data/resource-groups/2017-11-27 copying botocore/data/resource-groups/2017-11-27/service-2.json -> build/lib/botocore/data/resource-groups/2017-11-27 creating build/lib/botocore/data/resourcegroupstaggingapi creating build/lib/botocore/data/resourcegroupstaggingapi/2017-01-26 copying botocore/data/resourcegroupstaggingapi/2017-01-26/endpoint-rule-set-1.json -> build/lib/botocore/data/resourcegroupstaggingapi/2017-01-26 copying botocore/data/resourcegroupstaggingapi/2017-01-26/examples-1.json -> build/lib/botocore/data/resourcegroupstaggingapi/2017-01-26 copying botocore/data/resourcegroupstaggingapi/2017-01-26/paginators-1.json -> build/lib/botocore/data/resourcegroupstaggingapi/2017-01-26 copying botocore/data/resourcegroupstaggingapi/2017-01-26/service-2.json -> build/lib/botocore/data/resourcegroupstaggingapi/2017-01-26 creating build/lib/botocore/data/rolesanywhere creating build/lib/botocore/data/rolesanywhere/2018-05-10 copying botocore/data/rolesanywhere/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/rolesanywhere/2018-05-10 copying botocore/data/rolesanywhere/2018-05-10/paginators-1.json -> build/lib/botocore/data/rolesanywhere/2018-05-10 copying botocore/data/rolesanywhere/2018-05-10/service-2.json -> build/lib/botocore/data/rolesanywhere/2018-05-10 copying botocore/data/rolesanywhere/2018-05-10/waiters-2.json -> build/lib/botocore/data/rolesanywhere/2018-05-10 creating build/lib/botocore/data/route53-recovery-cluster creating build/lib/botocore/data/route53-recovery-cluster/2019-12-02 copying botocore/data/route53-recovery-cluster/2019-12-02/endpoint-rule-set-1.json -> build/lib/botocore/data/route53-recovery-cluster/2019-12-02 copying botocore/data/route53-recovery-cluster/2019-12-02/examples-1.json -> build/lib/botocore/data/route53-recovery-cluster/2019-12-02 copying botocore/data/route53-recovery-cluster/2019-12-02/paginators-1.json -> build/lib/botocore/data/route53-recovery-cluster/2019-12-02 copying botocore/data/route53-recovery-cluster/2019-12-02/service-2.json -> build/lib/botocore/data/route53-recovery-cluster/2019-12-02 creating build/lib/botocore/data/route53-recovery-control-config creating build/lib/botocore/data/route53-recovery-control-config/2020-11-02 copying botocore/data/route53-recovery-control-config/2020-11-02/endpoint-rule-set-1.json -> build/lib/botocore/data/route53-recovery-control-config/2020-11-02 copying botocore/data/route53-recovery-control-config/2020-11-02/paginators-1.json -> build/lib/botocore/data/route53-recovery-control-config/2020-11-02 copying botocore/data/route53-recovery-control-config/2020-11-02/service-2.json -> build/lib/botocore/data/route53-recovery-control-config/2020-11-02 copying botocore/data/route53-recovery-control-config/2020-11-02/waiters-2.json -> build/lib/botocore/data/route53-recovery-control-config/2020-11-02 creating build/lib/botocore/data/route53-recovery-readiness creating build/lib/botocore/data/route53-recovery-readiness/2019-12-02 copying botocore/data/route53-recovery-readiness/2019-12-02/endpoint-rule-set-1.json -> build/lib/botocore/data/route53-recovery-readiness/2019-12-02 copying botocore/data/route53-recovery-readiness/2019-12-02/paginators-1.json -> build/lib/botocore/data/route53-recovery-readiness/2019-12-02 copying botocore/data/route53-recovery-readiness/2019-12-02/service-2.json -> build/lib/botocore/data/route53-recovery-readiness/2019-12-02 creating build/lib/botocore/data/route53 creating build/lib/botocore/data/route53/2013-04-01 copying botocore/data/route53/2013-04-01/endpoint-rule-set-1.json -> build/lib/botocore/data/route53/2013-04-01 copying botocore/data/route53/2013-04-01/examples-1.json -> build/lib/botocore/data/route53/2013-04-01 copying botocore/data/route53/2013-04-01/paginators-1.json -> build/lib/botocore/data/route53/2013-04-01 copying botocore/data/route53/2013-04-01/service-2.json -> build/lib/botocore/data/route53/2013-04-01 copying botocore/data/route53/2013-04-01/waiters-2.json -> build/lib/botocore/data/route53/2013-04-01 creating build/lib/botocore/data/route53domains creating build/lib/botocore/data/route53domains/2014-05-15 copying botocore/data/route53domains/2014-05-15/endpoint-rule-set-1.json -> build/lib/botocore/data/route53domains/2014-05-15 copying botocore/data/route53domains/2014-05-15/examples-1.json -> build/lib/botocore/data/route53domains/2014-05-15 copying botocore/data/route53domains/2014-05-15/paginators-1.json -> build/lib/botocore/data/route53domains/2014-05-15 copying botocore/data/route53domains/2014-05-15/service-2.json -> build/lib/botocore/data/route53domains/2014-05-15 creating build/lib/botocore/data/route53globalresolver creating build/lib/botocore/data/route53globalresolver/2022-09-27 copying botocore/data/route53globalresolver/2022-09-27/endpoint-rule-set-1.json -> build/lib/botocore/data/route53globalresolver/2022-09-27 copying botocore/data/route53globalresolver/2022-09-27/paginators-1.json -> build/lib/botocore/data/route53globalresolver/2022-09-27 copying botocore/data/route53globalresolver/2022-09-27/service-2.json -> build/lib/botocore/data/route53globalresolver/2022-09-27 copying botocore/data/route53globalresolver/2022-09-27/waiters-2.json -> build/lib/botocore/data/route53globalresolver/2022-09-27 creating build/lib/botocore/data/route53profiles creating build/lib/botocore/data/route53profiles/2018-05-10 copying botocore/data/route53profiles/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/route53profiles/2018-05-10 copying botocore/data/route53profiles/2018-05-10/paginators-1.json -> build/lib/botocore/data/route53profiles/2018-05-10 copying botocore/data/route53profiles/2018-05-10/service-2.json -> build/lib/botocore/data/route53profiles/2018-05-10 creating build/lib/botocore/data/route53resolver creating build/lib/botocore/data/route53resolver/2018-04-01 copying botocore/data/route53resolver/2018-04-01/endpoint-rule-set-1.json -> build/lib/botocore/data/route53resolver/2018-04-01 copying botocore/data/route53resolver/2018-04-01/examples-1.json -> build/lib/botocore/data/route53resolver/2018-04-01 copying botocore/data/route53resolver/2018-04-01/paginators-1.json -> build/lib/botocore/data/route53resolver/2018-04-01 copying botocore/data/route53resolver/2018-04-01/paginators-1.sdk-extras.json -> build/lib/botocore/data/route53resolver/2018-04-01 copying botocore/data/route53resolver/2018-04-01/service-2.json -> build/lib/botocore/data/route53resolver/2018-04-01 creating build/lib/botocore/data/rtbfabric creating build/lib/botocore/data/rtbfabric/2023-05-15 copying botocore/data/rtbfabric/2023-05-15/endpoint-rule-set-1.json -> build/lib/botocore/data/rtbfabric/2023-05-15 copying botocore/data/rtbfabric/2023-05-15/paginators-1.json -> build/lib/botocore/data/rtbfabric/2023-05-15 copying botocore/data/rtbfabric/2023-05-15/service-2.json -> build/lib/botocore/data/rtbfabric/2023-05-15 copying botocore/data/rtbfabric/2023-05-15/waiters-2.json -> build/lib/botocore/data/rtbfabric/2023-05-15 creating build/lib/botocore/data/rum creating build/lib/botocore/data/rum/2018-05-10 copying botocore/data/rum/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/rum/2018-05-10 copying botocore/data/rum/2018-05-10/examples-1.json -> build/lib/botocore/data/rum/2018-05-10 copying botocore/data/rum/2018-05-10/paginators-1.json -> build/lib/botocore/data/rum/2018-05-10 copying botocore/data/rum/2018-05-10/service-2.json -> build/lib/botocore/data/rum/2018-05-10 copying botocore/data/rum/2018-05-10/waiters-2.json -> build/lib/botocore/data/rum/2018-05-10 creating build/lib/botocore/data/s3 creating build/lib/botocore/data/s3/2006-03-01 copying botocore/data/s3/2006-03-01/endpoint-rule-set-1.json -> build/lib/botocore/data/s3/2006-03-01 copying botocore/data/s3/2006-03-01/examples-1.json -> build/lib/botocore/data/s3/2006-03-01 copying botocore/data/s3/2006-03-01/paginators-1.json -> build/lib/botocore/data/s3/2006-03-01 copying botocore/data/s3/2006-03-01/paginators-1.sdk-extras.json -> build/lib/botocore/data/s3/2006-03-01 copying botocore/data/s3/2006-03-01/service-2.json -> build/lib/botocore/data/s3/2006-03-01 copying botocore/data/s3/2006-03-01/service-2.sdk-extras.json -> build/lib/botocore/data/s3/2006-03-01 copying botocore/data/s3/2006-03-01/waiters-2.json -> build/lib/botocore/data/s3/2006-03-01 creating build/lib/botocore/data/s3control creating build/lib/botocore/data/s3control/2018-08-20 copying botocore/data/s3control/2018-08-20/endpoint-rule-set-1.json -> build/lib/botocore/data/s3control/2018-08-20 copying botocore/data/s3control/2018-08-20/examples-1.json -> build/lib/botocore/data/s3control/2018-08-20 copying botocore/data/s3control/2018-08-20/paginators-1.json -> build/lib/botocore/data/s3control/2018-08-20 copying botocore/data/s3control/2018-08-20/service-2.json -> build/lib/botocore/data/s3control/2018-08-20 creating build/lib/botocore/data/s3files creating build/lib/botocore/data/s3files/2025-05-05 copying botocore/data/s3files/2025-05-05/endpoint-rule-set-1.json -> build/lib/botocore/data/s3files/2025-05-05 copying botocore/data/s3files/2025-05-05/paginators-1.json -> build/lib/botocore/data/s3files/2025-05-05 copying botocore/data/s3files/2025-05-05/service-2.json -> build/lib/botocore/data/s3files/2025-05-05 copying botocore/data/s3files/2025-05-05/waiters-2.json -> build/lib/botocore/data/s3files/2025-05-05 creating build/lib/botocore/data/s3outposts creating build/lib/botocore/data/s3outposts/2017-07-25 copying botocore/data/s3outposts/2017-07-25/endpoint-rule-set-1.json -> build/lib/botocore/data/s3outposts/2017-07-25 copying botocore/data/s3outposts/2017-07-25/examples-1.json -> build/lib/botocore/data/s3outposts/2017-07-25 copying botocore/data/s3outposts/2017-07-25/paginators-1.json -> build/lib/botocore/data/s3outposts/2017-07-25 copying botocore/data/s3outposts/2017-07-25/service-2.json -> build/lib/botocore/data/s3outposts/2017-07-25 creating build/lib/botocore/data/s3tables creating build/lib/botocore/data/s3tables/2018-05-10 copying botocore/data/s3tables/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/s3tables/2018-05-10 copying botocore/data/s3tables/2018-05-10/paginators-1.json -> build/lib/botocore/data/s3tables/2018-05-10 copying botocore/data/s3tables/2018-05-10/service-2.json -> build/lib/botocore/data/s3tables/2018-05-10 copying botocore/data/s3tables/2018-05-10/waiters-2.json -> build/lib/botocore/data/s3tables/2018-05-10 creating build/lib/botocore/data/s3vectors creating build/lib/botocore/data/s3vectors/2025-07-15 copying botocore/data/s3vectors/2025-07-15/endpoint-rule-set-1.json -> build/lib/botocore/data/s3vectors/2025-07-15 copying botocore/data/s3vectors/2025-07-15/paginators-1.json -> build/lib/botocore/data/s3vectors/2025-07-15 copying botocore/data/s3vectors/2025-07-15/service-2.json -> build/lib/botocore/data/s3vectors/2025-07-15 copying botocore/data/s3vectors/2025-07-15/waiters-2.json -> build/lib/botocore/data/s3vectors/2025-07-15 creating build/lib/botocore/data/sagemaker-a2i-runtime creating build/lib/botocore/data/sagemaker-a2i-runtime/2019-11-07 copying botocore/data/sagemaker-a2i-runtime/2019-11-07/endpoint-rule-set-1.json -> build/lib/botocore/data/sagemaker-a2i-runtime/2019-11-07 copying botocore/data/sagemaker-a2i-runtime/2019-11-07/examples-1.json -> build/lib/botocore/data/sagemaker-a2i-runtime/2019-11-07 copying botocore/data/sagemaker-a2i-runtime/2019-11-07/paginators-1.json -> build/lib/botocore/data/sagemaker-a2i-runtime/2019-11-07 copying botocore/data/sagemaker-a2i-runtime/2019-11-07/service-2.json -> build/lib/botocore/data/sagemaker-a2i-runtime/2019-11-07 creating build/lib/botocore/data/sagemaker-edge creating build/lib/botocore/data/sagemaker-edge/2020-09-23 copying botocore/data/sagemaker-edge/2020-09-23/endpoint-rule-set-1.json -> build/lib/botocore/data/sagemaker-edge/2020-09-23 copying botocore/data/sagemaker-edge/2020-09-23/examples-1.json -> build/lib/botocore/data/sagemaker-edge/2020-09-23 copying botocore/data/sagemaker-edge/2020-09-23/paginators-1.json -> build/lib/botocore/data/sagemaker-edge/2020-09-23 copying botocore/data/sagemaker-edge/2020-09-23/service-2.json -> build/lib/botocore/data/sagemaker-edge/2020-09-23 creating build/lib/botocore/data/sagemaker-featurestore-runtime creating build/lib/botocore/data/sagemaker-featurestore-runtime/2020-07-01 copying botocore/data/sagemaker-featurestore-runtime/2020-07-01/endpoint-rule-set-1.json -> build/lib/botocore/data/sagemaker-featurestore-runtime/2020-07-01 copying botocore/data/sagemaker-featurestore-runtime/2020-07-01/examples-1.json -> build/lib/botocore/data/sagemaker-featurestore-runtime/2020-07-01 copying botocore/data/sagemaker-featurestore-runtime/2020-07-01/paginators-1.json -> build/lib/botocore/data/sagemaker-featurestore-runtime/2020-07-01 copying botocore/data/sagemaker-featurestore-runtime/2020-07-01/service-2.json -> build/lib/botocore/data/sagemaker-featurestore-runtime/2020-07-01 creating build/lib/botocore/data/sagemaker-geospatial creating build/lib/botocore/data/sagemaker-geospatial/2020-05-27 copying botocore/data/sagemaker-geospatial/2020-05-27/endpoint-rule-set-1.json -> build/lib/botocore/data/sagemaker-geospatial/2020-05-27 copying botocore/data/sagemaker-geospatial/2020-05-27/paginators-1.json -> build/lib/botocore/data/sagemaker-geospatial/2020-05-27 copying botocore/data/sagemaker-geospatial/2020-05-27/service-2.json -> build/lib/botocore/data/sagemaker-geospatial/2020-05-27 creating build/lib/botocore/data/sagemaker-metrics creating build/lib/botocore/data/sagemaker-metrics/2022-09-30 copying botocore/data/sagemaker-metrics/2022-09-30/endpoint-rule-set-1.json -> build/lib/botocore/data/sagemaker-metrics/2022-09-30 copying botocore/data/sagemaker-metrics/2022-09-30/paginators-1.json -> build/lib/botocore/data/sagemaker-metrics/2022-09-30 copying botocore/data/sagemaker-metrics/2022-09-30/service-2.json -> build/lib/botocore/data/sagemaker-metrics/2022-09-30 creating build/lib/botocore/data/sagemaker-runtime creating build/lib/botocore/data/sagemaker-runtime/2017-05-13 copying botocore/data/sagemaker-runtime/2017-05-13/endpoint-rule-set-1.json -> build/lib/botocore/data/sagemaker-runtime/2017-05-13 copying botocore/data/sagemaker-runtime/2017-05-13/examples-1.json -> build/lib/botocore/data/sagemaker-runtime/2017-05-13 copying botocore/data/sagemaker-runtime/2017-05-13/paginators-1.json -> build/lib/botocore/data/sagemaker-runtime/2017-05-13 copying botocore/data/sagemaker-runtime/2017-05-13/service-2.json -> build/lib/botocore/data/sagemaker-runtime/2017-05-13 creating build/lib/botocore/data/sagemaker creating build/lib/botocore/data/sagemaker/2017-07-24 copying botocore/data/sagemaker/2017-07-24/endpoint-rule-set-1.json -> build/lib/botocore/data/sagemaker/2017-07-24 copying botocore/data/sagemaker/2017-07-24/examples-1.json -> build/lib/botocore/data/sagemaker/2017-07-24 copying botocore/data/sagemaker/2017-07-24/paginators-1.json -> build/lib/botocore/data/sagemaker/2017-07-24 copying botocore/data/sagemaker/2017-07-24/paginators-1.sdk-extras.json -> build/lib/botocore/data/sagemaker/2017-07-24 copying botocore/data/sagemaker/2017-07-24/service-2.json -> build/lib/botocore/data/sagemaker/2017-07-24 copying botocore/data/sagemaker/2017-07-24/waiters-2.json -> build/lib/botocore/data/sagemaker/2017-07-24 creating build/lib/botocore/data/savingsplans creating build/lib/botocore/data/savingsplans/2019-06-28 copying botocore/data/savingsplans/2019-06-28/endpoint-rule-set-1.json -> build/lib/botocore/data/savingsplans/2019-06-28 copying botocore/data/savingsplans/2019-06-28/examples-1.json -> build/lib/botocore/data/savingsplans/2019-06-28 copying botocore/data/savingsplans/2019-06-28/paginators-1.json -> build/lib/botocore/data/savingsplans/2019-06-28 copying botocore/data/savingsplans/2019-06-28/service-2.json -> build/lib/botocore/data/savingsplans/2019-06-28 creating build/lib/botocore/data/scheduler creating build/lib/botocore/data/scheduler/2021-06-30 copying botocore/data/scheduler/2021-06-30/endpoint-rule-set-1.json -> build/lib/botocore/data/scheduler/2021-06-30 copying botocore/data/scheduler/2021-06-30/paginators-1.json -> build/lib/botocore/data/scheduler/2021-06-30 copying botocore/data/scheduler/2021-06-30/service-2.json -> build/lib/botocore/data/scheduler/2021-06-30 creating build/lib/botocore/data/schemas creating build/lib/botocore/data/schemas/2019-12-02 copying botocore/data/schemas/2019-12-02/endpoint-rule-set-1.json -> build/lib/botocore/data/schemas/2019-12-02 copying botocore/data/schemas/2019-12-02/paginators-1.json -> build/lib/botocore/data/schemas/2019-12-02 copying botocore/data/schemas/2019-12-02/service-2.json -> build/lib/botocore/data/schemas/2019-12-02 copying botocore/data/schemas/2019-12-02/waiters-2.json -> build/lib/botocore/data/schemas/2019-12-02 creating build/lib/botocore/data/sdb creating build/lib/botocore/data/sdb/2009-04-15 copying botocore/data/sdb/2009-04-15/endpoint-rule-set-1.json -> build/lib/botocore/data/sdb/2009-04-15 copying botocore/data/sdb/2009-04-15/paginators-1.json -> build/lib/botocore/data/sdb/2009-04-15 copying botocore/data/sdb/2009-04-15/service-2.json -> build/lib/botocore/data/sdb/2009-04-15 creating build/lib/botocore/data/secretsmanager creating build/lib/botocore/data/secretsmanager/2017-10-17 copying botocore/data/secretsmanager/2017-10-17/endpoint-rule-set-1.json -> build/lib/botocore/data/secretsmanager/2017-10-17 copying botocore/data/secretsmanager/2017-10-17/examples-1.json -> build/lib/botocore/data/secretsmanager/2017-10-17 copying botocore/data/secretsmanager/2017-10-17/paginators-1.json -> build/lib/botocore/data/secretsmanager/2017-10-17 copying botocore/data/secretsmanager/2017-10-17/service-2.json -> build/lib/botocore/data/secretsmanager/2017-10-17 copying botocore/data/secretsmanager/2017-10-17/service-2.sdk-extras.json -> build/lib/botocore/data/secretsmanager/2017-10-17 creating build/lib/botocore/data/security-ir creating build/lib/botocore/data/security-ir/2018-05-10 copying botocore/data/security-ir/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/security-ir/2018-05-10 copying botocore/data/security-ir/2018-05-10/paginators-1.json -> build/lib/botocore/data/security-ir/2018-05-10 copying botocore/data/security-ir/2018-05-10/paginators-1.sdk-extras.json -> build/lib/botocore/data/security-ir/2018-05-10 copying botocore/data/security-ir/2018-05-10/service-2.json -> build/lib/botocore/data/security-ir/2018-05-10 copying botocore/data/security-ir/2018-05-10/waiters-2.json -> build/lib/botocore/data/security-ir/2018-05-10 creating build/lib/botocore/data/securityagent creating build/lib/botocore/data/securityagent/2025-09-06 copying botocore/data/securityagent/2025-09-06/endpoint-rule-set-1.json -> build/lib/botocore/data/securityagent/2025-09-06 copying botocore/data/securityagent/2025-09-06/paginators-1.json -> build/lib/botocore/data/securityagent/2025-09-06 copying botocore/data/securityagent/2025-09-06/service-2.json -> build/lib/botocore/data/securityagent/2025-09-06 copying botocore/data/securityagent/2025-09-06/waiters-2.json -> build/lib/botocore/data/securityagent/2025-09-06 creating build/lib/botocore/data/securityhub creating build/lib/botocore/data/securityhub/2018-10-26 copying botocore/data/securityhub/2018-10-26/endpoint-rule-set-1.json -> build/lib/botocore/data/securityhub/2018-10-26 copying botocore/data/securityhub/2018-10-26/examples-1.json -> build/lib/botocore/data/securityhub/2018-10-26 copying botocore/data/securityhub/2018-10-26/paginators-1.json -> build/lib/botocore/data/securityhub/2018-10-26 copying botocore/data/securityhub/2018-10-26/paginators-1.sdk-extras.json -> build/lib/botocore/data/securityhub/2018-10-26 copying botocore/data/securityhub/2018-10-26/service-2.json -> build/lib/botocore/data/securityhub/2018-10-26 creating build/lib/botocore/data/securitylake creating build/lib/botocore/data/securitylake/2018-05-10 copying botocore/data/securitylake/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/securitylake/2018-05-10 copying botocore/data/securitylake/2018-05-10/paginators-1.json -> build/lib/botocore/data/securitylake/2018-05-10 copying botocore/data/securitylake/2018-05-10/paginators-1.sdk-extras.json -> build/lib/botocore/data/securitylake/2018-05-10 copying botocore/data/securitylake/2018-05-10/service-2.json -> build/lib/botocore/data/securitylake/2018-05-10 creating build/lib/botocore/data/serverlessrepo creating build/lib/botocore/data/serverlessrepo/2017-09-08 copying botocore/data/serverlessrepo/2017-09-08/endpoint-rule-set-1.json -> build/lib/botocore/data/serverlessrepo/2017-09-08 copying botocore/data/serverlessrepo/2017-09-08/paginators-1.json -> build/lib/botocore/data/serverlessrepo/2017-09-08 copying botocore/data/serverlessrepo/2017-09-08/service-2.json -> build/lib/botocore/data/serverlessrepo/2017-09-08 creating build/lib/botocore/data/service-quotas creating build/lib/botocore/data/service-quotas/2019-06-24 copying botocore/data/service-quotas/2019-06-24/endpoint-rule-set-1.json -> build/lib/botocore/data/service-quotas/2019-06-24 copying botocore/data/service-quotas/2019-06-24/examples-1.json -> build/lib/botocore/data/service-quotas/2019-06-24 copying botocore/data/service-quotas/2019-06-24/paginators-1.json -> build/lib/botocore/data/service-quotas/2019-06-24 copying botocore/data/service-quotas/2019-06-24/service-2.json -> build/lib/botocore/data/service-quotas/2019-06-24 creating build/lib/botocore/data/servicecatalog-appregistry creating build/lib/botocore/data/servicecatalog-appregistry/2020-06-24 copying botocore/data/servicecatalog-appregistry/2020-06-24/endpoint-rule-set-1.json -> build/lib/botocore/data/servicecatalog-appregistry/2020-06-24 copying botocore/data/servicecatalog-appregistry/2020-06-24/examples-1.json -> build/lib/botocore/data/servicecatalog-appregistry/2020-06-24 copying botocore/data/servicecatalog-appregistry/2020-06-24/paginators-1.json -> build/lib/botocore/data/servicecatalog-appregistry/2020-06-24 copying botocore/data/servicecatalog-appregistry/2020-06-24/service-2.json -> build/lib/botocore/data/servicecatalog-appregistry/2020-06-24 creating build/lib/botocore/data/servicecatalog creating build/lib/botocore/data/servicecatalog/2015-12-10 copying botocore/data/servicecatalog/2015-12-10/endpoint-rule-set-1.json -> build/lib/botocore/data/servicecatalog/2015-12-10 copying botocore/data/servicecatalog/2015-12-10/examples-1.json -> build/lib/botocore/data/servicecatalog/2015-12-10 copying botocore/data/servicecatalog/2015-12-10/paginators-1.json -> build/lib/botocore/data/servicecatalog/2015-12-10 copying botocore/data/servicecatalog/2015-12-10/service-2.json -> build/lib/botocore/data/servicecatalog/2015-12-10 creating build/lib/botocore/data/servicediscovery creating build/lib/botocore/data/servicediscovery/2017-03-14 copying botocore/data/servicediscovery/2017-03-14/endpoint-rule-set-1.json -> build/lib/botocore/data/servicediscovery/2017-03-14 copying botocore/data/servicediscovery/2017-03-14/examples-1.json -> build/lib/botocore/data/servicediscovery/2017-03-14 copying botocore/data/servicediscovery/2017-03-14/paginators-1.json -> build/lib/botocore/data/servicediscovery/2017-03-14 copying botocore/data/servicediscovery/2017-03-14/paginators-1.sdk-extras.json -> build/lib/botocore/data/servicediscovery/2017-03-14 copying botocore/data/servicediscovery/2017-03-14/service-2.json -> build/lib/botocore/data/servicediscovery/2017-03-14 creating build/lib/botocore/data/ses creating build/lib/botocore/data/ses/2010-12-01 copying botocore/data/ses/2010-12-01/endpoint-rule-set-1.json -> build/lib/botocore/data/ses/2010-12-01 copying botocore/data/ses/2010-12-01/examples-1.json -> build/lib/botocore/data/ses/2010-12-01 copying botocore/data/ses/2010-12-01/paginators-1.json -> build/lib/botocore/data/ses/2010-12-01 copying botocore/data/ses/2010-12-01/service-2.json -> build/lib/botocore/data/ses/2010-12-01 copying botocore/data/ses/2010-12-01/waiters-2.json -> build/lib/botocore/data/ses/2010-12-01 creating build/lib/botocore/data/sesv2 creating build/lib/botocore/data/sesv2/2019-09-27 copying botocore/data/sesv2/2019-09-27/endpoint-rule-set-1.json -> build/lib/botocore/data/sesv2/2019-09-27 copying botocore/data/sesv2/2019-09-27/examples-1.json -> build/lib/botocore/data/sesv2/2019-09-27 copying botocore/data/sesv2/2019-09-27/paginators-1.json -> build/lib/botocore/data/sesv2/2019-09-27 copying botocore/data/sesv2/2019-09-27/service-2.json -> build/lib/botocore/data/sesv2/2019-09-27 creating build/lib/botocore/data/shield creating build/lib/botocore/data/shield/2016-06-02 copying botocore/data/shield/2016-06-02/endpoint-rule-set-1.json -> build/lib/botocore/data/shield/2016-06-02 copying botocore/data/shield/2016-06-02/examples-1.json -> build/lib/botocore/data/shield/2016-06-02 copying botocore/data/shield/2016-06-02/paginators-1.json -> build/lib/botocore/data/shield/2016-06-02 copying botocore/data/shield/2016-06-02/service-2.json -> build/lib/botocore/data/shield/2016-06-02 creating build/lib/botocore/data/signer-data creating build/lib/botocore/data/signer-data/2017-08-25 copying botocore/data/signer-data/2017-08-25/endpoint-rule-set-1.json -> build/lib/botocore/data/signer-data/2017-08-25 copying botocore/data/signer-data/2017-08-25/paginators-1.json -> build/lib/botocore/data/signer-data/2017-08-25 copying botocore/data/signer-data/2017-08-25/service-2.json -> build/lib/botocore/data/signer-data/2017-08-25 copying botocore/data/signer-data/2017-08-25/waiters-2.json -> build/lib/botocore/data/signer-data/2017-08-25 creating build/lib/botocore/data/signer creating build/lib/botocore/data/signer/2017-08-25 copying botocore/data/signer/2017-08-25/endpoint-rule-set-1.json -> build/lib/botocore/data/signer/2017-08-25 copying botocore/data/signer/2017-08-25/examples-1.json -> build/lib/botocore/data/signer/2017-08-25 copying botocore/data/signer/2017-08-25/paginators-1.json -> build/lib/botocore/data/signer/2017-08-25 copying botocore/data/signer/2017-08-25/service-2.json -> build/lib/botocore/data/signer/2017-08-25 copying botocore/data/signer/2017-08-25/waiters-2.json -> build/lib/botocore/data/signer/2017-08-25 creating build/lib/botocore/data/signin creating build/lib/botocore/data/signin/2023-01-01 copying botocore/data/signin/2023-01-01/endpoint-rule-set-1.json -> build/lib/botocore/data/signin/2023-01-01 copying botocore/data/signin/2023-01-01/paginators-1.json -> build/lib/botocore/data/signin/2023-01-01 copying botocore/data/signin/2023-01-01/service-2.json -> build/lib/botocore/data/signin/2023-01-01 creating build/lib/botocore/data/simpledbv2 creating build/lib/botocore/data/simpledbv2/2025-09-26 copying botocore/data/simpledbv2/2025-09-26/endpoint-rule-set-1.json -> build/lib/botocore/data/simpledbv2/2025-09-26 copying botocore/data/simpledbv2/2025-09-26/paginators-1.json -> build/lib/botocore/data/simpledbv2/2025-09-26 copying botocore/data/simpledbv2/2025-09-26/service-2.json -> build/lib/botocore/data/simpledbv2/2025-09-26 copying botocore/data/simpledbv2/2025-09-26/waiters-2.json -> build/lib/botocore/data/simpledbv2/2025-09-26 creating build/lib/botocore/data/simspaceweaver creating build/lib/botocore/data/simspaceweaver/2022-10-28 copying botocore/data/simspaceweaver/2022-10-28/endpoint-rule-set-1.json -> build/lib/botocore/data/simspaceweaver/2022-10-28 copying botocore/data/simspaceweaver/2022-10-28/paginators-1.json -> build/lib/botocore/data/simspaceweaver/2022-10-28 copying botocore/data/simspaceweaver/2022-10-28/service-2.json -> build/lib/botocore/data/simspaceweaver/2022-10-28 creating build/lib/botocore/data/sms-voice creating build/lib/botocore/data/sms-voice/2018-09-05 copying botocore/data/sms-voice/2018-09-05/endpoint-rule-set-1.json -> build/lib/botocore/data/sms-voice/2018-09-05 copying botocore/data/sms-voice/2018-09-05/service-2.json -> build/lib/botocore/data/sms-voice/2018-09-05 creating build/lib/botocore/data/snow-device-management creating build/lib/botocore/data/snow-device-management/2021-08-04 copying botocore/data/snow-device-management/2021-08-04/endpoint-rule-set-1.json -> build/lib/botocore/data/snow-device-management/2021-08-04 copying botocore/data/snow-device-management/2021-08-04/examples-1.json -> build/lib/botocore/data/snow-device-management/2021-08-04 copying botocore/data/snow-device-management/2021-08-04/paginators-1.json -> build/lib/botocore/data/snow-device-management/2021-08-04 copying botocore/data/snow-device-management/2021-08-04/service-2.json -> build/lib/botocore/data/snow-device-management/2021-08-04 creating build/lib/botocore/data/snowball creating build/lib/botocore/data/snowball/2016-06-30 copying botocore/data/snowball/2016-06-30/endpoint-rule-set-1.json -> build/lib/botocore/data/snowball/2016-06-30 copying botocore/data/snowball/2016-06-30/examples-1.json -> build/lib/botocore/data/snowball/2016-06-30 copying botocore/data/snowball/2016-06-30/paginators-1.json -> build/lib/botocore/data/snowball/2016-06-30 copying botocore/data/snowball/2016-06-30/service-2.json -> build/lib/botocore/data/snowball/2016-06-30 creating build/lib/botocore/data/sns creating build/lib/botocore/data/sns/2010-03-31 copying botocore/data/sns/2010-03-31/endpoint-rule-set-1.json -> build/lib/botocore/data/sns/2010-03-31 copying botocore/data/sns/2010-03-31/examples-1.json -> build/lib/botocore/data/sns/2010-03-31 copying botocore/data/sns/2010-03-31/paginators-1.json -> build/lib/botocore/data/sns/2010-03-31 copying botocore/data/sns/2010-03-31/service-2.json -> build/lib/botocore/data/sns/2010-03-31 creating build/lib/botocore/data/socialmessaging creating build/lib/botocore/data/socialmessaging/2024-01-01 copying botocore/data/socialmessaging/2024-01-01/endpoint-rule-set-1.json -> build/lib/botocore/data/socialmessaging/2024-01-01 copying botocore/data/socialmessaging/2024-01-01/paginators-1.json -> build/lib/botocore/data/socialmessaging/2024-01-01 copying botocore/data/socialmessaging/2024-01-01/service-2.json -> build/lib/botocore/data/socialmessaging/2024-01-01 creating build/lib/botocore/data/sqs creating build/lib/botocore/data/sqs/2012-11-05 copying botocore/data/sqs/2012-11-05/endpoint-rule-set-1.json -> build/lib/botocore/data/sqs/2012-11-05 copying botocore/data/sqs/2012-11-05/examples-1.json -> build/lib/botocore/data/sqs/2012-11-05 copying botocore/data/sqs/2012-11-05/paginators-1.json -> build/lib/botocore/data/sqs/2012-11-05 copying botocore/data/sqs/2012-11-05/service-2.json -> build/lib/botocore/data/sqs/2012-11-05 creating build/lib/botocore/data/ssm-contacts creating build/lib/botocore/data/ssm-contacts/2021-05-03 copying botocore/data/ssm-contacts/2021-05-03/endpoint-rule-set-1.json -> build/lib/botocore/data/ssm-contacts/2021-05-03 copying botocore/data/ssm-contacts/2021-05-03/examples-1.json -> build/lib/botocore/data/ssm-contacts/2021-05-03 copying botocore/data/ssm-contacts/2021-05-03/paginators-1.json -> build/lib/botocore/data/ssm-contacts/2021-05-03 copying botocore/data/ssm-contacts/2021-05-03/service-2.json -> build/lib/botocore/data/ssm-contacts/2021-05-03 creating build/lib/botocore/data/ssm-guiconnect creating build/lib/botocore/data/ssm-guiconnect/2021-05-01 copying botocore/data/ssm-guiconnect/2021-05-01/endpoint-rule-set-1.json -> build/lib/botocore/data/ssm-guiconnect/2021-05-01 copying botocore/data/ssm-guiconnect/2021-05-01/paginators-1.json -> build/lib/botocore/data/ssm-guiconnect/2021-05-01 copying botocore/data/ssm-guiconnect/2021-05-01/service-2.json -> build/lib/botocore/data/ssm-guiconnect/2021-05-01 creating build/lib/botocore/data/ssm-incidents creating build/lib/botocore/data/ssm-incidents/2018-05-10 copying botocore/data/ssm-incidents/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/ssm-incidents/2018-05-10 copying botocore/data/ssm-incidents/2018-05-10/examples-1.json -> build/lib/botocore/data/ssm-incidents/2018-05-10 copying botocore/data/ssm-incidents/2018-05-10/paginators-1.json -> build/lib/botocore/data/ssm-incidents/2018-05-10 copying botocore/data/ssm-incidents/2018-05-10/service-2.json -> build/lib/botocore/data/ssm-incidents/2018-05-10 copying botocore/data/ssm-incidents/2018-05-10/waiters-2.json -> build/lib/botocore/data/ssm-incidents/2018-05-10 creating build/lib/botocore/data/ssm-quicksetup creating build/lib/botocore/data/ssm-quicksetup/2018-05-10 copying botocore/data/ssm-quicksetup/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/ssm-quicksetup/2018-05-10 copying botocore/data/ssm-quicksetup/2018-05-10/paginators-1.json -> build/lib/botocore/data/ssm-quicksetup/2018-05-10 copying botocore/data/ssm-quicksetup/2018-05-10/service-2.json -> build/lib/botocore/data/ssm-quicksetup/2018-05-10 creating build/lib/botocore/data/ssm-sap creating build/lib/botocore/data/ssm-sap/2018-05-10 copying botocore/data/ssm-sap/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/ssm-sap/2018-05-10 copying botocore/data/ssm-sap/2018-05-10/paginators-1.json -> build/lib/botocore/data/ssm-sap/2018-05-10 copying botocore/data/ssm-sap/2018-05-10/service-2.json -> build/lib/botocore/data/ssm-sap/2018-05-10 creating build/lib/botocore/data/ssm creating build/lib/botocore/data/ssm/2014-11-06 copying botocore/data/ssm/2014-11-06/endpoint-rule-set-1.json -> build/lib/botocore/data/ssm/2014-11-06 copying botocore/data/ssm/2014-11-06/examples-1.json -> build/lib/botocore/data/ssm/2014-11-06 copying botocore/data/ssm/2014-11-06/paginators-1.json -> build/lib/botocore/data/ssm/2014-11-06 copying botocore/data/ssm/2014-11-06/service-2.json -> build/lib/botocore/data/ssm/2014-11-06 copying botocore/data/ssm/2014-11-06/waiters-2.json -> build/lib/botocore/data/ssm/2014-11-06 creating build/lib/botocore/data/sso-admin creating build/lib/botocore/data/sso-admin/2020-07-20 copying botocore/data/sso-admin/2020-07-20/endpoint-rule-set-1.json -> build/lib/botocore/data/sso-admin/2020-07-20 copying botocore/data/sso-admin/2020-07-20/examples-1.json -> build/lib/botocore/data/sso-admin/2020-07-20 copying botocore/data/sso-admin/2020-07-20/paginators-1.json -> build/lib/botocore/data/sso-admin/2020-07-20 copying botocore/data/sso-admin/2020-07-20/service-2.json -> build/lib/botocore/data/sso-admin/2020-07-20 copying botocore/data/sso-admin/2020-07-20/waiters-2.json -> build/lib/botocore/data/sso-admin/2020-07-20 creating build/lib/botocore/data/sso-oidc creating build/lib/botocore/data/sso-oidc/2019-06-10 copying botocore/data/sso-oidc/2019-06-10/endpoint-rule-set-1.json -> build/lib/botocore/data/sso-oidc/2019-06-10 copying botocore/data/sso-oidc/2019-06-10/examples-1.json -> build/lib/botocore/data/sso-oidc/2019-06-10 copying botocore/data/sso-oidc/2019-06-10/paginators-1.json -> build/lib/botocore/data/sso-oidc/2019-06-10 copying botocore/data/sso-oidc/2019-06-10/service-2.json -> build/lib/botocore/data/sso-oidc/2019-06-10 creating build/lib/botocore/data/sso creating build/lib/botocore/data/sso/2019-06-10 copying botocore/data/sso/2019-06-10/endpoint-rule-set-1.json -> build/lib/botocore/data/sso/2019-06-10 copying botocore/data/sso/2019-06-10/examples-1.json -> build/lib/botocore/data/sso/2019-06-10 copying botocore/data/sso/2019-06-10/paginators-1.json -> build/lib/botocore/data/sso/2019-06-10 copying botocore/data/sso/2019-06-10/service-2.json -> build/lib/botocore/data/sso/2019-06-10 creating build/lib/botocore/data/stepfunctions creating build/lib/botocore/data/stepfunctions/2016-11-23 copying botocore/data/stepfunctions/2016-11-23/endpoint-rule-set-1.json -> build/lib/botocore/data/stepfunctions/2016-11-23 copying botocore/data/stepfunctions/2016-11-23/examples-1.json -> build/lib/botocore/data/stepfunctions/2016-11-23 copying botocore/data/stepfunctions/2016-11-23/paginators-1.json -> build/lib/botocore/data/stepfunctions/2016-11-23 copying botocore/data/stepfunctions/2016-11-23/service-2.json -> build/lib/botocore/data/stepfunctions/2016-11-23 creating build/lib/botocore/data/storagegateway creating build/lib/botocore/data/storagegateway/2013-06-30 copying botocore/data/storagegateway/2013-06-30/endpoint-rule-set-1.json -> build/lib/botocore/data/storagegateway/2013-06-30 copying botocore/data/storagegateway/2013-06-30/examples-1.json -> build/lib/botocore/data/storagegateway/2013-06-30 copying botocore/data/storagegateway/2013-06-30/paginators-1.json -> build/lib/botocore/data/storagegateway/2013-06-30 copying botocore/data/storagegateway/2013-06-30/service-2.json -> build/lib/botocore/data/storagegateway/2013-06-30 creating build/lib/botocore/data/sts creating build/lib/botocore/data/sts/2011-06-15 copying botocore/data/sts/2011-06-15/endpoint-rule-set-1.json -> build/lib/botocore/data/sts/2011-06-15 copying botocore/data/sts/2011-06-15/examples-1.json -> build/lib/botocore/data/sts/2011-06-15 copying botocore/data/sts/2011-06-15/paginators-1.json -> build/lib/botocore/data/sts/2011-06-15 copying botocore/data/sts/2011-06-15/service-2.json -> build/lib/botocore/data/sts/2011-06-15 creating build/lib/botocore/data/supplychain creating build/lib/botocore/data/supplychain/2024-01-01 copying botocore/data/supplychain/2024-01-01/endpoint-rule-set-1.json -> build/lib/botocore/data/supplychain/2024-01-01 copying botocore/data/supplychain/2024-01-01/paginators-1.json -> build/lib/botocore/data/supplychain/2024-01-01 copying botocore/data/supplychain/2024-01-01/service-2.json -> build/lib/botocore/data/supplychain/2024-01-01 creating build/lib/botocore/data/support-app creating build/lib/botocore/data/support-app/2021-08-20 copying botocore/data/support-app/2021-08-20/endpoint-rule-set-1.json -> build/lib/botocore/data/support-app/2021-08-20 copying botocore/data/support-app/2021-08-20/paginators-1.json -> build/lib/botocore/data/support-app/2021-08-20 copying botocore/data/support-app/2021-08-20/service-2.json -> build/lib/botocore/data/support-app/2021-08-20 creating build/lib/botocore/data/support creating build/lib/botocore/data/support/2013-04-15 copying botocore/data/support/2013-04-15/endpoint-rule-set-1.json -> build/lib/botocore/data/support/2013-04-15 copying botocore/data/support/2013-04-15/examples-1.json -> build/lib/botocore/data/support/2013-04-15 copying botocore/data/support/2013-04-15/paginators-1.json -> build/lib/botocore/data/support/2013-04-15 copying botocore/data/support/2013-04-15/service-2.json -> build/lib/botocore/data/support/2013-04-15 creating build/lib/botocore/data/sustainability creating build/lib/botocore/data/sustainability/2018-05-10 copying botocore/data/sustainability/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/sustainability/2018-05-10 copying botocore/data/sustainability/2018-05-10/paginators-1.json -> build/lib/botocore/data/sustainability/2018-05-10 copying botocore/data/sustainability/2018-05-10/service-2.json -> build/lib/botocore/data/sustainability/2018-05-10 creating build/lib/botocore/data/swf creating build/lib/botocore/data/swf/2012-01-25 copying botocore/data/swf/2012-01-25/endpoint-rule-set-1.json -> build/lib/botocore/data/swf/2012-01-25 copying botocore/data/swf/2012-01-25/examples-1.json -> build/lib/botocore/data/swf/2012-01-25 copying botocore/data/swf/2012-01-25/paginators-1.json -> build/lib/botocore/data/swf/2012-01-25 copying botocore/data/swf/2012-01-25/service-2.json -> build/lib/botocore/data/swf/2012-01-25 creating build/lib/botocore/data/synthetics creating build/lib/botocore/data/synthetics/2017-10-11 copying botocore/data/synthetics/2017-10-11/endpoint-rule-set-1.json -> build/lib/botocore/data/synthetics/2017-10-11 copying botocore/data/synthetics/2017-10-11/examples-1.json -> build/lib/botocore/data/synthetics/2017-10-11 copying botocore/data/synthetics/2017-10-11/paginators-1.json -> build/lib/botocore/data/synthetics/2017-10-11 copying botocore/data/synthetics/2017-10-11/service-2.json -> build/lib/botocore/data/synthetics/2017-10-11 creating build/lib/botocore/data/taxsettings creating build/lib/botocore/data/taxsettings/2018-05-10 copying botocore/data/taxsettings/2018-05-10/endpoint-rule-set-1.json -> build/lib/botocore/data/taxsettings/2018-05-10 copying botocore/data/taxsettings/2018-05-10/paginators-1.json -> build/lib/botocore/data/taxsettings/2018-05-10 copying botocore/data/taxsettings/2018-05-10/service-2.json -> build/lib/botocore/data/taxsettings/2018-05-10 creating build/lib/botocore/data/textract creating build/lib/botocore/data/textract/2018-06-27 copying botocore/data/textract/2018-06-27/endpoint-rule-set-1.json -> build/lib/botocore/data/textract/2018-06-27 copying botocore/data/textract/2018-06-27/examples-1.json -> build/lib/botocore/data/textract/2018-06-27 copying botocore/data/textract/2018-06-27/paginators-1.json -> build/lib/botocore/data/textract/2018-06-27 copying botocore/data/textract/2018-06-27/service-2.json -> build/lib/botocore/data/textract/2018-06-27 creating build/lib/botocore/data/timestream-influxdb creating build/lib/botocore/data/timestream-influxdb/2023-01-27 copying botocore/data/timestream-influxdb/2023-01-27/endpoint-rule-set-1.json -> build/lib/botocore/data/timestream-influxdb/2023-01-27 copying botocore/data/timestream-influxdb/2023-01-27/paginators-1.json -> build/lib/botocore/data/timestream-influxdb/2023-01-27 copying botocore/data/timestream-influxdb/2023-01-27/service-2.json -> build/lib/botocore/data/timestream-influxdb/2023-01-27 creating build/lib/botocore/data/timestream-query creating build/lib/botocore/data/timestream-query/2018-11-01 copying botocore/data/timestream-query/2018-11-01/endpoint-rule-set-1.json -> build/lib/botocore/data/timestream-query/2018-11-01 copying botocore/data/timestream-query/2018-11-01/examples-1.json -> build/lib/botocore/data/timestream-query/2018-11-01 copying botocore/data/timestream-query/2018-11-01/paginators-1.json -> build/lib/botocore/data/timestream-query/2018-11-01 copying botocore/data/timestream-query/2018-11-01/service-2.json -> build/lib/botocore/data/timestream-query/2018-11-01 creating build/lib/botocore/data/timestream-write creating build/lib/botocore/data/timestream-write/2018-11-01 copying botocore/data/timestream-write/2018-11-01/endpoint-rule-set-1.json -> build/lib/botocore/data/timestream-write/2018-11-01 copying botocore/data/timestream-write/2018-11-01/examples-1.json -> build/lib/botocore/data/timestream-write/2018-11-01 copying botocore/data/timestream-write/2018-11-01/paginators-1.json -> build/lib/botocore/data/timestream-write/2018-11-01 copying botocore/data/timestream-write/2018-11-01/service-2.json -> build/lib/botocore/data/timestream-write/2018-11-01 creating build/lib/botocore/data/tnb creating build/lib/botocore/data/tnb/2008-10-21 copying botocore/data/tnb/2008-10-21/endpoint-rule-set-1.json -> build/lib/botocore/data/tnb/2008-10-21 copying botocore/data/tnb/2008-10-21/paginators-1.json -> build/lib/botocore/data/tnb/2008-10-21 copying botocore/data/tnb/2008-10-21/service-2.json -> build/lib/botocore/data/tnb/2008-10-21 creating build/lib/botocore/data/transcribe creating build/lib/botocore/data/transcribe/2017-10-26 copying botocore/data/transcribe/2017-10-26/endpoint-rule-set-1.json -> build/lib/botocore/data/transcribe/2017-10-26 copying botocore/data/transcribe/2017-10-26/examples-1.json -> build/lib/botocore/data/transcribe/2017-10-26 copying botocore/data/transcribe/2017-10-26/paginators-1.json -> build/lib/botocore/data/transcribe/2017-10-26 copying botocore/data/transcribe/2017-10-26/service-2.json -> build/lib/botocore/data/transcribe/2017-10-26 copying botocore/data/transcribe/2017-10-26/waiters-2.json -> build/lib/botocore/data/transcribe/2017-10-26 creating build/lib/botocore/data/transfer creating build/lib/botocore/data/transfer/2018-11-05 copying botocore/data/transfer/2018-11-05/endpoint-rule-set-1.json -> build/lib/botocore/data/transfer/2018-11-05 copying botocore/data/transfer/2018-11-05/examples-1.json -> build/lib/botocore/data/transfer/2018-11-05 copying botocore/data/transfer/2018-11-05/paginators-1.json -> build/lib/botocore/data/transfer/2018-11-05 copying botocore/data/transfer/2018-11-05/service-2.json -> build/lib/botocore/data/transfer/2018-11-05 copying botocore/data/transfer/2018-11-05/waiters-2.json -> build/lib/botocore/data/transfer/2018-11-05 creating build/lib/botocore/data/translate creating build/lib/botocore/data/translate/2017-07-01 copying botocore/data/translate/2017-07-01/endpoint-rule-set-1.json -> build/lib/botocore/data/translate/2017-07-01 copying botocore/data/translate/2017-07-01/examples-1.json -> build/lib/botocore/data/translate/2017-07-01 copying botocore/data/translate/2017-07-01/paginators-1.json -> build/lib/botocore/data/translate/2017-07-01 copying botocore/data/translate/2017-07-01/service-2.json -> build/lib/botocore/data/translate/2017-07-01 creating build/lib/botocore/data/trustedadvisor creating build/lib/botocore/data/trustedadvisor/2022-09-15 copying botocore/data/trustedadvisor/2022-09-15/endpoint-rule-set-1.json -> build/lib/botocore/data/trustedadvisor/2022-09-15 copying botocore/data/trustedadvisor/2022-09-15/paginators-1.json -> build/lib/botocore/data/trustedadvisor/2022-09-15 copying botocore/data/trustedadvisor/2022-09-15/service-2.json -> build/lib/botocore/data/trustedadvisor/2022-09-15 copying botocore/data/trustedadvisor/2022-09-15/waiters-2.json -> build/lib/botocore/data/trustedadvisor/2022-09-15 creating build/lib/botocore/data/uxc creating build/lib/botocore/data/uxc/2024-07-01 copying botocore/data/uxc/2024-07-01/endpoint-rule-set-1.json -> build/lib/botocore/data/uxc/2024-07-01 copying botocore/data/uxc/2024-07-01/paginators-1.json -> build/lib/botocore/data/uxc/2024-07-01 copying botocore/data/uxc/2024-07-01/service-2.json -> build/lib/botocore/data/uxc/2024-07-01 copying botocore/data/uxc/2024-07-01/waiters-2.json -> build/lib/botocore/data/uxc/2024-07-01 creating build/lib/botocore/data/verifiedpermissions creating build/lib/botocore/data/verifiedpermissions/2021-12-01 copying botocore/data/verifiedpermissions/2021-12-01/endpoint-rule-set-1.json -> build/lib/botocore/data/verifiedpermissions/2021-12-01 copying botocore/data/verifiedpermissions/2021-12-01/paginators-1.json -> build/lib/botocore/data/verifiedpermissions/2021-12-01 copying botocore/data/verifiedpermissions/2021-12-01/service-2.json -> build/lib/botocore/data/verifiedpermissions/2021-12-01 copying botocore/data/verifiedpermissions/2021-12-01/waiters-2.json -> build/lib/botocore/data/verifiedpermissions/2021-12-01 creating build/lib/botocore/data/voice-id creating build/lib/botocore/data/voice-id/2021-09-27 copying botocore/data/voice-id/2021-09-27/endpoint-rule-set-1.json -> build/lib/botocore/data/voice-id/2021-09-27 copying botocore/data/voice-id/2021-09-27/examples-1.json -> build/lib/botocore/data/voice-id/2021-09-27 copying botocore/data/voice-id/2021-09-27/paginators-1.json -> build/lib/botocore/data/voice-id/2021-09-27 copying botocore/data/voice-id/2021-09-27/service-2.json -> build/lib/botocore/data/voice-id/2021-09-27 creating build/lib/botocore/data/vpc-lattice creating build/lib/botocore/data/vpc-lattice/2022-11-30 copying botocore/data/vpc-lattice/2022-11-30/endpoint-rule-set-1.json -> build/lib/botocore/data/vpc-lattice/2022-11-30 copying botocore/data/vpc-lattice/2022-11-30/paginators-1.json -> build/lib/botocore/data/vpc-lattice/2022-11-30 copying botocore/data/vpc-lattice/2022-11-30/service-2.json -> build/lib/botocore/data/vpc-lattice/2022-11-30 copying botocore/data/vpc-lattice/2022-11-30/waiters-2.json -> build/lib/botocore/data/vpc-lattice/2022-11-30 creating build/lib/botocore/data/waf-regional creating build/lib/botocore/data/waf-regional/2016-11-28 copying botocore/data/waf-regional/2016-11-28/endpoint-rule-set-1.json -> build/lib/botocore/data/waf-regional/2016-11-28 copying botocore/data/waf-regional/2016-11-28/examples-1.json -> build/lib/botocore/data/waf-regional/2016-11-28 copying botocore/data/waf-regional/2016-11-28/paginators-1.json -> build/lib/botocore/data/waf-regional/2016-11-28 copying botocore/data/waf-regional/2016-11-28/service-2.json -> build/lib/botocore/data/waf-regional/2016-11-28 creating build/lib/botocore/data/waf creating build/lib/botocore/data/waf/2015-08-24 copying botocore/data/waf/2015-08-24/endpoint-rule-set-1.json -> build/lib/botocore/data/waf/2015-08-24 copying botocore/data/waf/2015-08-24/examples-1.json -> build/lib/botocore/data/waf/2015-08-24 copying botocore/data/waf/2015-08-24/paginators-1.json -> build/lib/botocore/data/waf/2015-08-24 copying botocore/data/waf/2015-08-24/service-2.json -> build/lib/botocore/data/waf/2015-08-24 creating build/lib/botocore/data/wafv2 creating build/lib/botocore/data/wafv2/2019-07-29 copying botocore/data/wafv2/2019-07-29/endpoint-rule-set-1.json -> build/lib/botocore/data/wafv2/2019-07-29 copying botocore/data/wafv2/2019-07-29/examples-1.json -> build/lib/botocore/data/wafv2/2019-07-29 copying botocore/data/wafv2/2019-07-29/paginators-1.json -> build/lib/botocore/data/wafv2/2019-07-29 copying botocore/data/wafv2/2019-07-29/service-2.json -> build/lib/botocore/data/wafv2/2019-07-29 creating build/lib/botocore/data/wellarchitected creating build/lib/botocore/data/wellarchitected/2020-03-31 copying botocore/data/wellarchitected/2020-03-31/endpoint-rule-set-1.json -> build/lib/botocore/data/wellarchitected/2020-03-31 copying botocore/data/wellarchitected/2020-03-31/examples-1.json -> build/lib/botocore/data/wellarchitected/2020-03-31 copying botocore/data/wellarchitected/2020-03-31/paginators-1.json -> build/lib/botocore/data/wellarchitected/2020-03-31 copying botocore/data/wellarchitected/2020-03-31/service-2.json -> build/lib/botocore/data/wellarchitected/2020-03-31 creating build/lib/botocore/data/wickr creating build/lib/botocore/data/wickr/2024-02-01 copying botocore/data/wickr/2024-02-01/endpoint-rule-set-1.json -> build/lib/botocore/data/wickr/2024-02-01 copying botocore/data/wickr/2024-02-01/paginators-1.json -> build/lib/botocore/data/wickr/2024-02-01 copying botocore/data/wickr/2024-02-01/service-2.json -> build/lib/botocore/data/wickr/2024-02-01 copying botocore/data/wickr/2024-02-01/waiters-2.json -> build/lib/botocore/data/wickr/2024-02-01 creating build/lib/botocore/data/wisdom creating build/lib/botocore/data/wisdom/2020-10-19 copying botocore/data/wisdom/2020-10-19/endpoint-rule-set-1.json -> build/lib/botocore/data/wisdom/2020-10-19 copying botocore/data/wisdom/2020-10-19/examples-1.json -> build/lib/botocore/data/wisdom/2020-10-19 copying botocore/data/wisdom/2020-10-19/paginators-1.json -> build/lib/botocore/data/wisdom/2020-10-19 copying botocore/data/wisdom/2020-10-19/service-2.json -> build/lib/botocore/data/wisdom/2020-10-19 creating build/lib/botocore/data/workdocs creating build/lib/botocore/data/workdocs/2016-05-01 copying botocore/data/workdocs/2016-05-01/endpoint-rule-set-1.json -> build/lib/botocore/data/workdocs/2016-05-01 copying botocore/data/workdocs/2016-05-01/examples-1.json -> build/lib/botocore/data/workdocs/2016-05-01 copying botocore/data/workdocs/2016-05-01/paginators-1.json -> build/lib/botocore/data/workdocs/2016-05-01 copying botocore/data/workdocs/2016-05-01/service-2.json -> build/lib/botocore/data/workdocs/2016-05-01 creating build/lib/botocore/data/workmail creating build/lib/botocore/data/workmail/2017-10-01 copying botocore/data/workmail/2017-10-01/endpoint-rule-set-1.json -> build/lib/botocore/data/workmail/2017-10-01 copying botocore/data/workmail/2017-10-01/examples-1.json -> build/lib/botocore/data/workmail/2017-10-01 copying botocore/data/workmail/2017-10-01/paginators-1.json -> build/lib/botocore/data/workmail/2017-10-01 copying botocore/data/workmail/2017-10-01/service-2.json -> build/lib/botocore/data/workmail/2017-10-01 creating build/lib/botocore/data/workmailmessageflow creating build/lib/botocore/data/workmailmessageflow/2019-05-01 copying botocore/data/workmailmessageflow/2019-05-01/endpoint-rule-set-1.json -> build/lib/botocore/data/workmailmessageflow/2019-05-01 copying botocore/data/workmailmessageflow/2019-05-01/examples-1.json -> build/lib/botocore/data/workmailmessageflow/2019-05-01 copying botocore/data/workmailmessageflow/2019-05-01/paginators-1.json -> build/lib/botocore/data/workmailmessageflow/2019-05-01 copying botocore/data/workmailmessageflow/2019-05-01/service-2.json -> build/lib/botocore/data/workmailmessageflow/2019-05-01 creating build/lib/botocore/data/workspaces-instances creating build/lib/botocore/data/workspaces-instances/2022-07-26 copying botocore/data/workspaces-instances/2022-07-26/endpoint-rule-set-1.json -> build/lib/botocore/data/workspaces-instances/2022-07-26 copying botocore/data/workspaces-instances/2022-07-26/paginators-1.json -> build/lib/botocore/data/workspaces-instances/2022-07-26 copying botocore/data/workspaces-instances/2022-07-26/service-2.json -> build/lib/botocore/data/workspaces-instances/2022-07-26 copying botocore/data/workspaces-instances/2022-07-26/waiters-2.json -> build/lib/botocore/data/workspaces-instances/2022-07-26 creating build/lib/botocore/data/workspaces-thin-client creating build/lib/botocore/data/workspaces-thin-client/2023-08-22 copying botocore/data/workspaces-thin-client/2023-08-22/endpoint-rule-set-1.json -> build/lib/botocore/data/workspaces-thin-client/2023-08-22 copying botocore/data/workspaces-thin-client/2023-08-22/paginators-1.json -> build/lib/botocore/data/workspaces-thin-client/2023-08-22 copying botocore/data/workspaces-thin-client/2023-08-22/service-2.json -> build/lib/botocore/data/workspaces-thin-client/2023-08-22 creating build/lib/botocore/data/workspaces-web creating build/lib/botocore/data/workspaces-web/2020-07-08 copying botocore/data/workspaces-web/2020-07-08/endpoint-rule-set-1.json -> build/lib/botocore/data/workspaces-web/2020-07-08 copying botocore/data/workspaces-web/2020-07-08/examples-1.json -> build/lib/botocore/data/workspaces-web/2020-07-08 copying botocore/data/workspaces-web/2020-07-08/paginators-1.json -> build/lib/botocore/data/workspaces-web/2020-07-08 copying botocore/data/workspaces-web/2020-07-08/service-2.json -> build/lib/botocore/data/workspaces-web/2020-07-08 copying botocore/data/workspaces-web/2020-07-08/waiters-2.json -> build/lib/botocore/data/workspaces-web/2020-07-08 creating build/lib/botocore/data/workspaces creating build/lib/botocore/data/workspaces/2015-04-08 copying botocore/data/workspaces/2015-04-08/endpoint-rule-set-1.json -> build/lib/botocore/data/workspaces/2015-04-08 copying botocore/data/workspaces/2015-04-08/examples-1.json -> build/lib/botocore/data/workspaces/2015-04-08 copying botocore/data/workspaces/2015-04-08/paginators-1.json -> build/lib/botocore/data/workspaces/2015-04-08 copying botocore/data/workspaces/2015-04-08/service-2.json -> build/lib/botocore/data/workspaces/2015-04-08 creating build/lib/botocore/data/xray creating build/lib/botocore/data/xray/2016-04-12 copying botocore/data/xray/2016-04-12/endpoint-rule-set-1.json -> build/lib/botocore/data/xray/2016-04-12 copying botocore/data/xray/2016-04-12/examples-1.json -> build/lib/botocore/data/xray/2016-04-12 copying botocore/data/xray/2016-04-12/paginators-1.json -> build/lib/botocore/data/xray/2016-04-12 copying botocore/data/xray/2016-04-12/service-2.json -> build/lib/botocore/data/xray/2016-04-12 installing to build/bdist.linux-aarch64/wheel running install running install_lib creating build/bdist.linux-aarch64 creating build/bdist.linux-aarch64/wheel creating build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/__init__.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/args.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/auth.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/awsrequest.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/client.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/compat.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/compress.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/config.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/configloader.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/configprovider.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/context.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/credentials.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/discovery.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/endpoint.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/endpoint_provider.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/errorfactory.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/eventstream.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/exceptions.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/handlers.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/history.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/hooks.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/httpchecksum.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/httpsession.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/loaders.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/model.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/monitoring.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/paginate.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/parsers.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/plugin.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/regions.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/response.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/retryhandler.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/serialize.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/session.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/signers.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/stub.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/tokens.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/translate.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/useragent.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/utils.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/validate.py -> build/bdist.linux-aarch64/wheel/botocore copying build/lib/botocore/waiter.py -> build/bdist.linux-aarch64/wheel/botocore creating build/bdist.linux-aarch64/wheel/botocore/crt copying build/lib/botocore/crt/__init__.py -> build/bdist.linux-aarch64/wheel/botocore/crt copying build/lib/botocore/crt/auth.py -> build/bdist.linux-aarch64/wheel/botocore/crt creating build/bdist.linux-aarch64/wheel/botocore/docs copying build/lib/botocore/docs/__init__.py -> build/bdist.linux-aarch64/wheel/botocore/docs copying build/lib/botocore/docs/client.py -> build/bdist.linux-aarch64/wheel/botocore/docs copying build/lib/botocore/docs/docstring.py -> build/bdist.linux-aarch64/wheel/botocore/docs copying build/lib/botocore/docs/example.py -> build/bdist.linux-aarch64/wheel/botocore/docs copying build/lib/botocore/docs/method.py -> build/bdist.linux-aarch64/wheel/botocore/docs copying build/lib/botocore/docs/paginator.py -> build/bdist.linux-aarch64/wheel/botocore/docs copying build/lib/botocore/docs/params.py -> build/bdist.linux-aarch64/wheel/botocore/docs copying build/lib/botocore/docs/service.py -> build/bdist.linux-aarch64/wheel/botocore/docs copying build/lib/botocore/docs/shape.py -> build/bdist.linux-aarch64/wheel/botocore/docs copying build/lib/botocore/docs/sharedexample.py -> build/bdist.linux-aarch64/wheel/botocore/docs copying build/lib/botocore/docs/translator.py -> build/bdist.linux-aarch64/wheel/botocore/docs copying build/lib/botocore/docs/utils.py -> build/bdist.linux-aarch64/wheel/botocore/docs copying build/lib/botocore/docs/waiter.py -> build/bdist.linux-aarch64/wheel/botocore/docs creating build/bdist.linux-aarch64/wheel/botocore/docs/bcdoc copying build/lib/botocore/docs/bcdoc/__init__.py -> build/bdist.linux-aarch64/wheel/botocore/docs/bcdoc copying build/lib/botocore/docs/bcdoc/docstringparser.py -> build/bdist.linux-aarch64/wheel/botocore/docs/bcdoc copying build/lib/botocore/docs/bcdoc/restdoc.py -> build/bdist.linux-aarch64/wheel/botocore/docs/bcdoc copying build/lib/botocore/docs/bcdoc/style.py -> build/bdist.linux-aarch64/wheel/botocore/docs/bcdoc creating build/bdist.linux-aarch64/wheel/botocore/retries copying build/lib/botocore/retries/__init__.py -> build/bdist.linux-aarch64/wheel/botocore/retries copying build/lib/botocore/retries/adaptive.py -> build/bdist.linux-aarch64/wheel/botocore/retries copying build/lib/botocore/retries/base.py -> build/bdist.linux-aarch64/wheel/botocore/retries copying build/lib/botocore/retries/bucket.py -> build/bdist.linux-aarch64/wheel/botocore/retries copying build/lib/botocore/retries/quota.py -> build/bdist.linux-aarch64/wheel/botocore/retries copying build/lib/botocore/retries/special.py -> build/bdist.linux-aarch64/wheel/botocore/retries copying build/lib/botocore/retries/standard.py -> build/bdist.linux-aarch64/wheel/botocore/retries copying build/lib/botocore/retries/throttling.py -> build/bdist.linux-aarch64/wheel/botocore/retries creating build/bdist.linux-aarch64/wheel/botocore/vendored copying build/lib/botocore/vendored/__init__.py -> build/bdist.linux-aarch64/wheel/botocore/vendored copying build/lib/botocore/vendored/six.py -> build/bdist.linux-aarch64/wheel/botocore/vendored creating build/bdist.linux-aarch64/wheel/botocore/vendored/requests copying build/lib/botocore/vendored/requests/__init__.py -> build/bdist.linux-aarch64/wheel/botocore/vendored/requests copying build/lib/botocore/vendored/requests/exceptions.py -> build/bdist.linux-aarch64/wheel/botocore/vendored/requests creating build/bdist.linux-aarch64/wheel/botocore/vendored/requests/packages copying build/lib/botocore/vendored/requests/packages/__init__.py -> build/bdist.linux-aarch64/wheel/botocore/vendored/requests/packages creating build/bdist.linux-aarch64/wheel/botocore/vendored/requests/packages/urllib3 copying build/lib/botocore/vendored/requests/packages/urllib3/__init__.py -> build/bdist.linux-aarch64/wheel/botocore/vendored/requests/packages/urllib3 copying build/lib/botocore/vendored/requests/packages/urllib3/exceptions.py -> build/bdist.linux-aarch64/wheel/botocore/vendored/requests/packages/urllib3 copying build/lib/botocore/cacert.pem -> build/bdist.linux-aarch64/wheel/botocore creating build/bdist.linux-aarch64/wheel/botocore/data copying build/lib/botocore/data/_retry.json -> build/bdist.linux-aarch64/wheel/botocore/data copying build/lib/botocore/data/endpoints.json -> build/bdist.linux-aarch64/wheel/botocore/data copying build/lib/botocore/data/partitions.json -> build/bdist.linux-aarch64/wheel/botocore/data copying build/lib/botocore/data/sdk-default-configuration.json -> build/bdist.linux-aarch64/wheel/botocore/data creating build/bdist.linux-aarch64/wheel/botocore/data/accessanalyzer creating build/bdist.linux-aarch64/wheel/botocore/data/accessanalyzer/2019-11-01 copying build/lib/botocore/data/accessanalyzer/2019-11-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/accessanalyzer/2019-11-01 copying build/lib/botocore/data/accessanalyzer/2019-11-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/accessanalyzer/2019-11-01 copying build/lib/botocore/data/accessanalyzer/2019-11-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/accessanalyzer/2019-11-01 copying build/lib/botocore/data/accessanalyzer/2019-11-01/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/accessanalyzer/2019-11-01 copying build/lib/botocore/data/accessanalyzer/2019-11-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/accessanalyzer/2019-11-01 creating build/bdist.linux-aarch64/wheel/botocore/data/account creating build/bdist.linux-aarch64/wheel/botocore/data/account/2021-02-01 copying build/lib/botocore/data/account/2021-02-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/account/2021-02-01 copying build/lib/botocore/data/account/2021-02-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/account/2021-02-01 copying build/lib/botocore/data/account/2021-02-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/account/2021-02-01 copying build/lib/botocore/data/account/2021-02-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/account/2021-02-01 creating build/bdist.linux-aarch64/wheel/botocore/data/acm-pca creating build/bdist.linux-aarch64/wheel/botocore/data/acm-pca/2017-08-22 copying build/lib/botocore/data/acm-pca/2017-08-22/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/acm-pca/2017-08-22 copying build/lib/botocore/data/acm-pca/2017-08-22/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/acm-pca/2017-08-22 copying build/lib/botocore/data/acm-pca/2017-08-22/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/acm-pca/2017-08-22 copying build/lib/botocore/data/acm-pca/2017-08-22/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/acm-pca/2017-08-22 copying build/lib/botocore/data/acm-pca/2017-08-22/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/acm-pca/2017-08-22 creating build/bdist.linux-aarch64/wheel/botocore/data/acm creating build/bdist.linux-aarch64/wheel/botocore/data/acm/2015-12-08 copying build/lib/botocore/data/acm/2015-12-08/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/acm/2015-12-08 copying build/lib/botocore/data/acm/2015-12-08/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/acm/2015-12-08 copying build/lib/botocore/data/acm/2015-12-08/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/acm/2015-12-08 copying build/lib/botocore/data/acm/2015-12-08/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/acm/2015-12-08 copying build/lib/botocore/data/acm/2015-12-08/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/acm/2015-12-08 creating build/bdist.linux-aarch64/wheel/botocore/data/aiops creating build/bdist.linux-aarch64/wheel/botocore/data/aiops/2018-05-10 copying build/lib/botocore/data/aiops/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/aiops/2018-05-10 copying build/lib/botocore/data/aiops/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/aiops/2018-05-10 copying build/lib/botocore/data/aiops/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/aiops/2018-05-10 copying build/lib/botocore/data/aiops/2018-05-10/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/aiops/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/amp creating build/bdist.linux-aarch64/wheel/botocore/data/amp/2020-08-01 copying build/lib/botocore/data/amp/2020-08-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/amp/2020-08-01 copying build/lib/botocore/data/amp/2020-08-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/amp/2020-08-01 copying build/lib/botocore/data/amp/2020-08-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/amp/2020-08-01 copying build/lib/botocore/data/amp/2020-08-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/amp/2020-08-01 copying build/lib/botocore/data/amp/2020-08-01/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/amp/2020-08-01 creating build/bdist.linux-aarch64/wheel/botocore/data/amplify creating build/bdist.linux-aarch64/wheel/botocore/data/amplify/2017-07-25 copying build/lib/botocore/data/amplify/2017-07-25/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/amplify/2017-07-25 copying build/lib/botocore/data/amplify/2017-07-25/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/amplify/2017-07-25 copying build/lib/botocore/data/amplify/2017-07-25/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/amplify/2017-07-25 copying build/lib/botocore/data/amplify/2017-07-25/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/amplify/2017-07-25 creating build/bdist.linux-aarch64/wheel/botocore/data/amplifybackend creating build/bdist.linux-aarch64/wheel/botocore/data/amplifybackend/2020-08-11 copying build/lib/botocore/data/amplifybackend/2020-08-11/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/amplifybackend/2020-08-11 copying build/lib/botocore/data/amplifybackend/2020-08-11/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/amplifybackend/2020-08-11 copying build/lib/botocore/data/amplifybackend/2020-08-11/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/amplifybackend/2020-08-11 creating build/bdist.linux-aarch64/wheel/botocore/data/amplifyuibuilder creating build/bdist.linux-aarch64/wheel/botocore/data/amplifyuibuilder/2021-08-11 copying build/lib/botocore/data/amplifyuibuilder/2021-08-11/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/amplifyuibuilder/2021-08-11 copying build/lib/botocore/data/amplifyuibuilder/2021-08-11/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/amplifyuibuilder/2021-08-11 copying build/lib/botocore/data/amplifyuibuilder/2021-08-11/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/amplifyuibuilder/2021-08-11 copying build/lib/botocore/data/amplifyuibuilder/2021-08-11/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/amplifyuibuilder/2021-08-11 copying build/lib/botocore/data/amplifyuibuilder/2021-08-11/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/amplifyuibuilder/2021-08-11 creating build/bdist.linux-aarch64/wheel/botocore/data/apigateway creating build/bdist.linux-aarch64/wheel/botocore/data/apigateway/2015-07-09 copying build/lib/botocore/data/apigateway/2015-07-09/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/apigateway/2015-07-09 copying build/lib/botocore/data/apigateway/2015-07-09/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/apigateway/2015-07-09 copying build/lib/botocore/data/apigateway/2015-07-09/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/apigateway/2015-07-09 copying build/lib/botocore/data/apigateway/2015-07-09/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/apigateway/2015-07-09 creating build/bdist.linux-aarch64/wheel/botocore/data/apigatewaymanagementapi creating build/bdist.linux-aarch64/wheel/botocore/data/apigatewaymanagementapi/2018-11-29 copying build/lib/botocore/data/apigatewaymanagementapi/2018-11-29/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/apigatewaymanagementapi/2018-11-29 copying build/lib/botocore/data/apigatewaymanagementapi/2018-11-29/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/apigatewaymanagementapi/2018-11-29 copying build/lib/botocore/data/apigatewaymanagementapi/2018-11-29/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/apigatewaymanagementapi/2018-11-29 creating build/bdist.linux-aarch64/wheel/botocore/data/apigatewayv2 creating build/bdist.linux-aarch64/wheel/botocore/data/apigatewayv2/2018-11-29 copying build/lib/botocore/data/apigatewayv2/2018-11-29/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/apigatewayv2/2018-11-29 copying build/lib/botocore/data/apigatewayv2/2018-11-29/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/apigatewayv2/2018-11-29 copying build/lib/botocore/data/apigatewayv2/2018-11-29/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/apigatewayv2/2018-11-29 creating build/bdist.linux-aarch64/wheel/botocore/data/appconfig creating build/bdist.linux-aarch64/wheel/botocore/data/appconfig/2019-10-09 copying build/lib/botocore/data/appconfig/2019-10-09/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/appconfig/2019-10-09 copying build/lib/botocore/data/appconfig/2019-10-09/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/appconfig/2019-10-09 copying build/lib/botocore/data/appconfig/2019-10-09/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/appconfig/2019-10-09 copying build/lib/botocore/data/appconfig/2019-10-09/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/appconfig/2019-10-09 copying build/lib/botocore/data/appconfig/2019-10-09/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/appconfig/2019-10-09 creating build/bdist.linux-aarch64/wheel/botocore/data/appconfigdata creating build/bdist.linux-aarch64/wheel/botocore/data/appconfigdata/2021-11-11 copying build/lib/botocore/data/appconfigdata/2021-11-11/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/appconfigdata/2021-11-11 copying build/lib/botocore/data/appconfigdata/2021-11-11/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/appconfigdata/2021-11-11 copying build/lib/botocore/data/appconfigdata/2021-11-11/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/appconfigdata/2021-11-11 copying build/lib/botocore/data/appconfigdata/2021-11-11/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/appconfigdata/2021-11-11 creating build/bdist.linux-aarch64/wheel/botocore/data/appfabric creating build/bdist.linux-aarch64/wheel/botocore/data/appfabric/2023-05-19 copying build/lib/botocore/data/appfabric/2023-05-19/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/appfabric/2023-05-19 copying build/lib/botocore/data/appfabric/2023-05-19/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/appfabric/2023-05-19 copying build/lib/botocore/data/appfabric/2023-05-19/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/appfabric/2023-05-19 copying build/lib/botocore/data/appfabric/2023-05-19/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/appfabric/2023-05-19 creating build/bdist.linux-aarch64/wheel/botocore/data/appflow creating build/bdist.linux-aarch64/wheel/botocore/data/appflow/2020-08-23 copying build/lib/botocore/data/appflow/2020-08-23/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/appflow/2020-08-23 copying build/lib/botocore/data/appflow/2020-08-23/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/appflow/2020-08-23 copying build/lib/botocore/data/appflow/2020-08-23/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/appflow/2020-08-23 copying build/lib/botocore/data/appflow/2020-08-23/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/appflow/2020-08-23 creating build/bdist.linux-aarch64/wheel/botocore/data/appintegrations creating build/bdist.linux-aarch64/wheel/botocore/data/appintegrations/2020-07-29 copying build/lib/botocore/data/appintegrations/2020-07-29/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/appintegrations/2020-07-29 copying build/lib/botocore/data/appintegrations/2020-07-29/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/appintegrations/2020-07-29 copying build/lib/botocore/data/appintegrations/2020-07-29/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/appintegrations/2020-07-29 copying build/lib/botocore/data/appintegrations/2020-07-29/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/appintegrations/2020-07-29 creating build/bdist.linux-aarch64/wheel/botocore/data/application-autoscaling creating build/bdist.linux-aarch64/wheel/botocore/data/application-autoscaling/2016-02-06 copying build/lib/botocore/data/application-autoscaling/2016-02-06/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/application-autoscaling/2016-02-06 copying build/lib/botocore/data/application-autoscaling/2016-02-06/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/application-autoscaling/2016-02-06 copying build/lib/botocore/data/application-autoscaling/2016-02-06/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/application-autoscaling/2016-02-06 copying build/lib/botocore/data/application-autoscaling/2016-02-06/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/application-autoscaling/2016-02-06 creating build/bdist.linux-aarch64/wheel/botocore/data/application-insights creating build/bdist.linux-aarch64/wheel/botocore/data/application-insights/2018-11-25 copying build/lib/botocore/data/application-insights/2018-11-25/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/application-insights/2018-11-25 copying build/lib/botocore/data/application-insights/2018-11-25/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/application-insights/2018-11-25 copying build/lib/botocore/data/application-insights/2018-11-25/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/application-insights/2018-11-25 copying build/lib/botocore/data/application-insights/2018-11-25/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/application-insights/2018-11-25 creating build/bdist.linux-aarch64/wheel/botocore/data/application-signals creating build/bdist.linux-aarch64/wheel/botocore/data/application-signals/2024-04-15 copying build/lib/botocore/data/application-signals/2024-04-15/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/application-signals/2024-04-15 copying build/lib/botocore/data/application-signals/2024-04-15/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/application-signals/2024-04-15 copying build/lib/botocore/data/application-signals/2024-04-15/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/application-signals/2024-04-15 copying build/lib/botocore/data/application-signals/2024-04-15/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/application-signals/2024-04-15 copying build/lib/botocore/data/application-signals/2024-04-15/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/application-signals/2024-04-15 creating build/bdist.linux-aarch64/wheel/botocore/data/applicationcostprofiler creating build/bdist.linux-aarch64/wheel/botocore/data/applicationcostprofiler/2020-09-10 copying build/lib/botocore/data/applicationcostprofiler/2020-09-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/applicationcostprofiler/2020-09-10 copying build/lib/botocore/data/applicationcostprofiler/2020-09-10/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/applicationcostprofiler/2020-09-10 copying build/lib/botocore/data/applicationcostprofiler/2020-09-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/applicationcostprofiler/2020-09-10 copying build/lib/botocore/data/applicationcostprofiler/2020-09-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/applicationcostprofiler/2020-09-10 creating build/bdist.linux-aarch64/wheel/botocore/data/appmesh creating build/bdist.linux-aarch64/wheel/botocore/data/appmesh/2018-10-01 copying build/lib/botocore/data/appmesh/2018-10-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/appmesh/2018-10-01 copying build/lib/botocore/data/appmesh/2018-10-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/appmesh/2018-10-01 copying build/lib/botocore/data/appmesh/2018-10-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/appmesh/2018-10-01 copying build/lib/botocore/data/appmesh/2018-10-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/appmesh/2018-10-01 creating build/bdist.linux-aarch64/wheel/botocore/data/appmesh/2019-01-25 copying build/lib/botocore/data/appmesh/2019-01-25/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/appmesh/2019-01-25 copying build/lib/botocore/data/appmesh/2019-01-25/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/appmesh/2019-01-25 copying build/lib/botocore/data/appmesh/2019-01-25/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/appmesh/2019-01-25 copying build/lib/botocore/data/appmesh/2019-01-25/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/appmesh/2019-01-25 creating build/bdist.linux-aarch64/wheel/botocore/data/apprunner creating build/bdist.linux-aarch64/wheel/botocore/data/apprunner/2020-05-15 copying build/lib/botocore/data/apprunner/2020-05-15/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/apprunner/2020-05-15 copying build/lib/botocore/data/apprunner/2020-05-15/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/apprunner/2020-05-15 copying build/lib/botocore/data/apprunner/2020-05-15/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/apprunner/2020-05-15 copying build/lib/botocore/data/apprunner/2020-05-15/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/apprunner/2020-05-15 creating build/bdist.linux-aarch64/wheel/botocore/data/appstream creating build/bdist.linux-aarch64/wheel/botocore/data/appstream/2016-12-01 copying build/lib/botocore/data/appstream/2016-12-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/appstream/2016-12-01 copying build/lib/botocore/data/appstream/2016-12-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/appstream/2016-12-01 copying build/lib/botocore/data/appstream/2016-12-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/appstream/2016-12-01 copying build/lib/botocore/data/appstream/2016-12-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/appstream/2016-12-01 copying build/lib/botocore/data/appstream/2016-12-01/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/appstream/2016-12-01 creating build/bdist.linux-aarch64/wheel/botocore/data/appsync creating build/bdist.linux-aarch64/wheel/botocore/data/appsync/2017-07-25 copying build/lib/botocore/data/appsync/2017-07-25/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/appsync/2017-07-25 copying build/lib/botocore/data/appsync/2017-07-25/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/appsync/2017-07-25 copying build/lib/botocore/data/appsync/2017-07-25/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/appsync/2017-07-25 copying build/lib/botocore/data/appsync/2017-07-25/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/appsync/2017-07-25 creating build/bdist.linux-aarch64/wheel/botocore/data/arc-region-switch creating build/bdist.linux-aarch64/wheel/botocore/data/arc-region-switch/2022-07-26 copying build/lib/botocore/data/arc-region-switch/2022-07-26/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/arc-region-switch/2022-07-26 copying build/lib/botocore/data/arc-region-switch/2022-07-26/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/arc-region-switch/2022-07-26 copying build/lib/botocore/data/arc-region-switch/2022-07-26/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/arc-region-switch/2022-07-26 copying build/lib/botocore/data/arc-region-switch/2022-07-26/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/arc-region-switch/2022-07-26 copying build/lib/botocore/data/arc-region-switch/2022-07-26/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/arc-region-switch/2022-07-26 creating build/bdist.linux-aarch64/wheel/botocore/data/arc-zonal-shift creating build/bdist.linux-aarch64/wheel/botocore/data/arc-zonal-shift/2022-10-30 copying build/lib/botocore/data/arc-zonal-shift/2022-10-30/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/arc-zonal-shift/2022-10-30 copying build/lib/botocore/data/arc-zonal-shift/2022-10-30/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/arc-zonal-shift/2022-10-30 copying build/lib/botocore/data/arc-zonal-shift/2022-10-30/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/arc-zonal-shift/2022-10-30 copying build/lib/botocore/data/arc-zonal-shift/2022-10-30/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/arc-zonal-shift/2022-10-30 creating build/bdist.linux-aarch64/wheel/botocore/data/artifact creating build/bdist.linux-aarch64/wheel/botocore/data/artifact/2018-05-10 copying build/lib/botocore/data/artifact/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/artifact/2018-05-10 copying build/lib/botocore/data/artifact/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/artifact/2018-05-10 copying build/lib/botocore/data/artifact/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/artifact/2018-05-10 copying build/lib/botocore/data/artifact/2018-05-10/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/artifact/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/athena creating build/bdist.linux-aarch64/wheel/botocore/data/athena/2017-05-18 copying build/lib/botocore/data/athena/2017-05-18/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/athena/2017-05-18 copying build/lib/botocore/data/athena/2017-05-18/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/athena/2017-05-18 copying build/lib/botocore/data/athena/2017-05-18/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/athena/2017-05-18 copying build/lib/botocore/data/athena/2017-05-18/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/athena/2017-05-18 creating build/bdist.linux-aarch64/wheel/botocore/data/auditmanager creating build/bdist.linux-aarch64/wheel/botocore/data/auditmanager/2017-07-25 copying build/lib/botocore/data/auditmanager/2017-07-25/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/auditmanager/2017-07-25 copying build/lib/botocore/data/auditmanager/2017-07-25/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/auditmanager/2017-07-25 copying build/lib/botocore/data/auditmanager/2017-07-25/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/auditmanager/2017-07-25 copying build/lib/botocore/data/auditmanager/2017-07-25/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/auditmanager/2017-07-25 creating build/bdist.linux-aarch64/wheel/botocore/data/autoscaling-plans creating build/bdist.linux-aarch64/wheel/botocore/data/autoscaling-plans/2018-01-06 copying build/lib/botocore/data/autoscaling-plans/2018-01-06/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/autoscaling-plans/2018-01-06 copying build/lib/botocore/data/autoscaling-plans/2018-01-06/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/autoscaling-plans/2018-01-06 copying build/lib/botocore/data/autoscaling-plans/2018-01-06/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/autoscaling-plans/2018-01-06 copying build/lib/botocore/data/autoscaling-plans/2018-01-06/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/autoscaling-plans/2018-01-06 creating build/bdist.linux-aarch64/wheel/botocore/data/autoscaling creating build/bdist.linux-aarch64/wheel/botocore/data/autoscaling/2011-01-01 copying build/lib/botocore/data/autoscaling/2011-01-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/autoscaling/2011-01-01 copying build/lib/botocore/data/autoscaling/2011-01-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/autoscaling/2011-01-01 copying build/lib/botocore/data/autoscaling/2011-01-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/autoscaling/2011-01-01 copying build/lib/botocore/data/autoscaling/2011-01-01/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/autoscaling/2011-01-01 copying build/lib/botocore/data/autoscaling/2011-01-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/autoscaling/2011-01-01 creating build/bdist.linux-aarch64/wheel/botocore/data/b2bi creating build/bdist.linux-aarch64/wheel/botocore/data/b2bi/2022-06-23 copying build/lib/botocore/data/b2bi/2022-06-23/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/b2bi/2022-06-23 copying build/lib/botocore/data/b2bi/2022-06-23/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/b2bi/2022-06-23 copying build/lib/botocore/data/b2bi/2022-06-23/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/b2bi/2022-06-23 copying build/lib/botocore/data/b2bi/2022-06-23/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/b2bi/2022-06-23 creating build/bdist.linux-aarch64/wheel/botocore/data/backup-gateway creating build/bdist.linux-aarch64/wheel/botocore/data/backup-gateway/2021-01-01 copying build/lib/botocore/data/backup-gateway/2021-01-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/backup-gateway/2021-01-01 copying build/lib/botocore/data/backup-gateway/2021-01-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/backup-gateway/2021-01-01 copying build/lib/botocore/data/backup-gateway/2021-01-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/backup-gateway/2021-01-01 copying build/lib/botocore/data/backup-gateway/2021-01-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/backup-gateway/2021-01-01 creating build/bdist.linux-aarch64/wheel/botocore/data/backup creating build/bdist.linux-aarch64/wheel/botocore/data/backup/2018-11-15 copying build/lib/botocore/data/backup/2018-11-15/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/backup/2018-11-15 copying build/lib/botocore/data/backup/2018-11-15/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/backup/2018-11-15 copying build/lib/botocore/data/backup/2018-11-15/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/backup/2018-11-15 copying build/lib/botocore/data/backup/2018-11-15/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/backup/2018-11-15 copying build/lib/botocore/data/backup/2018-11-15/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/backup/2018-11-15 creating build/bdist.linux-aarch64/wheel/botocore/data/backupsearch creating build/bdist.linux-aarch64/wheel/botocore/data/backupsearch/2018-05-10 copying build/lib/botocore/data/backupsearch/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/backupsearch/2018-05-10 copying build/lib/botocore/data/backupsearch/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/backupsearch/2018-05-10 copying build/lib/botocore/data/backupsearch/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/backupsearch/2018-05-10 copying build/lib/botocore/data/backupsearch/2018-05-10/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/backupsearch/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/batch creating build/bdist.linux-aarch64/wheel/botocore/data/batch/2016-08-10 copying build/lib/botocore/data/batch/2016-08-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/batch/2016-08-10 copying build/lib/botocore/data/batch/2016-08-10/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/batch/2016-08-10 copying build/lib/botocore/data/batch/2016-08-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/batch/2016-08-10 copying build/lib/botocore/data/batch/2016-08-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/batch/2016-08-10 creating build/bdist.linux-aarch64/wheel/botocore/data/bcm-dashboards creating build/bdist.linux-aarch64/wheel/botocore/data/bcm-dashboards/2025-08-18 copying build/lib/botocore/data/bcm-dashboards/2025-08-18/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/bcm-dashboards/2025-08-18 copying build/lib/botocore/data/bcm-dashboards/2025-08-18/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/bcm-dashboards/2025-08-18 copying build/lib/botocore/data/bcm-dashboards/2025-08-18/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/bcm-dashboards/2025-08-18 copying build/lib/botocore/data/bcm-dashboards/2025-08-18/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/bcm-dashboards/2025-08-18 creating build/bdist.linux-aarch64/wheel/botocore/data/bcm-data-exports creating build/bdist.linux-aarch64/wheel/botocore/data/bcm-data-exports/2023-11-26 copying build/lib/botocore/data/bcm-data-exports/2023-11-26/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/bcm-data-exports/2023-11-26 copying build/lib/botocore/data/bcm-data-exports/2023-11-26/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/bcm-data-exports/2023-11-26 copying build/lib/botocore/data/bcm-data-exports/2023-11-26/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/bcm-data-exports/2023-11-26 creating build/bdist.linux-aarch64/wheel/botocore/data/bcm-pricing-calculator creating build/bdist.linux-aarch64/wheel/botocore/data/bcm-pricing-calculator/2024-06-19 copying build/lib/botocore/data/bcm-pricing-calculator/2024-06-19/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/bcm-pricing-calculator/2024-06-19 copying build/lib/botocore/data/bcm-pricing-calculator/2024-06-19/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/bcm-pricing-calculator/2024-06-19 copying build/lib/botocore/data/bcm-pricing-calculator/2024-06-19/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/bcm-pricing-calculator/2024-06-19 copying build/lib/botocore/data/bcm-pricing-calculator/2024-06-19/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/bcm-pricing-calculator/2024-06-19 creating build/bdist.linux-aarch64/wheel/botocore/data/bcm-recommended-actions creating build/bdist.linux-aarch64/wheel/botocore/data/bcm-recommended-actions/2024-11-14 copying build/lib/botocore/data/bcm-recommended-actions/2024-11-14/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/bcm-recommended-actions/2024-11-14 copying build/lib/botocore/data/bcm-recommended-actions/2024-11-14/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/bcm-recommended-actions/2024-11-14 copying build/lib/botocore/data/bcm-recommended-actions/2024-11-14/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/bcm-recommended-actions/2024-11-14 copying build/lib/botocore/data/bcm-recommended-actions/2024-11-14/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/bcm-recommended-actions/2024-11-14 creating build/bdist.linux-aarch64/wheel/botocore/data/bedrock-agent-runtime creating build/bdist.linux-aarch64/wheel/botocore/data/bedrock-agent-runtime/2023-07-26 copying build/lib/botocore/data/bedrock-agent-runtime/2023-07-26/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/bedrock-agent-runtime/2023-07-26 copying build/lib/botocore/data/bedrock-agent-runtime/2023-07-26/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/bedrock-agent-runtime/2023-07-26 copying build/lib/botocore/data/bedrock-agent-runtime/2023-07-26/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/bedrock-agent-runtime/2023-07-26 copying build/lib/botocore/data/bedrock-agent-runtime/2023-07-26/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/bedrock-agent-runtime/2023-07-26 copying build/lib/botocore/data/bedrock-agent-runtime/2023-07-26/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/bedrock-agent-runtime/2023-07-26 creating build/bdist.linux-aarch64/wheel/botocore/data/bedrock-agent creating build/bdist.linux-aarch64/wheel/botocore/data/bedrock-agent/2023-06-05 copying build/lib/botocore/data/bedrock-agent/2023-06-05/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/bedrock-agent/2023-06-05 copying build/lib/botocore/data/bedrock-agent/2023-06-05/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/bedrock-agent/2023-06-05 copying build/lib/botocore/data/bedrock-agent/2023-06-05/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/bedrock-agent/2023-06-05 copying build/lib/botocore/data/bedrock-agent/2023-06-05/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/bedrock-agent/2023-06-05 creating build/bdist.linux-aarch64/wheel/botocore/data/bedrock-agentcore-control creating build/bdist.linux-aarch64/wheel/botocore/data/bedrock-agentcore-control/2023-06-05 copying build/lib/botocore/data/bedrock-agentcore-control/2023-06-05/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/bedrock-agentcore-control/2023-06-05 copying build/lib/botocore/data/bedrock-agentcore-control/2023-06-05/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/bedrock-agentcore-control/2023-06-05 copying build/lib/botocore/data/bedrock-agentcore-control/2023-06-05/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/bedrock-agentcore-control/2023-06-05 copying build/lib/botocore/data/bedrock-agentcore-control/2023-06-05/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/bedrock-agentcore-control/2023-06-05 creating build/bdist.linux-aarch64/wheel/botocore/data/bedrock-agentcore creating build/bdist.linux-aarch64/wheel/botocore/data/bedrock-agentcore/2024-02-28 copying build/lib/botocore/data/bedrock-agentcore/2024-02-28/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/bedrock-agentcore/2024-02-28 copying build/lib/botocore/data/bedrock-agentcore/2024-02-28/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/bedrock-agentcore/2024-02-28 copying build/lib/botocore/data/bedrock-agentcore/2024-02-28/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/bedrock-agentcore/2024-02-28 copying build/lib/botocore/data/bedrock-agentcore/2024-02-28/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/bedrock-agentcore/2024-02-28 creating build/bdist.linux-aarch64/wheel/botocore/data/bedrock-data-automation-runtime creating build/bdist.linux-aarch64/wheel/botocore/data/bedrock-data-automation-runtime/2024-06-13 copying build/lib/botocore/data/bedrock-data-automation-runtime/2024-06-13/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/bedrock-data-automation-runtime/2024-06-13 copying build/lib/botocore/data/bedrock-data-automation-runtime/2024-06-13/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/bedrock-data-automation-runtime/2024-06-13 copying build/lib/botocore/data/bedrock-data-automation-runtime/2024-06-13/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/bedrock-data-automation-runtime/2024-06-13 creating build/bdist.linux-aarch64/wheel/botocore/data/bedrock-data-automation creating build/bdist.linux-aarch64/wheel/botocore/data/bedrock-data-automation/2023-07-26 copying build/lib/botocore/data/bedrock-data-automation/2023-07-26/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/bedrock-data-automation/2023-07-26 copying build/lib/botocore/data/bedrock-data-automation/2023-07-26/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/bedrock-data-automation/2023-07-26 copying build/lib/botocore/data/bedrock-data-automation/2023-07-26/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/bedrock-data-automation/2023-07-26 creating build/bdist.linux-aarch64/wheel/botocore/data/bedrock-runtime creating build/bdist.linux-aarch64/wheel/botocore/data/bedrock-runtime/2023-09-30 copying build/lib/botocore/data/bedrock-runtime/2023-09-30/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/bedrock-runtime/2023-09-30 copying build/lib/botocore/data/bedrock-runtime/2023-09-30/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/bedrock-runtime/2023-09-30 copying build/lib/botocore/data/bedrock-runtime/2023-09-30/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/bedrock-runtime/2023-09-30 copying build/lib/botocore/data/bedrock-runtime/2023-09-30/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/bedrock-runtime/2023-09-30 creating build/bdist.linux-aarch64/wheel/botocore/data/bedrock creating build/bdist.linux-aarch64/wheel/botocore/data/bedrock/2023-04-20 copying build/lib/botocore/data/bedrock/2023-04-20/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/bedrock/2023-04-20 copying build/lib/botocore/data/bedrock/2023-04-20/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/bedrock/2023-04-20 copying build/lib/botocore/data/bedrock/2023-04-20/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/bedrock/2023-04-20 copying build/lib/botocore/data/bedrock/2023-04-20/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/bedrock/2023-04-20 creating build/bdist.linux-aarch64/wheel/botocore/data/billing creating build/bdist.linux-aarch64/wheel/botocore/data/billing/2023-09-07 copying build/lib/botocore/data/billing/2023-09-07/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/billing/2023-09-07 copying build/lib/botocore/data/billing/2023-09-07/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/billing/2023-09-07 copying build/lib/botocore/data/billing/2023-09-07/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/billing/2023-09-07 copying build/lib/botocore/data/billing/2023-09-07/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/billing/2023-09-07 creating build/bdist.linux-aarch64/wheel/botocore/data/billingconductor creating build/bdist.linux-aarch64/wheel/botocore/data/billingconductor/2021-07-30 copying build/lib/botocore/data/billingconductor/2021-07-30/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/billingconductor/2021-07-30 copying build/lib/botocore/data/billingconductor/2021-07-30/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/billingconductor/2021-07-30 copying build/lib/botocore/data/billingconductor/2021-07-30/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/billingconductor/2021-07-30 copying build/lib/botocore/data/billingconductor/2021-07-30/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/billingconductor/2021-07-30 copying build/lib/botocore/data/billingconductor/2021-07-30/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/billingconductor/2021-07-30 creating build/bdist.linux-aarch64/wheel/botocore/data/braket creating build/bdist.linux-aarch64/wheel/botocore/data/braket/2019-09-01 copying build/lib/botocore/data/braket/2019-09-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/braket/2019-09-01 copying build/lib/botocore/data/braket/2019-09-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/braket/2019-09-01 copying build/lib/botocore/data/braket/2019-09-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/braket/2019-09-01 copying build/lib/botocore/data/braket/2019-09-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/braket/2019-09-01 creating build/bdist.linux-aarch64/wheel/botocore/data/budgets creating build/bdist.linux-aarch64/wheel/botocore/data/budgets/2016-10-20 copying build/lib/botocore/data/budgets/2016-10-20/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/budgets/2016-10-20 copying build/lib/botocore/data/budgets/2016-10-20/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/budgets/2016-10-20 copying build/lib/botocore/data/budgets/2016-10-20/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/budgets/2016-10-20 copying build/lib/botocore/data/budgets/2016-10-20/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/budgets/2016-10-20 creating build/bdist.linux-aarch64/wheel/botocore/data/ce creating build/bdist.linux-aarch64/wheel/botocore/data/ce/2017-10-25 copying build/lib/botocore/data/ce/2017-10-25/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ce/2017-10-25 copying build/lib/botocore/data/ce/2017-10-25/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ce/2017-10-25 copying build/lib/botocore/data/ce/2017-10-25/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ce/2017-10-25 copying build/lib/botocore/data/ce/2017-10-25/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/ce/2017-10-25 copying build/lib/botocore/data/ce/2017-10-25/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ce/2017-10-25 creating build/bdist.linux-aarch64/wheel/botocore/data/chatbot creating build/bdist.linux-aarch64/wheel/botocore/data/chatbot/2017-10-11 copying build/lib/botocore/data/chatbot/2017-10-11/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/chatbot/2017-10-11 copying build/lib/botocore/data/chatbot/2017-10-11/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/chatbot/2017-10-11 copying build/lib/botocore/data/chatbot/2017-10-11/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/chatbot/2017-10-11 creating build/bdist.linux-aarch64/wheel/botocore/data/chime-sdk-identity creating build/bdist.linux-aarch64/wheel/botocore/data/chime-sdk-identity/2021-04-20 copying build/lib/botocore/data/chime-sdk-identity/2021-04-20/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/chime-sdk-identity/2021-04-20 copying build/lib/botocore/data/chime-sdk-identity/2021-04-20/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/chime-sdk-identity/2021-04-20 copying build/lib/botocore/data/chime-sdk-identity/2021-04-20/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/chime-sdk-identity/2021-04-20 copying build/lib/botocore/data/chime-sdk-identity/2021-04-20/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/chime-sdk-identity/2021-04-20 creating build/bdist.linux-aarch64/wheel/botocore/data/chime-sdk-media-pipelines creating build/bdist.linux-aarch64/wheel/botocore/data/chime-sdk-media-pipelines/2021-07-15 copying build/lib/botocore/data/chime-sdk-media-pipelines/2021-07-15/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/chime-sdk-media-pipelines/2021-07-15 copying build/lib/botocore/data/chime-sdk-media-pipelines/2021-07-15/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/chime-sdk-media-pipelines/2021-07-15 copying build/lib/botocore/data/chime-sdk-media-pipelines/2021-07-15/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/chime-sdk-media-pipelines/2021-07-15 creating build/bdist.linux-aarch64/wheel/botocore/data/chime-sdk-meetings creating build/bdist.linux-aarch64/wheel/botocore/data/chime-sdk-meetings/2021-07-15 copying build/lib/botocore/data/chime-sdk-meetings/2021-07-15/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/chime-sdk-meetings/2021-07-15 copying build/lib/botocore/data/chime-sdk-meetings/2021-07-15/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/chime-sdk-meetings/2021-07-15 copying build/lib/botocore/data/chime-sdk-meetings/2021-07-15/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/chime-sdk-meetings/2021-07-15 copying build/lib/botocore/data/chime-sdk-meetings/2021-07-15/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/chime-sdk-meetings/2021-07-15 creating build/bdist.linux-aarch64/wheel/botocore/data/chime-sdk-messaging creating build/bdist.linux-aarch64/wheel/botocore/data/chime-sdk-messaging/2021-05-15 copying build/lib/botocore/data/chime-sdk-messaging/2021-05-15/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/chime-sdk-messaging/2021-05-15 copying build/lib/botocore/data/chime-sdk-messaging/2021-05-15/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/chime-sdk-messaging/2021-05-15 copying build/lib/botocore/data/chime-sdk-messaging/2021-05-15/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/chime-sdk-messaging/2021-05-15 copying build/lib/botocore/data/chime-sdk-messaging/2021-05-15/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/chime-sdk-messaging/2021-05-15 creating build/bdist.linux-aarch64/wheel/botocore/data/chime-sdk-voice creating build/bdist.linux-aarch64/wheel/botocore/data/chime-sdk-voice/2022-08-03 copying build/lib/botocore/data/chime-sdk-voice/2022-08-03/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/chime-sdk-voice/2022-08-03 copying build/lib/botocore/data/chime-sdk-voice/2022-08-03/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/chime-sdk-voice/2022-08-03 copying build/lib/botocore/data/chime-sdk-voice/2022-08-03/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/chime-sdk-voice/2022-08-03 creating build/bdist.linux-aarch64/wheel/botocore/data/chime creating build/bdist.linux-aarch64/wheel/botocore/data/chime/2018-05-01 copying build/lib/botocore/data/chime/2018-05-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/chime/2018-05-01 copying build/lib/botocore/data/chime/2018-05-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/chime/2018-05-01 copying build/lib/botocore/data/chime/2018-05-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/chime/2018-05-01 copying build/lib/botocore/data/chime/2018-05-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/chime/2018-05-01 creating build/bdist.linux-aarch64/wheel/botocore/data/cleanrooms creating build/bdist.linux-aarch64/wheel/botocore/data/cleanrooms/2022-02-17 copying build/lib/botocore/data/cleanrooms/2022-02-17/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cleanrooms/2022-02-17 copying build/lib/botocore/data/cleanrooms/2022-02-17/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cleanrooms/2022-02-17 copying build/lib/botocore/data/cleanrooms/2022-02-17/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cleanrooms/2022-02-17 copying build/lib/botocore/data/cleanrooms/2022-02-17/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cleanrooms/2022-02-17 creating build/bdist.linux-aarch64/wheel/botocore/data/cleanroomsml creating build/bdist.linux-aarch64/wheel/botocore/data/cleanroomsml/2023-09-06 copying build/lib/botocore/data/cleanroomsml/2023-09-06/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cleanroomsml/2023-09-06 copying build/lib/botocore/data/cleanroomsml/2023-09-06/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cleanroomsml/2023-09-06 copying build/lib/botocore/data/cleanroomsml/2023-09-06/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cleanroomsml/2023-09-06 copying build/lib/botocore/data/cleanroomsml/2023-09-06/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cleanroomsml/2023-09-06 creating build/bdist.linux-aarch64/wheel/botocore/data/cloud9 creating build/bdist.linux-aarch64/wheel/botocore/data/cloud9/2017-09-23 copying build/lib/botocore/data/cloud9/2017-09-23/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloud9/2017-09-23 copying build/lib/botocore/data/cloud9/2017-09-23/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloud9/2017-09-23 copying build/lib/botocore/data/cloud9/2017-09-23/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloud9/2017-09-23 copying build/lib/botocore/data/cloud9/2017-09-23/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloud9/2017-09-23 creating build/bdist.linux-aarch64/wheel/botocore/data/cloudcontrol creating build/bdist.linux-aarch64/wheel/botocore/data/cloudcontrol/2021-09-30 copying build/lib/botocore/data/cloudcontrol/2021-09-30/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudcontrol/2021-09-30 copying build/lib/botocore/data/cloudcontrol/2021-09-30/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudcontrol/2021-09-30 copying build/lib/botocore/data/cloudcontrol/2021-09-30/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudcontrol/2021-09-30 copying build/lib/botocore/data/cloudcontrol/2021-09-30/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudcontrol/2021-09-30 copying build/lib/botocore/data/cloudcontrol/2021-09-30/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudcontrol/2021-09-30 copying build/lib/botocore/data/cloudcontrol/2021-09-30/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudcontrol/2021-09-30 creating build/bdist.linux-aarch64/wheel/botocore/data/clouddirectory creating build/bdist.linux-aarch64/wheel/botocore/data/clouddirectory/2016-05-10 copying build/lib/botocore/data/clouddirectory/2016-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/clouddirectory/2016-05-10 copying build/lib/botocore/data/clouddirectory/2016-05-10/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/clouddirectory/2016-05-10 copying build/lib/botocore/data/clouddirectory/2016-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/clouddirectory/2016-05-10 copying build/lib/botocore/data/clouddirectory/2016-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/clouddirectory/2016-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/clouddirectory/2017-01-11 copying build/lib/botocore/data/clouddirectory/2017-01-11/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/clouddirectory/2017-01-11 copying build/lib/botocore/data/clouddirectory/2017-01-11/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/clouddirectory/2017-01-11 copying build/lib/botocore/data/clouddirectory/2017-01-11/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/clouddirectory/2017-01-11 copying build/lib/botocore/data/clouddirectory/2017-01-11/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/clouddirectory/2017-01-11 creating build/bdist.linux-aarch64/wheel/botocore/data/cloudformation creating build/bdist.linux-aarch64/wheel/botocore/data/cloudformation/2010-05-15 copying build/lib/botocore/data/cloudformation/2010-05-15/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudformation/2010-05-15 copying build/lib/botocore/data/cloudformation/2010-05-15/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudformation/2010-05-15 copying build/lib/botocore/data/cloudformation/2010-05-15/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudformation/2010-05-15 copying build/lib/botocore/data/cloudformation/2010-05-15/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudformation/2010-05-15 copying build/lib/botocore/data/cloudformation/2010-05-15/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudformation/2010-05-15 creating build/bdist.linux-aarch64/wheel/botocore/data/cloudfront-keyvaluestore creating build/bdist.linux-aarch64/wheel/botocore/data/cloudfront-keyvaluestore/2022-07-26 copying build/lib/botocore/data/cloudfront-keyvaluestore/2022-07-26/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront-keyvaluestore/2022-07-26 copying build/lib/botocore/data/cloudfront-keyvaluestore/2022-07-26/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront-keyvaluestore/2022-07-26 copying build/lib/botocore/data/cloudfront-keyvaluestore/2022-07-26/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront-keyvaluestore/2022-07-26 creating build/bdist.linux-aarch64/wheel/botocore/data/cloudfront creating build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2014-05-31 copying build/lib/botocore/data/cloudfront/2014-05-31/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2014-05-31 copying build/lib/botocore/data/cloudfront/2014-05-31/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2014-05-31 copying build/lib/botocore/data/cloudfront/2014-05-31/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2014-05-31 copying build/lib/botocore/data/cloudfront/2014-05-31/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2014-05-31 creating build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2014-10-21 copying build/lib/botocore/data/cloudfront/2014-10-21/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2014-10-21 copying build/lib/botocore/data/cloudfront/2014-10-21/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2014-10-21 copying build/lib/botocore/data/cloudfront/2014-10-21/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2014-10-21 copying build/lib/botocore/data/cloudfront/2014-10-21/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2014-10-21 creating build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2014-11-06 copying build/lib/botocore/data/cloudfront/2014-11-06/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2014-11-06 copying build/lib/botocore/data/cloudfront/2014-11-06/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2014-11-06 copying build/lib/botocore/data/cloudfront/2014-11-06/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2014-11-06 copying build/lib/botocore/data/cloudfront/2014-11-06/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2014-11-06 creating build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2015-04-17 copying build/lib/botocore/data/cloudfront/2015-04-17/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2015-04-17 copying build/lib/botocore/data/cloudfront/2015-04-17/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2015-04-17 copying build/lib/botocore/data/cloudfront/2015-04-17/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2015-04-17 copying build/lib/botocore/data/cloudfront/2015-04-17/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2015-04-17 creating build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2015-07-27 copying build/lib/botocore/data/cloudfront/2015-07-27/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2015-07-27 copying build/lib/botocore/data/cloudfront/2015-07-27/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2015-07-27 copying build/lib/botocore/data/cloudfront/2015-07-27/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2015-07-27 copying build/lib/botocore/data/cloudfront/2015-07-27/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2015-07-27 creating build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2015-09-17 copying build/lib/botocore/data/cloudfront/2015-09-17/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2015-09-17 copying build/lib/botocore/data/cloudfront/2015-09-17/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2015-09-17 copying build/lib/botocore/data/cloudfront/2015-09-17/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2015-09-17 copying build/lib/botocore/data/cloudfront/2015-09-17/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2015-09-17 creating build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-01-13 copying build/lib/botocore/data/cloudfront/2016-01-13/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-01-13 copying build/lib/botocore/data/cloudfront/2016-01-13/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-01-13 copying build/lib/botocore/data/cloudfront/2016-01-13/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-01-13 copying build/lib/botocore/data/cloudfront/2016-01-13/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-01-13 creating build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-01-28 copying build/lib/botocore/data/cloudfront/2016-01-28/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-01-28 copying build/lib/botocore/data/cloudfront/2016-01-28/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-01-28 copying build/lib/botocore/data/cloudfront/2016-01-28/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-01-28 copying build/lib/botocore/data/cloudfront/2016-01-28/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-01-28 copying build/lib/botocore/data/cloudfront/2016-01-28/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-01-28 creating build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-08-01 copying build/lib/botocore/data/cloudfront/2016-08-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-08-01 copying build/lib/botocore/data/cloudfront/2016-08-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-08-01 copying build/lib/botocore/data/cloudfront/2016-08-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-08-01 copying build/lib/botocore/data/cloudfront/2016-08-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-08-01 copying build/lib/botocore/data/cloudfront/2016-08-01/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-08-01 creating build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-08-20 copying build/lib/botocore/data/cloudfront/2016-08-20/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-08-20 copying build/lib/botocore/data/cloudfront/2016-08-20/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-08-20 copying build/lib/botocore/data/cloudfront/2016-08-20/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-08-20 copying build/lib/botocore/data/cloudfront/2016-08-20/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-08-20 creating build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-09-07 copying build/lib/botocore/data/cloudfront/2016-09-07/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-09-07 copying build/lib/botocore/data/cloudfront/2016-09-07/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-09-07 copying build/lib/botocore/data/cloudfront/2016-09-07/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-09-07 copying build/lib/botocore/data/cloudfront/2016-09-07/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-09-07 copying build/lib/botocore/data/cloudfront/2016-09-07/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-09-07 creating build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-09-29 copying build/lib/botocore/data/cloudfront/2016-09-29/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-09-29 copying build/lib/botocore/data/cloudfront/2016-09-29/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-09-29 copying build/lib/botocore/data/cloudfront/2016-09-29/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-09-29 copying build/lib/botocore/data/cloudfront/2016-09-29/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-09-29 copying build/lib/botocore/data/cloudfront/2016-09-29/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-09-29 creating build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-11-25 copying build/lib/botocore/data/cloudfront/2016-11-25/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-11-25 copying build/lib/botocore/data/cloudfront/2016-11-25/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-11-25 copying build/lib/botocore/data/cloudfront/2016-11-25/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-11-25 copying build/lib/botocore/data/cloudfront/2016-11-25/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-11-25 copying build/lib/botocore/data/cloudfront/2016-11-25/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2016-11-25 creating build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2017-03-25 copying build/lib/botocore/data/cloudfront/2017-03-25/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2017-03-25 copying build/lib/botocore/data/cloudfront/2017-03-25/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2017-03-25 copying build/lib/botocore/data/cloudfront/2017-03-25/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2017-03-25 copying build/lib/botocore/data/cloudfront/2017-03-25/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2017-03-25 creating build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2017-10-30 copying build/lib/botocore/data/cloudfront/2017-10-30/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2017-10-30 copying build/lib/botocore/data/cloudfront/2017-10-30/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2017-10-30 copying build/lib/botocore/data/cloudfront/2017-10-30/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2017-10-30 copying build/lib/botocore/data/cloudfront/2017-10-30/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2017-10-30 copying build/lib/botocore/data/cloudfront/2017-10-30/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2017-10-30 creating build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2018-06-18 copying build/lib/botocore/data/cloudfront/2018-06-18/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2018-06-18 copying build/lib/botocore/data/cloudfront/2018-06-18/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2018-06-18 copying build/lib/botocore/data/cloudfront/2018-06-18/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2018-06-18 copying build/lib/botocore/data/cloudfront/2018-06-18/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2018-06-18 copying build/lib/botocore/data/cloudfront/2018-06-18/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2018-06-18 creating build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2018-11-05 copying build/lib/botocore/data/cloudfront/2018-11-05/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2018-11-05 copying build/lib/botocore/data/cloudfront/2018-11-05/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2018-11-05 copying build/lib/botocore/data/cloudfront/2018-11-05/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2018-11-05 copying build/lib/botocore/data/cloudfront/2018-11-05/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2018-11-05 copying build/lib/botocore/data/cloudfront/2018-11-05/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2018-11-05 creating build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2019-03-26 copying build/lib/botocore/data/cloudfront/2019-03-26/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2019-03-26 copying build/lib/botocore/data/cloudfront/2019-03-26/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2019-03-26 copying build/lib/botocore/data/cloudfront/2019-03-26/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2019-03-26 copying build/lib/botocore/data/cloudfront/2019-03-26/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2019-03-26 copying build/lib/botocore/data/cloudfront/2019-03-26/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2019-03-26 creating build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2020-05-31 copying build/lib/botocore/data/cloudfront/2020-05-31/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2020-05-31 copying build/lib/botocore/data/cloudfront/2020-05-31/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2020-05-31 copying build/lib/botocore/data/cloudfront/2020-05-31/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2020-05-31 copying build/lib/botocore/data/cloudfront/2020-05-31/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2020-05-31 copying build/lib/botocore/data/cloudfront/2020-05-31/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudfront/2020-05-31 creating build/bdist.linux-aarch64/wheel/botocore/data/cloudhsm creating build/bdist.linux-aarch64/wheel/botocore/data/cloudhsm/2014-05-30 copying build/lib/botocore/data/cloudhsm/2014-05-30/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudhsm/2014-05-30 copying build/lib/botocore/data/cloudhsm/2014-05-30/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudhsm/2014-05-30 copying build/lib/botocore/data/cloudhsm/2014-05-30/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudhsm/2014-05-30 copying build/lib/botocore/data/cloudhsm/2014-05-30/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudhsm/2014-05-30 creating build/bdist.linux-aarch64/wheel/botocore/data/cloudhsmv2 creating build/bdist.linux-aarch64/wheel/botocore/data/cloudhsmv2/2017-04-28 copying build/lib/botocore/data/cloudhsmv2/2017-04-28/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudhsmv2/2017-04-28 copying build/lib/botocore/data/cloudhsmv2/2017-04-28/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudhsmv2/2017-04-28 copying build/lib/botocore/data/cloudhsmv2/2017-04-28/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudhsmv2/2017-04-28 copying build/lib/botocore/data/cloudhsmv2/2017-04-28/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudhsmv2/2017-04-28 creating build/bdist.linux-aarch64/wheel/botocore/data/cloudsearch creating build/bdist.linux-aarch64/wheel/botocore/data/cloudsearch/2011-02-01 copying build/lib/botocore/data/cloudsearch/2011-02-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudsearch/2011-02-01 copying build/lib/botocore/data/cloudsearch/2011-02-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudsearch/2011-02-01 creating build/bdist.linux-aarch64/wheel/botocore/data/cloudsearch/2013-01-01 copying build/lib/botocore/data/cloudsearch/2013-01-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudsearch/2013-01-01 copying build/lib/botocore/data/cloudsearch/2013-01-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudsearch/2013-01-01 copying build/lib/botocore/data/cloudsearch/2013-01-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudsearch/2013-01-01 copying build/lib/botocore/data/cloudsearch/2013-01-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudsearch/2013-01-01 creating build/bdist.linux-aarch64/wheel/botocore/data/cloudsearchdomain creating build/bdist.linux-aarch64/wheel/botocore/data/cloudsearchdomain/2013-01-01 copying build/lib/botocore/data/cloudsearchdomain/2013-01-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudsearchdomain/2013-01-01 copying build/lib/botocore/data/cloudsearchdomain/2013-01-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudsearchdomain/2013-01-01 copying build/lib/botocore/data/cloudsearchdomain/2013-01-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudsearchdomain/2013-01-01 copying build/lib/botocore/data/cloudsearchdomain/2013-01-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudsearchdomain/2013-01-01 creating build/bdist.linux-aarch64/wheel/botocore/data/cloudtrail-data creating build/bdist.linux-aarch64/wheel/botocore/data/cloudtrail-data/2021-08-11 copying build/lib/botocore/data/cloudtrail-data/2021-08-11/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudtrail-data/2021-08-11 copying build/lib/botocore/data/cloudtrail-data/2021-08-11/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudtrail-data/2021-08-11 copying build/lib/botocore/data/cloudtrail-data/2021-08-11/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudtrail-data/2021-08-11 creating build/bdist.linux-aarch64/wheel/botocore/data/cloudtrail creating build/bdist.linux-aarch64/wheel/botocore/data/cloudtrail/2013-11-01 copying build/lib/botocore/data/cloudtrail/2013-11-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudtrail/2013-11-01 copying build/lib/botocore/data/cloudtrail/2013-11-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudtrail/2013-11-01 copying build/lib/botocore/data/cloudtrail/2013-11-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudtrail/2013-11-01 copying build/lib/botocore/data/cloudtrail/2013-11-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudtrail/2013-11-01 creating build/bdist.linux-aarch64/wheel/botocore/data/cloudwatch creating build/bdist.linux-aarch64/wheel/botocore/data/cloudwatch/2010-08-01 copying build/lib/botocore/data/cloudwatch/2010-08-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudwatch/2010-08-01 copying build/lib/botocore/data/cloudwatch/2010-08-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudwatch/2010-08-01 copying build/lib/botocore/data/cloudwatch/2010-08-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudwatch/2010-08-01 copying build/lib/botocore/data/cloudwatch/2010-08-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudwatch/2010-08-01 copying build/lib/botocore/data/cloudwatch/2010-08-01/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cloudwatch/2010-08-01 creating build/bdist.linux-aarch64/wheel/botocore/data/codeartifact creating build/bdist.linux-aarch64/wheel/botocore/data/codeartifact/2018-09-22 copying build/lib/botocore/data/codeartifact/2018-09-22/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codeartifact/2018-09-22 copying build/lib/botocore/data/codeartifact/2018-09-22/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codeartifact/2018-09-22 copying build/lib/botocore/data/codeartifact/2018-09-22/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codeartifact/2018-09-22 copying build/lib/botocore/data/codeartifact/2018-09-22/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/codeartifact/2018-09-22 copying build/lib/botocore/data/codeartifact/2018-09-22/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/codeartifact/2018-09-22 creating build/bdist.linux-aarch64/wheel/botocore/data/codebuild creating build/bdist.linux-aarch64/wheel/botocore/data/codebuild/2016-10-06 copying build/lib/botocore/data/codebuild/2016-10-06/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codebuild/2016-10-06 copying build/lib/botocore/data/codebuild/2016-10-06/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codebuild/2016-10-06 copying build/lib/botocore/data/codebuild/2016-10-06/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codebuild/2016-10-06 copying build/lib/botocore/data/codebuild/2016-10-06/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/codebuild/2016-10-06 creating build/bdist.linux-aarch64/wheel/botocore/data/codecatalyst creating build/bdist.linux-aarch64/wheel/botocore/data/codecatalyst/2022-09-28 copying build/lib/botocore/data/codecatalyst/2022-09-28/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codecatalyst/2022-09-28 copying build/lib/botocore/data/codecatalyst/2022-09-28/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codecatalyst/2022-09-28 copying build/lib/botocore/data/codecatalyst/2022-09-28/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/codecatalyst/2022-09-28 copying build/lib/botocore/data/codecatalyst/2022-09-28/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/codecatalyst/2022-09-28 creating build/bdist.linux-aarch64/wheel/botocore/data/codecommit creating build/bdist.linux-aarch64/wheel/botocore/data/codecommit/2015-04-13 copying build/lib/botocore/data/codecommit/2015-04-13/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codecommit/2015-04-13 copying build/lib/botocore/data/codecommit/2015-04-13/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codecommit/2015-04-13 copying build/lib/botocore/data/codecommit/2015-04-13/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codecommit/2015-04-13 copying build/lib/botocore/data/codecommit/2015-04-13/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/codecommit/2015-04-13 creating build/bdist.linux-aarch64/wheel/botocore/data/codeconnections creating build/bdist.linux-aarch64/wheel/botocore/data/codeconnections/2023-12-01 copying build/lib/botocore/data/codeconnections/2023-12-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codeconnections/2023-12-01 copying build/lib/botocore/data/codeconnections/2023-12-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codeconnections/2023-12-01 copying build/lib/botocore/data/codeconnections/2023-12-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/codeconnections/2023-12-01 creating build/bdist.linux-aarch64/wheel/botocore/data/codedeploy creating build/bdist.linux-aarch64/wheel/botocore/data/codedeploy/2014-10-06 copying build/lib/botocore/data/codedeploy/2014-10-06/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codedeploy/2014-10-06 copying build/lib/botocore/data/codedeploy/2014-10-06/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codedeploy/2014-10-06 copying build/lib/botocore/data/codedeploy/2014-10-06/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codedeploy/2014-10-06 copying build/lib/botocore/data/codedeploy/2014-10-06/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/codedeploy/2014-10-06 copying build/lib/botocore/data/codedeploy/2014-10-06/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/codedeploy/2014-10-06 creating build/bdist.linux-aarch64/wheel/botocore/data/codeguru-reviewer creating build/bdist.linux-aarch64/wheel/botocore/data/codeguru-reviewer/2019-09-19 copying build/lib/botocore/data/codeguru-reviewer/2019-09-19/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codeguru-reviewer/2019-09-19 copying build/lib/botocore/data/codeguru-reviewer/2019-09-19/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codeguru-reviewer/2019-09-19 copying build/lib/botocore/data/codeguru-reviewer/2019-09-19/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codeguru-reviewer/2019-09-19 copying build/lib/botocore/data/codeguru-reviewer/2019-09-19/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/codeguru-reviewer/2019-09-19 copying build/lib/botocore/data/codeguru-reviewer/2019-09-19/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/codeguru-reviewer/2019-09-19 creating build/bdist.linux-aarch64/wheel/botocore/data/codeguru-security creating build/bdist.linux-aarch64/wheel/botocore/data/codeguru-security/2018-05-10 copying build/lib/botocore/data/codeguru-security/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codeguru-security/2018-05-10 copying build/lib/botocore/data/codeguru-security/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codeguru-security/2018-05-10 copying build/lib/botocore/data/codeguru-security/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/codeguru-security/2018-05-10 copying build/lib/botocore/data/codeguru-security/2018-05-10/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/codeguru-security/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/codeguruprofiler creating build/bdist.linux-aarch64/wheel/botocore/data/codeguruprofiler/2019-07-18 copying build/lib/botocore/data/codeguruprofiler/2019-07-18/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codeguruprofiler/2019-07-18 copying build/lib/botocore/data/codeguruprofiler/2019-07-18/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codeguruprofiler/2019-07-18 copying build/lib/botocore/data/codeguruprofiler/2019-07-18/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codeguruprofiler/2019-07-18 copying build/lib/botocore/data/codeguruprofiler/2019-07-18/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/codeguruprofiler/2019-07-18 creating build/bdist.linux-aarch64/wheel/botocore/data/codepipeline creating build/bdist.linux-aarch64/wheel/botocore/data/codepipeline/2015-07-09 copying build/lib/botocore/data/codepipeline/2015-07-09/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codepipeline/2015-07-09 copying build/lib/botocore/data/codepipeline/2015-07-09/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codepipeline/2015-07-09 copying build/lib/botocore/data/codepipeline/2015-07-09/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codepipeline/2015-07-09 copying build/lib/botocore/data/codepipeline/2015-07-09/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/codepipeline/2015-07-09 creating build/bdist.linux-aarch64/wheel/botocore/data/codestar-connections creating build/bdist.linux-aarch64/wheel/botocore/data/codestar-connections/2019-12-01 copying build/lib/botocore/data/codestar-connections/2019-12-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codestar-connections/2019-12-01 copying build/lib/botocore/data/codestar-connections/2019-12-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codestar-connections/2019-12-01 copying build/lib/botocore/data/codestar-connections/2019-12-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codestar-connections/2019-12-01 copying build/lib/botocore/data/codestar-connections/2019-12-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/codestar-connections/2019-12-01 creating build/bdist.linux-aarch64/wheel/botocore/data/codestar-notifications creating build/bdist.linux-aarch64/wheel/botocore/data/codestar-notifications/2019-10-15 copying build/lib/botocore/data/codestar-notifications/2019-10-15/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codestar-notifications/2019-10-15 copying build/lib/botocore/data/codestar-notifications/2019-10-15/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codestar-notifications/2019-10-15 copying build/lib/botocore/data/codestar-notifications/2019-10-15/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/codestar-notifications/2019-10-15 copying build/lib/botocore/data/codestar-notifications/2019-10-15/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/codestar-notifications/2019-10-15 creating build/bdist.linux-aarch64/wheel/botocore/data/cognito-identity creating build/bdist.linux-aarch64/wheel/botocore/data/cognito-identity/2014-06-30 copying build/lib/botocore/data/cognito-identity/2014-06-30/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cognito-identity/2014-06-30 copying build/lib/botocore/data/cognito-identity/2014-06-30/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cognito-identity/2014-06-30 copying build/lib/botocore/data/cognito-identity/2014-06-30/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cognito-identity/2014-06-30 copying build/lib/botocore/data/cognito-identity/2014-06-30/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cognito-identity/2014-06-30 creating build/bdist.linux-aarch64/wheel/botocore/data/cognito-idp creating build/bdist.linux-aarch64/wheel/botocore/data/cognito-idp/2016-04-18 copying build/lib/botocore/data/cognito-idp/2016-04-18/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cognito-idp/2016-04-18 copying build/lib/botocore/data/cognito-idp/2016-04-18/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cognito-idp/2016-04-18 copying build/lib/botocore/data/cognito-idp/2016-04-18/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cognito-idp/2016-04-18 copying build/lib/botocore/data/cognito-idp/2016-04-18/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cognito-idp/2016-04-18 creating build/bdist.linux-aarch64/wheel/botocore/data/cognito-sync creating build/bdist.linux-aarch64/wheel/botocore/data/cognito-sync/2014-06-30 copying build/lib/botocore/data/cognito-sync/2014-06-30/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cognito-sync/2014-06-30 copying build/lib/botocore/data/cognito-sync/2014-06-30/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cognito-sync/2014-06-30 copying build/lib/botocore/data/cognito-sync/2014-06-30/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cognito-sync/2014-06-30 copying build/lib/botocore/data/cognito-sync/2014-06-30/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cognito-sync/2014-06-30 creating build/bdist.linux-aarch64/wheel/botocore/data/comprehend creating build/bdist.linux-aarch64/wheel/botocore/data/comprehend/2017-11-27 copying build/lib/botocore/data/comprehend/2017-11-27/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/comprehend/2017-11-27 copying build/lib/botocore/data/comprehend/2017-11-27/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/comprehend/2017-11-27 copying build/lib/botocore/data/comprehend/2017-11-27/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/comprehend/2017-11-27 copying build/lib/botocore/data/comprehend/2017-11-27/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/comprehend/2017-11-27 creating build/bdist.linux-aarch64/wheel/botocore/data/comprehendmedical creating build/bdist.linux-aarch64/wheel/botocore/data/comprehendmedical/2018-10-30 copying build/lib/botocore/data/comprehendmedical/2018-10-30/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/comprehendmedical/2018-10-30 copying build/lib/botocore/data/comprehendmedical/2018-10-30/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/comprehendmedical/2018-10-30 copying build/lib/botocore/data/comprehendmedical/2018-10-30/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/comprehendmedical/2018-10-30 copying build/lib/botocore/data/comprehendmedical/2018-10-30/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/comprehendmedical/2018-10-30 creating build/bdist.linux-aarch64/wheel/botocore/data/compute-optimizer-automation creating build/bdist.linux-aarch64/wheel/botocore/data/compute-optimizer-automation/2025-09-22 copying build/lib/botocore/data/compute-optimizer-automation/2025-09-22/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/compute-optimizer-automation/2025-09-22 copying build/lib/botocore/data/compute-optimizer-automation/2025-09-22/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/compute-optimizer-automation/2025-09-22 copying build/lib/botocore/data/compute-optimizer-automation/2025-09-22/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/compute-optimizer-automation/2025-09-22 copying build/lib/botocore/data/compute-optimizer-automation/2025-09-22/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/compute-optimizer-automation/2025-09-22 creating build/bdist.linux-aarch64/wheel/botocore/data/compute-optimizer creating build/bdist.linux-aarch64/wheel/botocore/data/compute-optimizer/2019-11-01 copying build/lib/botocore/data/compute-optimizer/2019-11-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/compute-optimizer/2019-11-01 copying build/lib/botocore/data/compute-optimizer/2019-11-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/compute-optimizer/2019-11-01 copying build/lib/botocore/data/compute-optimizer/2019-11-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/compute-optimizer/2019-11-01 copying build/lib/botocore/data/compute-optimizer/2019-11-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/compute-optimizer/2019-11-01 creating build/bdist.linux-aarch64/wheel/botocore/data/config creating build/bdist.linux-aarch64/wheel/botocore/data/config/2014-11-12 copying build/lib/botocore/data/config/2014-11-12/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/config/2014-11-12 copying build/lib/botocore/data/config/2014-11-12/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/config/2014-11-12 copying build/lib/botocore/data/config/2014-11-12/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/config/2014-11-12 copying build/lib/botocore/data/config/2014-11-12/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/config/2014-11-12 creating build/bdist.linux-aarch64/wheel/botocore/data/connect-contact-lens creating build/bdist.linux-aarch64/wheel/botocore/data/connect-contact-lens/2020-08-21 copying build/lib/botocore/data/connect-contact-lens/2020-08-21/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/connect-contact-lens/2020-08-21 copying build/lib/botocore/data/connect-contact-lens/2020-08-21/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/connect-contact-lens/2020-08-21 copying build/lib/botocore/data/connect-contact-lens/2020-08-21/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/connect-contact-lens/2020-08-21 copying build/lib/botocore/data/connect-contact-lens/2020-08-21/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/connect-contact-lens/2020-08-21 creating build/bdist.linux-aarch64/wheel/botocore/data/connect creating build/bdist.linux-aarch64/wheel/botocore/data/connect/2017-08-08 copying build/lib/botocore/data/connect/2017-08-08/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/connect/2017-08-08 copying build/lib/botocore/data/connect/2017-08-08/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/connect/2017-08-08 copying build/lib/botocore/data/connect/2017-08-08/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/connect/2017-08-08 copying build/lib/botocore/data/connect/2017-08-08/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/connect/2017-08-08 creating build/bdist.linux-aarch64/wheel/botocore/data/connectcampaigns creating build/bdist.linux-aarch64/wheel/botocore/data/connectcampaigns/2021-01-30 copying build/lib/botocore/data/connectcampaigns/2021-01-30/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/connectcampaigns/2021-01-30 copying build/lib/botocore/data/connectcampaigns/2021-01-30/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/connectcampaigns/2021-01-30 copying build/lib/botocore/data/connectcampaigns/2021-01-30/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/connectcampaigns/2021-01-30 creating build/bdist.linux-aarch64/wheel/botocore/data/connectcampaignsv2 creating build/bdist.linux-aarch64/wheel/botocore/data/connectcampaignsv2/2024-04-23 copying build/lib/botocore/data/connectcampaignsv2/2024-04-23/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/connectcampaignsv2/2024-04-23 copying build/lib/botocore/data/connectcampaignsv2/2024-04-23/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/connectcampaignsv2/2024-04-23 copying build/lib/botocore/data/connectcampaignsv2/2024-04-23/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/connectcampaignsv2/2024-04-23 creating build/bdist.linux-aarch64/wheel/botocore/data/connectcases creating build/bdist.linux-aarch64/wheel/botocore/data/connectcases/2022-10-03 copying build/lib/botocore/data/connectcases/2022-10-03/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/connectcases/2022-10-03 copying build/lib/botocore/data/connectcases/2022-10-03/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/connectcases/2022-10-03 copying build/lib/botocore/data/connectcases/2022-10-03/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/connectcases/2022-10-03 copying build/lib/botocore/data/connectcases/2022-10-03/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/connectcases/2022-10-03 copying build/lib/botocore/data/connectcases/2022-10-03/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/connectcases/2022-10-03 creating build/bdist.linux-aarch64/wheel/botocore/data/connecthealth creating build/bdist.linux-aarch64/wheel/botocore/data/connecthealth/2025-01-29 copying build/lib/botocore/data/connecthealth/2025-01-29/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/connecthealth/2025-01-29 copying build/lib/botocore/data/connecthealth/2025-01-29/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/connecthealth/2025-01-29 copying build/lib/botocore/data/connecthealth/2025-01-29/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/connecthealth/2025-01-29 copying build/lib/botocore/data/connecthealth/2025-01-29/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/connecthealth/2025-01-29 creating build/bdist.linux-aarch64/wheel/botocore/data/connectparticipant creating build/bdist.linux-aarch64/wheel/botocore/data/connectparticipant/2018-09-07 copying build/lib/botocore/data/connectparticipant/2018-09-07/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/connectparticipant/2018-09-07 copying build/lib/botocore/data/connectparticipant/2018-09-07/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/connectparticipant/2018-09-07 copying build/lib/botocore/data/connectparticipant/2018-09-07/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/connectparticipant/2018-09-07 copying build/lib/botocore/data/connectparticipant/2018-09-07/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/connectparticipant/2018-09-07 creating build/bdist.linux-aarch64/wheel/botocore/data/controlcatalog creating build/bdist.linux-aarch64/wheel/botocore/data/controlcatalog/2018-05-10 copying build/lib/botocore/data/controlcatalog/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/controlcatalog/2018-05-10 copying build/lib/botocore/data/controlcatalog/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/controlcatalog/2018-05-10 copying build/lib/botocore/data/controlcatalog/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/controlcatalog/2018-05-10 copying build/lib/botocore/data/controlcatalog/2018-05-10/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/controlcatalog/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/controltower creating build/bdist.linux-aarch64/wheel/botocore/data/controltower/2018-05-10 copying build/lib/botocore/data/controltower/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/controltower/2018-05-10 copying build/lib/botocore/data/controltower/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/controltower/2018-05-10 copying build/lib/botocore/data/controltower/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/controltower/2018-05-10 copying build/lib/botocore/data/controltower/2018-05-10/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/controltower/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/cost-optimization-hub creating build/bdist.linux-aarch64/wheel/botocore/data/cost-optimization-hub/2022-07-26 copying build/lib/botocore/data/cost-optimization-hub/2022-07-26/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cost-optimization-hub/2022-07-26 copying build/lib/botocore/data/cost-optimization-hub/2022-07-26/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cost-optimization-hub/2022-07-26 copying build/lib/botocore/data/cost-optimization-hub/2022-07-26/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/cost-optimization-hub/2022-07-26 copying build/lib/botocore/data/cost-optimization-hub/2022-07-26/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cost-optimization-hub/2022-07-26 copying build/lib/botocore/data/cost-optimization-hub/2022-07-26/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cost-optimization-hub/2022-07-26 creating build/bdist.linux-aarch64/wheel/botocore/data/cur creating build/bdist.linux-aarch64/wheel/botocore/data/cur/2017-01-06 copying build/lib/botocore/data/cur/2017-01-06/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cur/2017-01-06 copying build/lib/botocore/data/cur/2017-01-06/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cur/2017-01-06 copying build/lib/botocore/data/cur/2017-01-06/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/cur/2017-01-06 copying build/lib/botocore/data/cur/2017-01-06/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/cur/2017-01-06 creating build/bdist.linux-aarch64/wheel/botocore/data/customer-profiles creating build/bdist.linux-aarch64/wheel/botocore/data/customer-profiles/2020-08-15 copying build/lib/botocore/data/customer-profiles/2020-08-15/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/customer-profiles/2020-08-15 copying build/lib/botocore/data/customer-profiles/2020-08-15/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/customer-profiles/2020-08-15 copying build/lib/botocore/data/customer-profiles/2020-08-15/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/customer-profiles/2020-08-15 copying build/lib/botocore/data/customer-profiles/2020-08-15/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/customer-profiles/2020-08-15 copying build/lib/botocore/data/customer-profiles/2020-08-15/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/customer-profiles/2020-08-15 creating build/bdist.linux-aarch64/wheel/botocore/data/databrew creating build/bdist.linux-aarch64/wheel/botocore/data/databrew/2017-07-25 copying build/lib/botocore/data/databrew/2017-07-25/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/databrew/2017-07-25 copying build/lib/botocore/data/databrew/2017-07-25/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/databrew/2017-07-25 copying build/lib/botocore/data/databrew/2017-07-25/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/databrew/2017-07-25 copying build/lib/botocore/data/databrew/2017-07-25/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/databrew/2017-07-25 creating build/bdist.linux-aarch64/wheel/botocore/data/dataexchange creating build/bdist.linux-aarch64/wheel/botocore/data/dataexchange/2017-07-25 copying build/lib/botocore/data/dataexchange/2017-07-25/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/dataexchange/2017-07-25 copying build/lib/botocore/data/dataexchange/2017-07-25/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/dataexchange/2017-07-25 copying build/lib/botocore/data/dataexchange/2017-07-25/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/dataexchange/2017-07-25 copying build/lib/botocore/data/dataexchange/2017-07-25/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/dataexchange/2017-07-25 creating build/bdist.linux-aarch64/wheel/botocore/data/datapipeline creating build/bdist.linux-aarch64/wheel/botocore/data/datapipeline/2012-10-29 copying build/lib/botocore/data/datapipeline/2012-10-29/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/datapipeline/2012-10-29 copying build/lib/botocore/data/datapipeline/2012-10-29/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/datapipeline/2012-10-29 copying build/lib/botocore/data/datapipeline/2012-10-29/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/datapipeline/2012-10-29 copying build/lib/botocore/data/datapipeline/2012-10-29/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/datapipeline/2012-10-29 creating build/bdist.linux-aarch64/wheel/botocore/data/datasync creating build/bdist.linux-aarch64/wheel/botocore/data/datasync/2018-11-09 copying build/lib/botocore/data/datasync/2018-11-09/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/datasync/2018-11-09 copying build/lib/botocore/data/datasync/2018-11-09/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/datasync/2018-11-09 copying build/lib/botocore/data/datasync/2018-11-09/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/datasync/2018-11-09 copying build/lib/botocore/data/datasync/2018-11-09/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/datasync/2018-11-09 creating build/bdist.linux-aarch64/wheel/botocore/data/datazone creating build/bdist.linux-aarch64/wheel/botocore/data/datazone/2018-05-10 copying build/lib/botocore/data/datazone/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/datazone/2018-05-10 copying build/lib/botocore/data/datazone/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/datazone/2018-05-10 copying build/lib/botocore/data/datazone/2018-05-10/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/datazone/2018-05-10 copying build/lib/botocore/data/datazone/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/datazone/2018-05-10 copying build/lib/botocore/data/datazone/2018-05-10/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/datazone/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/dax creating build/bdist.linux-aarch64/wheel/botocore/data/dax/2017-04-19 copying build/lib/botocore/data/dax/2017-04-19/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/dax/2017-04-19 copying build/lib/botocore/data/dax/2017-04-19/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/dax/2017-04-19 copying build/lib/botocore/data/dax/2017-04-19/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/dax/2017-04-19 copying build/lib/botocore/data/dax/2017-04-19/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/dax/2017-04-19 creating build/bdist.linux-aarch64/wheel/botocore/data/deadline creating build/bdist.linux-aarch64/wheel/botocore/data/deadline/2023-10-12 copying build/lib/botocore/data/deadline/2023-10-12/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/deadline/2023-10-12 copying build/lib/botocore/data/deadline/2023-10-12/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/deadline/2023-10-12 copying build/lib/botocore/data/deadline/2023-10-12/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/deadline/2023-10-12 copying build/lib/botocore/data/deadline/2023-10-12/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/deadline/2023-10-12 copying build/lib/botocore/data/deadline/2023-10-12/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/deadline/2023-10-12 creating build/bdist.linux-aarch64/wheel/botocore/data/detective creating build/bdist.linux-aarch64/wheel/botocore/data/detective/2018-10-26 copying build/lib/botocore/data/detective/2018-10-26/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/detective/2018-10-26 copying build/lib/botocore/data/detective/2018-10-26/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/detective/2018-10-26 copying build/lib/botocore/data/detective/2018-10-26/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/detective/2018-10-26 copying build/lib/botocore/data/detective/2018-10-26/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/detective/2018-10-26 creating build/bdist.linux-aarch64/wheel/botocore/data/devicefarm creating build/bdist.linux-aarch64/wheel/botocore/data/devicefarm/2015-06-23 copying build/lib/botocore/data/devicefarm/2015-06-23/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/devicefarm/2015-06-23 copying build/lib/botocore/data/devicefarm/2015-06-23/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/devicefarm/2015-06-23 copying build/lib/botocore/data/devicefarm/2015-06-23/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/devicefarm/2015-06-23 copying build/lib/botocore/data/devicefarm/2015-06-23/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/devicefarm/2015-06-23 creating build/bdist.linux-aarch64/wheel/botocore/data/devops-agent creating build/bdist.linux-aarch64/wheel/botocore/data/devops-agent/2026-01-01 copying build/lib/botocore/data/devops-agent/2026-01-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/devops-agent/2026-01-01 copying build/lib/botocore/data/devops-agent/2026-01-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/devops-agent/2026-01-01 copying build/lib/botocore/data/devops-agent/2026-01-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/devops-agent/2026-01-01 creating build/bdist.linux-aarch64/wheel/botocore/data/devops-guru creating build/bdist.linux-aarch64/wheel/botocore/data/devops-guru/2020-12-01 copying build/lib/botocore/data/devops-guru/2020-12-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/devops-guru/2020-12-01 copying build/lib/botocore/data/devops-guru/2020-12-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/devops-guru/2020-12-01 copying build/lib/botocore/data/devops-guru/2020-12-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/devops-guru/2020-12-01 copying build/lib/botocore/data/devops-guru/2020-12-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/devops-guru/2020-12-01 creating build/bdist.linux-aarch64/wheel/botocore/data/directconnect creating build/bdist.linux-aarch64/wheel/botocore/data/directconnect/2012-10-25 copying build/lib/botocore/data/directconnect/2012-10-25/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/directconnect/2012-10-25 copying build/lib/botocore/data/directconnect/2012-10-25/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/directconnect/2012-10-25 copying build/lib/botocore/data/directconnect/2012-10-25/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/directconnect/2012-10-25 copying build/lib/botocore/data/directconnect/2012-10-25/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/directconnect/2012-10-25 creating build/bdist.linux-aarch64/wheel/botocore/data/discovery creating build/bdist.linux-aarch64/wheel/botocore/data/discovery/2015-11-01 copying build/lib/botocore/data/discovery/2015-11-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/discovery/2015-11-01 copying build/lib/botocore/data/discovery/2015-11-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/discovery/2015-11-01 copying build/lib/botocore/data/discovery/2015-11-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/discovery/2015-11-01 copying build/lib/botocore/data/discovery/2015-11-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/discovery/2015-11-01 creating build/bdist.linux-aarch64/wheel/botocore/data/dlm creating build/bdist.linux-aarch64/wheel/botocore/data/dlm/2018-01-12 copying build/lib/botocore/data/dlm/2018-01-12/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/dlm/2018-01-12 copying build/lib/botocore/data/dlm/2018-01-12/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/dlm/2018-01-12 copying build/lib/botocore/data/dlm/2018-01-12/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/dlm/2018-01-12 copying build/lib/botocore/data/dlm/2018-01-12/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/dlm/2018-01-12 creating build/bdist.linux-aarch64/wheel/botocore/data/dms creating build/bdist.linux-aarch64/wheel/botocore/data/dms/2016-01-01 copying build/lib/botocore/data/dms/2016-01-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/dms/2016-01-01 copying build/lib/botocore/data/dms/2016-01-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/dms/2016-01-01 copying build/lib/botocore/data/dms/2016-01-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/dms/2016-01-01 copying build/lib/botocore/data/dms/2016-01-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/dms/2016-01-01 copying build/lib/botocore/data/dms/2016-01-01/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/dms/2016-01-01 creating build/bdist.linux-aarch64/wheel/botocore/data/docdb-elastic creating build/bdist.linux-aarch64/wheel/botocore/data/docdb-elastic/2022-11-28 copying build/lib/botocore/data/docdb-elastic/2022-11-28/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/docdb-elastic/2022-11-28 copying build/lib/botocore/data/docdb-elastic/2022-11-28/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/docdb-elastic/2022-11-28 copying build/lib/botocore/data/docdb-elastic/2022-11-28/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/docdb-elastic/2022-11-28 creating build/bdist.linux-aarch64/wheel/botocore/data/docdb creating build/bdist.linux-aarch64/wheel/botocore/data/docdb/2014-10-31 copying build/lib/botocore/data/docdb/2014-10-31/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/docdb/2014-10-31 copying build/lib/botocore/data/docdb/2014-10-31/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/docdb/2014-10-31 copying build/lib/botocore/data/docdb/2014-10-31/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/docdb/2014-10-31 copying build/lib/botocore/data/docdb/2014-10-31/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/docdb/2014-10-31 copying build/lib/botocore/data/docdb/2014-10-31/service-2.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/docdb/2014-10-31 copying build/lib/botocore/data/docdb/2014-10-31/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/docdb/2014-10-31 creating build/bdist.linux-aarch64/wheel/botocore/data/drs creating build/bdist.linux-aarch64/wheel/botocore/data/drs/2020-02-26 copying build/lib/botocore/data/drs/2020-02-26/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/drs/2020-02-26 copying build/lib/botocore/data/drs/2020-02-26/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/drs/2020-02-26 copying build/lib/botocore/data/drs/2020-02-26/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/drs/2020-02-26 copying build/lib/botocore/data/drs/2020-02-26/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/drs/2020-02-26 creating build/bdist.linux-aarch64/wheel/botocore/data/ds-data creating build/bdist.linux-aarch64/wheel/botocore/data/ds-data/2023-05-31 copying build/lib/botocore/data/ds-data/2023-05-31/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ds-data/2023-05-31 copying build/lib/botocore/data/ds-data/2023-05-31/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ds-data/2023-05-31 copying build/lib/botocore/data/ds-data/2023-05-31/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/ds-data/2023-05-31 copying build/lib/botocore/data/ds-data/2023-05-31/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ds-data/2023-05-31 creating build/bdist.linux-aarch64/wheel/botocore/data/ds creating build/bdist.linux-aarch64/wheel/botocore/data/ds/2015-04-16 copying build/lib/botocore/data/ds/2015-04-16/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ds/2015-04-16 copying build/lib/botocore/data/ds/2015-04-16/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ds/2015-04-16 copying build/lib/botocore/data/ds/2015-04-16/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ds/2015-04-16 copying build/lib/botocore/data/ds/2015-04-16/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ds/2015-04-16 copying build/lib/botocore/data/ds/2015-04-16/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ds/2015-04-16 creating build/bdist.linux-aarch64/wheel/botocore/data/dsql creating build/bdist.linux-aarch64/wheel/botocore/data/dsql/2018-05-10 copying build/lib/botocore/data/dsql/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/dsql/2018-05-10 copying build/lib/botocore/data/dsql/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/dsql/2018-05-10 copying build/lib/botocore/data/dsql/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/dsql/2018-05-10 copying build/lib/botocore/data/dsql/2018-05-10/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/dsql/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/dynamodb creating build/bdist.linux-aarch64/wheel/botocore/data/dynamodb/2011-12-05 copying build/lib/botocore/data/dynamodb/2011-12-05/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/dynamodb/2011-12-05 copying build/lib/botocore/data/dynamodb/2011-12-05/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/dynamodb/2011-12-05 creating build/bdist.linux-aarch64/wheel/botocore/data/dynamodb/2012-08-10 copying build/lib/botocore/data/dynamodb/2012-08-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/dynamodb/2012-08-10 copying build/lib/botocore/data/dynamodb/2012-08-10/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/dynamodb/2012-08-10 copying build/lib/botocore/data/dynamodb/2012-08-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/dynamodb/2012-08-10 copying build/lib/botocore/data/dynamodb/2012-08-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/dynamodb/2012-08-10 copying build/lib/botocore/data/dynamodb/2012-08-10/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/dynamodb/2012-08-10 creating build/bdist.linux-aarch64/wheel/botocore/data/dynamodbstreams creating build/bdist.linux-aarch64/wheel/botocore/data/dynamodbstreams/2012-08-10 copying build/lib/botocore/data/dynamodbstreams/2012-08-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/dynamodbstreams/2012-08-10 copying build/lib/botocore/data/dynamodbstreams/2012-08-10/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/dynamodbstreams/2012-08-10 copying build/lib/botocore/data/dynamodbstreams/2012-08-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/dynamodbstreams/2012-08-10 copying build/lib/botocore/data/dynamodbstreams/2012-08-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/dynamodbstreams/2012-08-10 creating build/bdist.linux-aarch64/wheel/botocore/data/ebs creating build/bdist.linux-aarch64/wheel/botocore/data/ebs/2019-11-02 copying build/lib/botocore/data/ebs/2019-11-02/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ebs/2019-11-02 copying build/lib/botocore/data/ebs/2019-11-02/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ebs/2019-11-02 copying build/lib/botocore/data/ebs/2019-11-02/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ebs/2019-11-02 copying build/lib/botocore/data/ebs/2019-11-02/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ebs/2019-11-02 creating build/bdist.linux-aarch64/wheel/botocore/data/ec2-instance-connect creating build/bdist.linux-aarch64/wheel/botocore/data/ec2-instance-connect/2018-04-02 copying build/lib/botocore/data/ec2-instance-connect/2018-04-02/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2-instance-connect/2018-04-02 copying build/lib/botocore/data/ec2-instance-connect/2018-04-02/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2-instance-connect/2018-04-02 copying build/lib/botocore/data/ec2-instance-connect/2018-04-02/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2-instance-connect/2018-04-02 copying build/lib/botocore/data/ec2-instance-connect/2018-04-02/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2-instance-connect/2018-04-02 creating build/bdist.linux-aarch64/wheel/botocore/data/ec2 creating build/bdist.linux-aarch64/wheel/botocore/data/ec2/2014-09-01 copying build/lib/botocore/data/ec2/2014-09-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2014-09-01 copying build/lib/botocore/data/ec2/2014-09-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2014-09-01 copying build/lib/botocore/data/ec2/2014-09-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2014-09-01 copying build/lib/botocore/data/ec2/2014-09-01/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2014-09-01 creating build/bdist.linux-aarch64/wheel/botocore/data/ec2/2014-10-01 copying build/lib/botocore/data/ec2/2014-10-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2014-10-01 copying build/lib/botocore/data/ec2/2014-10-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2014-10-01 copying build/lib/botocore/data/ec2/2014-10-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2014-10-01 copying build/lib/botocore/data/ec2/2014-10-01/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2014-10-01 creating build/bdist.linux-aarch64/wheel/botocore/data/ec2/2015-03-01 copying build/lib/botocore/data/ec2/2015-03-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2015-03-01 copying build/lib/botocore/data/ec2/2015-03-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2015-03-01 copying build/lib/botocore/data/ec2/2015-03-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2015-03-01 copying build/lib/botocore/data/ec2/2015-03-01/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2015-03-01 creating build/bdist.linux-aarch64/wheel/botocore/data/ec2/2015-04-15 copying build/lib/botocore/data/ec2/2015-04-15/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2015-04-15 copying build/lib/botocore/data/ec2/2015-04-15/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2015-04-15 copying build/lib/botocore/data/ec2/2015-04-15/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2015-04-15 copying build/lib/botocore/data/ec2/2015-04-15/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2015-04-15 creating build/bdist.linux-aarch64/wheel/botocore/data/ec2/2015-10-01 copying build/lib/botocore/data/ec2/2015-10-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2015-10-01 copying build/lib/botocore/data/ec2/2015-10-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2015-10-01 copying build/lib/botocore/data/ec2/2015-10-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2015-10-01 copying build/lib/botocore/data/ec2/2015-10-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2015-10-01 copying build/lib/botocore/data/ec2/2015-10-01/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2015-10-01 creating build/bdist.linux-aarch64/wheel/botocore/data/ec2/2016-04-01 copying build/lib/botocore/data/ec2/2016-04-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2016-04-01 copying build/lib/botocore/data/ec2/2016-04-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2016-04-01 copying build/lib/botocore/data/ec2/2016-04-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2016-04-01 copying build/lib/botocore/data/ec2/2016-04-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2016-04-01 copying build/lib/botocore/data/ec2/2016-04-01/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2016-04-01 creating build/bdist.linux-aarch64/wheel/botocore/data/ec2/2016-09-15 copying build/lib/botocore/data/ec2/2016-09-15/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2016-09-15 copying build/lib/botocore/data/ec2/2016-09-15/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2016-09-15 copying build/lib/botocore/data/ec2/2016-09-15/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2016-09-15 copying build/lib/botocore/data/ec2/2016-09-15/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2016-09-15 copying build/lib/botocore/data/ec2/2016-09-15/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2016-09-15 creating build/bdist.linux-aarch64/wheel/botocore/data/ec2/2016-11-15 copying build/lib/botocore/data/ec2/2016-11-15/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2016-11-15 copying build/lib/botocore/data/ec2/2016-11-15/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2016-11-15 copying build/lib/botocore/data/ec2/2016-11-15/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2016-11-15 copying build/lib/botocore/data/ec2/2016-11-15/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2016-11-15 copying build/lib/botocore/data/ec2/2016-11-15/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2016-11-15 copying build/lib/botocore/data/ec2/2016-11-15/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ec2/2016-11-15 creating build/bdist.linux-aarch64/wheel/botocore/data/ecr-public creating build/bdist.linux-aarch64/wheel/botocore/data/ecr-public/2020-10-30 copying build/lib/botocore/data/ecr-public/2020-10-30/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ecr-public/2020-10-30 copying build/lib/botocore/data/ecr-public/2020-10-30/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ecr-public/2020-10-30 copying build/lib/botocore/data/ecr-public/2020-10-30/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ecr-public/2020-10-30 copying build/lib/botocore/data/ecr-public/2020-10-30/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ecr-public/2020-10-30 creating build/bdist.linux-aarch64/wheel/botocore/data/ecr creating build/bdist.linux-aarch64/wheel/botocore/data/ecr/2015-09-21 copying build/lib/botocore/data/ecr/2015-09-21/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ecr/2015-09-21 copying build/lib/botocore/data/ecr/2015-09-21/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ecr/2015-09-21 copying build/lib/botocore/data/ecr/2015-09-21/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ecr/2015-09-21 copying build/lib/botocore/data/ecr/2015-09-21/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ecr/2015-09-21 copying build/lib/botocore/data/ecr/2015-09-21/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ecr/2015-09-21 creating build/bdist.linux-aarch64/wheel/botocore/data/ecs creating build/bdist.linux-aarch64/wheel/botocore/data/ecs/2014-11-13 copying build/lib/botocore/data/ecs/2014-11-13/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ecs/2014-11-13 copying build/lib/botocore/data/ecs/2014-11-13/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ecs/2014-11-13 copying build/lib/botocore/data/ecs/2014-11-13/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ecs/2014-11-13 copying build/lib/botocore/data/ecs/2014-11-13/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ecs/2014-11-13 copying build/lib/botocore/data/ecs/2014-11-13/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ecs/2014-11-13 creating build/bdist.linux-aarch64/wheel/botocore/data/efs creating build/bdist.linux-aarch64/wheel/botocore/data/efs/2015-02-01 copying build/lib/botocore/data/efs/2015-02-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/efs/2015-02-01 copying build/lib/botocore/data/efs/2015-02-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/efs/2015-02-01 copying build/lib/botocore/data/efs/2015-02-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/efs/2015-02-01 copying build/lib/botocore/data/efs/2015-02-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/efs/2015-02-01 creating build/bdist.linux-aarch64/wheel/botocore/data/eks-auth creating build/bdist.linux-aarch64/wheel/botocore/data/eks-auth/2023-11-26 copying build/lib/botocore/data/eks-auth/2023-11-26/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/eks-auth/2023-11-26 copying build/lib/botocore/data/eks-auth/2023-11-26/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/eks-auth/2023-11-26 copying build/lib/botocore/data/eks-auth/2023-11-26/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/eks-auth/2023-11-26 copying build/lib/botocore/data/eks-auth/2023-11-26/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/eks-auth/2023-11-26 creating build/bdist.linux-aarch64/wheel/botocore/data/eks creating build/bdist.linux-aarch64/wheel/botocore/data/eks/2017-11-01 copying build/lib/botocore/data/eks/2017-11-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/eks/2017-11-01 copying build/lib/botocore/data/eks/2017-11-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/eks/2017-11-01 copying build/lib/botocore/data/eks/2017-11-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/eks/2017-11-01 copying build/lib/botocore/data/eks/2017-11-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/eks/2017-11-01 copying build/lib/botocore/data/eks/2017-11-01/service-2.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/eks/2017-11-01 copying build/lib/botocore/data/eks/2017-11-01/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/eks/2017-11-01 creating build/bdist.linux-aarch64/wheel/botocore/data/elasticache creating build/bdist.linux-aarch64/wheel/botocore/data/elasticache/2014-09-30 copying build/lib/botocore/data/elasticache/2014-09-30/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/elasticache/2014-09-30 copying build/lib/botocore/data/elasticache/2014-09-30/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/elasticache/2014-09-30 copying build/lib/botocore/data/elasticache/2014-09-30/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/elasticache/2014-09-30 copying build/lib/botocore/data/elasticache/2014-09-30/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/elasticache/2014-09-30 creating build/bdist.linux-aarch64/wheel/botocore/data/elasticache/2015-02-02 copying build/lib/botocore/data/elasticache/2015-02-02/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/elasticache/2015-02-02 copying build/lib/botocore/data/elasticache/2015-02-02/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/elasticache/2015-02-02 copying build/lib/botocore/data/elasticache/2015-02-02/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/elasticache/2015-02-02 copying build/lib/botocore/data/elasticache/2015-02-02/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/elasticache/2015-02-02 copying build/lib/botocore/data/elasticache/2015-02-02/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/elasticache/2015-02-02 creating build/bdist.linux-aarch64/wheel/botocore/data/elasticbeanstalk creating build/bdist.linux-aarch64/wheel/botocore/data/elasticbeanstalk/2010-12-01 copying build/lib/botocore/data/elasticbeanstalk/2010-12-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/elasticbeanstalk/2010-12-01 copying build/lib/botocore/data/elasticbeanstalk/2010-12-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/elasticbeanstalk/2010-12-01 copying build/lib/botocore/data/elasticbeanstalk/2010-12-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/elasticbeanstalk/2010-12-01 copying build/lib/botocore/data/elasticbeanstalk/2010-12-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/elasticbeanstalk/2010-12-01 copying build/lib/botocore/data/elasticbeanstalk/2010-12-01/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/elasticbeanstalk/2010-12-01 creating build/bdist.linux-aarch64/wheel/botocore/data/elb creating build/bdist.linux-aarch64/wheel/botocore/data/elb/2012-06-01 copying build/lib/botocore/data/elb/2012-06-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/elb/2012-06-01 copying build/lib/botocore/data/elb/2012-06-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/elb/2012-06-01 copying build/lib/botocore/data/elb/2012-06-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/elb/2012-06-01 copying build/lib/botocore/data/elb/2012-06-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/elb/2012-06-01 copying build/lib/botocore/data/elb/2012-06-01/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/elb/2012-06-01 creating build/bdist.linux-aarch64/wheel/botocore/data/elbv2 creating build/bdist.linux-aarch64/wheel/botocore/data/elbv2/2015-12-01 copying build/lib/botocore/data/elbv2/2015-12-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/elbv2/2015-12-01 copying build/lib/botocore/data/elbv2/2015-12-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/elbv2/2015-12-01 copying build/lib/botocore/data/elbv2/2015-12-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/elbv2/2015-12-01 copying build/lib/botocore/data/elbv2/2015-12-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/elbv2/2015-12-01 copying build/lib/botocore/data/elbv2/2015-12-01/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/elbv2/2015-12-01 creating build/bdist.linux-aarch64/wheel/botocore/data/elementalinference creating build/bdist.linux-aarch64/wheel/botocore/data/elementalinference/2018-11-14 copying build/lib/botocore/data/elementalinference/2018-11-14/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/elementalinference/2018-11-14 copying build/lib/botocore/data/elementalinference/2018-11-14/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/elementalinference/2018-11-14 copying build/lib/botocore/data/elementalinference/2018-11-14/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/elementalinference/2018-11-14 copying build/lib/botocore/data/elementalinference/2018-11-14/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/elementalinference/2018-11-14 creating build/bdist.linux-aarch64/wheel/botocore/data/emr-containers creating build/bdist.linux-aarch64/wheel/botocore/data/emr-containers/2020-10-01 copying build/lib/botocore/data/emr-containers/2020-10-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/emr-containers/2020-10-01 copying build/lib/botocore/data/emr-containers/2020-10-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/emr-containers/2020-10-01 copying build/lib/botocore/data/emr-containers/2020-10-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/emr-containers/2020-10-01 copying build/lib/botocore/data/emr-containers/2020-10-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/emr-containers/2020-10-01 creating build/bdist.linux-aarch64/wheel/botocore/data/emr-serverless creating build/bdist.linux-aarch64/wheel/botocore/data/emr-serverless/2021-07-13 copying build/lib/botocore/data/emr-serverless/2021-07-13/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/emr-serverless/2021-07-13 copying build/lib/botocore/data/emr-serverless/2021-07-13/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/emr-serverless/2021-07-13 copying build/lib/botocore/data/emr-serverless/2021-07-13/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/emr-serverless/2021-07-13 creating build/bdist.linux-aarch64/wheel/botocore/data/emr creating build/bdist.linux-aarch64/wheel/botocore/data/emr/2009-03-31 copying build/lib/botocore/data/emr/2009-03-31/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/emr/2009-03-31 copying build/lib/botocore/data/emr/2009-03-31/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/emr/2009-03-31 copying build/lib/botocore/data/emr/2009-03-31/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/emr/2009-03-31 copying build/lib/botocore/data/emr/2009-03-31/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/emr/2009-03-31 copying build/lib/botocore/data/emr/2009-03-31/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/emr/2009-03-31 creating build/bdist.linux-aarch64/wheel/botocore/data/entityresolution creating build/bdist.linux-aarch64/wheel/botocore/data/entityresolution/2018-05-10 copying build/lib/botocore/data/entityresolution/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/entityresolution/2018-05-10 copying build/lib/botocore/data/entityresolution/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/entityresolution/2018-05-10 copying build/lib/botocore/data/entityresolution/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/entityresolution/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/es creating build/bdist.linux-aarch64/wheel/botocore/data/es/2015-01-01 copying build/lib/botocore/data/es/2015-01-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/es/2015-01-01 copying build/lib/botocore/data/es/2015-01-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/es/2015-01-01 copying build/lib/botocore/data/es/2015-01-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/es/2015-01-01 copying build/lib/botocore/data/es/2015-01-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/es/2015-01-01 creating build/bdist.linux-aarch64/wheel/botocore/data/events creating build/bdist.linux-aarch64/wheel/botocore/data/events/2014-02-03 copying build/lib/botocore/data/events/2014-02-03/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/events/2014-02-03 copying build/lib/botocore/data/events/2014-02-03/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/events/2014-02-03 creating build/bdist.linux-aarch64/wheel/botocore/data/events/2015-10-07 copying build/lib/botocore/data/events/2015-10-07/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/events/2015-10-07 copying build/lib/botocore/data/events/2015-10-07/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/events/2015-10-07 copying build/lib/botocore/data/events/2015-10-07/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/events/2015-10-07 copying build/lib/botocore/data/events/2015-10-07/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/events/2015-10-07 creating build/bdist.linux-aarch64/wheel/botocore/data/evs creating build/bdist.linux-aarch64/wheel/botocore/data/evs/2023-07-27 copying build/lib/botocore/data/evs/2023-07-27/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/evs/2023-07-27 copying build/lib/botocore/data/evs/2023-07-27/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/evs/2023-07-27 copying build/lib/botocore/data/evs/2023-07-27/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/evs/2023-07-27 copying build/lib/botocore/data/evs/2023-07-27/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/evs/2023-07-27 creating build/bdist.linux-aarch64/wheel/botocore/data/finspace-data creating build/bdist.linux-aarch64/wheel/botocore/data/finspace-data/2020-07-13 copying build/lib/botocore/data/finspace-data/2020-07-13/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/finspace-data/2020-07-13 copying build/lib/botocore/data/finspace-data/2020-07-13/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/finspace-data/2020-07-13 copying build/lib/botocore/data/finspace-data/2020-07-13/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/finspace-data/2020-07-13 copying build/lib/botocore/data/finspace-data/2020-07-13/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/finspace-data/2020-07-13 creating build/bdist.linux-aarch64/wheel/botocore/data/finspace creating build/bdist.linux-aarch64/wheel/botocore/data/finspace/2021-03-12 copying build/lib/botocore/data/finspace/2021-03-12/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/finspace/2021-03-12 copying build/lib/botocore/data/finspace/2021-03-12/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/finspace/2021-03-12 copying build/lib/botocore/data/finspace/2021-03-12/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/finspace/2021-03-12 copying build/lib/botocore/data/finspace/2021-03-12/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/finspace/2021-03-12 creating build/bdist.linux-aarch64/wheel/botocore/data/firehose creating build/bdist.linux-aarch64/wheel/botocore/data/firehose/2015-08-04 copying build/lib/botocore/data/firehose/2015-08-04/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/firehose/2015-08-04 copying build/lib/botocore/data/firehose/2015-08-04/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/firehose/2015-08-04 copying build/lib/botocore/data/firehose/2015-08-04/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/firehose/2015-08-04 copying build/lib/botocore/data/firehose/2015-08-04/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/firehose/2015-08-04 creating build/bdist.linux-aarch64/wheel/botocore/data/fis creating build/bdist.linux-aarch64/wheel/botocore/data/fis/2020-12-01 copying build/lib/botocore/data/fis/2020-12-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/fis/2020-12-01 copying build/lib/botocore/data/fis/2020-12-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/fis/2020-12-01 copying build/lib/botocore/data/fis/2020-12-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/fis/2020-12-01 copying build/lib/botocore/data/fis/2020-12-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/fis/2020-12-01 creating build/bdist.linux-aarch64/wheel/botocore/data/fms creating build/bdist.linux-aarch64/wheel/botocore/data/fms/2018-01-01 copying build/lib/botocore/data/fms/2018-01-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/fms/2018-01-01 copying build/lib/botocore/data/fms/2018-01-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/fms/2018-01-01 copying build/lib/botocore/data/fms/2018-01-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/fms/2018-01-01 copying build/lib/botocore/data/fms/2018-01-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/fms/2018-01-01 creating build/bdist.linux-aarch64/wheel/botocore/data/forecast creating build/bdist.linux-aarch64/wheel/botocore/data/forecast/2018-06-26 copying build/lib/botocore/data/forecast/2018-06-26/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/forecast/2018-06-26 copying build/lib/botocore/data/forecast/2018-06-26/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/forecast/2018-06-26 copying build/lib/botocore/data/forecast/2018-06-26/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/forecast/2018-06-26 copying build/lib/botocore/data/forecast/2018-06-26/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/forecast/2018-06-26 creating build/bdist.linux-aarch64/wheel/botocore/data/forecastquery creating build/bdist.linux-aarch64/wheel/botocore/data/forecastquery/2018-06-26 copying build/lib/botocore/data/forecastquery/2018-06-26/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/forecastquery/2018-06-26 copying build/lib/botocore/data/forecastquery/2018-06-26/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/forecastquery/2018-06-26 copying build/lib/botocore/data/forecastquery/2018-06-26/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/forecastquery/2018-06-26 copying build/lib/botocore/data/forecastquery/2018-06-26/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/forecastquery/2018-06-26 creating build/bdist.linux-aarch64/wheel/botocore/data/frauddetector creating build/bdist.linux-aarch64/wheel/botocore/data/frauddetector/2019-11-15 copying build/lib/botocore/data/frauddetector/2019-11-15/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/frauddetector/2019-11-15 copying build/lib/botocore/data/frauddetector/2019-11-15/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/frauddetector/2019-11-15 copying build/lib/botocore/data/frauddetector/2019-11-15/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/frauddetector/2019-11-15 copying build/lib/botocore/data/frauddetector/2019-11-15/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/frauddetector/2019-11-15 creating build/bdist.linux-aarch64/wheel/botocore/data/freetier creating build/bdist.linux-aarch64/wheel/botocore/data/freetier/2023-09-07 copying build/lib/botocore/data/freetier/2023-09-07/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/freetier/2023-09-07 copying build/lib/botocore/data/freetier/2023-09-07/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/freetier/2023-09-07 copying build/lib/botocore/data/freetier/2023-09-07/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/freetier/2023-09-07 copying build/lib/botocore/data/freetier/2023-09-07/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/freetier/2023-09-07 creating build/bdist.linux-aarch64/wheel/botocore/data/fsx creating build/bdist.linux-aarch64/wheel/botocore/data/fsx/2018-03-01 copying build/lib/botocore/data/fsx/2018-03-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/fsx/2018-03-01 copying build/lib/botocore/data/fsx/2018-03-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/fsx/2018-03-01 copying build/lib/botocore/data/fsx/2018-03-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/fsx/2018-03-01 copying build/lib/botocore/data/fsx/2018-03-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/fsx/2018-03-01 creating build/bdist.linux-aarch64/wheel/botocore/data/gamelift creating build/bdist.linux-aarch64/wheel/botocore/data/gamelift/2015-10-01 copying build/lib/botocore/data/gamelift/2015-10-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/gamelift/2015-10-01 copying build/lib/botocore/data/gamelift/2015-10-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/gamelift/2015-10-01 copying build/lib/botocore/data/gamelift/2015-10-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/gamelift/2015-10-01 copying build/lib/botocore/data/gamelift/2015-10-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/gamelift/2015-10-01 creating build/bdist.linux-aarch64/wheel/botocore/data/gameliftstreams creating build/bdist.linux-aarch64/wheel/botocore/data/gameliftstreams/2018-05-10 copying build/lib/botocore/data/gameliftstreams/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/gameliftstreams/2018-05-10 copying build/lib/botocore/data/gameliftstreams/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/gameliftstreams/2018-05-10 copying build/lib/botocore/data/gameliftstreams/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/gameliftstreams/2018-05-10 copying build/lib/botocore/data/gameliftstreams/2018-05-10/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/gameliftstreams/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/geo-maps creating build/bdist.linux-aarch64/wheel/botocore/data/geo-maps/2020-11-19 copying build/lib/botocore/data/geo-maps/2020-11-19/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/geo-maps/2020-11-19 copying build/lib/botocore/data/geo-maps/2020-11-19/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/geo-maps/2020-11-19 copying build/lib/botocore/data/geo-maps/2020-11-19/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/geo-maps/2020-11-19 copying build/lib/botocore/data/geo-maps/2020-11-19/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/geo-maps/2020-11-19 creating build/bdist.linux-aarch64/wheel/botocore/data/geo-places creating build/bdist.linux-aarch64/wheel/botocore/data/geo-places/2020-11-19 copying build/lib/botocore/data/geo-places/2020-11-19/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/geo-places/2020-11-19 copying build/lib/botocore/data/geo-places/2020-11-19/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/geo-places/2020-11-19 copying build/lib/botocore/data/geo-places/2020-11-19/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/geo-places/2020-11-19 copying build/lib/botocore/data/geo-places/2020-11-19/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/geo-places/2020-11-19 creating build/bdist.linux-aarch64/wheel/botocore/data/geo-routes creating build/bdist.linux-aarch64/wheel/botocore/data/geo-routes/2020-11-19 copying build/lib/botocore/data/geo-routes/2020-11-19/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/geo-routes/2020-11-19 copying build/lib/botocore/data/geo-routes/2020-11-19/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/geo-routes/2020-11-19 copying build/lib/botocore/data/geo-routes/2020-11-19/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/geo-routes/2020-11-19 copying build/lib/botocore/data/geo-routes/2020-11-19/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/geo-routes/2020-11-19 creating build/bdist.linux-aarch64/wheel/botocore/data/glacier creating build/bdist.linux-aarch64/wheel/botocore/data/glacier/2012-06-01 copying build/lib/botocore/data/glacier/2012-06-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/glacier/2012-06-01 copying build/lib/botocore/data/glacier/2012-06-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/glacier/2012-06-01 copying build/lib/botocore/data/glacier/2012-06-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/glacier/2012-06-01 copying build/lib/botocore/data/glacier/2012-06-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/glacier/2012-06-01 copying build/lib/botocore/data/glacier/2012-06-01/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/glacier/2012-06-01 creating build/bdist.linux-aarch64/wheel/botocore/data/globalaccelerator creating build/bdist.linux-aarch64/wheel/botocore/data/globalaccelerator/2018-08-08 copying build/lib/botocore/data/globalaccelerator/2018-08-08/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/globalaccelerator/2018-08-08 copying build/lib/botocore/data/globalaccelerator/2018-08-08/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/globalaccelerator/2018-08-08 copying build/lib/botocore/data/globalaccelerator/2018-08-08/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/globalaccelerator/2018-08-08 copying build/lib/botocore/data/globalaccelerator/2018-08-08/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/globalaccelerator/2018-08-08 creating build/bdist.linux-aarch64/wheel/botocore/data/glue creating build/bdist.linux-aarch64/wheel/botocore/data/glue/2017-03-31 copying build/lib/botocore/data/glue/2017-03-31/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/glue/2017-03-31 copying build/lib/botocore/data/glue/2017-03-31/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/glue/2017-03-31 copying build/lib/botocore/data/glue/2017-03-31/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/glue/2017-03-31 copying build/lib/botocore/data/glue/2017-03-31/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/glue/2017-03-31 copying build/lib/botocore/data/glue/2017-03-31/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/glue/2017-03-31 creating build/bdist.linux-aarch64/wheel/botocore/data/grafana creating build/bdist.linux-aarch64/wheel/botocore/data/grafana/2020-08-18 copying build/lib/botocore/data/grafana/2020-08-18/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/grafana/2020-08-18 copying build/lib/botocore/data/grafana/2020-08-18/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/grafana/2020-08-18 copying build/lib/botocore/data/grafana/2020-08-18/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/grafana/2020-08-18 copying build/lib/botocore/data/grafana/2020-08-18/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/grafana/2020-08-18 copying build/lib/botocore/data/grafana/2020-08-18/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/grafana/2020-08-18 copying build/lib/botocore/data/grafana/2020-08-18/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/grafana/2020-08-18 creating build/bdist.linux-aarch64/wheel/botocore/data/greengrass creating build/bdist.linux-aarch64/wheel/botocore/data/greengrass/2017-06-07 copying build/lib/botocore/data/greengrass/2017-06-07/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/greengrass/2017-06-07 copying build/lib/botocore/data/greengrass/2017-06-07/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/greengrass/2017-06-07 copying build/lib/botocore/data/greengrass/2017-06-07/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/greengrass/2017-06-07 creating build/bdist.linux-aarch64/wheel/botocore/data/greengrassv2 creating build/bdist.linux-aarch64/wheel/botocore/data/greengrassv2/2020-11-30 copying build/lib/botocore/data/greengrassv2/2020-11-30/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/greengrassv2/2020-11-30 copying build/lib/botocore/data/greengrassv2/2020-11-30/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/greengrassv2/2020-11-30 copying build/lib/botocore/data/greengrassv2/2020-11-30/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/greengrassv2/2020-11-30 copying build/lib/botocore/data/greengrassv2/2020-11-30/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/greengrassv2/2020-11-30 creating build/bdist.linux-aarch64/wheel/botocore/data/groundstation creating build/bdist.linux-aarch64/wheel/botocore/data/groundstation/2019-05-23 copying build/lib/botocore/data/groundstation/2019-05-23/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/groundstation/2019-05-23 copying build/lib/botocore/data/groundstation/2019-05-23/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/groundstation/2019-05-23 copying build/lib/botocore/data/groundstation/2019-05-23/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/groundstation/2019-05-23 copying build/lib/botocore/data/groundstation/2019-05-23/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/groundstation/2019-05-23 copying build/lib/botocore/data/groundstation/2019-05-23/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/groundstation/2019-05-23 creating build/bdist.linux-aarch64/wheel/botocore/data/guardduty creating build/bdist.linux-aarch64/wheel/botocore/data/guardduty/2017-11-28 copying build/lib/botocore/data/guardduty/2017-11-28/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/guardduty/2017-11-28 copying build/lib/botocore/data/guardduty/2017-11-28/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/guardduty/2017-11-28 copying build/lib/botocore/data/guardduty/2017-11-28/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/guardduty/2017-11-28 copying build/lib/botocore/data/guardduty/2017-11-28/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/guardduty/2017-11-28 creating build/bdist.linux-aarch64/wheel/botocore/data/health creating build/bdist.linux-aarch64/wheel/botocore/data/health/2016-08-04 copying build/lib/botocore/data/health/2016-08-04/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/health/2016-08-04 copying build/lib/botocore/data/health/2016-08-04/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/health/2016-08-04 copying build/lib/botocore/data/health/2016-08-04/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/health/2016-08-04 copying build/lib/botocore/data/health/2016-08-04/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/health/2016-08-04 creating build/bdist.linux-aarch64/wheel/botocore/data/healthlake creating build/bdist.linux-aarch64/wheel/botocore/data/healthlake/2017-07-01 copying build/lib/botocore/data/healthlake/2017-07-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/healthlake/2017-07-01 copying build/lib/botocore/data/healthlake/2017-07-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/healthlake/2017-07-01 copying build/lib/botocore/data/healthlake/2017-07-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/healthlake/2017-07-01 copying build/lib/botocore/data/healthlake/2017-07-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/healthlake/2017-07-01 copying build/lib/botocore/data/healthlake/2017-07-01/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/healthlake/2017-07-01 creating build/bdist.linux-aarch64/wheel/botocore/data/iam creating build/bdist.linux-aarch64/wheel/botocore/data/iam/2010-05-08 copying build/lib/botocore/data/iam/2010-05-08/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iam/2010-05-08 copying build/lib/botocore/data/iam/2010-05-08/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iam/2010-05-08 copying build/lib/botocore/data/iam/2010-05-08/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iam/2010-05-08 copying build/lib/botocore/data/iam/2010-05-08/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/iam/2010-05-08 copying build/lib/botocore/data/iam/2010-05-08/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/iam/2010-05-08 creating build/bdist.linux-aarch64/wheel/botocore/data/identitystore creating build/bdist.linux-aarch64/wheel/botocore/data/identitystore/2020-06-15 copying build/lib/botocore/data/identitystore/2020-06-15/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/identitystore/2020-06-15 copying build/lib/botocore/data/identitystore/2020-06-15/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/identitystore/2020-06-15 copying build/lib/botocore/data/identitystore/2020-06-15/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/identitystore/2020-06-15 copying build/lib/botocore/data/identitystore/2020-06-15/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/identitystore/2020-06-15 creating build/bdist.linux-aarch64/wheel/botocore/data/imagebuilder creating build/bdist.linux-aarch64/wheel/botocore/data/imagebuilder/2019-12-02 copying build/lib/botocore/data/imagebuilder/2019-12-02/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/imagebuilder/2019-12-02 copying build/lib/botocore/data/imagebuilder/2019-12-02/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/imagebuilder/2019-12-02 copying build/lib/botocore/data/imagebuilder/2019-12-02/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/imagebuilder/2019-12-02 copying build/lib/botocore/data/imagebuilder/2019-12-02/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/imagebuilder/2019-12-02 copying build/lib/botocore/data/imagebuilder/2019-12-02/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/imagebuilder/2019-12-02 creating build/bdist.linux-aarch64/wheel/botocore/data/importexport creating build/bdist.linux-aarch64/wheel/botocore/data/importexport/2010-06-01 copying build/lib/botocore/data/importexport/2010-06-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/importexport/2010-06-01 copying build/lib/botocore/data/importexport/2010-06-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/importexport/2010-06-01 copying build/lib/botocore/data/importexport/2010-06-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/importexport/2010-06-01 creating build/bdist.linux-aarch64/wheel/botocore/data/inspector-scan creating build/bdist.linux-aarch64/wheel/botocore/data/inspector-scan/2023-08-08 copying build/lib/botocore/data/inspector-scan/2023-08-08/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/inspector-scan/2023-08-08 copying build/lib/botocore/data/inspector-scan/2023-08-08/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/inspector-scan/2023-08-08 copying build/lib/botocore/data/inspector-scan/2023-08-08/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/inspector-scan/2023-08-08 creating build/bdist.linux-aarch64/wheel/botocore/data/inspector creating build/bdist.linux-aarch64/wheel/botocore/data/inspector/2015-08-18 copying build/lib/botocore/data/inspector/2015-08-18/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/inspector/2015-08-18 copying build/lib/botocore/data/inspector/2015-08-18/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/inspector/2015-08-18 creating build/bdist.linux-aarch64/wheel/botocore/data/inspector/2016-02-16 copying build/lib/botocore/data/inspector/2016-02-16/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/inspector/2016-02-16 copying build/lib/botocore/data/inspector/2016-02-16/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/inspector/2016-02-16 copying build/lib/botocore/data/inspector/2016-02-16/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/inspector/2016-02-16 copying build/lib/botocore/data/inspector/2016-02-16/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/inspector/2016-02-16 creating build/bdist.linux-aarch64/wheel/botocore/data/inspector2 creating build/bdist.linux-aarch64/wheel/botocore/data/inspector2/2020-06-08 copying build/lib/botocore/data/inspector2/2020-06-08/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/inspector2/2020-06-08 copying build/lib/botocore/data/inspector2/2020-06-08/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/inspector2/2020-06-08 copying build/lib/botocore/data/inspector2/2020-06-08/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/inspector2/2020-06-08 copying build/lib/botocore/data/inspector2/2020-06-08/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/inspector2/2020-06-08 copying build/lib/botocore/data/inspector2/2020-06-08/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/inspector2/2020-06-08 creating build/bdist.linux-aarch64/wheel/botocore/data/interconnect creating build/bdist.linux-aarch64/wheel/botocore/data/interconnect/2022-07-26 copying build/lib/botocore/data/interconnect/2022-07-26/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/interconnect/2022-07-26 copying build/lib/botocore/data/interconnect/2022-07-26/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/interconnect/2022-07-26 copying build/lib/botocore/data/interconnect/2022-07-26/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/interconnect/2022-07-26 copying build/lib/botocore/data/interconnect/2022-07-26/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/interconnect/2022-07-26 creating build/bdist.linux-aarch64/wheel/botocore/data/internetmonitor creating build/bdist.linux-aarch64/wheel/botocore/data/internetmonitor/2021-06-03 copying build/lib/botocore/data/internetmonitor/2021-06-03/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/internetmonitor/2021-06-03 copying build/lib/botocore/data/internetmonitor/2021-06-03/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/internetmonitor/2021-06-03 copying build/lib/botocore/data/internetmonitor/2021-06-03/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/internetmonitor/2021-06-03 copying build/lib/botocore/data/internetmonitor/2021-06-03/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/internetmonitor/2021-06-03 creating build/bdist.linux-aarch64/wheel/botocore/data/invoicing creating build/bdist.linux-aarch64/wheel/botocore/data/invoicing/2024-12-01 copying build/lib/botocore/data/invoicing/2024-12-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/invoicing/2024-12-01 copying build/lib/botocore/data/invoicing/2024-12-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/invoicing/2024-12-01 copying build/lib/botocore/data/invoicing/2024-12-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/invoicing/2024-12-01 copying build/lib/botocore/data/invoicing/2024-12-01/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/invoicing/2024-12-01 creating build/bdist.linux-aarch64/wheel/botocore/data/iot-data creating build/bdist.linux-aarch64/wheel/botocore/data/iot-data/2015-05-28 copying build/lib/botocore/data/iot-data/2015-05-28/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iot-data/2015-05-28 copying build/lib/botocore/data/iot-data/2015-05-28/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iot-data/2015-05-28 copying build/lib/botocore/data/iot-data/2015-05-28/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iot-data/2015-05-28 copying build/lib/botocore/data/iot-data/2015-05-28/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/iot-data/2015-05-28 creating build/bdist.linux-aarch64/wheel/botocore/data/iot-jobs-data creating build/bdist.linux-aarch64/wheel/botocore/data/iot-jobs-data/2017-09-29 copying build/lib/botocore/data/iot-jobs-data/2017-09-29/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iot-jobs-data/2017-09-29 copying build/lib/botocore/data/iot-jobs-data/2017-09-29/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iot-jobs-data/2017-09-29 copying build/lib/botocore/data/iot-jobs-data/2017-09-29/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iot-jobs-data/2017-09-29 copying build/lib/botocore/data/iot-jobs-data/2017-09-29/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/iot-jobs-data/2017-09-29 creating build/bdist.linux-aarch64/wheel/botocore/data/iot-managed-integrations creating build/bdist.linux-aarch64/wheel/botocore/data/iot-managed-integrations/2025-03-03 copying build/lib/botocore/data/iot-managed-integrations/2025-03-03/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iot-managed-integrations/2025-03-03 copying build/lib/botocore/data/iot-managed-integrations/2025-03-03/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iot-managed-integrations/2025-03-03 copying build/lib/botocore/data/iot-managed-integrations/2025-03-03/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/iot-managed-integrations/2025-03-03 creating build/bdist.linux-aarch64/wheel/botocore/data/iot creating build/bdist.linux-aarch64/wheel/botocore/data/iot/2015-05-28 copying build/lib/botocore/data/iot/2015-05-28/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iot/2015-05-28 copying build/lib/botocore/data/iot/2015-05-28/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iot/2015-05-28 copying build/lib/botocore/data/iot/2015-05-28/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iot/2015-05-28 copying build/lib/botocore/data/iot/2015-05-28/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/iot/2015-05-28 creating build/bdist.linux-aarch64/wheel/botocore/data/iotdeviceadvisor creating build/bdist.linux-aarch64/wheel/botocore/data/iotdeviceadvisor/2020-09-18 copying build/lib/botocore/data/iotdeviceadvisor/2020-09-18/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotdeviceadvisor/2020-09-18 copying build/lib/botocore/data/iotdeviceadvisor/2020-09-18/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotdeviceadvisor/2020-09-18 copying build/lib/botocore/data/iotdeviceadvisor/2020-09-18/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotdeviceadvisor/2020-09-18 copying build/lib/botocore/data/iotdeviceadvisor/2020-09-18/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotdeviceadvisor/2020-09-18 creating build/bdist.linux-aarch64/wheel/botocore/data/iotevents-data creating build/bdist.linux-aarch64/wheel/botocore/data/iotevents-data/2018-10-23 copying build/lib/botocore/data/iotevents-data/2018-10-23/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotevents-data/2018-10-23 copying build/lib/botocore/data/iotevents-data/2018-10-23/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotevents-data/2018-10-23 copying build/lib/botocore/data/iotevents-data/2018-10-23/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotevents-data/2018-10-23 copying build/lib/botocore/data/iotevents-data/2018-10-23/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotevents-data/2018-10-23 creating build/bdist.linux-aarch64/wheel/botocore/data/iotevents creating build/bdist.linux-aarch64/wheel/botocore/data/iotevents/2018-07-27 copying build/lib/botocore/data/iotevents/2018-07-27/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotevents/2018-07-27 copying build/lib/botocore/data/iotevents/2018-07-27/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotevents/2018-07-27 copying build/lib/botocore/data/iotevents/2018-07-27/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotevents/2018-07-27 copying build/lib/botocore/data/iotevents/2018-07-27/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotevents/2018-07-27 creating build/bdist.linux-aarch64/wheel/botocore/data/iotfleetwise creating build/bdist.linux-aarch64/wheel/botocore/data/iotfleetwise/2021-06-17 copying build/lib/botocore/data/iotfleetwise/2021-06-17/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotfleetwise/2021-06-17 copying build/lib/botocore/data/iotfleetwise/2021-06-17/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotfleetwise/2021-06-17 copying build/lib/botocore/data/iotfleetwise/2021-06-17/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotfleetwise/2021-06-17 copying build/lib/botocore/data/iotfleetwise/2021-06-17/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotfleetwise/2021-06-17 creating build/bdist.linux-aarch64/wheel/botocore/data/iotsecuretunneling creating build/bdist.linux-aarch64/wheel/botocore/data/iotsecuretunneling/2018-10-05 copying build/lib/botocore/data/iotsecuretunneling/2018-10-05/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotsecuretunneling/2018-10-05 copying build/lib/botocore/data/iotsecuretunneling/2018-10-05/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotsecuretunneling/2018-10-05 copying build/lib/botocore/data/iotsecuretunneling/2018-10-05/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotsecuretunneling/2018-10-05 copying build/lib/botocore/data/iotsecuretunneling/2018-10-05/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotsecuretunneling/2018-10-05 creating build/bdist.linux-aarch64/wheel/botocore/data/iotsitewise creating build/bdist.linux-aarch64/wheel/botocore/data/iotsitewise/2019-12-02 copying build/lib/botocore/data/iotsitewise/2019-12-02/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotsitewise/2019-12-02 copying build/lib/botocore/data/iotsitewise/2019-12-02/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotsitewise/2019-12-02 copying build/lib/botocore/data/iotsitewise/2019-12-02/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotsitewise/2019-12-02 copying build/lib/botocore/data/iotsitewise/2019-12-02/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotsitewise/2019-12-02 copying build/lib/botocore/data/iotsitewise/2019-12-02/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotsitewise/2019-12-02 copying build/lib/botocore/data/iotsitewise/2019-12-02/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotsitewise/2019-12-02 creating build/bdist.linux-aarch64/wheel/botocore/data/iotthingsgraph creating build/bdist.linux-aarch64/wheel/botocore/data/iotthingsgraph/2018-09-06 copying build/lib/botocore/data/iotthingsgraph/2018-09-06/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotthingsgraph/2018-09-06 copying build/lib/botocore/data/iotthingsgraph/2018-09-06/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotthingsgraph/2018-09-06 copying build/lib/botocore/data/iotthingsgraph/2018-09-06/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotthingsgraph/2018-09-06 copying build/lib/botocore/data/iotthingsgraph/2018-09-06/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotthingsgraph/2018-09-06 creating build/bdist.linux-aarch64/wheel/botocore/data/iottwinmaker creating build/bdist.linux-aarch64/wheel/botocore/data/iottwinmaker/2021-11-29 copying build/lib/botocore/data/iottwinmaker/2021-11-29/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iottwinmaker/2021-11-29 copying build/lib/botocore/data/iottwinmaker/2021-11-29/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iottwinmaker/2021-11-29 copying build/lib/botocore/data/iottwinmaker/2021-11-29/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iottwinmaker/2021-11-29 copying build/lib/botocore/data/iottwinmaker/2021-11-29/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/iottwinmaker/2021-11-29 copying build/lib/botocore/data/iottwinmaker/2021-11-29/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/iottwinmaker/2021-11-29 creating build/bdist.linux-aarch64/wheel/botocore/data/iotwireless creating build/bdist.linux-aarch64/wheel/botocore/data/iotwireless/2020-11-22 copying build/lib/botocore/data/iotwireless/2020-11-22/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotwireless/2020-11-22 copying build/lib/botocore/data/iotwireless/2020-11-22/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotwireless/2020-11-22 copying build/lib/botocore/data/iotwireless/2020-11-22/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotwireless/2020-11-22 copying build/lib/botocore/data/iotwireless/2020-11-22/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/iotwireless/2020-11-22 creating build/bdist.linux-aarch64/wheel/botocore/data/ivs-realtime creating build/bdist.linux-aarch64/wheel/botocore/data/ivs-realtime/2020-07-14 copying build/lib/botocore/data/ivs-realtime/2020-07-14/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ivs-realtime/2020-07-14 copying build/lib/botocore/data/ivs-realtime/2020-07-14/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ivs-realtime/2020-07-14 copying build/lib/botocore/data/ivs-realtime/2020-07-14/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ivs-realtime/2020-07-14 copying build/lib/botocore/data/ivs-realtime/2020-07-14/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ivs-realtime/2020-07-14 creating build/bdist.linux-aarch64/wheel/botocore/data/ivs creating build/bdist.linux-aarch64/wheel/botocore/data/ivs/2020-07-14 copying build/lib/botocore/data/ivs/2020-07-14/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ivs/2020-07-14 copying build/lib/botocore/data/ivs/2020-07-14/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ivs/2020-07-14 copying build/lib/botocore/data/ivs/2020-07-14/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ivs/2020-07-14 copying build/lib/botocore/data/ivs/2020-07-14/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ivs/2020-07-14 creating build/bdist.linux-aarch64/wheel/botocore/data/ivschat creating build/bdist.linux-aarch64/wheel/botocore/data/ivschat/2020-07-14 copying build/lib/botocore/data/ivschat/2020-07-14/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ivschat/2020-07-14 copying build/lib/botocore/data/ivschat/2020-07-14/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ivschat/2020-07-14 copying build/lib/botocore/data/ivschat/2020-07-14/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ivschat/2020-07-14 copying build/lib/botocore/data/ivschat/2020-07-14/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ivschat/2020-07-14 copying build/lib/botocore/data/ivschat/2020-07-14/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ivschat/2020-07-14 creating build/bdist.linux-aarch64/wheel/botocore/data/kafka creating build/bdist.linux-aarch64/wheel/botocore/data/kafka/2018-11-14 copying build/lib/botocore/data/kafka/2018-11-14/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kafka/2018-11-14 copying build/lib/botocore/data/kafka/2018-11-14/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kafka/2018-11-14 copying build/lib/botocore/data/kafka/2018-11-14/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/kafka/2018-11-14 creating build/bdist.linux-aarch64/wheel/botocore/data/kafkaconnect creating build/bdist.linux-aarch64/wheel/botocore/data/kafkaconnect/2021-09-14 copying build/lib/botocore/data/kafkaconnect/2021-09-14/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kafkaconnect/2021-09-14 copying build/lib/botocore/data/kafkaconnect/2021-09-14/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kafkaconnect/2021-09-14 copying build/lib/botocore/data/kafkaconnect/2021-09-14/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kafkaconnect/2021-09-14 copying build/lib/botocore/data/kafkaconnect/2021-09-14/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/kafkaconnect/2021-09-14 copying build/lib/botocore/data/kafkaconnect/2021-09-14/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/kafkaconnect/2021-09-14 creating build/bdist.linux-aarch64/wheel/botocore/data/kendra-ranking creating build/bdist.linux-aarch64/wheel/botocore/data/kendra-ranking/2022-10-19 copying build/lib/botocore/data/kendra-ranking/2022-10-19/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kendra-ranking/2022-10-19 copying build/lib/botocore/data/kendra-ranking/2022-10-19/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kendra-ranking/2022-10-19 copying build/lib/botocore/data/kendra-ranking/2022-10-19/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/kendra-ranking/2022-10-19 creating build/bdist.linux-aarch64/wheel/botocore/data/kendra creating build/bdist.linux-aarch64/wheel/botocore/data/kendra/2019-02-03 copying build/lib/botocore/data/kendra/2019-02-03/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kendra/2019-02-03 copying build/lib/botocore/data/kendra/2019-02-03/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kendra/2019-02-03 copying build/lib/botocore/data/kendra/2019-02-03/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kendra/2019-02-03 copying build/lib/botocore/data/kendra/2019-02-03/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/kendra/2019-02-03 creating build/bdist.linux-aarch64/wheel/botocore/data/keyspaces creating build/bdist.linux-aarch64/wheel/botocore/data/keyspaces/2022-02-10 copying build/lib/botocore/data/keyspaces/2022-02-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/keyspaces/2022-02-10 copying build/lib/botocore/data/keyspaces/2022-02-10/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/keyspaces/2022-02-10 copying build/lib/botocore/data/keyspaces/2022-02-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/keyspaces/2022-02-10 copying build/lib/botocore/data/keyspaces/2022-02-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/keyspaces/2022-02-10 copying build/lib/botocore/data/keyspaces/2022-02-10/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/keyspaces/2022-02-10 creating build/bdist.linux-aarch64/wheel/botocore/data/keyspacesstreams creating build/bdist.linux-aarch64/wheel/botocore/data/keyspacesstreams/2024-09-09 copying build/lib/botocore/data/keyspacesstreams/2024-09-09/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/keyspacesstreams/2024-09-09 copying build/lib/botocore/data/keyspacesstreams/2024-09-09/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/keyspacesstreams/2024-09-09 copying build/lib/botocore/data/keyspacesstreams/2024-09-09/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/keyspacesstreams/2024-09-09 copying build/lib/botocore/data/keyspacesstreams/2024-09-09/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/keyspacesstreams/2024-09-09 creating build/bdist.linux-aarch64/wheel/botocore/data/kinesis-video-archived-media creating build/bdist.linux-aarch64/wheel/botocore/data/kinesis-video-archived-media/2017-09-30 copying build/lib/botocore/data/kinesis-video-archived-media/2017-09-30/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesis-video-archived-media/2017-09-30 copying build/lib/botocore/data/kinesis-video-archived-media/2017-09-30/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesis-video-archived-media/2017-09-30 copying build/lib/botocore/data/kinesis-video-archived-media/2017-09-30/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesis-video-archived-media/2017-09-30 copying build/lib/botocore/data/kinesis-video-archived-media/2017-09-30/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesis-video-archived-media/2017-09-30 creating build/bdist.linux-aarch64/wheel/botocore/data/kinesis-video-media creating build/bdist.linux-aarch64/wheel/botocore/data/kinesis-video-media/2017-09-30 copying build/lib/botocore/data/kinesis-video-media/2017-09-30/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesis-video-media/2017-09-30 copying build/lib/botocore/data/kinesis-video-media/2017-09-30/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesis-video-media/2017-09-30 copying build/lib/botocore/data/kinesis-video-media/2017-09-30/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesis-video-media/2017-09-30 copying build/lib/botocore/data/kinesis-video-media/2017-09-30/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesis-video-media/2017-09-30 creating build/bdist.linux-aarch64/wheel/botocore/data/kinesis-video-signaling creating build/bdist.linux-aarch64/wheel/botocore/data/kinesis-video-signaling/2019-12-04 copying build/lib/botocore/data/kinesis-video-signaling/2019-12-04/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesis-video-signaling/2019-12-04 copying build/lib/botocore/data/kinesis-video-signaling/2019-12-04/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesis-video-signaling/2019-12-04 copying build/lib/botocore/data/kinesis-video-signaling/2019-12-04/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesis-video-signaling/2019-12-04 copying build/lib/botocore/data/kinesis-video-signaling/2019-12-04/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesis-video-signaling/2019-12-04 creating build/bdist.linux-aarch64/wheel/botocore/data/kinesis-video-webrtc-storage creating build/bdist.linux-aarch64/wheel/botocore/data/kinesis-video-webrtc-storage/2018-05-10 copying build/lib/botocore/data/kinesis-video-webrtc-storage/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesis-video-webrtc-storage/2018-05-10 copying build/lib/botocore/data/kinesis-video-webrtc-storage/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesis-video-webrtc-storage/2018-05-10 copying build/lib/botocore/data/kinesis-video-webrtc-storage/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesis-video-webrtc-storage/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/kinesis creating build/bdist.linux-aarch64/wheel/botocore/data/kinesis/2013-12-02 copying build/lib/botocore/data/kinesis/2013-12-02/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesis/2013-12-02 copying build/lib/botocore/data/kinesis/2013-12-02/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesis/2013-12-02 copying build/lib/botocore/data/kinesis/2013-12-02/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesis/2013-12-02 copying build/lib/botocore/data/kinesis/2013-12-02/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesis/2013-12-02 copying build/lib/botocore/data/kinesis/2013-12-02/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesis/2013-12-02 creating build/bdist.linux-aarch64/wheel/botocore/data/kinesisanalytics creating build/bdist.linux-aarch64/wheel/botocore/data/kinesisanalytics/2015-08-14 copying build/lib/botocore/data/kinesisanalytics/2015-08-14/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesisanalytics/2015-08-14 copying build/lib/botocore/data/kinesisanalytics/2015-08-14/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesisanalytics/2015-08-14 copying build/lib/botocore/data/kinesisanalytics/2015-08-14/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesisanalytics/2015-08-14 copying build/lib/botocore/data/kinesisanalytics/2015-08-14/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesisanalytics/2015-08-14 creating build/bdist.linux-aarch64/wheel/botocore/data/kinesisanalyticsv2 creating build/bdist.linux-aarch64/wheel/botocore/data/kinesisanalyticsv2/2018-05-23 copying build/lib/botocore/data/kinesisanalyticsv2/2018-05-23/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesisanalyticsv2/2018-05-23 copying build/lib/botocore/data/kinesisanalyticsv2/2018-05-23/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesisanalyticsv2/2018-05-23 copying build/lib/botocore/data/kinesisanalyticsv2/2018-05-23/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesisanalyticsv2/2018-05-23 copying build/lib/botocore/data/kinesisanalyticsv2/2018-05-23/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesisanalyticsv2/2018-05-23 creating build/bdist.linux-aarch64/wheel/botocore/data/kinesisvideo creating build/bdist.linux-aarch64/wheel/botocore/data/kinesisvideo/2017-09-30 copying build/lib/botocore/data/kinesisvideo/2017-09-30/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesisvideo/2017-09-30 copying build/lib/botocore/data/kinesisvideo/2017-09-30/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesisvideo/2017-09-30 copying build/lib/botocore/data/kinesisvideo/2017-09-30/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesisvideo/2017-09-30 copying build/lib/botocore/data/kinesisvideo/2017-09-30/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/kinesisvideo/2017-09-30 creating build/bdist.linux-aarch64/wheel/botocore/data/kms creating build/bdist.linux-aarch64/wheel/botocore/data/kms/2014-11-01 copying build/lib/botocore/data/kms/2014-11-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kms/2014-11-01 copying build/lib/botocore/data/kms/2014-11-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kms/2014-11-01 copying build/lib/botocore/data/kms/2014-11-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/kms/2014-11-01 copying build/lib/botocore/data/kms/2014-11-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/kms/2014-11-01 creating build/bdist.linux-aarch64/wheel/botocore/data/lakeformation creating build/bdist.linux-aarch64/wheel/botocore/data/lakeformation/2017-03-31 copying build/lib/botocore/data/lakeformation/2017-03-31/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/lakeformation/2017-03-31 copying build/lib/botocore/data/lakeformation/2017-03-31/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/lakeformation/2017-03-31 copying build/lib/botocore/data/lakeformation/2017-03-31/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/lakeformation/2017-03-31 copying build/lib/botocore/data/lakeformation/2017-03-31/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/lakeformation/2017-03-31 copying build/lib/botocore/data/lakeformation/2017-03-31/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/lakeformation/2017-03-31 creating build/bdist.linux-aarch64/wheel/botocore/data/lambda creating build/bdist.linux-aarch64/wheel/botocore/data/lambda/2014-11-11 copying build/lib/botocore/data/lambda/2014-11-11/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/lambda/2014-11-11 copying build/lib/botocore/data/lambda/2014-11-11/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/lambda/2014-11-11 creating build/bdist.linux-aarch64/wheel/botocore/data/lambda/2015-03-31 copying build/lib/botocore/data/lambda/2015-03-31/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/lambda/2015-03-31 copying build/lib/botocore/data/lambda/2015-03-31/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/lambda/2015-03-31 copying build/lib/botocore/data/lambda/2015-03-31/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/lambda/2015-03-31 copying build/lib/botocore/data/lambda/2015-03-31/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/lambda/2015-03-31 copying build/lib/botocore/data/lambda/2015-03-31/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/lambda/2015-03-31 copying build/lib/botocore/data/lambda/2015-03-31/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/lambda/2015-03-31 creating build/bdist.linux-aarch64/wheel/botocore/data/launch-wizard creating build/bdist.linux-aarch64/wheel/botocore/data/launch-wizard/2018-05-10 copying build/lib/botocore/data/launch-wizard/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/launch-wizard/2018-05-10 copying build/lib/botocore/data/launch-wizard/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/launch-wizard/2018-05-10 copying build/lib/botocore/data/launch-wizard/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/launch-wizard/2018-05-10 copying build/lib/botocore/data/launch-wizard/2018-05-10/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/launch-wizard/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/lex-models creating build/bdist.linux-aarch64/wheel/botocore/data/lex-models/2017-04-19 copying build/lib/botocore/data/lex-models/2017-04-19/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/lex-models/2017-04-19 copying build/lib/botocore/data/lex-models/2017-04-19/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/lex-models/2017-04-19 copying build/lib/botocore/data/lex-models/2017-04-19/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/lex-models/2017-04-19 copying build/lib/botocore/data/lex-models/2017-04-19/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/lex-models/2017-04-19 creating build/bdist.linux-aarch64/wheel/botocore/data/lex-runtime creating build/bdist.linux-aarch64/wheel/botocore/data/lex-runtime/2016-11-28 copying build/lib/botocore/data/lex-runtime/2016-11-28/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/lex-runtime/2016-11-28 copying build/lib/botocore/data/lex-runtime/2016-11-28/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/lex-runtime/2016-11-28 copying build/lib/botocore/data/lex-runtime/2016-11-28/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/lex-runtime/2016-11-28 copying build/lib/botocore/data/lex-runtime/2016-11-28/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/lex-runtime/2016-11-28 creating build/bdist.linux-aarch64/wheel/botocore/data/lexv2-models creating build/bdist.linux-aarch64/wheel/botocore/data/lexv2-models/2020-08-07 copying build/lib/botocore/data/lexv2-models/2020-08-07/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/lexv2-models/2020-08-07 copying build/lib/botocore/data/lexv2-models/2020-08-07/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/lexv2-models/2020-08-07 copying build/lib/botocore/data/lexv2-models/2020-08-07/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/lexv2-models/2020-08-07 copying build/lib/botocore/data/lexv2-models/2020-08-07/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/lexv2-models/2020-08-07 copying build/lib/botocore/data/lexv2-models/2020-08-07/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/lexv2-models/2020-08-07 creating build/bdist.linux-aarch64/wheel/botocore/data/lexv2-runtime creating build/bdist.linux-aarch64/wheel/botocore/data/lexv2-runtime/2020-08-07 copying build/lib/botocore/data/lexv2-runtime/2020-08-07/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/lexv2-runtime/2020-08-07 copying build/lib/botocore/data/lexv2-runtime/2020-08-07/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/lexv2-runtime/2020-08-07 copying build/lib/botocore/data/lexv2-runtime/2020-08-07/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/lexv2-runtime/2020-08-07 copying build/lib/botocore/data/lexv2-runtime/2020-08-07/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/lexv2-runtime/2020-08-07 creating build/bdist.linux-aarch64/wheel/botocore/data/license-manager-linux-subscriptions creating build/bdist.linux-aarch64/wheel/botocore/data/license-manager-linux-subscriptions/2018-05-10 copying build/lib/botocore/data/license-manager-linux-subscriptions/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/license-manager-linux-subscriptions/2018-05-10 copying build/lib/botocore/data/license-manager-linux-subscriptions/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/license-manager-linux-subscriptions/2018-05-10 copying build/lib/botocore/data/license-manager-linux-subscriptions/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/license-manager-linux-subscriptions/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/license-manager-user-subscriptions creating build/bdist.linux-aarch64/wheel/botocore/data/license-manager-user-subscriptions/2018-05-10 copying build/lib/botocore/data/license-manager-user-subscriptions/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/license-manager-user-subscriptions/2018-05-10 copying build/lib/botocore/data/license-manager-user-subscriptions/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/license-manager-user-subscriptions/2018-05-10 copying build/lib/botocore/data/license-manager-user-subscriptions/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/license-manager-user-subscriptions/2018-05-10 copying build/lib/botocore/data/license-manager-user-subscriptions/2018-05-10/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/license-manager-user-subscriptions/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/license-manager creating build/bdist.linux-aarch64/wheel/botocore/data/license-manager/2018-08-01 copying build/lib/botocore/data/license-manager/2018-08-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/license-manager/2018-08-01 copying build/lib/botocore/data/license-manager/2018-08-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/license-manager/2018-08-01 copying build/lib/botocore/data/license-manager/2018-08-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/license-manager/2018-08-01 copying build/lib/botocore/data/license-manager/2018-08-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/license-manager/2018-08-01 creating build/bdist.linux-aarch64/wheel/botocore/data/lightsail creating build/bdist.linux-aarch64/wheel/botocore/data/lightsail/2016-11-28 copying build/lib/botocore/data/lightsail/2016-11-28/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/lightsail/2016-11-28 copying build/lib/botocore/data/lightsail/2016-11-28/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/lightsail/2016-11-28 copying build/lib/botocore/data/lightsail/2016-11-28/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/lightsail/2016-11-28 copying build/lib/botocore/data/lightsail/2016-11-28/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/lightsail/2016-11-28 creating build/bdist.linux-aarch64/wheel/botocore/data/location creating build/bdist.linux-aarch64/wheel/botocore/data/location/2020-11-19 copying build/lib/botocore/data/location/2020-11-19/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/location/2020-11-19 copying build/lib/botocore/data/location/2020-11-19/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/location/2020-11-19 copying build/lib/botocore/data/location/2020-11-19/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/location/2020-11-19 copying build/lib/botocore/data/location/2020-11-19/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/location/2020-11-19 copying build/lib/botocore/data/location/2020-11-19/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/location/2020-11-19 copying build/lib/botocore/data/location/2020-11-19/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/location/2020-11-19 creating build/bdist.linux-aarch64/wheel/botocore/data/logs creating build/bdist.linux-aarch64/wheel/botocore/data/logs/2014-03-28 copying build/lib/botocore/data/logs/2014-03-28/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/logs/2014-03-28 copying build/lib/botocore/data/logs/2014-03-28/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/logs/2014-03-28 copying build/lib/botocore/data/logs/2014-03-28/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/logs/2014-03-28 copying build/lib/botocore/data/logs/2014-03-28/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/logs/2014-03-28 copying build/lib/botocore/data/logs/2014-03-28/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/logs/2014-03-28 creating build/bdist.linux-aarch64/wheel/botocore/data/lookoutequipment creating build/bdist.linux-aarch64/wheel/botocore/data/lookoutequipment/2020-12-15 copying build/lib/botocore/data/lookoutequipment/2020-12-15/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/lookoutequipment/2020-12-15 copying build/lib/botocore/data/lookoutequipment/2020-12-15/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/lookoutequipment/2020-12-15 copying build/lib/botocore/data/lookoutequipment/2020-12-15/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/lookoutequipment/2020-12-15 copying build/lib/botocore/data/lookoutequipment/2020-12-15/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/lookoutequipment/2020-12-15 creating build/bdist.linux-aarch64/wheel/botocore/data/m2 creating build/bdist.linux-aarch64/wheel/botocore/data/m2/2021-04-28 copying build/lib/botocore/data/m2/2021-04-28/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/m2/2021-04-28 copying build/lib/botocore/data/m2/2021-04-28/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/m2/2021-04-28 copying build/lib/botocore/data/m2/2021-04-28/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/m2/2021-04-28 creating build/bdist.linux-aarch64/wheel/botocore/data/machinelearning creating build/bdist.linux-aarch64/wheel/botocore/data/machinelearning/2014-12-12 copying build/lib/botocore/data/machinelearning/2014-12-12/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/machinelearning/2014-12-12 copying build/lib/botocore/data/machinelearning/2014-12-12/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/machinelearning/2014-12-12 copying build/lib/botocore/data/machinelearning/2014-12-12/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/machinelearning/2014-12-12 copying build/lib/botocore/data/machinelearning/2014-12-12/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/machinelearning/2014-12-12 copying build/lib/botocore/data/machinelearning/2014-12-12/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/machinelearning/2014-12-12 creating build/bdist.linux-aarch64/wheel/botocore/data/macie2 creating build/bdist.linux-aarch64/wheel/botocore/data/macie2/2020-01-01 copying build/lib/botocore/data/macie2/2020-01-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/macie2/2020-01-01 copying build/lib/botocore/data/macie2/2020-01-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/macie2/2020-01-01 copying build/lib/botocore/data/macie2/2020-01-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/macie2/2020-01-01 copying build/lib/botocore/data/macie2/2020-01-01/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/macie2/2020-01-01 creating build/bdist.linux-aarch64/wheel/botocore/data/mailmanager creating build/bdist.linux-aarch64/wheel/botocore/data/mailmanager/2023-10-17 copying build/lib/botocore/data/mailmanager/2023-10-17/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mailmanager/2023-10-17 copying build/lib/botocore/data/mailmanager/2023-10-17/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mailmanager/2023-10-17 copying build/lib/botocore/data/mailmanager/2023-10-17/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/mailmanager/2023-10-17 copying build/lib/botocore/data/mailmanager/2023-10-17/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/mailmanager/2023-10-17 creating build/bdist.linux-aarch64/wheel/botocore/data/managedblockchain-query creating build/bdist.linux-aarch64/wheel/botocore/data/managedblockchain-query/2023-05-04 copying build/lib/botocore/data/managedblockchain-query/2023-05-04/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/managedblockchain-query/2023-05-04 copying build/lib/botocore/data/managedblockchain-query/2023-05-04/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/managedblockchain-query/2023-05-04 copying build/lib/botocore/data/managedblockchain-query/2023-05-04/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/managedblockchain-query/2023-05-04 copying build/lib/botocore/data/managedblockchain-query/2023-05-04/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/managedblockchain-query/2023-05-04 creating build/bdist.linux-aarch64/wheel/botocore/data/managedblockchain creating build/bdist.linux-aarch64/wheel/botocore/data/managedblockchain/2018-09-24 copying build/lib/botocore/data/managedblockchain/2018-09-24/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/managedblockchain/2018-09-24 copying build/lib/botocore/data/managedblockchain/2018-09-24/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/managedblockchain/2018-09-24 copying build/lib/botocore/data/managedblockchain/2018-09-24/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/managedblockchain/2018-09-24 copying build/lib/botocore/data/managedblockchain/2018-09-24/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/managedblockchain/2018-09-24 creating build/bdist.linux-aarch64/wheel/botocore/data/marketplace-agreement creating build/bdist.linux-aarch64/wheel/botocore/data/marketplace-agreement/2020-03-01 copying build/lib/botocore/data/marketplace-agreement/2020-03-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/marketplace-agreement/2020-03-01 copying build/lib/botocore/data/marketplace-agreement/2020-03-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/marketplace-agreement/2020-03-01 copying build/lib/botocore/data/marketplace-agreement/2020-03-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/marketplace-agreement/2020-03-01 copying build/lib/botocore/data/marketplace-agreement/2020-03-01/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/marketplace-agreement/2020-03-01 creating build/bdist.linux-aarch64/wheel/botocore/data/marketplace-catalog creating build/bdist.linux-aarch64/wheel/botocore/data/marketplace-catalog/2018-09-17 copying build/lib/botocore/data/marketplace-catalog/2018-09-17/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/marketplace-catalog/2018-09-17 copying build/lib/botocore/data/marketplace-catalog/2018-09-17/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/marketplace-catalog/2018-09-17 copying build/lib/botocore/data/marketplace-catalog/2018-09-17/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/marketplace-catalog/2018-09-17 copying build/lib/botocore/data/marketplace-catalog/2018-09-17/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/marketplace-catalog/2018-09-17 creating build/bdist.linux-aarch64/wheel/botocore/data/marketplace-deployment creating build/bdist.linux-aarch64/wheel/botocore/data/marketplace-deployment/2023-01-25 copying build/lib/botocore/data/marketplace-deployment/2023-01-25/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/marketplace-deployment/2023-01-25 copying build/lib/botocore/data/marketplace-deployment/2023-01-25/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/marketplace-deployment/2023-01-25 copying build/lib/botocore/data/marketplace-deployment/2023-01-25/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/marketplace-deployment/2023-01-25 creating build/bdist.linux-aarch64/wheel/botocore/data/marketplace-discovery creating build/bdist.linux-aarch64/wheel/botocore/data/marketplace-discovery/2026-02-05 copying build/lib/botocore/data/marketplace-discovery/2026-02-05/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/marketplace-discovery/2026-02-05 copying build/lib/botocore/data/marketplace-discovery/2026-02-05/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/marketplace-discovery/2026-02-05 copying build/lib/botocore/data/marketplace-discovery/2026-02-05/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/marketplace-discovery/2026-02-05 copying build/lib/botocore/data/marketplace-discovery/2026-02-05/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/marketplace-discovery/2026-02-05 copying build/lib/botocore/data/marketplace-discovery/2026-02-05/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/marketplace-discovery/2026-02-05 creating build/bdist.linux-aarch64/wheel/botocore/data/marketplace-entitlement creating build/bdist.linux-aarch64/wheel/botocore/data/marketplace-entitlement/2017-01-11 copying build/lib/botocore/data/marketplace-entitlement/2017-01-11/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/marketplace-entitlement/2017-01-11 copying build/lib/botocore/data/marketplace-entitlement/2017-01-11/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/marketplace-entitlement/2017-01-11 copying build/lib/botocore/data/marketplace-entitlement/2017-01-11/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/marketplace-entitlement/2017-01-11 copying build/lib/botocore/data/marketplace-entitlement/2017-01-11/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/marketplace-entitlement/2017-01-11 creating build/bdist.linux-aarch64/wheel/botocore/data/marketplace-reporting creating build/bdist.linux-aarch64/wheel/botocore/data/marketplace-reporting/2018-05-10 copying build/lib/botocore/data/marketplace-reporting/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/marketplace-reporting/2018-05-10 copying build/lib/botocore/data/marketplace-reporting/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/marketplace-reporting/2018-05-10 copying build/lib/botocore/data/marketplace-reporting/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/marketplace-reporting/2018-05-10 copying build/lib/botocore/data/marketplace-reporting/2018-05-10/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/marketplace-reporting/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/marketplacecommerceanalytics creating build/bdist.linux-aarch64/wheel/botocore/data/marketplacecommerceanalytics/2015-07-01 copying build/lib/botocore/data/marketplacecommerceanalytics/2015-07-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/marketplacecommerceanalytics/2015-07-01 copying build/lib/botocore/data/marketplacecommerceanalytics/2015-07-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/marketplacecommerceanalytics/2015-07-01 copying build/lib/botocore/data/marketplacecommerceanalytics/2015-07-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/marketplacecommerceanalytics/2015-07-01 copying build/lib/botocore/data/marketplacecommerceanalytics/2015-07-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/marketplacecommerceanalytics/2015-07-01 creating build/bdist.linux-aarch64/wheel/botocore/data/mediaconnect creating build/bdist.linux-aarch64/wheel/botocore/data/mediaconnect/2018-11-14 copying build/lib/botocore/data/mediaconnect/2018-11-14/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mediaconnect/2018-11-14 copying build/lib/botocore/data/mediaconnect/2018-11-14/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mediaconnect/2018-11-14 copying build/lib/botocore/data/mediaconnect/2018-11-14/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/mediaconnect/2018-11-14 copying build/lib/botocore/data/mediaconnect/2018-11-14/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/mediaconnect/2018-11-14 creating build/bdist.linux-aarch64/wheel/botocore/data/mediaconvert creating build/bdist.linux-aarch64/wheel/botocore/data/mediaconvert/2017-08-29 copying build/lib/botocore/data/mediaconvert/2017-08-29/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mediaconvert/2017-08-29 copying build/lib/botocore/data/mediaconvert/2017-08-29/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mediaconvert/2017-08-29 copying build/lib/botocore/data/mediaconvert/2017-08-29/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/mediaconvert/2017-08-29 copying build/lib/botocore/data/mediaconvert/2017-08-29/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/mediaconvert/2017-08-29 creating build/bdist.linux-aarch64/wheel/botocore/data/medialive creating build/bdist.linux-aarch64/wheel/botocore/data/medialive/2017-10-14 copying build/lib/botocore/data/medialive/2017-10-14/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/medialive/2017-10-14 copying build/lib/botocore/data/medialive/2017-10-14/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/medialive/2017-10-14 copying build/lib/botocore/data/medialive/2017-10-14/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/medialive/2017-10-14 copying build/lib/botocore/data/medialive/2017-10-14/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/medialive/2017-10-14 creating build/bdist.linux-aarch64/wheel/botocore/data/mediapackage-vod creating build/bdist.linux-aarch64/wheel/botocore/data/mediapackage-vod/2018-11-07 copying build/lib/botocore/data/mediapackage-vod/2018-11-07/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mediapackage-vod/2018-11-07 copying build/lib/botocore/data/mediapackage-vod/2018-11-07/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mediapackage-vod/2018-11-07 copying build/lib/botocore/data/mediapackage-vod/2018-11-07/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/mediapackage-vod/2018-11-07 creating build/bdist.linux-aarch64/wheel/botocore/data/mediapackage creating build/bdist.linux-aarch64/wheel/botocore/data/mediapackage/2017-10-12 copying build/lib/botocore/data/mediapackage/2017-10-12/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mediapackage/2017-10-12 copying build/lib/botocore/data/mediapackage/2017-10-12/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mediapackage/2017-10-12 copying build/lib/botocore/data/mediapackage/2017-10-12/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/mediapackage/2017-10-12 creating build/bdist.linux-aarch64/wheel/botocore/data/mediapackagev2 creating build/bdist.linux-aarch64/wheel/botocore/data/mediapackagev2/2022-12-25 copying build/lib/botocore/data/mediapackagev2/2022-12-25/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mediapackagev2/2022-12-25 copying build/lib/botocore/data/mediapackagev2/2022-12-25/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mediapackagev2/2022-12-25 copying build/lib/botocore/data/mediapackagev2/2022-12-25/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/mediapackagev2/2022-12-25 copying build/lib/botocore/data/mediapackagev2/2022-12-25/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/mediapackagev2/2022-12-25 creating build/bdist.linux-aarch64/wheel/botocore/data/mediastore-data creating build/bdist.linux-aarch64/wheel/botocore/data/mediastore-data/2017-09-01 copying build/lib/botocore/data/mediastore-data/2017-09-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mediastore-data/2017-09-01 copying build/lib/botocore/data/mediastore-data/2017-09-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mediastore-data/2017-09-01 copying build/lib/botocore/data/mediastore-data/2017-09-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mediastore-data/2017-09-01 copying build/lib/botocore/data/mediastore-data/2017-09-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/mediastore-data/2017-09-01 creating build/bdist.linux-aarch64/wheel/botocore/data/mediastore creating build/bdist.linux-aarch64/wheel/botocore/data/mediastore/2017-09-01 copying build/lib/botocore/data/mediastore/2017-09-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mediastore/2017-09-01 copying build/lib/botocore/data/mediastore/2017-09-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mediastore/2017-09-01 copying build/lib/botocore/data/mediastore/2017-09-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mediastore/2017-09-01 copying build/lib/botocore/data/mediastore/2017-09-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/mediastore/2017-09-01 creating build/bdist.linux-aarch64/wheel/botocore/data/mediatailor creating build/bdist.linux-aarch64/wheel/botocore/data/mediatailor/2018-04-23 copying build/lib/botocore/data/mediatailor/2018-04-23/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mediatailor/2018-04-23 copying build/lib/botocore/data/mediatailor/2018-04-23/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mediatailor/2018-04-23 copying build/lib/botocore/data/mediatailor/2018-04-23/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/mediatailor/2018-04-23 creating build/bdist.linux-aarch64/wheel/botocore/data/medical-imaging creating build/bdist.linux-aarch64/wheel/botocore/data/medical-imaging/2023-07-19 copying build/lib/botocore/data/medical-imaging/2023-07-19/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/medical-imaging/2023-07-19 copying build/lib/botocore/data/medical-imaging/2023-07-19/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/medical-imaging/2023-07-19 copying build/lib/botocore/data/medical-imaging/2023-07-19/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/medical-imaging/2023-07-19 copying build/lib/botocore/data/medical-imaging/2023-07-19/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/medical-imaging/2023-07-19 copying build/lib/botocore/data/medical-imaging/2023-07-19/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/medical-imaging/2023-07-19 creating build/bdist.linux-aarch64/wheel/botocore/data/memorydb creating build/bdist.linux-aarch64/wheel/botocore/data/memorydb/2021-01-01 copying build/lib/botocore/data/memorydb/2021-01-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/memorydb/2021-01-01 copying build/lib/botocore/data/memorydb/2021-01-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/memorydb/2021-01-01 copying build/lib/botocore/data/memorydb/2021-01-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/memorydb/2021-01-01 copying build/lib/botocore/data/memorydb/2021-01-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/memorydb/2021-01-01 creating build/bdist.linux-aarch64/wheel/botocore/data/meteringmarketplace creating build/bdist.linux-aarch64/wheel/botocore/data/meteringmarketplace/2016-01-14 copying build/lib/botocore/data/meteringmarketplace/2016-01-14/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/meteringmarketplace/2016-01-14 copying build/lib/botocore/data/meteringmarketplace/2016-01-14/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/meteringmarketplace/2016-01-14 copying build/lib/botocore/data/meteringmarketplace/2016-01-14/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/meteringmarketplace/2016-01-14 copying build/lib/botocore/data/meteringmarketplace/2016-01-14/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/meteringmarketplace/2016-01-14 creating build/bdist.linux-aarch64/wheel/botocore/data/mgh creating build/bdist.linux-aarch64/wheel/botocore/data/mgh/2017-05-31 copying build/lib/botocore/data/mgh/2017-05-31/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mgh/2017-05-31 copying build/lib/botocore/data/mgh/2017-05-31/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mgh/2017-05-31 copying build/lib/botocore/data/mgh/2017-05-31/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mgh/2017-05-31 copying build/lib/botocore/data/mgh/2017-05-31/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/mgh/2017-05-31 creating build/bdist.linux-aarch64/wheel/botocore/data/mgn creating build/bdist.linux-aarch64/wheel/botocore/data/mgn/2020-02-26 copying build/lib/botocore/data/mgn/2020-02-26/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mgn/2020-02-26 copying build/lib/botocore/data/mgn/2020-02-26/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mgn/2020-02-26 copying build/lib/botocore/data/mgn/2020-02-26/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mgn/2020-02-26 copying build/lib/botocore/data/mgn/2020-02-26/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/mgn/2020-02-26 copying build/lib/botocore/data/mgn/2020-02-26/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/mgn/2020-02-26 creating build/bdist.linux-aarch64/wheel/botocore/data/migration-hub-refactor-spaces creating build/bdist.linux-aarch64/wheel/botocore/data/migration-hub-refactor-spaces/2021-10-26 copying build/lib/botocore/data/migration-hub-refactor-spaces/2021-10-26/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/migration-hub-refactor-spaces/2021-10-26 copying build/lib/botocore/data/migration-hub-refactor-spaces/2021-10-26/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/migration-hub-refactor-spaces/2021-10-26 copying build/lib/botocore/data/migration-hub-refactor-spaces/2021-10-26/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/migration-hub-refactor-spaces/2021-10-26 copying build/lib/botocore/data/migration-hub-refactor-spaces/2021-10-26/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/migration-hub-refactor-spaces/2021-10-26 creating build/bdist.linux-aarch64/wheel/botocore/data/migrationhub-config creating build/bdist.linux-aarch64/wheel/botocore/data/migrationhub-config/2019-06-30 copying build/lib/botocore/data/migrationhub-config/2019-06-30/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/migrationhub-config/2019-06-30 copying build/lib/botocore/data/migrationhub-config/2019-06-30/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/migrationhub-config/2019-06-30 copying build/lib/botocore/data/migrationhub-config/2019-06-30/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/migrationhub-config/2019-06-30 copying build/lib/botocore/data/migrationhub-config/2019-06-30/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/migrationhub-config/2019-06-30 creating build/bdist.linux-aarch64/wheel/botocore/data/migrationhuborchestrator creating build/bdist.linux-aarch64/wheel/botocore/data/migrationhuborchestrator/2021-08-28 copying build/lib/botocore/data/migrationhuborchestrator/2021-08-28/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/migrationhuborchestrator/2021-08-28 copying build/lib/botocore/data/migrationhuborchestrator/2021-08-28/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/migrationhuborchestrator/2021-08-28 copying build/lib/botocore/data/migrationhuborchestrator/2021-08-28/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/migrationhuborchestrator/2021-08-28 copying build/lib/botocore/data/migrationhuborchestrator/2021-08-28/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/migrationhuborchestrator/2021-08-28 creating build/bdist.linux-aarch64/wheel/botocore/data/migrationhubstrategy creating build/bdist.linux-aarch64/wheel/botocore/data/migrationhubstrategy/2020-02-19 copying build/lib/botocore/data/migrationhubstrategy/2020-02-19/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/migrationhubstrategy/2020-02-19 copying build/lib/botocore/data/migrationhubstrategy/2020-02-19/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/migrationhubstrategy/2020-02-19 copying build/lib/botocore/data/migrationhubstrategy/2020-02-19/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/migrationhubstrategy/2020-02-19 copying build/lib/botocore/data/migrationhubstrategy/2020-02-19/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/migrationhubstrategy/2020-02-19 copying build/lib/botocore/data/migrationhubstrategy/2020-02-19/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/migrationhubstrategy/2020-02-19 creating build/bdist.linux-aarch64/wheel/botocore/data/mpa creating build/bdist.linux-aarch64/wheel/botocore/data/mpa/2022-07-26 copying build/lib/botocore/data/mpa/2022-07-26/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mpa/2022-07-26 copying build/lib/botocore/data/mpa/2022-07-26/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mpa/2022-07-26 copying build/lib/botocore/data/mpa/2022-07-26/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/mpa/2022-07-26 copying build/lib/botocore/data/mpa/2022-07-26/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/mpa/2022-07-26 creating build/bdist.linux-aarch64/wheel/botocore/data/mq creating build/bdist.linux-aarch64/wheel/botocore/data/mq/2017-11-27 copying build/lib/botocore/data/mq/2017-11-27/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mq/2017-11-27 copying build/lib/botocore/data/mq/2017-11-27/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mq/2017-11-27 copying build/lib/botocore/data/mq/2017-11-27/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/mq/2017-11-27 creating build/bdist.linux-aarch64/wheel/botocore/data/mturk creating build/bdist.linux-aarch64/wheel/botocore/data/mturk/2017-01-17 copying build/lib/botocore/data/mturk/2017-01-17/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mturk/2017-01-17 copying build/lib/botocore/data/mturk/2017-01-17/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mturk/2017-01-17 copying build/lib/botocore/data/mturk/2017-01-17/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mturk/2017-01-17 copying build/lib/botocore/data/mturk/2017-01-17/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/mturk/2017-01-17 creating build/bdist.linux-aarch64/wheel/botocore/data/mwaa-serverless creating build/bdist.linux-aarch64/wheel/botocore/data/mwaa-serverless/2024-07-26 copying build/lib/botocore/data/mwaa-serverless/2024-07-26/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mwaa-serverless/2024-07-26 copying build/lib/botocore/data/mwaa-serverless/2024-07-26/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mwaa-serverless/2024-07-26 copying build/lib/botocore/data/mwaa-serverless/2024-07-26/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/mwaa-serverless/2024-07-26 copying build/lib/botocore/data/mwaa-serverless/2024-07-26/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/mwaa-serverless/2024-07-26 creating build/bdist.linux-aarch64/wheel/botocore/data/mwaa creating build/bdist.linux-aarch64/wheel/botocore/data/mwaa/2020-07-01 copying build/lib/botocore/data/mwaa/2020-07-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mwaa/2020-07-01 copying build/lib/botocore/data/mwaa/2020-07-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mwaa/2020-07-01 copying build/lib/botocore/data/mwaa/2020-07-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/mwaa/2020-07-01 copying build/lib/botocore/data/mwaa/2020-07-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/mwaa/2020-07-01 creating build/bdist.linux-aarch64/wheel/botocore/data/neptune-graph creating build/bdist.linux-aarch64/wheel/botocore/data/neptune-graph/2023-11-29 copying build/lib/botocore/data/neptune-graph/2023-11-29/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/neptune-graph/2023-11-29 copying build/lib/botocore/data/neptune-graph/2023-11-29/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/neptune-graph/2023-11-29 copying build/lib/botocore/data/neptune-graph/2023-11-29/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/neptune-graph/2023-11-29 copying build/lib/botocore/data/neptune-graph/2023-11-29/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/neptune-graph/2023-11-29 creating build/bdist.linux-aarch64/wheel/botocore/data/neptune creating build/bdist.linux-aarch64/wheel/botocore/data/neptune/2014-10-31 copying build/lib/botocore/data/neptune/2014-10-31/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/neptune/2014-10-31 copying build/lib/botocore/data/neptune/2014-10-31/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/neptune/2014-10-31 copying build/lib/botocore/data/neptune/2014-10-31/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/neptune/2014-10-31 copying build/lib/botocore/data/neptune/2014-10-31/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/neptune/2014-10-31 copying build/lib/botocore/data/neptune/2014-10-31/service-2.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/neptune/2014-10-31 copying build/lib/botocore/data/neptune/2014-10-31/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/neptune/2014-10-31 creating build/bdist.linux-aarch64/wheel/botocore/data/neptunedata creating build/bdist.linux-aarch64/wheel/botocore/data/neptunedata/2023-08-01 copying build/lib/botocore/data/neptunedata/2023-08-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/neptunedata/2023-08-01 copying build/lib/botocore/data/neptunedata/2023-08-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/neptunedata/2023-08-01 copying build/lib/botocore/data/neptunedata/2023-08-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/neptunedata/2023-08-01 creating build/bdist.linux-aarch64/wheel/botocore/data/network-firewall creating build/bdist.linux-aarch64/wheel/botocore/data/network-firewall/2020-11-12 copying build/lib/botocore/data/network-firewall/2020-11-12/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/network-firewall/2020-11-12 copying build/lib/botocore/data/network-firewall/2020-11-12/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/network-firewall/2020-11-12 copying build/lib/botocore/data/network-firewall/2020-11-12/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/network-firewall/2020-11-12 copying build/lib/botocore/data/network-firewall/2020-11-12/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/network-firewall/2020-11-12 copying build/lib/botocore/data/network-firewall/2020-11-12/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/network-firewall/2020-11-12 creating build/bdist.linux-aarch64/wheel/botocore/data/networkflowmonitor creating build/bdist.linux-aarch64/wheel/botocore/data/networkflowmonitor/2023-04-19 copying build/lib/botocore/data/networkflowmonitor/2023-04-19/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/networkflowmonitor/2023-04-19 copying build/lib/botocore/data/networkflowmonitor/2023-04-19/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/networkflowmonitor/2023-04-19 copying build/lib/botocore/data/networkflowmonitor/2023-04-19/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/networkflowmonitor/2023-04-19 copying build/lib/botocore/data/networkflowmonitor/2023-04-19/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/networkflowmonitor/2023-04-19 copying build/lib/botocore/data/networkflowmonitor/2023-04-19/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/networkflowmonitor/2023-04-19 creating build/bdist.linux-aarch64/wheel/botocore/data/networkmanager creating build/bdist.linux-aarch64/wheel/botocore/data/networkmanager/2019-07-05 copying build/lib/botocore/data/networkmanager/2019-07-05/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/networkmanager/2019-07-05 copying build/lib/botocore/data/networkmanager/2019-07-05/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/networkmanager/2019-07-05 copying build/lib/botocore/data/networkmanager/2019-07-05/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/networkmanager/2019-07-05 copying build/lib/botocore/data/networkmanager/2019-07-05/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/networkmanager/2019-07-05 creating build/bdist.linux-aarch64/wheel/botocore/data/networkmonitor creating build/bdist.linux-aarch64/wheel/botocore/data/networkmonitor/2023-08-01 copying build/lib/botocore/data/networkmonitor/2023-08-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/networkmonitor/2023-08-01 copying build/lib/botocore/data/networkmonitor/2023-08-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/networkmonitor/2023-08-01 copying build/lib/botocore/data/networkmonitor/2023-08-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/networkmonitor/2023-08-01 copying build/lib/botocore/data/networkmonitor/2023-08-01/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/networkmonitor/2023-08-01 creating build/bdist.linux-aarch64/wheel/botocore/data/notifications creating build/bdist.linux-aarch64/wheel/botocore/data/notifications/2018-05-10 copying build/lib/botocore/data/notifications/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/notifications/2018-05-10 copying build/lib/botocore/data/notifications/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/notifications/2018-05-10 copying build/lib/botocore/data/notifications/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/notifications/2018-05-10 copying build/lib/botocore/data/notifications/2018-05-10/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/notifications/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/notificationscontacts creating build/bdist.linux-aarch64/wheel/botocore/data/notificationscontacts/2018-05-10 copying build/lib/botocore/data/notificationscontacts/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/notificationscontacts/2018-05-10 copying build/lib/botocore/data/notificationscontacts/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/notificationscontacts/2018-05-10 copying build/lib/botocore/data/notificationscontacts/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/notificationscontacts/2018-05-10 copying build/lib/botocore/data/notificationscontacts/2018-05-10/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/notificationscontacts/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/nova-act creating build/bdist.linux-aarch64/wheel/botocore/data/nova-act/2025-08-22 copying build/lib/botocore/data/nova-act/2025-08-22/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/nova-act/2025-08-22 copying build/lib/botocore/data/nova-act/2025-08-22/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/nova-act/2025-08-22 copying build/lib/botocore/data/nova-act/2025-08-22/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/nova-act/2025-08-22 copying build/lib/botocore/data/nova-act/2025-08-22/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/nova-act/2025-08-22 creating build/bdist.linux-aarch64/wheel/botocore/data/oam creating build/bdist.linux-aarch64/wheel/botocore/data/oam/2022-06-10 copying build/lib/botocore/data/oam/2022-06-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/oam/2022-06-10 copying build/lib/botocore/data/oam/2022-06-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/oam/2022-06-10 copying build/lib/botocore/data/oam/2022-06-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/oam/2022-06-10 creating build/bdist.linux-aarch64/wheel/botocore/data/observabilityadmin creating build/bdist.linux-aarch64/wheel/botocore/data/observabilityadmin/2018-05-10 copying build/lib/botocore/data/observabilityadmin/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/observabilityadmin/2018-05-10 copying build/lib/botocore/data/observabilityadmin/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/observabilityadmin/2018-05-10 copying build/lib/botocore/data/observabilityadmin/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/observabilityadmin/2018-05-10 copying build/lib/botocore/data/observabilityadmin/2018-05-10/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/observabilityadmin/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/odb creating build/bdist.linux-aarch64/wheel/botocore/data/odb/2024-08-20 copying build/lib/botocore/data/odb/2024-08-20/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/odb/2024-08-20 copying build/lib/botocore/data/odb/2024-08-20/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/odb/2024-08-20 copying build/lib/botocore/data/odb/2024-08-20/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/odb/2024-08-20 copying build/lib/botocore/data/odb/2024-08-20/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/odb/2024-08-20 creating build/bdist.linux-aarch64/wheel/botocore/data/omics creating build/bdist.linux-aarch64/wheel/botocore/data/omics/2022-11-28 copying build/lib/botocore/data/omics/2022-11-28/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/omics/2022-11-28 copying build/lib/botocore/data/omics/2022-11-28/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/omics/2022-11-28 copying build/lib/botocore/data/omics/2022-11-28/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/omics/2022-11-28 copying build/lib/botocore/data/omics/2022-11-28/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/omics/2022-11-28 creating build/bdist.linux-aarch64/wheel/botocore/data/opensearch creating build/bdist.linux-aarch64/wheel/botocore/data/opensearch/2021-01-01 copying build/lib/botocore/data/opensearch/2021-01-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/opensearch/2021-01-01 copying build/lib/botocore/data/opensearch/2021-01-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/opensearch/2021-01-01 copying build/lib/botocore/data/opensearch/2021-01-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/opensearch/2021-01-01 copying build/lib/botocore/data/opensearch/2021-01-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/opensearch/2021-01-01 creating build/bdist.linux-aarch64/wheel/botocore/data/opensearchserverless creating build/bdist.linux-aarch64/wheel/botocore/data/opensearchserverless/2021-11-01 copying build/lib/botocore/data/opensearchserverless/2021-11-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/opensearchserverless/2021-11-01 copying build/lib/botocore/data/opensearchserverless/2021-11-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/opensearchserverless/2021-11-01 copying build/lib/botocore/data/opensearchserverless/2021-11-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/opensearchserverless/2021-11-01 copying build/lib/botocore/data/opensearchserverless/2021-11-01/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/opensearchserverless/2021-11-01 creating build/bdist.linux-aarch64/wheel/botocore/data/organizations creating build/bdist.linux-aarch64/wheel/botocore/data/organizations/2016-11-28 copying build/lib/botocore/data/organizations/2016-11-28/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/organizations/2016-11-28 copying build/lib/botocore/data/organizations/2016-11-28/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/organizations/2016-11-28 copying build/lib/botocore/data/organizations/2016-11-28/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/organizations/2016-11-28 copying build/lib/botocore/data/organizations/2016-11-28/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/organizations/2016-11-28 copying build/lib/botocore/data/organizations/2016-11-28/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/organizations/2016-11-28 creating build/bdist.linux-aarch64/wheel/botocore/data/osis creating build/bdist.linux-aarch64/wheel/botocore/data/osis/2022-01-01 copying build/lib/botocore/data/osis/2022-01-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/osis/2022-01-01 copying build/lib/botocore/data/osis/2022-01-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/osis/2022-01-01 copying build/lib/botocore/data/osis/2022-01-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/osis/2022-01-01 creating build/bdist.linux-aarch64/wheel/botocore/data/outposts creating build/bdist.linux-aarch64/wheel/botocore/data/outposts/2019-12-03 copying build/lib/botocore/data/outposts/2019-12-03/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/outposts/2019-12-03 copying build/lib/botocore/data/outposts/2019-12-03/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/outposts/2019-12-03 copying build/lib/botocore/data/outposts/2019-12-03/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/outposts/2019-12-03 copying build/lib/botocore/data/outposts/2019-12-03/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/outposts/2019-12-03 copying build/lib/botocore/data/outposts/2019-12-03/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/outposts/2019-12-03 creating build/bdist.linux-aarch64/wheel/botocore/data/panorama creating build/bdist.linux-aarch64/wheel/botocore/data/panorama/2019-07-24 copying build/lib/botocore/data/panorama/2019-07-24/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/panorama/2019-07-24 copying build/lib/botocore/data/panorama/2019-07-24/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/panorama/2019-07-24 copying build/lib/botocore/data/panorama/2019-07-24/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/panorama/2019-07-24 copying build/lib/botocore/data/panorama/2019-07-24/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/panorama/2019-07-24 creating build/bdist.linux-aarch64/wheel/botocore/data/partnercentral-account creating build/bdist.linux-aarch64/wheel/botocore/data/partnercentral-account/2025-04-04 copying build/lib/botocore/data/partnercentral-account/2025-04-04/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/partnercentral-account/2025-04-04 copying build/lib/botocore/data/partnercentral-account/2025-04-04/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/partnercentral-account/2025-04-04 copying build/lib/botocore/data/partnercentral-account/2025-04-04/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/partnercentral-account/2025-04-04 copying build/lib/botocore/data/partnercentral-account/2025-04-04/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/partnercentral-account/2025-04-04 creating build/bdist.linux-aarch64/wheel/botocore/data/partnercentral-benefits creating build/bdist.linux-aarch64/wheel/botocore/data/partnercentral-benefits/2018-05-10 copying build/lib/botocore/data/partnercentral-benefits/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/partnercentral-benefits/2018-05-10 copying build/lib/botocore/data/partnercentral-benefits/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/partnercentral-benefits/2018-05-10 copying build/lib/botocore/data/partnercentral-benefits/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/partnercentral-benefits/2018-05-10 copying build/lib/botocore/data/partnercentral-benefits/2018-05-10/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/partnercentral-benefits/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/partnercentral-channel creating build/bdist.linux-aarch64/wheel/botocore/data/partnercentral-channel/2024-03-18 copying build/lib/botocore/data/partnercentral-channel/2024-03-18/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/partnercentral-channel/2024-03-18 copying build/lib/botocore/data/partnercentral-channel/2024-03-18/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/partnercentral-channel/2024-03-18 copying build/lib/botocore/data/partnercentral-channel/2024-03-18/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/partnercentral-channel/2024-03-18 copying build/lib/botocore/data/partnercentral-channel/2024-03-18/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/partnercentral-channel/2024-03-18 creating build/bdist.linux-aarch64/wheel/botocore/data/partnercentral-selling creating build/bdist.linux-aarch64/wheel/botocore/data/partnercentral-selling/2022-07-26 copying build/lib/botocore/data/partnercentral-selling/2022-07-26/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/partnercentral-selling/2022-07-26 copying build/lib/botocore/data/partnercentral-selling/2022-07-26/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/partnercentral-selling/2022-07-26 copying build/lib/botocore/data/partnercentral-selling/2022-07-26/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/partnercentral-selling/2022-07-26 copying build/lib/botocore/data/partnercentral-selling/2022-07-26/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/partnercentral-selling/2022-07-26 creating build/bdist.linux-aarch64/wheel/botocore/data/payment-cryptography-data creating build/bdist.linux-aarch64/wheel/botocore/data/payment-cryptography-data/2022-02-03 copying build/lib/botocore/data/payment-cryptography-data/2022-02-03/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/payment-cryptography-data/2022-02-03 copying build/lib/botocore/data/payment-cryptography-data/2022-02-03/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/payment-cryptography-data/2022-02-03 copying build/lib/botocore/data/payment-cryptography-data/2022-02-03/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/payment-cryptography-data/2022-02-03 copying build/lib/botocore/data/payment-cryptography-data/2022-02-03/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/payment-cryptography-data/2022-02-03 creating build/bdist.linux-aarch64/wheel/botocore/data/payment-cryptography creating build/bdist.linux-aarch64/wheel/botocore/data/payment-cryptography/2021-09-14 copying build/lib/botocore/data/payment-cryptography/2021-09-14/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/payment-cryptography/2021-09-14 copying build/lib/botocore/data/payment-cryptography/2021-09-14/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/payment-cryptography/2021-09-14 copying build/lib/botocore/data/payment-cryptography/2021-09-14/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/payment-cryptography/2021-09-14 copying build/lib/botocore/data/payment-cryptography/2021-09-14/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/payment-cryptography/2021-09-14 creating build/bdist.linux-aarch64/wheel/botocore/data/pca-connector-ad creating build/bdist.linux-aarch64/wheel/botocore/data/pca-connector-ad/2018-05-10 copying build/lib/botocore/data/pca-connector-ad/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/pca-connector-ad/2018-05-10 copying build/lib/botocore/data/pca-connector-ad/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/pca-connector-ad/2018-05-10 copying build/lib/botocore/data/pca-connector-ad/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/pca-connector-ad/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/pca-connector-scep creating build/bdist.linux-aarch64/wheel/botocore/data/pca-connector-scep/2018-05-10 copying build/lib/botocore/data/pca-connector-scep/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/pca-connector-scep/2018-05-10 copying build/lib/botocore/data/pca-connector-scep/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/pca-connector-scep/2018-05-10 copying build/lib/botocore/data/pca-connector-scep/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/pca-connector-scep/2018-05-10 copying build/lib/botocore/data/pca-connector-scep/2018-05-10/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/pca-connector-scep/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/pcs creating build/bdist.linux-aarch64/wheel/botocore/data/pcs/2023-02-10 copying build/lib/botocore/data/pcs/2023-02-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/pcs/2023-02-10 copying build/lib/botocore/data/pcs/2023-02-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/pcs/2023-02-10 copying build/lib/botocore/data/pcs/2023-02-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/pcs/2023-02-10 copying build/lib/botocore/data/pcs/2023-02-10/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/pcs/2023-02-10 creating build/bdist.linux-aarch64/wheel/botocore/data/personalize-events creating build/bdist.linux-aarch64/wheel/botocore/data/personalize-events/2018-03-22 copying build/lib/botocore/data/personalize-events/2018-03-22/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/personalize-events/2018-03-22 copying build/lib/botocore/data/personalize-events/2018-03-22/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/personalize-events/2018-03-22 copying build/lib/botocore/data/personalize-events/2018-03-22/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/personalize-events/2018-03-22 copying build/lib/botocore/data/personalize-events/2018-03-22/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/personalize-events/2018-03-22 creating build/bdist.linux-aarch64/wheel/botocore/data/personalize-runtime creating build/bdist.linux-aarch64/wheel/botocore/data/personalize-runtime/2018-05-22 copying build/lib/botocore/data/personalize-runtime/2018-05-22/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/personalize-runtime/2018-05-22 copying build/lib/botocore/data/personalize-runtime/2018-05-22/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/personalize-runtime/2018-05-22 copying build/lib/botocore/data/personalize-runtime/2018-05-22/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/personalize-runtime/2018-05-22 copying build/lib/botocore/data/personalize-runtime/2018-05-22/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/personalize-runtime/2018-05-22 creating build/bdist.linux-aarch64/wheel/botocore/data/personalize creating build/bdist.linux-aarch64/wheel/botocore/data/personalize/2018-05-22 copying build/lib/botocore/data/personalize/2018-05-22/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/personalize/2018-05-22 copying build/lib/botocore/data/personalize/2018-05-22/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/personalize/2018-05-22 copying build/lib/botocore/data/personalize/2018-05-22/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/personalize/2018-05-22 copying build/lib/botocore/data/personalize/2018-05-22/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/personalize/2018-05-22 creating build/bdist.linux-aarch64/wheel/botocore/data/pi creating build/bdist.linux-aarch64/wheel/botocore/data/pi/2018-02-27 copying build/lib/botocore/data/pi/2018-02-27/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/pi/2018-02-27 copying build/lib/botocore/data/pi/2018-02-27/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/pi/2018-02-27 copying build/lib/botocore/data/pi/2018-02-27/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/pi/2018-02-27 copying build/lib/botocore/data/pi/2018-02-27/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/pi/2018-02-27 creating build/bdist.linux-aarch64/wheel/botocore/data/pinpoint-email creating build/bdist.linux-aarch64/wheel/botocore/data/pinpoint-email/2018-07-26 copying build/lib/botocore/data/pinpoint-email/2018-07-26/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/pinpoint-email/2018-07-26 copying build/lib/botocore/data/pinpoint-email/2018-07-26/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/pinpoint-email/2018-07-26 copying build/lib/botocore/data/pinpoint-email/2018-07-26/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/pinpoint-email/2018-07-26 copying build/lib/botocore/data/pinpoint-email/2018-07-26/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/pinpoint-email/2018-07-26 creating build/bdist.linux-aarch64/wheel/botocore/data/pinpoint-sms-voice-v2 creating build/bdist.linux-aarch64/wheel/botocore/data/pinpoint-sms-voice-v2/2022-03-31 copying build/lib/botocore/data/pinpoint-sms-voice-v2/2022-03-31/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/pinpoint-sms-voice-v2/2022-03-31 copying build/lib/botocore/data/pinpoint-sms-voice-v2/2022-03-31/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/pinpoint-sms-voice-v2/2022-03-31 copying build/lib/botocore/data/pinpoint-sms-voice-v2/2022-03-31/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/pinpoint-sms-voice-v2/2022-03-31 copying build/lib/botocore/data/pinpoint-sms-voice-v2/2022-03-31/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/pinpoint-sms-voice-v2/2022-03-31 copying build/lib/botocore/data/pinpoint-sms-voice-v2/2022-03-31/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/pinpoint-sms-voice-v2/2022-03-31 copying build/lib/botocore/data/pinpoint-sms-voice-v2/2022-03-31/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/pinpoint-sms-voice-v2/2022-03-31 creating build/bdist.linux-aarch64/wheel/botocore/data/pinpoint-sms-voice creating build/bdist.linux-aarch64/wheel/botocore/data/pinpoint-sms-voice/2018-09-05 copying build/lib/botocore/data/pinpoint-sms-voice/2018-09-05/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/pinpoint-sms-voice/2018-09-05 copying build/lib/botocore/data/pinpoint-sms-voice/2018-09-05/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/pinpoint-sms-voice/2018-09-05 creating build/bdist.linux-aarch64/wheel/botocore/data/pinpoint creating build/bdist.linux-aarch64/wheel/botocore/data/pinpoint/2016-12-01 copying build/lib/botocore/data/pinpoint/2016-12-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/pinpoint/2016-12-01 copying build/lib/botocore/data/pinpoint/2016-12-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/pinpoint/2016-12-01 copying build/lib/botocore/data/pinpoint/2016-12-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/pinpoint/2016-12-01 creating build/bdist.linux-aarch64/wheel/botocore/data/pipes creating build/bdist.linux-aarch64/wheel/botocore/data/pipes/2015-10-07 copying build/lib/botocore/data/pipes/2015-10-07/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/pipes/2015-10-07 copying build/lib/botocore/data/pipes/2015-10-07/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/pipes/2015-10-07 copying build/lib/botocore/data/pipes/2015-10-07/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/pipes/2015-10-07 copying build/lib/botocore/data/pipes/2015-10-07/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/pipes/2015-10-07 creating build/bdist.linux-aarch64/wheel/botocore/data/polly creating build/bdist.linux-aarch64/wheel/botocore/data/polly/2016-06-10 copying build/lib/botocore/data/polly/2016-06-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/polly/2016-06-10 copying build/lib/botocore/data/polly/2016-06-10/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/polly/2016-06-10 copying build/lib/botocore/data/polly/2016-06-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/polly/2016-06-10 copying build/lib/botocore/data/polly/2016-06-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/polly/2016-06-10 creating build/bdist.linux-aarch64/wheel/botocore/data/pricing creating build/bdist.linux-aarch64/wheel/botocore/data/pricing/2017-10-15 copying build/lib/botocore/data/pricing/2017-10-15/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/pricing/2017-10-15 copying build/lib/botocore/data/pricing/2017-10-15/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/pricing/2017-10-15 copying build/lib/botocore/data/pricing/2017-10-15/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/pricing/2017-10-15 copying build/lib/botocore/data/pricing/2017-10-15/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/pricing/2017-10-15 copying build/lib/botocore/data/pricing/2017-10-15/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/pricing/2017-10-15 creating build/bdist.linux-aarch64/wheel/botocore/data/proton creating build/bdist.linux-aarch64/wheel/botocore/data/proton/2020-07-20 copying build/lib/botocore/data/proton/2020-07-20/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/proton/2020-07-20 copying build/lib/botocore/data/proton/2020-07-20/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/proton/2020-07-20 copying build/lib/botocore/data/proton/2020-07-20/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/proton/2020-07-20 copying build/lib/botocore/data/proton/2020-07-20/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/proton/2020-07-20 copying build/lib/botocore/data/proton/2020-07-20/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/proton/2020-07-20 creating build/bdist.linux-aarch64/wheel/botocore/data/qapps creating build/bdist.linux-aarch64/wheel/botocore/data/qapps/2023-11-27 copying build/lib/botocore/data/qapps/2023-11-27/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/qapps/2023-11-27 copying build/lib/botocore/data/qapps/2023-11-27/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/qapps/2023-11-27 copying build/lib/botocore/data/qapps/2023-11-27/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/qapps/2023-11-27 copying build/lib/botocore/data/qapps/2023-11-27/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/qapps/2023-11-27 creating build/bdist.linux-aarch64/wheel/botocore/data/qbusiness creating build/bdist.linux-aarch64/wheel/botocore/data/qbusiness/2023-11-27 copying build/lib/botocore/data/qbusiness/2023-11-27/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/qbusiness/2023-11-27 copying build/lib/botocore/data/qbusiness/2023-11-27/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/qbusiness/2023-11-27 copying build/lib/botocore/data/qbusiness/2023-11-27/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/qbusiness/2023-11-27 copying build/lib/botocore/data/qbusiness/2023-11-27/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/qbusiness/2023-11-27 copying build/lib/botocore/data/qbusiness/2023-11-27/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/qbusiness/2023-11-27 creating build/bdist.linux-aarch64/wheel/botocore/data/qconnect creating build/bdist.linux-aarch64/wheel/botocore/data/qconnect/2020-10-19 copying build/lib/botocore/data/qconnect/2020-10-19/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/qconnect/2020-10-19 copying build/lib/botocore/data/qconnect/2020-10-19/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/qconnect/2020-10-19 copying build/lib/botocore/data/qconnect/2020-10-19/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/qconnect/2020-10-19 copying build/lib/botocore/data/qconnect/2020-10-19/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/qconnect/2020-10-19 creating build/bdist.linux-aarch64/wheel/botocore/data/quicksight creating build/bdist.linux-aarch64/wheel/botocore/data/quicksight/2018-04-01 copying build/lib/botocore/data/quicksight/2018-04-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/quicksight/2018-04-01 copying build/lib/botocore/data/quicksight/2018-04-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/quicksight/2018-04-01 copying build/lib/botocore/data/quicksight/2018-04-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/quicksight/2018-04-01 copying build/lib/botocore/data/quicksight/2018-04-01/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/quicksight/2018-04-01 copying build/lib/botocore/data/quicksight/2018-04-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/quicksight/2018-04-01 creating build/bdist.linux-aarch64/wheel/botocore/data/ram creating build/bdist.linux-aarch64/wheel/botocore/data/ram/2018-01-04 copying build/lib/botocore/data/ram/2018-01-04/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ram/2018-01-04 copying build/lib/botocore/data/ram/2018-01-04/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ram/2018-01-04 copying build/lib/botocore/data/ram/2018-01-04/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ram/2018-01-04 copying build/lib/botocore/data/ram/2018-01-04/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ram/2018-01-04 creating build/bdist.linux-aarch64/wheel/botocore/data/rbin creating build/bdist.linux-aarch64/wheel/botocore/data/rbin/2021-06-15 copying build/lib/botocore/data/rbin/2021-06-15/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/rbin/2021-06-15 copying build/lib/botocore/data/rbin/2021-06-15/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/rbin/2021-06-15 copying build/lib/botocore/data/rbin/2021-06-15/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/rbin/2021-06-15 copying build/lib/botocore/data/rbin/2021-06-15/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/rbin/2021-06-15 creating build/bdist.linux-aarch64/wheel/botocore/data/rds-data creating build/bdist.linux-aarch64/wheel/botocore/data/rds-data/2018-08-01 copying build/lib/botocore/data/rds-data/2018-08-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/rds-data/2018-08-01 copying build/lib/botocore/data/rds-data/2018-08-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/rds-data/2018-08-01 copying build/lib/botocore/data/rds-data/2018-08-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/rds-data/2018-08-01 copying build/lib/botocore/data/rds-data/2018-08-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/rds-data/2018-08-01 creating build/bdist.linux-aarch64/wheel/botocore/data/rds creating build/bdist.linux-aarch64/wheel/botocore/data/rds/2014-09-01 copying build/lib/botocore/data/rds/2014-09-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/rds/2014-09-01 copying build/lib/botocore/data/rds/2014-09-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/rds/2014-09-01 copying build/lib/botocore/data/rds/2014-09-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/rds/2014-09-01 copying build/lib/botocore/data/rds/2014-09-01/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/rds/2014-09-01 creating build/bdist.linux-aarch64/wheel/botocore/data/rds/2014-10-31 copying build/lib/botocore/data/rds/2014-10-31/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/rds/2014-10-31 copying build/lib/botocore/data/rds/2014-10-31/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/rds/2014-10-31 copying build/lib/botocore/data/rds/2014-10-31/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/rds/2014-10-31 copying build/lib/botocore/data/rds/2014-10-31/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/rds/2014-10-31 copying build/lib/botocore/data/rds/2014-10-31/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/rds/2014-10-31 copying build/lib/botocore/data/rds/2014-10-31/service-2.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/rds/2014-10-31 copying build/lib/botocore/data/rds/2014-10-31/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/rds/2014-10-31 creating build/bdist.linux-aarch64/wheel/botocore/data/redshift-data creating build/bdist.linux-aarch64/wheel/botocore/data/redshift-data/2019-12-20 copying build/lib/botocore/data/redshift-data/2019-12-20/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/redshift-data/2019-12-20 copying build/lib/botocore/data/redshift-data/2019-12-20/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/redshift-data/2019-12-20 copying build/lib/botocore/data/redshift-data/2019-12-20/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/redshift-data/2019-12-20 copying build/lib/botocore/data/redshift-data/2019-12-20/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/redshift-data/2019-12-20 copying build/lib/botocore/data/redshift-data/2019-12-20/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/redshift-data/2019-12-20 creating build/bdist.linux-aarch64/wheel/botocore/data/redshift-serverless creating build/bdist.linux-aarch64/wheel/botocore/data/redshift-serverless/2021-04-21 copying build/lib/botocore/data/redshift-serverless/2021-04-21/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/redshift-serverless/2021-04-21 copying build/lib/botocore/data/redshift-serverless/2021-04-21/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/redshift-serverless/2021-04-21 copying build/lib/botocore/data/redshift-serverless/2021-04-21/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/redshift-serverless/2021-04-21 creating build/bdist.linux-aarch64/wheel/botocore/data/redshift creating build/bdist.linux-aarch64/wheel/botocore/data/redshift/2012-12-01 copying build/lib/botocore/data/redshift/2012-12-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/redshift/2012-12-01 copying build/lib/botocore/data/redshift/2012-12-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/redshift/2012-12-01 copying build/lib/botocore/data/redshift/2012-12-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/redshift/2012-12-01 copying build/lib/botocore/data/redshift/2012-12-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/redshift/2012-12-01 copying build/lib/botocore/data/redshift/2012-12-01/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/redshift/2012-12-01 creating build/bdist.linux-aarch64/wheel/botocore/data/rekognition creating build/bdist.linux-aarch64/wheel/botocore/data/rekognition/2016-06-27 copying build/lib/botocore/data/rekognition/2016-06-27/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/rekognition/2016-06-27 copying build/lib/botocore/data/rekognition/2016-06-27/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/rekognition/2016-06-27 copying build/lib/botocore/data/rekognition/2016-06-27/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/rekognition/2016-06-27 copying build/lib/botocore/data/rekognition/2016-06-27/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/rekognition/2016-06-27 copying build/lib/botocore/data/rekognition/2016-06-27/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/rekognition/2016-06-27 creating build/bdist.linux-aarch64/wheel/botocore/data/repostspace creating build/bdist.linux-aarch64/wheel/botocore/data/repostspace/2022-05-13 copying build/lib/botocore/data/repostspace/2022-05-13/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/repostspace/2022-05-13 copying build/lib/botocore/data/repostspace/2022-05-13/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/repostspace/2022-05-13 copying build/lib/botocore/data/repostspace/2022-05-13/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/repostspace/2022-05-13 copying build/lib/botocore/data/repostspace/2022-05-13/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/repostspace/2022-05-13 creating build/bdist.linux-aarch64/wheel/botocore/data/resiliencehub creating build/bdist.linux-aarch64/wheel/botocore/data/resiliencehub/2020-04-30 copying build/lib/botocore/data/resiliencehub/2020-04-30/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/resiliencehub/2020-04-30 copying build/lib/botocore/data/resiliencehub/2020-04-30/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/resiliencehub/2020-04-30 copying build/lib/botocore/data/resiliencehub/2020-04-30/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/resiliencehub/2020-04-30 copying build/lib/botocore/data/resiliencehub/2020-04-30/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/resiliencehub/2020-04-30 creating build/bdist.linux-aarch64/wheel/botocore/data/resource-explorer-2 creating build/bdist.linux-aarch64/wheel/botocore/data/resource-explorer-2/2022-07-28 copying build/lib/botocore/data/resource-explorer-2/2022-07-28/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/resource-explorer-2/2022-07-28 copying build/lib/botocore/data/resource-explorer-2/2022-07-28/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/resource-explorer-2/2022-07-28 copying build/lib/botocore/data/resource-explorer-2/2022-07-28/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/resource-explorer-2/2022-07-28 copying build/lib/botocore/data/resource-explorer-2/2022-07-28/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/resource-explorer-2/2022-07-28 copying build/lib/botocore/data/resource-explorer-2/2022-07-28/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/resource-explorer-2/2022-07-28 creating build/bdist.linux-aarch64/wheel/botocore/data/resource-groups creating build/bdist.linux-aarch64/wheel/botocore/data/resource-groups/2017-11-27 copying build/lib/botocore/data/resource-groups/2017-11-27/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/resource-groups/2017-11-27 copying build/lib/botocore/data/resource-groups/2017-11-27/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/resource-groups/2017-11-27 copying build/lib/botocore/data/resource-groups/2017-11-27/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/resource-groups/2017-11-27 copying build/lib/botocore/data/resource-groups/2017-11-27/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/resource-groups/2017-11-27 copying build/lib/botocore/data/resource-groups/2017-11-27/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/resource-groups/2017-11-27 creating build/bdist.linux-aarch64/wheel/botocore/data/resourcegroupstaggingapi creating build/bdist.linux-aarch64/wheel/botocore/data/resourcegroupstaggingapi/2017-01-26 copying build/lib/botocore/data/resourcegroupstaggingapi/2017-01-26/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/resourcegroupstaggingapi/2017-01-26 copying build/lib/botocore/data/resourcegroupstaggingapi/2017-01-26/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/resourcegroupstaggingapi/2017-01-26 copying build/lib/botocore/data/resourcegroupstaggingapi/2017-01-26/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/resourcegroupstaggingapi/2017-01-26 copying build/lib/botocore/data/resourcegroupstaggingapi/2017-01-26/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/resourcegroupstaggingapi/2017-01-26 creating build/bdist.linux-aarch64/wheel/botocore/data/rolesanywhere creating build/bdist.linux-aarch64/wheel/botocore/data/rolesanywhere/2018-05-10 copying build/lib/botocore/data/rolesanywhere/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/rolesanywhere/2018-05-10 copying build/lib/botocore/data/rolesanywhere/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/rolesanywhere/2018-05-10 copying build/lib/botocore/data/rolesanywhere/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/rolesanywhere/2018-05-10 copying build/lib/botocore/data/rolesanywhere/2018-05-10/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/rolesanywhere/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/route53-recovery-cluster creating build/bdist.linux-aarch64/wheel/botocore/data/route53-recovery-cluster/2019-12-02 copying build/lib/botocore/data/route53-recovery-cluster/2019-12-02/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53-recovery-cluster/2019-12-02 copying build/lib/botocore/data/route53-recovery-cluster/2019-12-02/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53-recovery-cluster/2019-12-02 copying build/lib/botocore/data/route53-recovery-cluster/2019-12-02/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53-recovery-cluster/2019-12-02 copying build/lib/botocore/data/route53-recovery-cluster/2019-12-02/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53-recovery-cluster/2019-12-02 creating build/bdist.linux-aarch64/wheel/botocore/data/route53-recovery-control-config creating build/bdist.linux-aarch64/wheel/botocore/data/route53-recovery-control-config/2020-11-02 copying build/lib/botocore/data/route53-recovery-control-config/2020-11-02/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53-recovery-control-config/2020-11-02 copying build/lib/botocore/data/route53-recovery-control-config/2020-11-02/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53-recovery-control-config/2020-11-02 copying build/lib/botocore/data/route53-recovery-control-config/2020-11-02/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53-recovery-control-config/2020-11-02 copying build/lib/botocore/data/route53-recovery-control-config/2020-11-02/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53-recovery-control-config/2020-11-02 creating build/bdist.linux-aarch64/wheel/botocore/data/route53-recovery-readiness creating build/bdist.linux-aarch64/wheel/botocore/data/route53-recovery-readiness/2019-12-02 copying build/lib/botocore/data/route53-recovery-readiness/2019-12-02/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53-recovery-readiness/2019-12-02 copying build/lib/botocore/data/route53-recovery-readiness/2019-12-02/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53-recovery-readiness/2019-12-02 copying build/lib/botocore/data/route53-recovery-readiness/2019-12-02/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53-recovery-readiness/2019-12-02 creating build/bdist.linux-aarch64/wheel/botocore/data/route53 creating build/bdist.linux-aarch64/wheel/botocore/data/route53/2013-04-01 copying build/lib/botocore/data/route53/2013-04-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53/2013-04-01 copying build/lib/botocore/data/route53/2013-04-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53/2013-04-01 copying build/lib/botocore/data/route53/2013-04-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53/2013-04-01 copying build/lib/botocore/data/route53/2013-04-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53/2013-04-01 copying build/lib/botocore/data/route53/2013-04-01/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53/2013-04-01 creating build/bdist.linux-aarch64/wheel/botocore/data/route53domains creating build/bdist.linux-aarch64/wheel/botocore/data/route53domains/2014-05-15 copying build/lib/botocore/data/route53domains/2014-05-15/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53domains/2014-05-15 copying build/lib/botocore/data/route53domains/2014-05-15/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53domains/2014-05-15 copying build/lib/botocore/data/route53domains/2014-05-15/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53domains/2014-05-15 copying build/lib/botocore/data/route53domains/2014-05-15/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53domains/2014-05-15 creating build/bdist.linux-aarch64/wheel/botocore/data/route53globalresolver creating build/bdist.linux-aarch64/wheel/botocore/data/route53globalresolver/2022-09-27 copying build/lib/botocore/data/route53globalresolver/2022-09-27/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53globalresolver/2022-09-27 copying build/lib/botocore/data/route53globalresolver/2022-09-27/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53globalresolver/2022-09-27 copying build/lib/botocore/data/route53globalresolver/2022-09-27/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53globalresolver/2022-09-27 copying build/lib/botocore/data/route53globalresolver/2022-09-27/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53globalresolver/2022-09-27 creating build/bdist.linux-aarch64/wheel/botocore/data/route53profiles creating build/bdist.linux-aarch64/wheel/botocore/data/route53profiles/2018-05-10 copying build/lib/botocore/data/route53profiles/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53profiles/2018-05-10 copying build/lib/botocore/data/route53profiles/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53profiles/2018-05-10 copying build/lib/botocore/data/route53profiles/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53profiles/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/route53resolver creating build/bdist.linux-aarch64/wheel/botocore/data/route53resolver/2018-04-01 copying build/lib/botocore/data/route53resolver/2018-04-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53resolver/2018-04-01 copying build/lib/botocore/data/route53resolver/2018-04-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53resolver/2018-04-01 copying build/lib/botocore/data/route53resolver/2018-04-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53resolver/2018-04-01 copying build/lib/botocore/data/route53resolver/2018-04-01/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53resolver/2018-04-01 copying build/lib/botocore/data/route53resolver/2018-04-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/route53resolver/2018-04-01 creating build/bdist.linux-aarch64/wheel/botocore/data/rtbfabric creating build/bdist.linux-aarch64/wheel/botocore/data/rtbfabric/2023-05-15 copying build/lib/botocore/data/rtbfabric/2023-05-15/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/rtbfabric/2023-05-15 copying build/lib/botocore/data/rtbfabric/2023-05-15/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/rtbfabric/2023-05-15 copying build/lib/botocore/data/rtbfabric/2023-05-15/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/rtbfabric/2023-05-15 copying build/lib/botocore/data/rtbfabric/2023-05-15/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/rtbfabric/2023-05-15 creating build/bdist.linux-aarch64/wheel/botocore/data/rum creating build/bdist.linux-aarch64/wheel/botocore/data/rum/2018-05-10 copying build/lib/botocore/data/rum/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/rum/2018-05-10 copying build/lib/botocore/data/rum/2018-05-10/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/rum/2018-05-10 copying build/lib/botocore/data/rum/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/rum/2018-05-10 copying build/lib/botocore/data/rum/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/rum/2018-05-10 copying build/lib/botocore/data/rum/2018-05-10/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/rum/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/s3 creating build/bdist.linux-aarch64/wheel/botocore/data/s3/2006-03-01 copying build/lib/botocore/data/s3/2006-03-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/s3/2006-03-01 copying build/lib/botocore/data/s3/2006-03-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/s3/2006-03-01 copying build/lib/botocore/data/s3/2006-03-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/s3/2006-03-01 copying build/lib/botocore/data/s3/2006-03-01/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/s3/2006-03-01 copying build/lib/botocore/data/s3/2006-03-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/s3/2006-03-01 copying build/lib/botocore/data/s3/2006-03-01/service-2.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/s3/2006-03-01 copying build/lib/botocore/data/s3/2006-03-01/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/s3/2006-03-01 creating build/bdist.linux-aarch64/wheel/botocore/data/s3control creating build/bdist.linux-aarch64/wheel/botocore/data/s3control/2018-08-20 copying build/lib/botocore/data/s3control/2018-08-20/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/s3control/2018-08-20 copying build/lib/botocore/data/s3control/2018-08-20/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/s3control/2018-08-20 copying build/lib/botocore/data/s3control/2018-08-20/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/s3control/2018-08-20 copying build/lib/botocore/data/s3control/2018-08-20/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/s3control/2018-08-20 creating build/bdist.linux-aarch64/wheel/botocore/data/s3files creating build/bdist.linux-aarch64/wheel/botocore/data/s3files/2025-05-05 copying build/lib/botocore/data/s3files/2025-05-05/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/s3files/2025-05-05 copying build/lib/botocore/data/s3files/2025-05-05/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/s3files/2025-05-05 copying build/lib/botocore/data/s3files/2025-05-05/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/s3files/2025-05-05 copying build/lib/botocore/data/s3files/2025-05-05/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/s3files/2025-05-05 creating build/bdist.linux-aarch64/wheel/botocore/data/s3outposts creating build/bdist.linux-aarch64/wheel/botocore/data/s3outposts/2017-07-25 copying build/lib/botocore/data/s3outposts/2017-07-25/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/s3outposts/2017-07-25 copying build/lib/botocore/data/s3outposts/2017-07-25/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/s3outposts/2017-07-25 copying build/lib/botocore/data/s3outposts/2017-07-25/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/s3outposts/2017-07-25 copying build/lib/botocore/data/s3outposts/2017-07-25/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/s3outposts/2017-07-25 creating build/bdist.linux-aarch64/wheel/botocore/data/s3tables creating build/bdist.linux-aarch64/wheel/botocore/data/s3tables/2018-05-10 copying build/lib/botocore/data/s3tables/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/s3tables/2018-05-10 copying build/lib/botocore/data/s3tables/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/s3tables/2018-05-10 copying build/lib/botocore/data/s3tables/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/s3tables/2018-05-10 copying build/lib/botocore/data/s3tables/2018-05-10/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/s3tables/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/s3vectors creating build/bdist.linux-aarch64/wheel/botocore/data/s3vectors/2025-07-15 copying build/lib/botocore/data/s3vectors/2025-07-15/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/s3vectors/2025-07-15 copying build/lib/botocore/data/s3vectors/2025-07-15/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/s3vectors/2025-07-15 copying build/lib/botocore/data/s3vectors/2025-07-15/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/s3vectors/2025-07-15 copying build/lib/botocore/data/s3vectors/2025-07-15/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/s3vectors/2025-07-15 creating build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-a2i-runtime creating build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-a2i-runtime/2019-11-07 copying build/lib/botocore/data/sagemaker-a2i-runtime/2019-11-07/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-a2i-runtime/2019-11-07 copying build/lib/botocore/data/sagemaker-a2i-runtime/2019-11-07/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-a2i-runtime/2019-11-07 copying build/lib/botocore/data/sagemaker-a2i-runtime/2019-11-07/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-a2i-runtime/2019-11-07 copying build/lib/botocore/data/sagemaker-a2i-runtime/2019-11-07/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-a2i-runtime/2019-11-07 creating build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-edge creating build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-edge/2020-09-23 copying build/lib/botocore/data/sagemaker-edge/2020-09-23/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-edge/2020-09-23 copying build/lib/botocore/data/sagemaker-edge/2020-09-23/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-edge/2020-09-23 copying build/lib/botocore/data/sagemaker-edge/2020-09-23/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-edge/2020-09-23 copying build/lib/botocore/data/sagemaker-edge/2020-09-23/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-edge/2020-09-23 creating build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-featurestore-runtime creating build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-featurestore-runtime/2020-07-01 copying build/lib/botocore/data/sagemaker-featurestore-runtime/2020-07-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-featurestore-runtime/2020-07-01 copying build/lib/botocore/data/sagemaker-featurestore-runtime/2020-07-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-featurestore-runtime/2020-07-01 copying build/lib/botocore/data/sagemaker-featurestore-runtime/2020-07-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-featurestore-runtime/2020-07-01 copying build/lib/botocore/data/sagemaker-featurestore-runtime/2020-07-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-featurestore-runtime/2020-07-01 creating build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-geospatial creating build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-geospatial/2020-05-27 copying build/lib/botocore/data/sagemaker-geospatial/2020-05-27/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-geospatial/2020-05-27 copying build/lib/botocore/data/sagemaker-geospatial/2020-05-27/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-geospatial/2020-05-27 copying build/lib/botocore/data/sagemaker-geospatial/2020-05-27/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-geospatial/2020-05-27 creating build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-metrics creating build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-metrics/2022-09-30 copying build/lib/botocore/data/sagemaker-metrics/2022-09-30/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-metrics/2022-09-30 copying build/lib/botocore/data/sagemaker-metrics/2022-09-30/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-metrics/2022-09-30 copying build/lib/botocore/data/sagemaker-metrics/2022-09-30/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-metrics/2022-09-30 creating build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-runtime creating build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-runtime/2017-05-13 copying build/lib/botocore/data/sagemaker-runtime/2017-05-13/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-runtime/2017-05-13 copying build/lib/botocore/data/sagemaker-runtime/2017-05-13/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-runtime/2017-05-13 copying build/lib/botocore/data/sagemaker-runtime/2017-05-13/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-runtime/2017-05-13 copying build/lib/botocore/data/sagemaker-runtime/2017-05-13/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/sagemaker-runtime/2017-05-13 creating build/bdist.linux-aarch64/wheel/botocore/data/sagemaker creating build/bdist.linux-aarch64/wheel/botocore/data/sagemaker/2017-07-24 copying build/lib/botocore/data/sagemaker/2017-07-24/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sagemaker/2017-07-24 copying build/lib/botocore/data/sagemaker/2017-07-24/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sagemaker/2017-07-24 copying build/lib/botocore/data/sagemaker/2017-07-24/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sagemaker/2017-07-24 copying build/lib/botocore/data/sagemaker/2017-07-24/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/sagemaker/2017-07-24 copying build/lib/botocore/data/sagemaker/2017-07-24/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/sagemaker/2017-07-24 copying build/lib/botocore/data/sagemaker/2017-07-24/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/sagemaker/2017-07-24 creating build/bdist.linux-aarch64/wheel/botocore/data/savingsplans creating build/bdist.linux-aarch64/wheel/botocore/data/savingsplans/2019-06-28 copying build/lib/botocore/data/savingsplans/2019-06-28/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/savingsplans/2019-06-28 copying build/lib/botocore/data/savingsplans/2019-06-28/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/savingsplans/2019-06-28 copying build/lib/botocore/data/savingsplans/2019-06-28/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/savingsplans/2019-06-28 copying build/lib/botocore/data/savingsplans/2019-06-28/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/savingsplans/2019-06-28 creating build/bdist.linux-aarch64/wheel/botocore/data/scheduler creating build/bdist.linux-aarch64/wheel/botocore/data/scheduler/2021-06-30 copying build/lib/botocore/data/scheduler/2021-06-30/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/scheduler/2021-06-30 copying build/lib/botocore/data/scheduler/2021-06-30/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/scheduler/2021-06-30 copying build/lib/botocore/data/scheduler/2021-06-30/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/scheduler/2021-06-30 creating build/bdist.linux-aarch64/wheel/botocore/data/schemas creating build/bdist.linux-aarch64/wheel/botocore/data/schemas/2019-12-02 copying build/lib/botocore/data/schemas/2019-12-02/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/schemas/2019-12-02 copying build/lib/botocore/data/schemas/2019-12-02/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/schemas/2019-12-02 copying build/lib/botocore/data/schemas/2019-12-02/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/schemas/2019-12-02 copying build/lib/botocore/data/schemas/2019-12-02/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/schemas/2019-12-02 creating build/bdist.linux-aarch64/wheel/botocore/data/sdb creating build/bdist.linux-aarch64/wheel/botocore/data/sdb/2009-04-15 copying build/lib/botocore/data/sdb/2009-04-15/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sdb/2009-04-15 copying build/lib/botocore/data/sdb/2009-04-15/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sdb/2009-04-15 copying build/lib/botocore/data/sdb/2009-04-15/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/sdb/2009-04-15 creating build/bdist.linux-aarch64/wheel/botocore/data/secretsmanager creating build/bdist.linux-aarch64/wheel/botocore/data/secretsmanager/2017-10-17 copying build/lib/botocore/data/secretsmanager/2017-10-17/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/secretsmanager/2017-10-17 copying build/lib/botocore/data/secretsmanager/2017-10-17/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/secretsmanager/2017-10-17 copying build/lib/botocore/data/secretsmanager/2017-10-17/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/secretsmanager/2017-10-17 copying build/lib/botocore/data/secretsmanager/2017-10-17/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/secretsmanager/2017-10-17 copying build/lib/botocore/data/secretsmanager/2017-10-17/service-2.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/secretsmanager/2017-10-17 creating build/bdist.linux-aarch64/wheel/botocore/data/security-ir creating build/bdist.linux-aarch64/wheel/botocore/data/security-ir/2018-05-10 copying build/lib/botocore/data/security-ir/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/security-ir/2018-05-10 copying build/lib/botocore/data/security-ir/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/security-ir/2018-05-10 copying build/lib/botocore/data/security-ir/2018-05-10/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/security-ir/2018-05-10 copying build/lib/botocore/data/security-ir/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/security-ir/2018-05-10 copying build/lib/botocore/data/security-ir/2018-05-10/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/security-ir/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/securityagent creating build/bdist.linux-aarch64/wheel/botocore/data/securityagent/2025-09-06 copying build/lib/botocore/data/securityagent/2025-09-06/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/securityagent/2025-09-06 copying build/lib/botocore/data/securityagent/2025-09-06/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/securityagent/2025-09-06 copying build/lib/botocore/data/securityagent/2025-09-06/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/securityagent/2025-09-06 copying build/lib/botocore/data/securityagent/2025-09-06/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/securityagent/2025-09-06 creating build/bdist.linux-aarch64/wheel/botocore/data/securityhub creating build/bdist.linux-aarch64/wheel/botocore/data/securityhub/2018-10-26 copying build/lib/botocore/data/securityhub/2018-10-26/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/securityhub/2018-10-26 copying build/lib/botocore/data/securityhub/2018-10-26/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/securityhub/2018-10-26 copying build/lib/botocore/data/securityhub/2018-10-26/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/securityhub/2018-10-26 copying build/lib/botocore/data/securityhub/2018-10-26/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/securityhub/2018-10-26 copying build/lib/botocore/data/securityhub/2018-10-26/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/securityhub/2018-10-26 creating build/bdist.linux-aarch64/wheel/botocore/data/securitylake creating build/bdist.linux-aarch64/wheel/botocore/data/securitylake/2018-05-10 copying build/lib/botocore/data/securitylake/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/securitylake/2018-05-10 copying build/lib/botocore/data/securitylake/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/securitylake/2018-05-10 copying build/lib/botocore/data/securitylake/2018-05-10/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/securitylake/2018-05-10 copying build/lib/botocore/data/securitylake/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/securitylake/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/serverlessrepo creating build/bdist.linux-aarch64/wheel/botocore/data/serverlessrepo/2017-09-08 copying build/lib/botocore/data/serverlessrepo/2017-09-08/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/serverlessrepo/2017-09-08 copying build/lib/botocore/data/serverlessrepo/2017-09-08/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/serverlessrepo/2017-09-08 copying build/lib/botocore/data/serverlessrepo/2017-09-08/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/serverlessrepo/2017-09-08 creating build/bdist.linux-aarch64/wheel/botocore/data/service-quotas creating build/bdist.linux-aarch64/wheel/botocore/data/service-quotas/2019-06-24 copying build/lib/botocore/data/service-quotas/2019-06-24/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/service-quotas/2019-06-24 copying build/lib/botocore/data/service-quotas/2019-06-24/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/service-quotas/2019-06-24 copying build/lib/botocore/data/service-quotas/2019-06-24/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/service-quotas/2019-06-24 copying build/lib/botocore/data/service-quotas/2019-06-24/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/service-quotas/2019-06-24 creating build/bdist.linux-aarch64/wheel/botocore/data/servicecatalog-appregistry creating build/bdist.linux-aarch64/wheel/botocore/data/servicecatalog-appregistry/2020-06-24 copying build/lib/botocore/data/servicecatalog-appregistry/2020-06-24/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/servicecatalog-appregistry/2020-06-24 copying build/lib/botocore/data/servicecatalog-appregistry/2020-06-24/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/servicecatalog-appregistry/2020-06-24 copying build/lib/botocore/data/servicecatalog-appregistry/2020-06-24/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/servicecatalog-appregistry/2020-06-24 copying build/lib/botocore/data/servicecatalog-appregistry/2020-06-24/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/servicecatalog-appregistry/2020-06-24 creating build/bdist.linux-aarch64/wheel/botocore/data/servicecatalog creating build/bdist.linux-aarch64/wheel/botocore/data/servicecatalog/2015-12-10 copying build/lib/botocore/data/servicecatalog/2015-12-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/servicecatalog/2015-12-10 copying build/lib/botocore/data/servicecatalog/2015-12-10/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/servicecatalog/2015-12-10 copying build/lib/botocore/data/servicecatalog/2015-12-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/servicecatalog/2015-12-10 copying build/lib/botocore/data/servicecatalog/2015-12-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/servicecatalog/2015-12-10 creating build/bdist.linux-aarch64/wheel/botocore/data/servicediscovery creating build/bdist.linux-aarch64/wheel/botocore/data/servicediscovery/2017-03-14 copying build/lib/botocore/data/servicediscovery/2017-03-14/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/servicediscovery/2017-03-14 copying build/lib/botocore/data/servicediscovery/2017-03-14/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/servicediscovery/2017-03-14 copying build/lib/botocore/data/servicediscovery/2017-03-14/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/servicediscovery/2017-03-14 copying build/lib/botocore/data/servicediscovery/2017-03-14/paginators-1.sdk-extras.json -> build/bdist.linux-aarch64/wheel/botocore/data/servicediscovery/2017-03-14 copying build/lib/botocore/data/servicediscovery/2017-03-14/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/servicediscovery/2017-03-14 creating build/bdist.linux-aarch64/wheel/botocore/data/ses creating build/bdist.linux-aarch64/wheel/botocore/data/ses/2010-12-01 copying build/lib/botocore/data/ses/2010-12-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ses/2010-12-01 copying build/lib/botocore/data/ses/2010-12-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ses/2010-12-01 copying build/lib/botocore/data/ses/2010-12-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ses/2010-12-01 copying build/lib/botocore/data/ses/2010-12-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ses/2010-12-01 copying build/lib/botocore/data/ses/2010-12-01/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ses/2010-12-01 creating build/bdist.linux-aarch64/wheel/botocore/data/sesv2 creating build/bdist.linux-aarch64/wheel/botocore/data/sesv2/2019-09-27 copying build/lib/botocore/data/sesv2/2019-09-27/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sesv2/2019-09-27 copying build/lib/botocore/data/sesv2/2019-09-27/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sesv2/2019-09-27 copying build/lib/botocore/data/sesv2/2019-09-27/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sesv2/2019-09-27 copying build/lib/botocore/data/sesv2/2019-09-27/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/sesv2/2019-09-27 creating build/bdist.linux-aarch64/wheel/botocore/data/shield creating build/bdist.linux-aarch64/wheel/botocore/data/shield/2016-06-02 copying build/lib/botocore/data/shield/2016-06-02/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/shield/2016-06-02 copying build/lib/botocore/data/shield/2016-06-02/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/shield/2016-06-02 copying build/lib/botocore/data/shield/2016-06-02/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/shield/2016-06-02 copying build/lib/botocore/data/shield/2016-06-02/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/shield/2016-06-02 creating build/bdist.linux-aarch64/wheel/botocore/data/signer-data creating build/bdist.linux-aarch64/wheel/botocore/data/signer-data/2017-08-25 copying build/lib/botocore/data/signer-data/2017-08-25/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/signer-data/2017-08-25 copying build/lib/botocore/data/signer-data/2017-08-25/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/signer-data/2017-08-25 copying build/lib/botocore/data/signer-data/2017-08-25/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/signer-data/2017-08-25 copying build/lib/botocore/data/signer-data/2017-08-25/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/signer-data/2017-08-25 creating build/bdist.linux-aarch64/wheel/botocore/data/signer creating build/bdist.linux-aarch64/wheel/botocore/data/signer/2017-08-25 copying build/lib/botocore/data/signer/2017-08-25/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/signer/2017-08-25 copying build/lib/botocore/data/signer/2017-08-25/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/signer/2017-08-25 copying build/lib/botocore/data/signer/2017-08-25/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/signer/2017-08-25 copying build/lib/botocore/data/signer/2017-08-25/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/signer/2017-08-25 copying build/lib/botocore/data/signer/2017-08-25/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/signer/2017-08-25 creating build/bdist.linux-aarch64/wheel/botocore/data/signin creating build/bdist.linux-aarch64/wheel/botocore/data/signin/2023-01-01 copying build/lib/botocore/data/signin/2023-01-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/signin/2023-01-01 copying build/lib/botocore/data/signin/2023-01-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/signin/2023-01-01 copying build/lib/botocore/data/signin/2023-01-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/signin/2023-01-01 creating build/bdist.linux-aarch64/wheel/botocore/data/simpledbv2 creating build/bdist.linux-aarch64/wheel/botocore/data/simpledbv2/2025-09-26 copying build/lib/botocore/data/simpledbv2/2025-09-26/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/simpledbv2/2025-09-26 copying build/lib/botocore/data/simpledbv2/2025-09-26/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/simpledbv2/2025-09-26 copying build/lib/botocore/data/simpledbv2/2025-09-26/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/simpledbv2/2025-09-26 copying build/lib/botocore/data/simpledbv2/2025-09-26/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/simpledbv2/2025-09-26 creating build/bdist.linux-aarch64/wheel/botocore/data/simspaceweaver creating build/bdist.linux-aarch64/wheel/botocore/data/simspaceweaver/2022-10-28 copying build/lib/botocore/data/simspaceweaver/2022-10-28/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/simspaceweaver/2022-10-28 copying build/lib/botocore/data/simspaceweaver/2022-10-28/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/simspaceweaver/2022-10-28 copying build/lib/botocore/data/simspaceweaver/2022-10-28/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/simspaceweaver/2022-10-28 creating build/bdist.linux-aarch64/wheel/botocore/data/sms-voice creating build/bdist.linux-aarch64/wheel/botocore/data/sms-voice/2018-09-05 copying build/lib/botocore/data/sms-voice/2018-09-05/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sms-voice/2018-09-05 copying build/lib/botocore/data/sms-voice/2018-09-05/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/sms-voice/2018-09-05 creating build/bdist.linux-aarch64/wheel/botocore/data/snow-device-management creating build/bdist.linux-aarch64/wheel/botocore/data/snow-device-management/2021-08-04 copying build/lib/botocore/data/snow-device-management/2021-08-04/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/snow-device-management/2021-08-04 copying build/lib/botocore/data/snow-device-management/2021-08-04/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/snow-device-management/2021-08-04 copying build/lib/botocore/data/snow-device-management/2021-08-04/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/snow-device-management/2021-08-04 copying build/lib/botocore/data/snow-device-management/2021-08-04/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/snow-device-management/2021-08-04 creating build/bdist.linux-aarch64/wheel/botocore/data/snowball creating build/bdist.linux-aarch64/wheel/botocore/data/snowball/2016-06-30 copying build/lib/botocore/data/snowball/2016-06-30/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/snowball/2016-06-30 copying build/lib/botocore/data/snowball/2016-06-30/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/snowball/2016-06-30 copying build/lib/botocore/data/snowball/2016-06-30/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/snowball/2016-06-30 copying build/lib/botocore/data/snowball/2016-06-30/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/snowball/2016-06-30 creating build/bdist.linux-aarch64/wheel/botocore/data/sns creating build/bdist.linux-aarch64/wheel/botocore/data/sns/2010-03-31 copying build/lib/botocore/data/sns/2010-03-31/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sns/2010-03-31 copying build/lib/botocore/data/sns/2010-03-31/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sns/2010-03-31 copying build/lib/botocore/data/sns/2010-03-31/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sns/2010-03-31 copying build/lib/botocore/data/sns/2010-03-31/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/sns/2010-03-31 creating build/bdist.linux-aarch64/wheel/botocore/data/socialmessaging creating build/bdist.linux-aarch64/wheel/botocore/data/socialmessaging/2024-01-01 copying build/lib/botocore/data/socialmessaging/2024-01-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/socialmessaging/2024-01-01 copying build/lib/botocore/data/socialmessaging/2024-01-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/socialmessaging/2024-01-01 copying build/lib/botocore/data/socialmessaging/2024-01-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/socialmessaging/2024-01-01 creating build/bdist.linux-aarch64/wheel/botocore/data/sqs creating build/bdist.linux-aarch64/wheel/botocore/data/sqs/2012-11-05 copying build/lib/botocore/data/sqs/2012-11-05/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sqs/2012-11-05 copying build/lib/botocore/data/sqs/2012-11-05/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sqs/2012-11-05 copying build/lib/botocore/data/sqs/2012-11-05/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sqs/2012-11-05 copying build/lib/botocore/data/sqs/2012-11-05/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/sqs/2012-11-05 creating build/bdist.linux-aarch64/wheel/botocore/data/ssm-contacts creating build/bdist.linux-aarch64/wheel/botocore/data/ssm-contacts/2021-05-03 copying build/lib/botocore/data/ssm-contacts/2021-05-03/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ssm-contacts/2021-05-03 copying build/lib/botocore/data/ssm-contacts/2021-05-03/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ssm-contacts/2021-05-03 copying build/lib/botocore/data/ssm-contacts/2021-05-03/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ssm-contacts/2021-05-03 copying build/lib/botocore/data/ssm-contacts/2021-05-03/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ssm-contacts/2021-05-03 creating build/bdist.linux-aarch64/wheel/botocore/data/ssm-guiconnect creating build/bdist.linux-aarch64/wheel/botocore/data/ssm-guiconnect/2021-05-01 copying build/lib/botocore/data/ssm-guiconnect/2021-05-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ssm-guiconnect/2021-05-01 copying build/lib/botocore/data/ssm-guiconnect/2021-05-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ssm-guiconnect/2021-05-01 copying build/lib/botocore/data/ssm-guiconnect/2021-05-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ssm-guiconnect/2021-05-01 creating build/bdist.linux-aarch64/wheel/botocore/data/ssm-incidents creating build/bdist.linux-aarch64/wheel/botocore/data/ssm-incidents/2018-05-10 copying build/lib/botocore/data/ssm-incidents/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ssm-incidents/2018-05-10 copying build/lib/botocore/data/ssm-incidents/2018-05-10/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ssm-incidents/2018-05-10 copying build/lib/botocore/data/ssm-incidents/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ssm-incidents/2018-05-10 copying build/lib/botocore/data/ssm-incidents/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ssm-incidents/2018-05-10 copying build/lib/botocore/data/ssm-incidents/2018-05-10/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ssm-incidents/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/ssm-quicksetup creating build/bdist.linux-aarch64/wheel/botocore/data/ssm-quicksetup/2018-05-10 copying build/lib/botocore/data/ssm-quicksetup/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ssm-quicksetup/2018-05-10 copying build/lib/botocore/data/ssm-quicksetup/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ssm-quicksetup/2018-05-10 copying build/lib/botocore/data/ssm-quicksetup/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ssm-quicksetup/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/ssm-sap creating build/bdist.linux-aarch64/wheel/botocore/data/ssm-sap/2018-05-10 copying build/lib/botocore/data/ssm-sap/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ssm-sap/2018-05-10 copying build/lib/botocore/data/ssm-sap/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ssm-sap/2018-05-10 copying build/lib/botocore/data/ssm-sap/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ssm-sap/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/ssm creating build/bdist.linux-aarch64/wheel/botocore/data/ssm/2014-11-06 copying build/lib/botocore/data/ssm/2014-11-06/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ssm/2014-11-06 copying build/lib/botocore/data/ssm/2014-11-06/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ssm/2014-11-06 copying build/lib/botocore/data/ssm/2014-11-06/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/ssm/2014-11-06 copying build/lib/botocore/data/ssm/2014-11-06/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ssm/2014-11-06 copying build/lib/botocore/data/ssm/2014-11-06/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/ssm/2014-11-06 creating build/bdist.linux-aarch64/wheel/botocore/data/sso-admin creating build/bdist.linux-aarch64/wheel/botocore/data/sso-admin/2020-07-20 copying build/lib/botocore/data/sso-admin/2020-07-20/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sso-admin/2020-07-20 copying build/lib/botocore/data/sso-admin/2020-07-20/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sso-admin/2020-07-20 copying build/lib/botocore/data/sso-admin/2020-07-20/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sso-admin/2020-07-20 copying build/lib/botocore/data/sso-admin/2020-07-20/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/sso-admin/2020-07-20 copying build/lib/botocore/data/sso-admin/2020-07-20/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/sso-admin/2020-07-20 creating build/bdist.linux-aarch64/wheel/botocore/data/sso-oidc creating build/bdist.linux-aarch64/wheel/botocore/data/sso-oidc/2019-06-10 copying build/lib/botocore/data/sso-oidc/2019-06-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sso-oidc/2019-06-10 copying build/lib/botocore/data/sso-oidc/2019-06-10/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sso-oidc/2019-06-10 copying build/lib/botocore/data/sso-oidc/2019-06-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sso-oidc/2019-06-10 copying build/lib/botocore/data/sso-oidc/2019-06-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/sso-oidc/2019-06-10 creating build/bdist.linux-aarch64/wheel/botocore/data/sso creating build/bdist.linux-aarch64/wheel/botocore/data/sso/2019-06-10 copying build/lib/botocore/data/sso/2019-06-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sso/2019-06-10 copying build/lib/botocore/data/sso/2019-06-10/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sso/2019-06-10 copying build/lib/botocore/data/sso/2019-06-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sso/2019-06-10 copying build/lib/botocore/data/sso/2019-06-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/sso/2019-06-10 creating build/bdist.linux-aarch64/wheel/botocore/data/stepfunctions creating build/bdist.linux-aarch64/wheel/botocore/data/stepfunctions/2016-11-23 copying build/lib/botocore/data/stepfunctions/2016-11-23/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/stepfunctions/2016-11-23 copying build/lib/botocore/data/stepfunctions/2016-11-23/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/stepfunctions/2016-11-23 copying build/lib/botocore/data/stepfunctions/2016-11-23/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/stepfunctions/2016-11-23 copying build/lib/botocore/data/stepfunctions/2016-11-23/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/stepfunctions/2016-11-23 creating build/bdist.linux-aarch64/wheel/botocore/data/storagegateway creating build/bdist.linux-aarch64/wheel/botocore/data/storagegateway/2013-06-30 copying build/lib/botocore/data/storagegateway/2013-06-30/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/storagegateway/2013-06-30 copying build/lib/botocore/data/storagegateway/2013-06-30/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/storagegateway/2013-06-30 copying build/lib/botocore/data/storagegateway/2013-06-30/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/storagegateway/2013-06-30 copying build/lib/botocore/data/storagegateway/2013-06-30/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/storagegateway/2013-06-30 creating build/bdist.linux-aarch64/wheel/botocore/data/sts creating build/bdist.linux-aarch64/wheel/botocore/data/sts/2011-06-15 copying build/lib/botocore/data/sts/2011-06-15/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sts/2011-06-15 copying build/lib/botocore/data/sts/2011-06-15/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sts/2011-06-15 copying build/lib/botocore/data/sts/2011-06-15/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sts/2011-06-15 copying build/lib/botocore/data/sts/2011-06-15/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/sts/2011-06-15 creating build/bdist.linux-aarch64/wheel/botocore/data/supplychain creating build/bdist.linux-aarch64/wheel/botocore/data/supplychain/2024-01-01 copying build/lib/botocore/data/supplychain/2024-01-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/supplychain/2024-01-01 copying build/lib/botocore/data/supplychain/2024-01-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/supplychain/2024-01-01 copying build/lib/botocore/data/supplychain/2024-01-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/supplychain/2024-01-01 creating build/bdist.linux-aarch64/wheel/botocore/data/support-app creating build/bdist.linux-aarch64/wheel/botocore/data/support-app/2021-08-20 copying build/lib/botocore/data/support-app/2021-08-20/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/support-app/2021-08-20 copying build/lib/botocore/data/support-app/2021-08-20/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/support-app/2021-08-20 copying build/lib/botocore/data/support-app/2021-08-20/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/support-app/2021-08-20 creating build/bdist.linux-aarch64/wheel/botocore/data/support creating build/bdist.linux-aarch64/wheel/botocore/data/support/2013-04-15 copying build/lib/botocore/data/support/2013-04-15/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/support/2013-04-15 copying build/lib/botocore/data/support/2013-04-15/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/support/2013-04-15 copying build/lib/botocore/data/support/2013-04-15/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/support/2013-04-15 copying build/lib/botocore/data/support/2013-04-15/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/support/2013-04-15 creating build/bdist.linux-aarch64/wheel/botocore/data/sustainability creating build/bdist.linux-aarch64/wheel/botocore/data/sustainability/2018-05-10 copying build/lib/botocore/data/sustainability/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sustainability/2018-05-10 copying build/lib/botocore/data/sustainability/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/sustainability/2018-05-10 copying build/lib/botocore/data/sustainability/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/sustainability/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/swf creating build/bdist.linux-aarch64/wheel/botocore/data/swf/2012-01-25 copying build/lib/botocore/data/swf/2012-01-25/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/swf/2012-01-25 copying build/lib/botocore/data/swf/2012-01-25/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/swf/2012-01-25 copying build/lib/botocore/data/swf/2012-01-25/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/swf/2012-01-25 copying build/lib/botocore/data/swf/2012-01-25/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/swf/2012-01-25 creating build/bdist.linux-aarch64/wheel/botocore/data/synthetics creating build/bdist.linux-aarch64/wheel/botocore/data/synthetics/2017-10-11 copying build/lib/botocore/data/synthetics/2017-10-11/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/synthetics/2017-10-11 copying build/lib/botocore/data/synthetics/2017-10-11/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/synthetics/2017-10-11 copying build/lib/botocore/data/synthetics/2017-10-11/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/synthetics/2017-10-11 copying build/lib/botocore/data/synthetics/2017-10-11/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/synthetics/2017-10-11 creating build/bdist.linux-aarch64/wheel/botocore/data/taxsettings creating build/bdist.linux-aarch64/wheel/botocore/data/taxsettings/2018-05-10 copying build/lib/botocore/data/taxsettings/2018-05-10/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/taxsettings/2018-05-10 copying build/lib/botocore/data/taxsettings/2018-05-10/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/taxsettings/2018-05-10 copying build/lib/botocore/data/taxsettings/2018-05-10/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/taxsettings/2018-05-10 creating build/bdist.linux-aarch64/wheel/botocore/data/textract creating build/bdist.linux-aarch64/wheel/botocore/data/textract/2018-06-27 copying build/lib/botocore/data/textract/2018-06-27/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/textract/2018-06-27 copying build/lib/botocore/data/textract/2018-06-27/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/textract/2018-06-27 copying build/lib/botocore/data/textract/2018-06-27/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/textract/2018-06-27 copying build/lib/botocore/data/textract/2018-06-27/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/textract/2018-06-27 creating build/bdist.linux-aarch64/wheel/botocore/data/timestream-influxdb creating build/bdist.linux-aarch64/wheel/botocore/data/timestream-influxdb/2023-01-27 copying build/lib/botocore/data/timestream-influxdb/2023-01-27/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/timestream-influxdb/2023-01-27 copying build/lib/botocore/data/timestream-influxdb/2023-01-27/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/timestream-influxdb/2023-01-27 copying build/lib/botocore/data/timestream-influxdb/2023-01-27/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/timestream-influxdb/2023-01-27 creating build/bdist.linux-aarch64/wheel/botocore/data/timestream-query creating build/bdist.linux-aarch64/wheel/botocore/data/timestream-query/2018-11-01 copying build/lib/botocore/data/timestream-query/2018-11-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/timestream-query/2018-11-01 copying build/lib/botocore/data/timestream-query/2018-11-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/timestream-query/2018-11-01 copying build/lib/botocore/data/timestream-query/2018-11-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/timestream-query/2018-11-01 copying build/lib/botocore/data/timestream-query/2018-11-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/timestream-query/2018-11-01 creating build/bdist.linux-aarch64/wheel/botocore/data/timestream-write creating build/bdist.linux-aarch64/wheel/botocore/data/timestream-write/2018-11-01 copying build/lib/botocore/data/timestream-write/2018-11-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/timestream-write/2018-11-01 copying build/lib/botocore/data/timestream-write/2018-11-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/timestream-write/2018-11-01 copying build/lib/botocore/data/timestream-write/2018-11-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/timestream-write/2018-11-01 copying build/lib/botocore/data/timestream-write/2018-11-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/timestream-write/2018-11-01 creating build/bdist.linux-aarch64/wheel/botocore/data/tnb creating build/bdist.linux-aarch64/wheel/botocore/data/tnb/2008-10-21 copying build/lib/botocore/data/tnb/2008-10-21/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/tnb/2008-10-21 copying build/lib/botocore/data/tnb/2008-10-21/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/tnb/2008-10-21 copying build/lib/botocore/data/tnb/2008-10-21/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/tnb/2008-10-21 creating build/bdist.linux-aarch64/wheel/botocore/data/transcribe creating build/bdist.linux-aarch64/wheel/botocore/data/transcribe/2017-10-26 copying build/lib/botocore/data/transcribe/2017-10-26/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/transcribe/2017-10-26 copying build/lib/botocore/data/transcribe/2017-10-26/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/transcribe/2017-10-26 copying build/lib/botocore/data/transcribe/2017-10-26/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/transcribe/2017-10-26 copying build/lib/botocore/data/transcribe/2017-10-26/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/transcribe/2017-10-26 copying build/lib/botocore/data/transcribe/2017-10-26/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/transcribe/2017-10-26 creating build/bdist.linux-aarch64/wheel/botocore/data/transfer creating build/bdist.linux-aarch64/wheel/botocore/data/transfer/2018-11-05 copying build/lib/botocore/data/transfer/2018-11-05/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/transfer/2018-11-05 copying build/lib/botocore/data/transfer/2018-11-05/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/transfer/2018-11-05 copying build/lib/botocore/data/transfer/2018-11-05/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/transfer/2018-11-05 copying build/lib/botocore/data/transfer/2018-11-05/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/transfer/2018-11-05 copying build/lib/botocore/data/transfer/2018-11-05/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/transfer/2018-11-05 creating build/bdist.linux-aarch64/wheel/botocore/data/translate creating build/bdist.linux-aarch64/wheel/botocore/data/translate/2017-07-01 copying build/lib/botocore/data/translate/2017-07-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/translate/2017-07-01 copying build/lib/botocore/data/translate/2017-07-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/translate/2017-07-01 copying build/lib/botocore/data/translate/2017-07-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/translate/2017-07-01 copying build/lib/botocore/data/translate/2017-07-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/translate/2017-07-01 creating build/bdist.linux-aarch64/wheel/botocore/data/trustedadvisor creating build/bdist.linux-aarch64/wheel/botocore/data/trustedadvisor/2022-09-15 copying build/lib/botocore/data/trustedadvisor/2022-09-15/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/trustedadvisor/2022-09-15 copying build/lib/botocore/data/trustedadvisor/2022-09-15/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/trustedadvisor/2022-09-15 copying build/lib/botocore/data/trustedadvisor/2022-09-15/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/trustedadvisor/2022-09-15 copying build/lib/botocore/data/trustedadvisor/2022-09-15/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/trustedadvisor/2022-09-15 creating build/bdist.linux-aarch64/wheel/botocore/data/uxc creating build/bdist.linux-aarch64/wheel/botocore/data/uxc/2024-07-01 copying build/lib/botocore/data/uxc/2024-07-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/uxc/2024-07-01 copying build/lib/botocore/data/uxc/2024-07-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/uxc/2024-07-01 copying build/lib/botocore/data/uxc/2024-07-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/uxc/2024-07-01 copying build/lib/botocore/data/uxc/2024-07-01/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/uxc/2024-07-01 creating build/bdist.linux-aarch64/wheel/botocore/data/verifiedpermissions creating build/bdist.linux-aarch64/wheel/botocore/data/verifiedpermissions/2021-12-01 copying build/lib/botocore/data/verifiedpermissions/2021-12-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/verifiedpermissions/2021-12-01 copying build/lib/botocore/data/verifiedpermissions/2021-12-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/verifiedpermissions/2021-12-01 copying build/lib/botocore/data/verifiedpermissions/2021-12-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/verifiedpermissions/2021-12-01 copying build/lib/botocore/data/verifiedpermissions/2021-12-01/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/verifiedpermissions/2021-12-01 creating build/bdist.linux-aarch64/wheel/botocore/data/voice-id creating build/bdist.linux-aarch64/wheel/botocore/data/voice-id/2021-09-27 copying build/lib/botocore/data/voice-id/2021-09-27/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/voice-id/2021-09-27 copying build/lib/botocore/data/voice-id/2021-09-27/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/voice-id/2021-09-27 copying build/lib/botocore/data/voice-id/2021-09-27/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/voice-id/2021-09-27 copying build/lib/botocore/data/voice-id/2021-09-27/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/voice-id/2021-09-27 creating build/bdist.linux-aarch64/wheel/botocore/data/vpc-lattice creating build/bdist.linux-aarch64/wheel/botocore/data/vpc-lattice/2022-11-30 copying build/lib/botocore/data/vpc-lattice/2022-11-30/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/vpc-lattice/2022-11-30 copying build/lib/botocore/data/vpc-lattice/2022-11-30/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/vpc-lattice/2022-11-30 copying build/lib/botocore/data/vpc-lattice/2022-11-30/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/vpc-lattice/2022-11-30 copying build/lib/botocore/data/vpc-lattice/2022-11-30/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/vpc-lattice/2022-11-30 creating build/bdist.linux-aarch64/wheel/botocore/data/waf-regional creating build/bdist.linux-aarch64/wheel/botocore/data/waf-regional/2016-11-28 copying build/lib/botocore/data/waf-regional/2016-11-28/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/waf-regional/2016-11-28 copying build/lib/botocore/data/waf-regional/2016-11-28/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/waf-regional/2016-11-28 copying build/lib/botocore/data/waf-regional/2016-11-28/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/waf-regional/2016-11-28 copying build/lib/botocore/data/waf-regional/2016-11-28/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/waf-regional/2016-11-28 creating build/bdist.linux-aarch64/wheel/botocore/data/waf creating build/bdist.linux-aarch64/wheel/botocore/data/waf/2015-08-24 copying build/lib/botocore/data/waf/2015-08-24/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/waf/2015-08-24 copying build/lib/botocore/data/waf/2015-08-24/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/waf/2015-08-24 copying build/lib/botocore/data/waf/2015-08-24/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/waf/2015-08-24 copying build/lib/botocore/data/waf/2015-08-24/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/waf/2015-08-24 creating build/bdist.linux-aarch64/wheel/botocore/data/wafv2 creating build/bdist.linux-aarch64/wheel/botocore/data/wafv2/2019-07-29 copying build/lib/botocore/data/wafv2/2019-07-29/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/wafv2/2019-07-29 copying build/lib/botocore/data/wafv2/2019-07-29/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/wafv2/2019-07-29 copying build/lib/botocore/data/wafv2/2019-07-29/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/wafv2/2019-07-29 copying build/lib/botocore/data/wafv2/2019-07-29/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/wafv2/2019-07-29 creating build/bdist.linux-aarch64/wheel/botocore/data/wellarchitected creating build/bdist.linux-aarch64/wheel/botocore/data/wellarchitected/2020-03-31 copying build/lib/botocore/data/wellarchitected/2020-03-31/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/wellarchitected/2020-03-31 copying build/lib/botocore/data/wellarchitected/2020-03-31/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/wellarchitected/2020-03-31 copying build/lib/botocore/data/wellarchitected/2020-03-31/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/wellarchitected/2020-03-31 copying build/lib/botocore/data/wellarchitected/2020-03-31/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/wellarchitected/2020-03-31 creating build/bdist.linux-aarch64/wheel/botocore/data/wickr creating build/bdist.linux-aarch64/wheel/botocore/data/wickr/2024-02-01 copying build/lib/botocore/data/wickr/2024-02-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/wickr/2024-02-01 copying build/lib/botocore/data/wickr/2024-02-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/wickr/2024-02-01 copying build/lib/botocore/data/wickr/2024-02-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/wickr/2024-02-01 copying build/lib/botocore/data/wickr/2024-02-01/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/wickr/2024-02-01 creating build/bdist.linux-aarch64/wheel/botocore/data/wisdom creating build/bdist.linux-aarch64/wheel/botocore/data/wisdom/2020-10-19 copying build/lib/botocore/data/wisdom/2020-10-19/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/wisdom/2020-10-19 copying build/lib/botocore/data/wisdom/2020-10-19/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/wisdom/2020-10-19 copying build/lib/botocore/data/wisdom/2020-10-19/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/wisdom/2020-10-19 copying build/lib/botocore/data/wisdom/2020-10-19/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/wisdom/2020-10-19 creating build/bdist.linux-aarch64/wheel/botocore/data/workdocs creating build/bdist.linux-aarch64/wheel/botocore/data/workdocs/2016-05-01 copying build/lib/botocore/data/workdocs/2016-05-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/workdocs/2016-05-01 copying build/lib/botocore/data/workdocs/2016-05-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/workdocs/2016-05-01 copying build/lib/botocore/data/workdocs/2016-05-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/workdocs/2016-05-01 copying build/lib/botocore/data/workdocs/2016-05-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/workdocs/2016-05-01 creating build/bdist.linux-aarch64/wheel/botocore/data/workmail creating build/bdist.linux-aarch64/wheel/botocore/data/workmail/2017-10-01 copying build/lib/botocore/data/workmail/2017-10-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/workmail/2017-10-01 copying build/lib/botocore/data/workmail/2017-10-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/workmail/2017-10-01 copying build/lib/botocore/data/workmail/2017-10-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/workmail/2017-10-01 copying build/lib/botocore/data/workmail/2017-10-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/workmail/2017-10-01 creating build/bdist.linux-aarch64/wheel/botocore/data/workmailmessageflow creating build/bdist.linux-aarch64/wheel/botocore/data/workmailmessageflow/2019-05-01 copying build/lib/botocore/data/workmailmessageflow/2019-05-01/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/workmailmessageflow/2019-05-01 copying build/lib/botocore/data/workmailmessageflow/2019-05-01/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/workmailmessageflow/2019-05-01 copying build/lib/botocore/data/workmailmessageflow/2019-05-01/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/workmailmessageflow/2019-05-01 copying build/lib/botocore/data/workmailmessageflow/2019-05-01/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/workmailmessageflow/2019-05-01 creating build/bdist.linux-aarch64/wheel/botocore/data/workspaces-instances creating build/bdist.linux-aarch64/wheel/botocore/data/workspaces-instances/2022-07-26 copying build/lib/botocore/data/workspaces-instances/2022-07-26/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/workspaces-instances/2022-07-26 copying build/lib/botocore/data/workspaces-instances/2022-07-26/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/workspaces-instances/2022-07-26 copying build/lib/botocore/data/workspaces-instances/2022-07-26/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/workspaces-instances/2022-07-26 copying build/lib/botocore/data/workspaces-instances/2022-07-26/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/workspaces-instances/2022-07-26 creating build/bdist.linux-aarch64/wheel/botocore/data/workspaces-thin-client creating build/bdist.linux-aarch64/wheel/botocore/data/workspaces-thin-client/2023-08-22 copying build/lib/botocore/data/workspaces-thin-client/2023-08-22/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/workspaces-thin-client/2023-08-22 copying build/lib/botocore/data/workspaces-thin-client/2023-08-22/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/workspaces-thin-client/2023-08-22 copying build/lib/botocore/data/workspaces-thin-client/2023-08-22/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/workspaces-thin-client/2023-08-22 creating build/bdist.linux-aarch64/wheel/botocore/data/workspaces-web creating build/bdist.linux-aarch64/wheel/botocore/data/workspaces-web/2020-07-08 copying build/lib/botocore/data/workspaces-web/2020-07-08/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/workspaces-web/2020-07-08 copying build/lib/botocore/data/workspaces-web/2020-07-08/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/workspaces-web/2020-07-08 copying build/lib/botocore/data/workspaces-web/2020-07-08/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/workspaces-web/2020-07-08 copying build/lib/botocore/data/workspaces-web/2020-07-08/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/workspaces-web/2020-07-08 copying build/lib/botocore/data/workspaces-web/2020-07-08/waiters-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/workspaces-web/2020-07-08 creating build/bdist.linux-aarch64/wheel/botocore/data/workspaces creating build/bdist.linux-aarch64/wheel/botocore/data/workspaces/2015-04-08 copying build/lib/botocore/data/workspaces/2015-04-08/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/workspaces/2015-04-08 copying build/lib/botocore/data/workspaces/2015-04-08/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/workspaces/2015-04-08 copying build/lib/botocore/data/workspaces/2015-04-08/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/workspaces/2015-04-08 copying build/lib/botocore/data/workspaces/2015-04-08/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/workspaces/2015-04-08 creating build/bdist.linux-aarch64/wheel/botocore/data/xray creating build/bdist.linux-aarch64/wheel/botocore/data/xray/2016-04-12 copying build/lib/botocore/data/xray/2016-04-12/endpoint-rule-set-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/xray/2016-04-12 copying build/lib/botocore/data/xray/2016-04-12/examples-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/xray/2016-04-12 copying build/lib/botocore/data/xray/2016-04-12/paginators-1.json -> build/bdist.linux-aarch64/wheel/botocore/data/xray/2016-04-12 copying build/lib/botocore/data/xray/2016-04-12/service-2.json -> build/bdist.linux-aarch64/wheel/botocore/data/xray/2016-04-12 running install_egg_info Copying botocore.egg-info to build/bdist.linux-aarch64/wheel/botocore-1.42.97-py3.11.egg-info running install_scripts creating build/bdist.linux-aarch64/wheel/botocore-1.42.97.dist-info/WHEEL creating '/builddir/build/BUILD/botocore-1.42.97/.pyproject-builddir/pip-wheel-vy6wauxg/.tmp-yy35jfgj/botocore-1.42.97-py3-none-any.whl' and adding 'build/bdist.linux-aarch64/wheel' to it adding 'botocore/__init__.py' adding 'botocore/args.py' adding 'botocore/auth.py' adding 'botocore/awsrequest.py' adding 'botocore/cacert.pem' adding 'botocore/client.py' adding 'botocore/compat.py' adding 'botocore/compress.py' adding 'botocore/config.py' adding 'botocore/configloader.py' adding 'botocore/configprovider.py' adding 'botocore/context.py' adding 'botocore/credentials.py' adding 'botocore/discovery.py' adding 'botocore/endpoint.py' adding 'botocore/endpoint_provider.py' adding 'botocore/errorfactory.py' adding 'botocore/eventstream.py' adding 'botocore/exceptions.py' adding 'botocore/handlers.py' adding 'botocore/history.py' adding 'botocore/hooks.py' adding 'botocore/httpchecksum.py' adding 'botocore/httpsession.py' adding 'botocore/loaders.py' adding 'botocore/model.py' adding 'botocore/monitoring.py' adding 'botocore/paginate.py' adding 'botocore/parsers.py' adding 'botocore/plugin.py' adding 'botocore/regions.py' adding 'botocore/response.py' adding 'botocore/retryhandler.py' adding 'botocore/serialize.py' adding 'botocore/session.py' adding 'botocore/signers.py' adding 'botocore/stub.py' adding 'botocore/tokens.py' adding 'botocore/translate.py' adding 'botocore/useragent.py' adding 'botocore/utils.py' adding 'botocore/validate.py' adding 'botocore/waiter.py' adding 'botocore/crt/__init__.py' adding 'botocore/crt/auth.py' adding 'botocore/data/_retry.json' adding 'botocore/data/endpoints.json' adding 'botocore/data/partitions.json' adding 'botocore/data/sdk-default-configuration.json' adding 'botocore/data/accessanalyzer/2019-11-01/endpoint-rule-set-1.json' adding 'botocore/data/accessanalyzer/2019-11-01/examples-1.json' adding 'botocore/data/accessanalyzer/2019-11-01/paginators-1.json' adding 'botocore/data/accessanalyzer/2019-11-01/paginators-1.sdk-extras.json' adding 'botocore/data/accessanalyzer/2019-11-01/service-2.json' adding 'botocore/data/account/2021-02-01/endpoint-rule-set-1.json' adding 'botocore/data/account/2021-02-01/examples-1.json' adding 'botocore/data/account/2021-02-01/paginators-1.json' adding 'botocore/data/account/2021-02-01/service-2.json' adding 'botocore/data/acm/2015-12-08/endpoint-rule-set-1.json' adding 'botocore/data/acm/2015-12-08/examples-1.json' adding 'botocore/data/acm/2015-12-08/paginators-1.json' adding 'botocore/data/acm/2015-12-08/service-2.json' adding 'botocore/data/acm/2015-12-08/waiters-2.json' adding 'botocore/data/acm-pca/2017-08-22/endpoint-rule-set-1.json' adding 'botocore/data/acm-pca/2017-08-22/examples-1.json' adding 'botocore/data/acm-pca/2017-08-22/paginators-1.json' adding 'botocore/data/acm-pca/2017-08-22/service-2.json' adding 'botocore/data/acm-pca/2017-08-22/waiters-2.json' adding 'botocore/data/aiops/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/aiops/2018-05-10/paginators-1.json' adding 'botocore/data/aiops/2018-05-10/service-2.json' adding 'botocore/data/aiops/2018-05-10/waiters-2.json' adding 'botocore/data/amp/2020-08-01/endpoint-rule-set-1.json' adding 'botocore/data/amp/2020-08-01/examples-1.json' adding 'botocore/data/amp/2020-08-01/paginators-1.json' adding 'botocore/data/amp/2020-08-01/service-2.json' adding 'botocore/data/amp/2020-08-01/waiters-2.json' adding 'botocore/data/amplify/2017-07-25/endpoint-rule-set-1.json' adding 'botocore/data/amplify/2017-07-25/examples-1.json' adding 'botocore/data/amplify/2017-07-25/paginators-1.json' adding 'botocore/data/amplify/2017-07-25/service-2.json' adding 'botocore/data/amplifybackend/2020-08-11/endpoint-rule-set-1.json' adding 'botocore/data/amplifybackend/2020-08-11/paginators-1.json' adding 'botocore/data/amplifybackend/2020-08-11/service-2.json' adding 'botocore/data/amplifyuibuilder/2021-08-11/endpoint-rule-set-1.json' adding 'botocore/data/amplifyuibuilder/2021-08-11/examples-1.json' adding 'botocore/data/amplifyuibuilder/2021-08-11/paginators-1.json' adding 'botocore/data/amplifyuibuilder/2021-08-11/service-2.json' adding 'botocore/data/amplifyuibuilder/2021-08-11/waiters-2.json' adding 'botocore/data/apigateway/2015-07-09/endpoint-rule-set-1.json' adding 'botocore/data/apigateway/2015-07-09/examples-1.json' adding 'botocore/data/apigateway/2015-07-09/paginators-1.json' adding 'botocore/data/apigateway/2015-07-09/service-2.json' adding 'botocore/data/apigatewaymanagementapi/2018-11-29/endpoint-rule-set-1.json' adding 'botocore/data/apigatewaymanagementapi/2018-11-29/paginators-1.json' adding 'botocore/data/apigatewaymanagementapi/2018-11-29/service-2.json' adding 'botocore/data/apigatewayv2/2018-11-29/endpoint-rule-set-1.json' adding 'botocore/data/apigatewayv2/2018-11-29/paginators-1.json' adding 'botocore/data/apigatewayv2/2018-11-29/service-2.json' adding 'botocore/data/appconfig/2019-10-09/endpoint-rule-set-1.json' adding 'botocore/data/appconfig/2019-10-09/examples-1.json' adding 'botocore/data/appconfig/2019-10-09/paginators-1.json' adding 'botocore/data/appconfig/2019-10-09/service-2.json' adding 'botocore/data/appconfig/2019-10-09/waiters-2.json' adding 'botocore/data/appconfigdata/2021-11-11/endpoint-rule-set-1.json' adding 'botocore/data/appconfigdata/2021-11-11/examples-1.json' adding 'botocore/data/appconfigdata/2021-11-11/paginators-1.json' adding 'botocore/data/appconfigdata/2021-11-11/service-2.json' adding 'botocore/data/appfabric/2023-05-19/endpoint-rule-set-1.json' adding 'botocore/data/appfabric/2023-05-19/paginators-1.json' adding 'botocore/data/appfabric/2023-05-19/service-2.json' adding 'botocore/data/appfabric/2023-05-19/waiters-2.json' adding 'botocore/data/appflow/2020-08-23/endpoint-rule-set-1.json' adding 'botocore/data/appflow/2020-08-23/examples-1.json' adding 'botocore/data/appflow/2020-08-23/paginators-1.json' adding 'botocore/data/appflow/2020-08-23/service-2.json' adding 'botocore/data/appintegrations/2020-07-29/endpoint-rule-set-1.json' adding 'botocore/data/appintegrations/2020-07-29/examples-1.json' adding 'botocore/data/appintegrations/2020-07-29/paginators-1.json' adding 'botocore/data/appintegrations/2020-07-29/service-2.json' adding 'botocore/data/application-autoscaling/2016-02-06/endpoint-rule-set-1.json' adding 'botocore/data/application-autoscaling/2016-02-06/examples-1.json' adding 'botocore/data/application-autoscaling/2016-02-06/paginators-1.json' adding 'botocore/data/application-autoscaling/2016-02-06/service-2.json' adding 'botocore/data/application-insights/2018-11-25/endpoint-rule-set-1.json' adding 'botocore/data/application-insights/2018-11-25/examples-1.json' adding 'botocore/data/application-insights/2018-11-25/paginators-1.json' adding 'botocore/data/application-insights/2018-11-25/service-2.json' adding 'botocore/data/application-signals/2024-04-15/endpoint-rule-set-1.json' adding 'botocore/data/application-signals/2024-04-15/paginators-1.json' adding 'botocore/data/application-signals/2024-04-15/paginators-1.sdk-extras.json' adding 'botocore/data/application-signals/2024-04-15/service-2.json' adding 'botocore/data/application-signals/2024-04-15/waiters-2.json' adding 'botocore/data/applicationcostprofiler/2020-09-10/endpoint-rule-set-1.json' adding 'botocore/data/applicationcostprofiler/2020-09-10/examples-1.json' adding 'botocore/data/applicationcostprofiler/2020-09-10/paginators-1.json' adding 'botocore/data/applicationcostprofiler/2020-09-10/service-2.json' adding 'botocore/data/appmesh/2018-10-01/endpoint-rule-set-1.json' adding 'botocore/data/appmesh/2018-10-01/examples-1.json' adding 'botocore/data/appmesh/2018-10-01/paginators-1.json' adding 'botocore/data/appmesh/2018-10-01/service-2.json' adding 'botocore/data/appmesh/2019-01-25/endpoint-rule-set-1.json' adding 'botocore/data/appmesh/2019-01-25/examples-1.json' adding 'botocore/data/appmesh/2019-01-25/paginators-1.json' adding 'botocore/data/appmesh/2019-01-25/service-2.json' adding 'botocore/data/apprunner/2020-05-15/endpoint-rule-set-1.json' adding 'botocore/data/apprunner/2020-05-15/examples-1.json' adding 'botocore/data/apprunner/2020-05-15/paginators-1.json' adding 'botocore/data/apprunner/2020-05-15/service-2.json' adding 'botocore/data/appstream/2016-12-01/endpoint-rule-set-1.json' adding 'botocore/data/appstream/2016-12-01/examples-1.json' adding 'botocore/data/appstream/2016-12-01/paginators-1.json' adding 'botocore/data/appstream/2016-12-01/service-2.json' adding 'botocore/data/appstream/2016-12-01/waiters-2.json' adding 'botocore/data/appsync/2017-07-25/endpoint-rule-set-1.json' adding 'botocore/data/appsync/2017-07-25/examples-1.json' adding 'botocore/data/appsync/2017-07-25/paginators-1.json' adding 'botocore/data/appsync/2017-07-25/service-2.json' adding 'botocore/data/arc-region-switch/2022-07-26/endpoint-rule-set-1.json' adding 'botocore/data/arc-region-switch/2022-07-26/paginators-1.json' adding 'botocore/data/arc-region-switch/2022-07-26/paginators-1.sdk-extras.json' adding 'botocore/data/arc-region-switch/2022-07-26/service-2.json' adding 'botocore/data/arc-region-switch/2022-07-26/waiters-2.json' adding 'botocore/data/arc-zonal-shift/2022-10-30/endpoint-rule-set-1.json' adding 'botocore/data/arc-zonal-shift/2022-10-30/paginators-1.json' adding 'botocore/data/arc-zonal-shift/2022-10-30/service-2.json' adding 'botocore/data/arc-zonal-shift/2022-10-30/waiters-2.json' adding 'botocore/data/artifact/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/artifact/2018-05-10/paginators-1.json' adding 'botocore/data/artifact/2018-05-10/service-2.json' adding 'botocore/data/artifact/2018-05-10/waiters-2.json' adding 'botocore/data/athena/2017-05-18/endpoint-rule-set-1.json' adding 'botocore/data/athena/2017-05-18/examples-1.json' adding 'botocore/data/athena/2017-05-18/paginators-1.json' adding 'botocore/data/athena/2017-05-18/service-2.json' adding 'botocore/data/auditmanager/2017-07-25/endpoint-rule-set-1.json' adding 'botocore/data/auditmanager/2017-07-25/examples-1.json' adding 'botocore/data/auditmanager/2017-07-25/paginators-1.json' adding 'botocore/data/auditmanager/2017-07-25/service-2.json' adding 'botocore/data/autoscaling/2011-01-01/endpoint-rule-set-1.json' adding 'botocore/data/autoscaling/2011-01-01/examples-1.json' adding 'botocore/data/autoscaling/2011-01-01/paginators-1.json' adding 'botocore/data/autoscaling/2011-01-01/paginators-1.sdk-extras.json' adding 'botocore/data/autoscaling/2011-01-01/service-2.json' adding 'botocore/data/autoscaling-plans/2018-01-06/endpoint-rule-set-1.json' adding 'botocore/data/autoscaling-plans/2018-01-06/examples-1.json' adding 'botocore/data/autoscaling-plans/2018-01-06/paginators-1.json' adding 'botocore/data/autoscaling-plans/2018-01-06/service-2.json' adding 'botocore/data/b2bi/2022-06-23/endpoint-rule-set-1.json' adding 'botocore/data/b2bi/2022-06-23/paginators-1.json' adding 'botocore/data/b2bi/2022-06-23/service-2.json' adding 'botocore/data/b2bi/2022-06-23/waiters-2.json' adding 'botocore/data/backup/2018-11-15/endpoint-rule-set-1.json' adding 'botocore/data/backup/2018-11-15/examples-1.json' adding 'botocore/data/backup/2018-11-15/paginators-1.json' adding 'botocore/data/backup/2018-11-15/paginators-1.sdk-extras.json' adding 'botocore/data/backup/2018-11-15/service-2.json' adding 'botocore/data/backup-gateway/2021-01-01/endpoint-rule-set-1.json' adding 'botocore/data/backup-gateway/2021-01-01/examples-1.json' adding 'botocore/data/backup-gateway/2021-01-01/paginators-1.json' adding 'botocore/data/backup-gateway/2021-01-01/service-2.json' adding 'botocore/data/backupsearch/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/backupsearch/2018-05-10/paginators-1.json' adding 'botocore/data/backupsearch/2018-05-10/service-2.json' adding 'botocore/data/backupsearch/2018-05-10/waiters-2.json' adding 'botocore/data/batch/2016-08-10/endpoint-rule-set-1.json' adding 'botocore/data/batch/2016-08-10/examples-1.json' adding 'botocore/data/batch/2016-08-10/paginators-1.json' adding 'botocore/data/batch/2016-08-10/service-2.json' adding 'botocore/data/bcm-dashboards/2025-08-18/endpoint-rule-set-1.json' adding 'botocore/data/bcm-dashboards/2025-08-18/paginators-1.json' adding 'botocore/data/bcm-dashboards/2025-08-18/service-2.json' adding 'botocore/data/bcm-dashboards/2025-08-18/waiters-2.json' adding 'botocore/data/bcm-data-exports/2023-11-26/endpoint-rule-set-1.json' adding 'botocore/data/bcm-data-exports/2023-11-26/paginators-1.json' adding 'botocore/data/bcm-data-exports/2023-11-26/service-2.json' adding 'botocore/data/bcm-pricing-calculator/2024-06-19/endpoint-rule-set-1.json' adding 'botocore/data/bcm-pricing-calculator/2024-06-19/paginators-1.json' adding 'botocore/data/bcm-pricing-calculator/2024-06-19/service-2.json' adding 'botocore/data/bcm-pricing-calculator/2024-06-19/waiters-2.json' adding 'botocore/data/bcm-recommended-actions/2024-11-14/endpoint-rule-set-1.json' adding 'botocore/data/bcm-recommended-actions/2024-11-14/paginators-1.json' adding 'botocore/data/bcm-recommended-actions/2024-11-14/service-2.json' adding 'botocore/data/bcm-recommended-actions/2024-11-14/waiters-2.json' adding 'botocore/data/bedrock/2023-04-20/endpoint-rule-set-1.json' adding 'botocore/data/bedrock/2023-04-20/paginators-1.json' adding 'botocore/data/bedrock/2023-04-20/service-2.json' adding 'botocore/data/bedrock/2023-04-20/waiters-2.json' adding 'botocore/data/bedrock-agent/2023-06-05/endpoint-rule-set-1.json' adding 'botocore/data/bedrock-agent/2023-06-05/paginators-1.json' adding 'botocore/data/bedrock-agent/2023-06-05/service-2.json' adding 'botocore/data/bedrock-agent/2023-06-05/waiters-2.json' adding 'botocore/data/bedrock-agent-runtime/2023-07-26/endpoint-rule-set-1.json' adding 'botocore/data/bedrock-agent-runtime/2023-07-26/paginators-1.json' adding 'botocore/data/bedrock-agent-runtime/2023-07-26/paginators-1.sdk-extras.json' adding 'botocore/data/bedrock-agent-runtime/2023-07-26/service-2.json' adding 'botocore/data/bedrock-agent-runtime/2023-07-26/waiters-2.json' adding 'botocore/data/bedrock-agentcore/2024-02-28/endpoint-rule-set-1.json' adding 'botocore/data/bedrock-agentcore/2024-02-28/paginators-1.json' adding 'botocore/data/bedrock-agentcore/2024-02-28/service-2.json' adding 'botocore/data/bedrock-agentcore/2024-02-28/waiters-2.json' adding 'botocore/data/bedrock-agentcore-control/2023-06-05/endpoint-rule-set-1.json' adding 'botocore/data/bedrock-agentcore-control/2023-06-05/paginators-1.json' adding 'botocore/data/bedrock-agentcore-control/2023-06-05/service-2.json' adding 'botocore/data/bedrock-agentcore-control/2023-06-05/waiters-2.json' adding 'botocore/data/bedrock-data-automation/2023-07-26/endpoint-rule-set-1.json' adding 'botocore/data/bedrock-data-automation/2023-07-26/paginators-1.json' adding 'botocore/data/bedrock-data-automation/2023-07-26/service-2.json' adding 'botocore/data/bedrock-data-automation-runtime/2024-06-13/endpoint-rule-set-1.json' adding 'botocore/data/bedrock-data-automation-runtime/2024-06-13/paginators-1.json' adding 'botocore/data/bedrock-data-automation-runtime/2024-06-13/service-2.json' adding 'botocore/data/bedrock-runtime/2023-09-30/endpoint-rule-set-1.json' adding 'botocore/data/bedrock-runtime/2023-09-30/paginators-1.json' adding 'botocore/data/bedrock-runtime/2023-09-30/service-2.json' adding 'botocore/data/bedrock-runtime/2023-09-30/waiters-2.json' adding 'botocore/data/billing/2023-09-07/endpoint-rule-set-1.json' adding 'botocore/data/billing/2023-09-07/paginators-1.json' adding 'botocore/data/billing/2023-09-07/service-2.json' adding 'botocore/data/billing/2023-09-07/waiters-2.json' adding 'botocore/data/billingconductor/2021-07-30/endpoint-rule-set-1.json' adding 'botocore/data/billingconductor/2021-07-30/examples-1.json' adding 'botocore/data/billingconductor/2021-07-30/paginators-1.json' adding 'botocore/data/billingconductor/2021-07-30/service-2.json' adding 'botocore/data/billingconductor/2021-07-30/waiters-2.json' adding 'botocore/data/braket/2019-09-01/endpoint-rule-set-1.json' adding 'botocore/data/braket/2019-09-01/examples-1.json' adding 'botocore/data/braket/2019-09-01/paginators-1.json' adding 'botocore/data/braket/2019-09-01/service-2.json' adding 'botocore/data/budgets/2016-10-20/endpoint-rule-set-1.json' adding 'botocore/data/budgets/2016-10-20/examples-1.json' adding 'botocore/data/budgets/2016-10-20/paginators-1.json' adding 'botocore/data/budgets/2016-10-20/service-2.json' adding 'botocore/data/ce/2017-10-25/endpoint-rule-set-1.json' adding 'botocore/data/ce/2017-10-25/examples-1.json' adding 'botocore/data/ce/2017-10-25/paginators-1.json' adding 'botocore/data/ce/2017-10-25/paginators-1.sdk-extras.json' adding 'botocore/data/ce/2017-10-25/service-2.json' adding 'botocore/data/chatbot/2017-10-11/endpoint-rule-set-1.json' adding 'botocore/data/chatbot/2017-10-11/paginators-1.json' adding 'botocore/data/chatbot/2017-10-11/service-2.json' adding 'botocore/data/chime/2018-05-01/endpoint-rule-set-1.json' adding 'botocore/data/chime/2018-05-01/examples-1.json' adding 'botocore/data/chime/2018-05-01/paginators-1.json' adding 'botocore/data/chime/2018-05-01/service-2.json' adding 'botocore/data/chime-sdk-identity/2021-04-20/endpoint-rule-set-1.json' adding 'botocore/data/chime-sdk-identity/2021-04-20/examples-1.json' adding 'botocore/data/chime-sdk-identity/2021-04-20/paginators-1.json' adding 'botocore/data/chime-sdk-identity/2021-04-20/service-2.json' adding 'botocore/data/chime-sdk-media-pipelines/2021-07-15/endpoint-rule-set-1.json' adding 'botocore/data/chime-sdk-media-pipelines/2021-07-15/paginators-1.json' adding 'botocore/data/chime-sdk-media-pipelines/2021-07-15/service-2.json' adding 'botocore/data/chime-sdk-meetings/2021-07-15/endpoint-rule-set-1.json' adding 'botocore/data/chime-sdk-meetings/2021-07-15/examples-1.json' adding 'botocore/data/chime-sdk-meetings/2021-07-15/paginators-1.json' adding 'botocore/data/chime-sdk-meetings/2021-07-15/service-2.json' adding 'botocore/data/chime-sdk-messaging/2021-05-15/endpoint-rule-set-1.json' adding 'botocore/data/chime-sdk-messaging/2021-05-15/examples-1.json' adding 'botocore/data/chime-sdk-messaging/2021-05-15/paginators-1.json' adding 'botocore/data/chime-sdk-messaging/2021-05-15/service-2.json' adding 'botocore/data/chime-sdk-voice/2022-08-03/endpoint-rule-set-1.json' adding 'botocore/data/chime-sdk-voice/2022-08-03/paginators-1.json' adding 'botocore/data/chime-sdk-voice/2022-08-03/service-2.json' adding 'botocore/data/cleanrooms/2022-02-17/endpoint-rule-set-1.json' adding 'botocore/data/cleanrooms/2022-02-17/paginators-1.json' adding 'botocore/data/cleanrooms/2022-02-17/service-2.json' adding 'botocore/data/cleanrooms/2022-02-17/waiters-2.json' adding 'botocore/data/cleanroomsml/2023-09-06/endpoint-rule-set-1.json' adding 'botocore/data/cleanroomsml/2023-09-06/paginators-1.json' adding 'botocore/data/cleanroomsml/2023-09-06/service-2.json' adding 'botocore/data/cleanroomsml/2023-09-06/waiters-2.json' adding 'botocore/data/cloud9/2017-09-23/endpoint-rule-set-1.json' adding 'botocore/data/cloud9/2017-09-23/examples-1.json' adding 'botocore/data/cloud9/2017-09-23/paginators-1.json' adding 'botocore/data/cloud9/2017-09-23/service-2.json' adding 'botocore/data/cloudcontrol/2021-09-30/endpoint-rule-set-1.json' adding 'botocore/data/cloudcontrol/2021-09-30/examples-1.json' adding 'botocore/data/cloudcontrol/2021-09-30/paginators-1.json' adding 'botocore/data/cloudcontrol/2021-09-30/paginators-1.sdk-extras.json' adding 'botocore/data/cloudcontrol/2021-09-30/service-2.json' adding 'botocore/data/cloudcontrol/2021-09-30/waiters-2.json' adding 'botocore/data/clouddirectory/2016-05-10/endpoint-rule-set-1.json' adding 'botocore/data/clouddirectory/2016-05-10/examples-1.json' adding 'botocore/data/clouddirectory/2016-05-10/paginators-1.json' adding 'botocore/data/clouddirectory/2016-05-10/service-2.json' adding 'botocore/data/clouddirectory/2017-01-11/endpoint-rule-set-1.json' adding 'botocore/data/clouddirectory/2017-01-11/examples-1.json' adding 'botocore/data/clouddirectory/2017-01-11/paginators-1.json' adding 'botocore/data/clouddirectory/2017-01-11/service-2.json' adding 'botocore/data/cloudformation/2010-05-15/endpoint-rule-set-1.json' adding 'botocore/data/cloudformation/2010-05-15/examples-1.json' adding 'botocore/data/cloudformation/2010-05-15/paginators-1.json' adding 'botocore/data/cloudformation/2010-05-15/service-2.json' adding 'botocore/data/cloudformation/2010-05-15/waiters-2.json' adding 'botocore/data/cloudfront/2014-05-31/endpoint-rule-set-1.json' adding 'botocore/data/cloudfront/2014-05-31/paginators-1.json' adding 'botocore/data/cloudfront/2014-05-31/service-2.json' adding 'botocore/data/cloudfront/2014-05-31/waiters-2.json' adding 'botocore/data/cloudfront/2014-10-21/endpoint-rule-set-1.json' adding 'botocore/data/cloudfront/2014-10-21/paginators-1.json' adding 'botocore/data/cloudfront/2014-10-21/service-2.json' adding 'botocore/data/cloudfront/2014-10-21/waiters-2.json' adding 'botocore/data/cloudfront/2014-11-06/endpoint-rule-set-1.json' adding 'botocore/data/cloudfront/2014-11-06/paginators-1.json' adding 'botocore/data/cloudfront/2014-11-06/service-2.json' adding 'botocore/data/cloudfront/2014-11-06/waiters-2.json' adding 'botocore/data/cloudfront/2015-04-17/endpoint-rule-set-1.json' adding 'botocore/data/cloudfront/2015-04-17/paginators-1.json' adding 'botocore/data/cloudfront/2015-04-17/service-2.json' adding 'botocore/data/cloudfront/2015-04-17/waiters-2.json' adding 'botocore/data/cloudfront/2015-07-27/endpoint-rule-set-1.json' adding 'botocore/data/cloudfront/2015-07-27/paginators-1.json' adding 'botocore/data/cloudfront/2015-07-27/service-2.json' adding 'botocore/data/cloudfront/2015-07-27/waiters-2.json' adding 'botocore/data/cloudfront/2015-09-17/endpoint-rule-set-1.json' adding 'botocore/data/cloudfront/2015-09-17/paginators-1.json' adding 'botocore/data/cloudfront/2015-09-17/service-2.json' adding 'botocore/data/cloudfront/2015-09-17/waiters-2.json' adding 'botocore/data/cloudfront/2016-01-13/endpoint-rule-set-1.json' adding 'botocore/data/cloudfront/2016-01-13/paginators-1.json' adding 'botocore/data/cloudfront/2016-01-13/service-2.json' adding 'botocore/data/cloudfront/2016-01-13/waiters-2.json' adding 'botocore/data/cloudfront/2016-01-28/endpoint-rule-set-1.json' adding 'botocore/data/cloudfront/2016-01-28/examples-1.json' adding 'botocore/data/cloudfront/2016-01-28/paginators-1.json' adding 'botocore/data/cloudfront/2016-01-28/service-2.json' adding 'botocore/data/cloudfront/2016-01-28/waiters-2.json' adding 'botocore/data/cloudfront/2016-08-01/endpoint-rule-set-1.json' adding 'botocore/data/cloudfront/2016-08-01/examples-1.json' adding 'botocore/data/cloudfront/2016-08-01/paginators-1.json' adding 'botocore/data/cloudfront/2016-08-01/service-2.json' adding 'botocore/data/cloudfront/2016-08-01/waiters-2.json' adding 'botocore/data/cloudfront/2016-08-20/endpoint-rule-set-1.json' adding 'botocore/data/cloudfront/2016-08-20/paginators-1.json' adding 'botocore/data/cloudfront/2016-08-20/service-2.json' adding 'botocore/data/cloudfront/2016-08-20/waiters-2.json' adding 'botocore/data/cloudfront/2016-09-07/endpoint-rule-set-1.json' adding 'botocore/data/cloudfront/2016-09-07/examples-1.json' adding 'botocore/data/cloudfront/2016-09-07/paginators-1.json' adding 'botocore/data/cloudfront/2016-09-07/service-2.json' adding 'botocore/data/cloudfront/2016-09-07/waiters-2.json' adding 'botocore/data/cloudfront/2016-09-29/endpoint-rule-set-1.json' adding 'botocore/data/cloudfront/2016-09-29/examples-1.json' adding 'botocore/data/cloudfront/2016-09-29/paginators-1.json' adding 'botocore/data/cloudfront/2016-09-29/service-2.json' adding 'botocore/data/cloudfront/2016-09-29/waiters-2.json' adding 'botocore/data/cloudfront/2016-11-25/endpoint-rule-set-1.json' adding 'botocore/data/cloudfront/2016-11-25/examples-1.json' adding 'botocore/data/cloudfront/2016-11-25/paginators-1.json' adding 'botocore/data/cloudfront/2016-11-25/service-2.json' adding 'botocore/data/cloudfront/2016-11-25/waiters-2.json' adding 'botocore/data/cloudfront/2017-03-25/endpoint-rule-set-1.json' adding 'botocore/data/cloudfront/2017-03-25/paginators-1.json' adding 'botocore/data/cloudfront/2017-03-25/service-2.json' adding 'botocore/data/cloudfront/2017-03-25/waiters-2.json' adding 'botocore/data/cloudfront/2017-10-30/endpoint-rule-set-1.json' adding 'botocore/data/cloudfront/2017-10-30/examples-1.json' adding 'botocore/data/cloudfront/2017-10-30/paginators-1.json' adding 'botocore/data/cloudfront/2017-10-30/service-2.json' adding 'botocore/data/cloudfront/2017-10-30/waiters-2.json' adding 'botocore/data/cloudfront/2018-06-18/endpoint-rule-set-1.json' adding 'botocore/data/cloudfront/2018-06-18/examples-1.json' adding 'botocore/data/cloudfront/2018-06-18/paginators-1.json' adding 'botocore/data/cloudfront/2018-06-18/service-2.json' adding 'botocore/data/cloudfront/2018-06-18/waiters-2.json' adding 'botocore/data/cloudfront/2018-11-05/endpoint-rule-set-1.json' adding 'botocore/data/cloudfront/2018-11-05/examples-1.json' adding 'botocore/data/cloudfront/2018-11-05/paginators-1.json' adding 'botocore/data/cloudfront/2018-11-05/service-2.json' adding 'botocore/data/cloudfront/2018-11-05/waiters-2.json' adding 'botocore/data/cloudfront/2019-03-26/endpoint-rule-set-1.json' adding 'botocore/data/cloudfront/2019-03-26/examples-1.json' adding 'botocore/data/cloudfront/2019-03-26/paginators-1.json' adding 'botocore/data/cloudfront/2019-03-26/service-2.json' adding 'botocore/data/cloudfront/2019-03-26/waiters-2.json' adding 'botocore/data/cloudfront/2020-05-31/endpoint-rule-set-1.json' adding 'botocore/data/cloudfront/2020-05-31/examples-1.json' adding 'botocore/data/cloudfront/2020-05-31/paginators-1.json' adding 'botocore/data/cloudfront/2020-05-31/service-2.json' adding 'botocore/data/cloudfront/2020-05-31/waiters-2.json' adding 'botocore/data/cloudfront-keyvaluestore/2022-07-26/endpoint-rule-set-1.json' adding 'botocore/data/cloudfront-keyvaluestore/2022-07-26/paginators-1.json' adding 'botocore/data/cloudfront-keyvaluestore/2022-07-26/service-2.json' adding 'botocore/data/cloudhsm/2014-05-30/endpoint-rule-set-1.json' adding 'botocore/data/cloudhsm/2014-05-30/examples-1.json' adding 'botocore/data/cloudhsm/2014-05-30/paginators-1.json' adding 'botocore/data/cloudhsm/2014-05-30/service-2.json' adding 'botocore/data/cloudhsmv2/2017-04-28/endpoint-rule-set-1.json' adding 'botocore/data/cloudhsmv2/2017-04-28/examples-1.json' adding 'botocore/data/cloudhsmv2/2017-04-28/paginators-1.json' adding 'botocore/data/cloudhsmv2/2017-04-28/service-2.json' adding 'botocore/data/cloudsearch/2011-02-01/endpoint-rule-set-1.json' adding 'botocore/data/cloudsearch/2011-02-01/service-2.json' adding 'botocore/data/cloudsearch/2013-01-01/endpoint-rule-set-1.json' adding 'botocore/data/cloudsearch/2013-01-01/examples-1.json' adding 'botocore/data/cloudsearch/2013-01-01/paginators-1.json' adding 'botocore/data/cloudsearch/2013-01-01/service-2.json' adding 'botocore/data/cloudsearchdomain/2013-01-01/endpoint-rule-set-1.json' adding 'botocore/data/cloudsearchdomain/2013-01-01/examples-1.json' adding 'botocore/data/cloudsearchdomain/2013-01-01/paginators-1.json' adding 'botocore/data/cloudsearchdomain/2013-01-01/service-2.json' adding 'botocore/data/cloudtrail/2013-11-01/endpoint-rule-set-1.json' adding 'botocore/data/cloudtrail/2013-11-01/examples-1.json' adding 'botocore/data/cloudtrail/2013-11-01/paginators-1.json' adding 'botocore/data/cloudtrail/2013-11-01/service-2.json' adding 'botocore/data/cloudtrail-data/2021-08-11/endpoint-rule-set-1.json' adding 'botocore/data/cloudtrail-data/2021-08-11/paginators-1.json' adding 'botocore/data/cloudtrail-data/2021-08-11/service-2.json' adding 'botocore/data/cloudwatch/2010-08-01/endpoint-rule-set-1.json' adding 'botocore/data/cloudwatch/2010-08-01/examples-1.json' adding 'botocore/data/cloudwatch/2010-08-01/paginators-1.json' adding 'botocore/data/cloudwatch/2010-08-01/service-2.json' adding 'botocore/data/cloudwatch/2010-08-01/waiters-2.json' adding 'botocore/data/codeartifact/2018-09-22/endpoint-rule-set-1.json' adding 'botocore/data/codeartifact/2018-09-22/examples-1.json' adding 'botocore/data/codeartifact/2018-09-22/paginators-1.json' adding 'botocore/data/codeartifact/2018-09-22/paginators-1.sdk-extras.json' adding 'botocore/data/codeartifact/2018-09-22/service-2.json' adding 'botocore/data/codebuild/2016-10-06/endpoint-rule-set-1.json' adding 'botocore/data/codebuild/2016-10-06/examples-1.json' adding 'botocore/data/codebuild/2016-10-06/paginators-1.json' adding 'botocore/data/codebuild/2016-10-06/service-2.json' adding 'botocore/data/codecatalyst/2022-09-28/endpoint-rule-set-1.json' adding 'botocore/data/codecatalyst/2022-09-28/paginators-1.json' adding 'botocore/data/codecatalyst/2022-09-28/service-2.json' adding 'botocore/data/codecatalyst/2022-09-28/waiters-2.json' adding 'botocore/data/codecommit/2015-04-13/endpoint-rule-set-1.json' adding 'botocore/data/codecommit/2015-04-13/examples-1.json' adding 'botocore/data/codecommit/2015-04-13/paginators-1.json' adding 'botocore/data/codecommit/2015-04-13/service-2.json' adding 'botocore/data/codeconnections/2023-12-01/endpoint-rule-set-1.json' adding 'botocore/data/codeconnections/2023-12-01/paginators-1.json' adding 'botocore/data/codeconnections/2023-12-01/service-2.json' adding 'botocore/data/codedeploy/2014-10-06/endpoint-rule-set-1.json' adding 'botocore/data/codedeploy/2014-10-06/examples-1.json' adding 'botocore/data/codedeploy/2014-10-06/paginators-1.json' adding 'botocore/data/codedeploy/2014-10-06/service-2.json' adding 'botocore/data/codedeploy/2014-10-06/waiters-2.json' adding 'botocore/data/codeguru-reviewer/2019-09-19/endpoint-rule-set-1.json' adding 'botocore/data/codeguru-reviewer/2019-09-19/examples-1.json' adding 'botocore/data/codeguru-reviewer/2019-09-19/paginators-1.json' adding 'botocore/data/codeguru-reviewer/2019-09-19/service-2.json' adding 'botocore/data/codeguru-reviewer/2019-09-19/waiters-2.json' adding 'botocore/data/codeguru-security/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/codeguru-security/2018-05-10/paginators-1.json' adding 'botocore/data/codeguru-security/2018-05-10/service-2.json' adding 'botocore/data/codeguru-security/2018-05-10/waiters-2.json' adding 'botocore/data/codeguruprofiler/2019-07-18/endpoint-rule-set-1.json' adding 'botocore/data/codeguruprofiler/2019-07-18/examples-1.json' adding 'botocore/data/codeguruprofiler/2019-07-18/paginators-1.json' adding 'botocore/data/codeguruprofiler/2019-07-18/service-2.json' adding 'botocore/data/codepipeline/2015-07-09/endpoint-rule-set-1.json' adding 'botocore/data/codepipeline/2015-07-09/examples-1.json' adding 'botocore/data/codepipeline/2015-07-09/paginators-1.json' adding 'botocore/data/codepipeline/2015-07-09/service-2.json' adding 'botocore/data/codestar-connections/2019-12-01/endpoint-rule-set-1.json' adding 'botocore/data/codestar-connections/2019-12-01/examples-1.json' adding 'botocore/data/codestar-connections/2019-12-01/paginators-1.json' adding 'botocore/data/codestar-connections/2019-12-01/service-2.json' adding 'botocore/data/codestar-notifications/2019-10-15/endpoint-rule-set-1.json' adding 'botocore/data/codestar-notifications/2019-10-15/examples-1.json' adding 'botocore/data/codestar-notifications/2019-10-15/paginators-1.json' adding 'botocore/data/codestar-notifications/2019-10-15/service-2.json' adding 'botocore/data/cognito-identity/2014-06-30/endpoint-rule-set-1.json' adding 'botocore/data/cognito-identity/2014-06-30/examples-1.json' adding 'botocore/data/cognito-identity/2014-06-30/paginators-1.json' adding 'botocore/data/cognito-identity/2014-06-30/service-2.json' adding 'botocore/data/cognito-idp/2016-04-18/endpoint-rule-set-1.json' adding 'botocore/data/cognito-idp/2016-04-18/examples-1.json' adding 'botocore/data/cognito-idp/2016-04-18/paginators-1.json' adding 'botocore/data/cognito-idp/2016-04-18/service-2.json' adding 'botocore/data/cognito-sync/2014-06-30/endpoint-rule-set-1.json' adding 'botocore/data/cognito-sync/2014-06-30/examples-1.json' adding 'botocore/data/cognito-sync/2014-06-30/paginators-1.json' adding 'botocore/data/cognito-sync/2014-06-30/service-2.json' adding 'botocore/data/comprehend/2017-11-27/endpoint-rule-set-1.json' adding 'botocore/data/comprehend/2017-11-27/examples-1.json' adding 'botocore/data/comprehend/2017-11-27/paginators-1.json' adding 'botocore/data/comprehend/2017-11-27/service-2.json' adding 'botocore/data/comprehendmedical/2018-10-30/endpoint-rule-set-1.json' adding 'botocore/data/comprehendmedical/2018-10-30/examples-1.json' adding 'botocore/data/comprehendmedical/2018-10-30/paginators-1.json' adding 'botocore/data/comprehendmedical/2018-10-30/service-2.json' adding 'botocore/data/compute-optimizer/2019-11-01/endpoint-rule-set-1.json' adding 'botocore/data/compute-optimizer/2019-11-01/examples-1.json' adding 'botocore/data/compute-optimizer/2019-11-01/paginators-1.json' adding 'botocore/data/compute-optimizer/2019-11-01/service-2.json' adding 'botocore/data/compute-optimizer-automation/2025-09-22/endpoint-rule-set-1.json' adding 'botocore/data/compute-optimizer-automation/2025-09-22/paginators-1.json' adding 'botocore/data/compute-optimizer-automation/2025-09-22/service-2.json' adding 'botocore/data/compute-optimizer-automation/2025-09-22/waiters-2.json' adding 'botocore/data/config/2014-11-12/endpoint-rule-set-1.json' adding 'botocore/data/config/2014-11-12/examples-1.json' adding 'botocore/data/config/2014-11-12/paginators-1.json' adding 'botocore/data/config/2014-11-12/service-2.json' adding 'botocore/data/connect/2017-08-08/endpoint-rule-set-1.json' adding 'botocore/data/connect/2017-08-08/examples-1.json' adding 'botocore/data/connect/2017-08-08/paginators-1.json' adding 'botocore/data/connect/2017-08-08/service-2.json' adding 'botocore/data/connect-contact-lens/2020-08-21/endpoint-rule-set-1.json' adding 'botocore/data/connect-contact-lens/2020-08-21/examples-1.json' adding 'botocore/data/connect-contact-lens/2020-08-21/paginators-1.json' adding 'botocore/data/connect-contact-lens/2020-08-21/service-2.json' adding 'botocore/data/connectcampaigns/2021-01-30/endpoint-rule-set-1.json' adding 'botocore/data/connectcampaigns/2021-01-30/paginators-1.json' adding 'botocore/data/connectcampaigns/2021-01-30/service-2.json' adding 'botocore/data/connectcampaignsv2/2024-04-23/endpoint-rule-set-1.json' adding 'botocore/data/connectcampaignsv2/2024-04-23/paginators-1.json' adding 'botocore/data/connectcampaignsv2/2024-04-23/service-2.json' adding 'botocore/data/connectcases/2022-10-03/endpoint-rule-set-1.json' adding 'botocore/data/connectcases/2022-10-03/paginators-1.json' adding 'botocore/data/connectcases/2022-10-03/paginators-1.sdk-extras.json' adding 'botocore/data/connectcases/2022-10-03/service-2.json' adding 'botocore/data/connectcases/2022-10-03/waiters-2.json' adding 'botocore/data/connecthealth/2025-01-29/endpoint-rule-set-1.json' adding 'botocore/data/connecthealth/2025-01-29/paginators-1.json' adding 'botocore/data/connecthealth/2025-01-29/service-2.json' adding 'botocore/data/connecthealth/2025-01-29/waiters-2.json' adding 'botocore/data/connectparticipant/2018-09-07/endpoint-rule-set-1.json' adding 'botocore/data/connectparticipant/2018-09-07/examples-1.json' adding 'botocore/data/connectparticipant/2018-09-07/paginators-1.json' adding 'botocore/data/connectparticipant/2018-09-07/service-2.json' adding 'botocore/data/controlcatalog/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/controlcatalog/2018-05-10/paginators-1.json' adding 'botocore/data/controlcatalog/2018-05-10/service-2.json' adding 'botocore/data/controlcatalog/2018-05-10/waiters-2.json' adding 'botocore/data/controltower/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/controltower/2018-05-10/paginators-1.json' adding 'botocore/data/controltower/2018-05-10/service-2.json' adding 'botocore/data/controltower/2018-05-10/waiters-2.json' adding 'botocore/data/cost-optimization-hub/2022-07-26/endpoint-rule-set-1.json' adding 'botocore/data/cost-optimization-hub/2022-07-26/paginators-1.json' adding 'botocore/data/cost-optimization-hub/2022-07-26/paginators-1.sdk-extras.json' adding 'botocore/data/cost-optimization-hub/2022-07-26/service-2.json' adding 'botocore/data/cost-optimization-hub/2022-07-26/waiters-2.json' adding 'botocore/data/cur/2017-01-06/endpoint-rule-set-1.json' adding 'botocore/data/cur/2017-01-06/examples-1.json' adding 'botocore/data/cur/2017-01-06/paginators-1.json' adding 'botocore/data/cur/2017-01-06/service-2.json' adding 'botocore/data/customer-profiles/2020-08-15/endpoint-rule-set-1.json' adding 'botocore/data/customer-profiles/2020-08-15/examples-1.json' adding 'botocore/data/customer-profiles/2020-08-15/paginators-1.json' adding 'botocore/data/customer-profiles/2020-08-15/paginators-1.sdk-extras.json' adding 'botocore/data/customer-profiles/2020-08-15/service-2.json' adding 'botocore/data/databrew/2017-07-25/endpoint-rule-set-1.json' adding 'botocore/data/databrew/2017-07-25/examples-1.json' adding 'botocore/data/databrew/2017-07-25/paginators-1.json' adding 'botocore/data/databrew/2017-07-25/service-2.json' adding 'botocore/data/dataexchange/2017-07-25/endpoint-rule-set-1.json' adding 'botocore/data/dataexchange/2017-07-25/paginators-1.json' adding 'botocore/data/dataexchange/2017-07-25/service-2.json' adding 'botocore/data/dataexchange/2017-07-25/waiters-2.json' adding 'botocore/data/datapipeline/2012-10-29/endpoint-rule-set-1.json' adding 'botocore/data/datapipeline/2012-10-29/examples-1.json' adding 'botocore/data/datapipeline/2012-10-29/paginators-1.json' adding 'botocore/data/datapipeline/2012-10-29/service-2.json' adding 'botocore/data/datasync/2018-11-09/endpoint-rule-set-1.json' adding 'botocore/data/datasync/2018-11-09/examples-1.json' adding 'botocore/data/datasync/2018-11-09/paginators-1.json' adding 'botocore/data/datasync/2018-11-09/service-2.json' adding 'botocore/data/datazone/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/datazone/2018-05-10/paginators-1.json' adding 'botocore/data/datazone/2018-05-10/paginators-1.sdk-extras.json' adding 'botocore/data/datazone/2018-05-10/service-2.json' adding 'botocore/data/datazone/2018-05-10/waiters-2.json' adding 'botocore/data/dax/2017-04-19/endpoint-rule-set-1.json' adding 'botocore/data/dax/2017-04-19/examples-1.json' adding 'botocore/data/dax/2017-04-19/paginators-1.json' adding 'botocore/data/dax/2017-04-19/service-2.json' adding 'botocore/data/deadline/2023-10-12/endpoint-rule-set-1.json' adding 'botocore/data/deadline/2023-10-12/paginators-1.json' adding 'botocore/data/deadline/2023-10-12/paginators-1.sdk-extras.json' adding 'botocore/data/deadline/2023-10-12/service-2.json' adding 'botocore/data/deadline/2023-10-12/waiters-2.json' adding 'botocore/data/detective/2018-10-26/endpoint-rule-set-1.json' adding 'botocore/data/detective/2018-10-26/examples-1.json' adding 'botocore/data/detective/2018-10-26/paginators-1.json' adding 'botocore/data/detective/2018-10-26/service-2.json' adding 'botocore/data/devicefarm/2015-06-23/endpoint-rule-set-1.json' adding 'botocore/data/devicefarm/2015-06-23/examples-1.json' adding 'botocore/data/devicefarm/2015-06-23/paginators-1.json' adding 'botocore/data/devicefarm/2015-06-23/service-2.json' adding 'botocore/data/devops-agent/2026-01-01/endpoint-rule-set-1.json' adding 'botocore/data/devops-agent/2026-01-01/paginators-1.json' adding 'botocore/data/devops-agent/2026-01-01/service-2.json' adding 'botocore/data/devops-guru/2020-12-01/endpoint-rule-set-1.json' adding 'botocore/data/devops-guru/2020-12-01/examples-1.json' adding 'botocore/data/devops-guru/2020-12-01/paginators-1.json' adding 'botocore/data/devops-guru/2020-12-01/service-2.json' adding 'botocore/data/directconnect/2012-10-25/endpoint-rule-set-1.json' adding 'botocore/data/directconnect/2012-10-25/examples-1.json' adding 'botocore/data/directconnect/2012-10-25/paginators-1.json' adding 'botocore/data/directconnect/2012-10-25/service-2.json' adding 'botocore/data/discovery/2015-11-01/endpoint-rule-set-1.json' adding 'botocore/data/discovery/2015-11-01/examples-1.json' adding 'botocore/data/discovery/2015-11-01/paginators-1.json' adding 'botocore/data/discovery/2015-11-01/service-2.json' adding 'botocore/data/dlm/2018-01-12/endpoint-rule-set-1.json' adding 'botocore/data/dlm/2018-01-12/examples-1.json' adding 'botocore/data/dlm/2018-01-12/paginators-1.json' adding 'botocore/data/dlm/2018-01-12/service-2.json' adding 'botocore/data/dms/2016-01-01/endpoint-rule-set-1.json' adding 'botocore/data/dms/2016-01-01/examples-1.json' adding 'botocore/data/dms/2016-01-01/paginators-1.json' adding 'botocore/data/dms/2016-01-01/service-2.json' adding 'botocore/data/dms/2016-01-01/waiters-2.json' adding 'botocore/data/docdb/2014-10-31/endpoint-rule-set-1.json' adding 'botocore/data/docdb/2014-10-31/examples-1.json' adding 'botocore/data/docdb/2014-10-31/paginators-1.json' adding 'botocore/data/docdb/2014-10-31/service-2.json' adding 'botocore/data/docdb/2014-10-31/service-2.sdk-extras.json' adding 'botocore/data/docdb/2014-10-31/waiters-2.json' adding 'botocore/data/docdb-elastic/2022-11-28/endpoint-rule-set-1.json' adding 'botocore/data/docdb-elastic/2022-11-28/paginators-1.json' adding 'botocore/data/docdb-elastic/2022-11-28/service-2.json' adding 'botocore/data/drs/2020-02-26/endpoint-rule-set-1.json' adding 'botocore/data/drs/2020-02-26/examples-1.json' adding 'botocore/data/drs/2020-02-26/paginators-1.json' adding 'botocore/data/drs/2020-02-26/service-2.json' adding 'botocore/data/ds/2015-04-16/endpoint-rule-set-1.json' adding 'botocore/data/ds/2015-04-16/examples-1.json' adding 'botocore/data/ds/2015-04-16/paginators-1.json' adding 'botocore/data/ds/2015-04-16/service-2.json' adding 'botocore/data/ds/2015-04-16/waiters-2.json' adding 'botocore/data/ds-data/2023-05-31/endpoint-rule-set-1.json' adding 'botocore/data/ds-data/2023-05-31/paginators-1.json' adding 'botocore/data/ds-data/2023-05-31/paginators-1.sdk-extras.json' adding 'botocore/data/ds-data/2023-05-31/service-2.json' adding 'botocore/data/dsql/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/dsql/2018-05-10/paginators-1.json' adding 'botocore/data/dsql/2018-05-10/service-2.json' adding 'botocore/data/dsql/2018-05-10/waiters-2.json' adding 'botocore/data/dynamodb/2011-12-05/endpoint-rule-set-1.json' adding 'botocore/data/dynamodb/2011-12-05/examples-1.json' adding 'botocore/data/dynamodb/2012-08-10/endpoint-rule-set-1.json' adding 'botocore/data/dynamodb/2012-08-10/examples-1.json' adding 'botocore/data/dynamodb/2012-08-10/paginators-1.json' adding 'botocore/data/dynamodb/2012-08-10/service-2.json' adding 'botocore/data/dynamodb/2012-08-10/waiters-2.json' adding 'botocore/data/dynamodbstreams/2012-08-10/endpoint-rule-set-1.json' adding 'botocore/data/dynamodbstreams/2012-08-10/examples-1.json' adding 'botocore/data/dynamodbstreams/2012-08-10/paginators-1.json' adding 'botocore/data/dynamodbstreams/2012-08-10/service-2.json' adding 'botocore/data/ebs/2019-11-02/endpoint-rule-set-1.json' adding 'botocore/data/ebs/2019-11-02/examples-1.json' adding 'botocore/data/ebs/2019-11-02/paginators-1.json' adding 'botocore/data/ebs/2019-11-02/service-2.json' adding 'botocore/data/ec2/2014-09-01/endpoint-rule-set-1.json' adding 'botocore/data/ec2/2014-09-01/paginators-1.json' adding 'botocore/data/ec2/2014-09-01/service-2.json' adding 'botocore/data/ec2/2014-09-01/waiters-2.json' adding 'botocore/data/ec2/2014-10-01/endpoint-rule-set-1.json' adding 'botocore/data/ec2/2014-10-01/paginators-1.json' adding 'botocore/data/ec2/2014-10-01/service-2.json' adding 'botocore/data/ec2/2014-10-01/waiters-2.json' adding 'botocore/data/ec2/2015-03-01/endpoint-rule-set-1.json' adding 'botocore/data/ec2/2015-03-01/paginators-1.json' adding 'botocore/data/ec2/2015-03-01/service-2.json' adding 'botocore/data/ec2/2015-03-01/waiters-2.json' adding 'botocore/data/ec2/2015-04-15/endpoint-rule-set-1.json' adding 'botocore/data/ec2/2015-04-15/paginators-1.json' adding 'botocore/data/ec2/2015-04-15/service-2.json' adding 'botocore/data/ec2/2015-04-15/waiters-2.json' adding 'botocore/data/ec2/2015-10-01/endpoint-rule-set-1.json' adding 'botocore/data/ec2/2015-10-01/examples-1.json' adding 'botocore/data/ec2/2015-10-01/paginators-1.json' adding 'botocore/data/ec2/2015-10-01/service-2.json' adding 'botocore/data/ec2/2015-10-01/waiters-2.json' adding 'botocore/data/ec2/2016-04-01/endpoint-rule-set-1.json' adding 'botocore/data/ec2/2016-04-01/examples-1.json' adding 'botocore/data/ec2/2016-04-01/paginators-1.json' adding 'botocore/data/ec2/2016-04-01/service-2.json' adding 'botocore/data/ec2/2016-04-01/waiters-2.json' adding 'botocore/data/ec2/2016-09-15/endpoint-rule-set-1.json' adding 'botocore/data/ec2/2016-09-15/examples-1.json' adding 'botocore/data/ec2/2016-09-15/paginators-1.json' adding 'botocore/data/ec2/2016-09-15/service-2.json' adding 'botocore/data/ec2/2016-09-15/waiters-2.json' adding 'botocore/data/ec2/2016-11-15/endpoint-rule-set-1.json' adding 'botocore/data/ec2/2016-11-15/examples-1.json' adding 'botocore/data/ec2/2016-11-15/paginators-1.json' adding 'botocore/data/ec2/2016-11-15/paginators-1.sdk-extras.json' adding 'botocore/data/ec2/2016-11-15/service-2.json' adding 'botocore/data/ec2/2016-11-15/waiters-2.json' adding 'botocore/data/ec2-instance-connect/2018-04-02/endpoint-rule-set-1.json' adding 'botocore/data/ec2-instance-connect/2018-04-02/examples-1.json' adding 'botocore/data/ec2-instance-connect/2018-04-02/paginators-1.json' adding 'botocore/data/ec2-instance-connect/2018-04-02/service-2.json' adding 'botocore/data/ecr/2015-09-21/endpoint-rule-set-1.json' adding 'botocore/data/ecr/2015-09-21/examples-1.json' adding 'botocore/data/ecr/2015-09-21/paginators-1.json' adding 'botocore/data/ecr/2015-09-21/service-2.json' adding 'botocore/data/ecr/2015-09-21/waiters-2.json' adding 'botocore/data/ecr-public/2020-10-30/endpoint-rule-set-1.json' adding 'botocore/data/ecr-public/2020-10-30/examples-1.json' adding 'botocore/data/ecr-public/2020-10-30/paginators-1.json' adding 'botocore/data/ecr-public/2020-10-30/service-2.json' adding 'botocore/data/ecs/2014-11-13/endpoint-rule-set-1.json' adding 'botocore/data/ecs/2014-11-13/examples-1.json' adding 'botocore/data/ecs/2014-11-13/paginators-1.json' adding 'botocore/data/ecs/2014-11-13/service-2.json' adding 'botocore/data/ecs/2014-11-13/waiters-2.json' adding 'botocore/data/efs/2015-02-01/endpoint-rule-set-1.json' adding 'botocore/data/efs/2015-02-01/examples-1.json' adding 'botocore/data/efs/2015-02-01/paginators-1.json' adding 'botocore/data/efs/2015-02-01/service-2.json' adding 'botocore/data/eks/2017-11-01/endpoint-rule-set-1.json' adding 'botocore/data/eks/2017-11-01/examples-1.json' adding 'botocore/data/eks/2017-11-01/paginators-1.json' adding 'botocore/data/eks/2017-11-01/service-2.json' adding 'botocore/data/eks/2017-11-01/service-2.sdk-extras.json' adding 'botocore/data/eks/2017-11-01/waiters-2.json' adding 'botocore/data/eks-auth/2023-11-26/endpoint-rule-set-1.json' adding 'botocore/data/eks-auth/2023-11-26/paginators-1.json' adding 'botocore/data/eks-auth/2023-11-26/service-2.json' adding 'botocore/data/eks-auth/2023-11-26/waiters-2.json' adding 'botocore/data/elasticache/2014-09-30/endpoint-rule-set-1.json' adding 'botocore/data/elasticache/2014-09-30/paginators-1.json' adding 'botocore/data/elasticache/2014-09-30/service-2.json' adding 'botocore/data/elasticache/2014-09-30/waiters-2.json' adding 'botocore/data/elasticache/2015-02-02/endpoint-rule-set-1.json' adding 'botocore/data/elasticache/2015-02-02/examples-1.json' adding 'botocore/data/elasticache/2015-02-02/paginators-1.json' adding 'botocore/data/elasticache/2015-02-02/service-2.json' adding 'botocore/data/elasticache/2015-02-02/waiters-2.json' adding 'botocore/data/elasticbeanstalk/2010-12-01/endpoint-rule-set-1.json' adding 'botocore/data/elasticbeanstalk/2010-12-01/examples-1.json' adding 'botocore/data/elasticbeanstalk/2010-12-01/paginators-1.json' adding 'botocore/data/elasticbeanstalk/2010-12-01/service-2.json' adding 'botocore/data/elasticbeanstalk/2010-12-01/waiters-2.json' adding 'botocore/data/elb/2012-06-01/endpoint-rule-set-1.json' adding 'botocore/data/elb/2012-06-01/examples-1.json' adding 'botocore/data/elb/2012-06-01/paginators-1.json' adding 'botocore/data/elb/2012-06-01/service-2.json' adding 'botocore/data/elb/2012-06-01/waiters-2.json' adding 'botocore/data/elbv2/2015-12-01/endpoint-rule-set-1.json' adding 'botocore/data/elbv2/2015-12-01/examples-1.json' adding 'botocore/data/elbv2/2015-12-01/paginators-1.json' adding 'botocore/data/elbv2/2015-12-01/service-2.json' adding 'botocore/data/elbv2/2015-12-01/waiters-2.json' adding 'botocore/data/elementalinference/2018-11-14/endpoint-rule-set-1.json' adding 'botocore/data/elementalinference/2018-11-14/paginators-1.json' adding 'botocore/data/elementalinference/2018-11-14/service-2.json' adding 'botocore/data/elementalinference/2018-11-14/waiters-2.json' adding 'botocore/data/emr/2009-03-31/endpoint-rule-set-1.json' adding 'botocore/data/emr/2009-03-31/examples-1.json' adding 'botocore/data/emr/2009-03-31/paginators-1.json' adding 'botocore/data/emr/2009-03-31/service-2.json' adding 'botocore/data/emr/2009-03-31/waiters-2.json' adding 'botocore/data/emr-containers/2020-10-01/endpoint-rule-set-1.json' adding 'botocore/data/emr-containers/2020-10-01/examples-1.json' adding 'botocore/data/emr-containers/2020-10-01/paginators-1.json' adding 'botocore/data/emr-containers/2020-10-01/service-2.json' adding 'botocore/data/emr-serverless/2021-07-13/endpoint-rule-set-1.json' adding 'botocore/data/emr-serverless/2021-07-13/paginators-1.json' adding 'botocore/data/emr-serverless/2021-07-13/service-2.json' adding 'botocore/data/entityresolution/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/entityresolution/2018-05-10/paginators-1.json' adding 'botocore/data/entityresolution/2018-05-10/service-2.json' adding 'botocore/data/es/2015-01-01/endpoint-rule-set-1.json' adding 'botocore/data/es/2015-01-01/examples-1.json' adding 'botocore/data/es/2015-01-01/paginators-1.json' adding 'botocore/data/es/2015-01-01/service-2.json' adding 'botocore/data/events/2014-02-03/endpoint-rule-set-1.json' adding 'botocore/data/events/2014-02-03/service-2.json' adding 'botocore/data/events/2015-10-07/endpoint-rule-set-1.json' adding 'botocore/data/events/2015-10-07/examples-1.json' adding 'botocore/data/events/2015-10-07/paginators-1.json' adding 'botocore/data/events/2015-10-07/service-2.json' adding 'botocore/data/evs/2023-07-27/endpoint-rule-set-1.json' adding 'botocore/data/evs/2023-07-27/paginators-1.json' adding 'botocore/data/evs/2023-07-27/service-2.json' adding 'botocore/data/evs/2023-07-27/waiters-2.json' adding 'botocore/data/finspace/2021-03-12/endpoint-rule-set-1.json' adding 'botocore/data/finspace/2021-03-12/examples-1.json' adding 'botocore/data/finspace/2021-03-12/paginators-1.json' adding 'botocore/data/finspace/2021-03-12/service-2.json' adding 'botocore/data/finspace-data/2020-07-13/endpoint-rule-set-1.json' adding 'botocore/data/finspace-data/2020-07-13/examples-1.json' adding 'botocore/data/finspace-data/2020-07-13/paginators-1.json' adding 'botocore/data/finspace-data/2020-07-13/service-2.json' adding 'botocore/data/firehose/2015-08-04/endpoint-rule-set-1.json' adding 'botocore/data/firehose/2015-08-04/examples-1.json' adding 'botocore/data/firehose/2015-08-04/paginators-1.json' adding 'botocore/data/firehose/2015-08-04/service-2.json' adding 'botocore/data/fis/2020-12-01/endpoint-rule-set-1.json' adding 'botocore/data/fis/2020-12-01/examples-1.json' adding 'botocore/data/fis/2020-12-01/paginators-1.json' adding 'botocore/data/fis/2020-12-01/service-2.json' adding 'botocore/data/fms/2018-01-01/endpoint-rule-set-1.json' adding 'botocore/data/fms/2018-01-01/examples-1.json' adding 'botocore/data/fms/2018-01-01/paginators-1.json' adding 'botocore/data/fms/2018-01-01/service-2.json' adding 'botocore/data/forecast/2018-06-26/endpoint-rule-set-1.json' adding 'botocore/data/forecast/2018-06-26/examples-1.json' adding 'botocore/data/forecast/2018-06-26/paginators-1.json' adding 'botocore/data/forecast/2018-06-26/service-2.json' adding 'botocore/data/forecastquery/2018-06-26/endpoint-rule-set-1.json' adding 'botocore/data/forecastquery/2018-06-26/examples-1.json' adding 'botocore/data/forecastquery/2018-06-26/paginators-1.json' adding 'botocore/data/forecastquery/2018-06-26/service-2.json' adding 'botocore/data/frauddetector/2019-11-15/endpoint-rule-set-1.json' adding 'botocore/data/frauddetector/2019-11-15/examples-1.json' adding 'botocore/data/frauddetector/2019-11-15/paginators-1.json' adding 'botocore/data/frauddetector/2019-11-15/service-2.json' adding 'botocore/data/freetier/2023-09-07/endpoint-rule-set-1.json' adding 'botocore/data/freetier/2023-09-07/paginators-1.json' adding 'botocore/data/freetier/2023-09-07/service-2.json' adding 'botocore/data/freetier/2023-09-07/waiters-2.json' adding 'botocore/data/fsx/2018-03-01/endpoint-rule-set-1.json' adding 'botocore/data/fsx/2018-03-01/examples-1.json' adding 'botocore/data/fsx/2018-03-01/paginators-1.json' adding 'botocore/data/fsx/2018-03-01/service-2.json' adding 'botocore/data/gamelift/2015-10-01/endpoint-rule-set-1.json' adding 'botocore/data/gamelift/2015-10-01/examples-1.json' adding 'botocore/data/gamelift/2015-10-01/paginators-1.json' adding 'botocore/data/gamelift/2015-10-01/service-2.json' adding 'botocore/data/gameliftstreams/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/gameliftstreams/2018-05-10/paginators-1.json' adding 'botocore/data/gameliftstreams/2018-05-10/service-2.json' adding 'botocore/data/gameliftstreams/2018-05-10/waiters-2.json' adding 'botocore/data/geo-maps/2020-11-19/endpoint-rule-set-1.json' adding 'botocore/data/geo-maps/2020-11-19/paginators-1.json' adding 'botocore/data/geo-maps/2020-11-19/service-2.json' adding 'botocore/data/geo-maps/2020-11-19/waiters-2.json' adding 'botocore/data/geo-places/2020-11-19/endpoint-rule-set-1.json' adding 'botocore/data/geo-places/2020-11-19/paginators-1.json' adding 'botocore/data/geo-places/2020-11-19/service-2.json' adding 'botocore/data/geo-places/2020-11-19/waiters-2.json' adding 'botocore/data/geo-routes/2020-11-19/endpoint-rule-set-1.json' adding 'botocore/data/geo-routes/2020-11-19/paginators-1.json' adding 'botocore/data/geo-routes/2020-11-19/service-2.json' adding 'botocore/data/geo-routes/2020-11-19/waiters-2.json' adding 'botocore/data/glacier/2012-06-01/endpoint-rule-set-1.json' adding 'botocore/data/glacier/2012-06-01/examples-1.json' adding 'botocore/data/glacier/2012-06-01/paginators-1.json' adding 'botocore/data/glacier/2012-06-01/service-2.json' adding 'botocore/data/glacier/2012-06-01/waiters-2.json' adding 'botocore/data/globalaccelerator/2018-08-08/endpoint-rule-set-1.json' adding 'botocore/data/globalaccelerator/2018-08-08/examples-1.json' adding 'botocore/data/globalaccelerator/2018-08-08/paginators-1.json' adding 'botocore/data/globalaccelerator/2018-08-08/service-2.json' adding 'botocore/data/glue/2017-03-31/endpoint-rule-set-1.json' adding 'botocore/data/glue/2017-03-31/examples-1.json' adding 'botocore/data/glue/2017-03-31/paginators-1.json' adding 'botocore/data/glue/2017-03-31/paginators-1.sdk-extras.json' adding 'botocore/data/glue/2017-03-31/service-2.json' adding 'botocore/data/grafana/2020-08-18/endpoint-rule-set-1.json' adding 'botocore/data/grafana/2020-08-18/examples-1.json' adding 'botocore/data/grafana/2020-08-18/paginators-1.json' adding 'botocore/data/grafana/2020-08-18/paginators-1.sdk-extras.json' adding 'botocore/data/grafana/2020-08-18/service-2.json' adding 'botocore/data/grafana/2020-08-18/waiters-2.json' adding 'botocore/data/greengrass/2017-06-07/endpoint-rule-set-1.json' adding 'botocore/data/greengrass/2017-06-07/paginators-1.json' adding 'botocore/data/greengrass/2017-06-07/service-2.json' adding 'botocore/data/greengrassv2/2020-11-30/endpoint-rule-set-1.json' adding 'botocore/data/greengrassv2/2020-11-30/examples-1.json' adding 'botocore/data/greengrassv2/2020-11-30/paginators-1.json' adding 'botocore/data/greengrassv2/2020-11-30/service-2.json' adding 'botocore/data/groundstation/2019-05-23/endpoint-rule-set-1.json' adding 'botocore/data/groundstation/2019-05-23/examples-1.json' adding 'botocore/data/groundstation/2019-05-23/paginators-1.json' adding 'botocore/data/groundstation/2019-05-23/service-2.json' adding 'botocore/data/groundstation/2019-05-23/waiters-2.json' adding 'botocore/data/guardduty/2017-11-28/endpoint-rule-set-1.json' adding 'botocore/data/guardduty/2017-11-28/examples-1.json' adding 'botocore/data/guardduty/2017-11-28/paginators-1.json' adding 'botocore/data/guardduty/2017-11-28/service-2.json' adding 'botocore/data/health/2016-08-04/endpoint-rule-set-1.json' adding 'botocore/data/health/2016-08-04/examples-1.json' adding 'botocore/data/health/2016-08-04/paginators-1.json' adding 'botocore/data/health/2016-08-04/service-2.json' adding 'botocore/data/healthlake/2017-07-01/endpoint-rule-set-1.json' adding 'botocore/data/healthlake/2017-07-01/examples-1.json' adding 'botocore/data/healthlake/2017-07-01/paginators-1.json' adding 'botocore/data/healthlake/2017-07-01/service-2.json' adding 'botocore/data/healthlake/2017-07-01/waiters-2.json' adding 'botocore/data/iam/2010-05-08/endpoint-rule-set-1.json' adding 'botocore/data/iam/2010-05-08/examples-1.json' adding 'botocore/data/iam/2010-05-08/paginators-1.json' adding 'botocore/data/iam/2010-05-08/service-2.json' adding 'botocore/data/iam/2010-05-08/waiters-2.json' adding 'botocore/data/identitystore/2020-06-15/endpoint-rule-set-1.json' adding 'botocore/data/identitystore/2020-06-15/examples-1.json' adding 'botocore/data/identitystore/2020-06-15/paginators-1.json' adding 'botocore/data/identitystore/2020-06-15/service-2.json' adding 'botocore/data/imagebuilder/2019-12-02/endpoint-rule-set-1.json' adding 'botocore/data/imagebuilder/2019-12-02/examples-1.json' adding 'botocore/data/imagebuilder/2019-12-02/paginators-1.json' adding 'botocore/data/imagebuilder/2019-12-02/paginators-1.sdk-extras.json' adding 'botocore/data/imagebuilder/2019-12-02/service-2.json' adding 'botocore/data/importexport/2010-06-01/endpoint-rule-set-1.json' adding 'botocore/data/importexport/2010-06-01/paginators-1.json' adding 'botocore/data/importexport/2010-06-01/service-2.json' adding 'botocore/data/inspector/2015-08-18/endpoint-rule-set-1.json' adding 'botocore/data/inspector/2015-08-18/service-2.json' adding 'botocore/data/inspector/2016-02-16/endpoint-rule-set-1.json' adding 'botocore/data/inspector/2016-02-16/examples-1.json' adding 'botocore/data/inspector/2016-02-16/paginators-1.json' adding 'botocore/data/inspector/2016-02-16/service-2.json' adding 'botocore/data/inspector-scan/2023-08-08/endpoint-rule-set-1.json' adding 'botocore/data/inspector-scan/2023-08-08/paginators-1.json' adding 'botocore/data/inspector-scan/2023-08-08/service-2.json' adding 'botocore/data/inspector2/2020-06-08/endpoint-rule-set-1.json' adding 'botocore/data/inspector2/2020-06-08/examples-1.json' adding 'botocore/data/inspector2/2020-06-08/paginators-1.json' adding 'botocore/data/inspector2/2020-06-08/paginators-1.sdk-extras.json' adding 'botocore/data/inspector2/2020-06-08/service-2.json' adding 'botocore/data/interconnect/2022-07-26/endpoint-rule-set-1.json' adding 'botocore/data/interconnect/2022-07-26/paginators-1.json' adding 'botocore/data/interconnect/2022-07-26/service-2.json' adding 'botocore/data/interconnect/2022-07-26/waiters-2.json' adding 'botocore/data/internetmonitor/2021-06-03/endpoint-rule-set-1.json' adding 'botocore/data/internetmonitor/2021-06-03/paginators-1.json' adding 'botocore/data/internetmonitor/2021-06-03/service-2.json' adding 'botocore/data/internetmonitor/2021-06-03/waiters-2.json' adding 'botocore/data/invoicing/2024-12-01/endpoint-rule-set-1.json' adding 'botocore/data/invoicing/2024-12-01/paginators-1.json' adding 'botocore/data/invoicing/2024-12-01/service-2.json' adding 'botocore/data/invoicing/2024-12-01/waiters-2.json' adding 'botocore/data/iot/2015-05-28/endpoint-rule-set-1.json' adding 'botocore/data/iot/2015-05-28/examples-1.json' adding 'botocore/data/iot/2015-05-28/paginators-1.json' adding 'botocore/data/iot/2015-05-28/service-2.json' adding 'botocore/data/iot-data/2015-05-28/endpoint-rule-set-1.json' adding 'botocore/data/iot-data/2015-05-28/examples-1.json' adding 'botocore/data/iot-data/2015-05-28/paginators-1.json' adding 'botocore/data/iot-data/2015-05-28/service-2.json' adding 'botocore/data/iot-jobs-data/2017-09-29/endpoint-rule-set-1.json' adding 'botocore/data/iot-jobs-data/2017-09-29/examples-1.json' adding 'botocore/data/iot-jobs-data/2017-09-29/paginators-1.json' adding 'botocore/data/iot-jobs-data/2017-09-29/service-2.json' adding 'botocore/data/iot-managed-integrations/2025-03-03/endpoint-rule-set-1.json' adding 'botocore/data/iot-managed-integrations/2025-03-03/paginators-1.json' adding 'botocore/data/iot-managed-integrations/2025-03-03/service-2.json' adding 'botocore/data/iotdeviceadvisor/2020-09-18/endpoint-rule-set-1.json' adding 'botocore/data/iotdeviceadvisor/2020-09-18/examples-1.json' adding 'botocore/data/iotdeviceadvisor/2020-09-18/paginators-1.json' adding 'botocore/data/iotdeviceadvisor/2020-09-18/service-2.json' adding 'botocore/data/iotevents/2018-07-27/endpoint-rule-set-1.json' adding 'botocore/data/iotevents/2018-07-27/examples-1.json' adding 'botocore/data/iotevents/2018-07-27/paginators-1.json' adding 'botocore/data/iotevents/2018-07-27/service-2.json' adding 'botocore/data/iotevents-data/2018-10-23/endpoint-rule-set-1.json' adding 'botocore/data/iotevents-data/2018-10-23/examples-1.json' adding 'botocore/data/iotevents-data/2018-10-23/paginators-1.json' adding 'botocore/data/iotevents-data/2018-10-23/service-2.json' adding 'botocore/data/iotfleetwise/2021-06-17/endpoint-rule-set-1.json' adding 'botocore/data/iotfleetwise/2021-06-17/paginators-1.json' adding 'botocore/data/iotfleetwise/2021-06-17/service-2.json' adding 'botocore/data/iotfleetwise/2021-06-17/waiters-2.json' adding 'botocore/data/iotsecuretunneling/2018-10-05/endpoint-rule-set-1.json' adding 'botocore/data/iotsecuretunneling/2018-10-05/examples-1.json' adding 'botocore/data/iotsecuretunneling/2018-10-05/paginators-1.json' adding 'botocore/data/iotsecuretunneling/2018-10-05/service-2.json' adding 'botocore/data/iotsitewise/2019-12-02/endpoint-rule-set-1.json' adding 'botocore/data/iotsitewise/2019-12-02/examples-1.json' adding 'botocore/data/iotsitewise/2019-12-02/paginators-1.json' adding 'botocore/data/iotsitewise/2019-12-02/paginators-1.sdk-extras.json' adding 'botocore/data/iotsitewise/2019-12-02/service-2.json' adding 'botocore/data/iotsitewise/2019-12-02/waiters-2.json' adding 'botocore/data/iotthingsgraph/2018-09-06/endpoint-rule-set-1.json' adding 'botocore/data/iotthingsgraph/2018-09-06/examples-1.json' adding 'botocore/data/iotthingsgraph/2018-09-06/paginators-1.json' adding 'botocore/data/iotthingsgraph/2018-09-06/service-2.json' adding 'botocore/data/iottwinmaker/2021-11-29/endpoint-rule-set-1.json' adding 'botocore/data/iottwinmaker/2021-11-29/examples-1.json' adding 'botocore/data/iottwinmaker/2021-11-29/paginators-1.json' adding 'botocore/data/iottwinmaker/2021-11-29/service-2.json' adding 'botocore/data/iottwinmaker/2021-11-29/waiters-2.json' adding 'botocore/data/iotwireless/2020-11-22/endpoint-rule-set-1.json' adding 'botocore/data/iotwireless/2020-11-22/examples-1.json' adding 'botocore/data/iotwireless/2020-11-22/paginators-1.json' adding 'botocore/data/iotwireless/2020-11-22/service-2.json' adding 'botocore/data/ivs/2020-07-14/endpoint-rule-set-1.json' adding 'botocore/data/ivs/2020-07-14/examples-1.json' adding 'botocore/data/ivs/2020-07-14/paginators-1.json' adding 'botocore/data/ivs/2020-07-14/service-2.json' adding 'botocore/data/ivs-realtime/2020-07-14/endpoint-rule-set-1.json' adding 'botocore/data/ivs-realtime/2020-07-14/paginators-1.json' adding 'botocore/data/ivs-realtime/2020-07-14/service-2.json' adding 'botocore/data/ivs-realtime/2020-07-14/waiters-2.json' adding 'botocore/data/ivschat/2020-07-14/endpoint-rule-set-1.json' adding 'botocore/data/ivschat/2020-07-14/examples-1.json' adding 'botocore/data/ivschat/2020-07-14/paginators-1.json' adding 'botocore/data/ivschat/2020-07-14/service-2.json' adding 'botocore/data/ivschat/2020-07-14/waiters-2.json' adding 'botocore/data/kafka/2018-11-14/endpoint-rule-set-1.json' adding 'botocore/data/kafka/2018-11-14/paginators-1.json' adding 'botocore/data/kafka/2018-11-14/service-2.json' adding 'botocore/data/kafkaconnect/2021-09-14/endpoint-rule-set-1.json' adding 'botocore/data/kafkaconnect/2021-09-14/examples-1.json' adding 'botocore/data/kafkaconnect/2021-09-14/paginators-1.json' adding 'botocore/data/kafkaconnect/2021-09-14/service-2.json' adding 'botocore/data/kafkaconnect/2021-09-14/waiters-2.json' adding 'botocore/data/kendra/2019-02-03/endpoint-rule-set-1.json' adding 'botocore/data/kendra/2019-02-03/examples-1.json' adding 'botocore/data/kendra/2019-02-03/paginators-1.json' adding 'botocore/data/kendra/2019-02-03/service-2.json' adding 'botocore/data/kendra-ranking/2022-10-19/endpoint-rule-set-1.json' adding 'botocore/data/kendra-ranking/2022-10-19/paginators-1.json' adding 'botocore/data/kendra-ranking/2022-10-19/service-2.json' adding 'botocore/data/keyspaces/2022-02-10/endpoint-rule-set-1.json' adding 'botocore/data/keyspaces/2022-02-10/examples-1.json' adding 'botocore/data/keyspaces/2022-02-10/paginators-1.json' adding 'botocore/data/keyspaces/2022-02-10/service-2.json' adding 'botocore/data/keyspaces/2022-02-10/waiters-2.json' adding 'botocore/data/keyspacesstreams/2024-09-09/endpoint-rule-set-1.json' adding 'botocore/data/keyspacesstreams/2024-09-09/paginators-1.json' adding 'botocore/data/keyspacesstreams/2024-09-09/paginators-1.sdk-extras.json' adding 'botocore/data/keyspacesstreams/2024-09-09/service-2.json' adding 'botocore/data/kinesis/2013-12-02/endpoint-rule-set-1.json' adding 'botocore/data/kinesis/2013-12-02/examples-1.json' adding 'botocore/data/kinesis/2013-12-02/paginators-1.json' adding 'botocore/data/kinesis/2013-12-02/service-2.json' adding 'botocore/data/kinesis/2013-12-02/waiters-2.json' adding 'botocore/data/kinesis-video-archived-media/2017-09-30/endpoint-rule-set-1.json' adding 'botocore/data/kinesis-video-archived-media/2017-09-30/examples-1.json' adding 'botocore/data/kinesis-video-archived-media/2017-09-30/paginators-1.json' adding 'botocore/data/kinesis-video-archived-media/2017-09-30/service-2.json' adding 'botocore/data/kinesis-video-media/2017-09-30/endpoint-rule-set-1.json' adding 'botocore/data/kinesis-video-media/2017-09-30/examples-1.json' adding 'botocore/data/kinesis-video-media/2017-09-30/paginators-1.json' adding 'botocore/data/kinesis-video-media/2017-09-30/service-2.json' adding 'botocore/data/kinesis-video-signaling/2019-12-04/endpoint-rule-set-1.json' adding 'botocore/data/kinesis-video-signaling/2019-12-04/examples-1.json' adding 'botocore/data/kinesis-video-signaling/2019-12-04/paginators-1.json' adding 'botocore/data/kinesis-video-signaling/2019-12-04/service-2.json' adding 'botocore/data/kinesis-video-webrtc-storage/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/kinesis-video-webrtc-storage/2018-05-10/paginators-1.json' adding 'botocore/data/kinesis-video-webrtc-storage/2018-05-10/service-2.json' adding 'botocore/data/kinesisanalytics/2015-08-14/endpoint-rule-set-1.json' adding 'botocore/data/kinesisanalytics/2015-08-14/examples-1.json' adding 'botocore/data/kinesisanalytics/2015-08-14/paginators-1.json' adding 'botocore/data/kinesisanalytics/2015-08-14/service-2.json' adding 'botocore/data/kinesisanalyticsv2/2018-05-23/endpoint-rule-set-1.json' adding 'botocore/data/kinesisanalyticsv2/2018-05-23/examples-1.json' adding 'botocore/data/kinesisanalyticsv2/2018-05-23/paginators-1.json' adding 'botocore/data/kinesisanalyticsv2/2018-05-23/service-2.json' adding 'botocore/data/kinesisvideo/2017-09-30/endpoint-rule-set-1.json' adding 'botocore/data/kinesisvideo/2017-09-30/examples-1.json' adding 'botocore/data/kinesisvideo/2017-09-30/paginators-1.json' adding 'botocore/data/kinesisvideo/2017-09-30/service-2.json' adding 'botocore/data/kms/2014-11-01/endpoint-rule-set-1.json' adding 'botocore/data/kms/2014-11-01/examples-1.json' adding 'botocore/data/kms/2014-11-01/paginators-1.json' adding 'botocore/data/kms/2014-11-01/service-2.json' adding 'botocore/data/lakeformation/2017-03-31/endpoint-rule-set-1.json' adding 'botocore/data/lakeformation/2017-03-31/examples-1.json' adding 'botocore/data/lakeformation/2017-03-31/paginators-1.json' adding 'botocore/data/lakeformation/2017-03-31/paginators-1.sdk-extras.json' adding 'botocore/data/lakeformation/2017-03-31/service-2.json' adding 'botocore/data/lambda/2014-11-11/endpoint-rule-set-1.json' adding 'botocore/data/lambda/2014-11-11/service-2.json' adding 'botocore/data/lambda/2015-03-31/endpoint-rule-set-1.json' adding 'botocore/data/lambda/2015-03-31/examples-1.json' adding 'botocore/data/lambda/2015-03-31/paginators-1.json' adding 'botocore/data/lambda/2015-03-31/paginators-1.sdk-extras.json' adding 'botocore/data/lambda/2015-03-31/service-2.json' adding 'botocore/data/lambda/2015-03-31/waiters-2.json' adding 'botocore/data/launch-wizard/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/launch-wizard/2018-05-10/paginators-1.json' adding 'botocore/data/launch-wizard/2018-05-10/service-2.json' adding 'botocore/data/launch-wizard/2018-05-10/waiters-2.json' adding 'botocore/data/lex-models/2017-04-19/endpoint-rule-set-1.json' adding 'botocore/data/lex-models/2017-04-19/examples-1.json' adding 'botocore/data/lex-models/2017-04-19/paginators-1.json' adding 'botocore/data/lex-models/2017-04-19/service-2.json' adding 'botocore/data/lex-runtime/2016-11-28/endpoint-rule-set-1.json' adding 'botocore/data/lex-runtime/2016-11-28/examples-1.json' adding 'botocore/data/lex-runtime/2016-11-28/paginators-1.json' adding 'botocore/data/lex-runtime/2016-11-28/service-2.json' adding 'botocore/data/lexv2-models/2020-08-07/endpoint-rule-set-1.json' adding 'botocore/data/lexv2-models/2020-08-07/examples-1.json' adding 'botocore/data/lexv2-models/2020-08-07/paginators-1.json' adding 'botocore/data/lexv2-models/2020-08-07/service-2.json' adding 'botocore/data/lexv2-models/2020-08-07/waiters-2.json' adding 'botocore/data/lexv2-runtime/2020-08-07/endpoint-rule-set-1.json' adding 'botocore/data/lexv2-runtime/2020-08-07/examples-1.json' adding 'botocore/data/lexv2-runtime/2020-08-07/paginators-1.json' adding 'botocore/data/lexv2-runtime/2020-08-07/service-2.json' adding 'botocore/data/license-manager/2018-08-01/endpoint-rule-set-1.json' adding 'botocore/data/license-manager/2018-08-01/examples-1.json' adding 'botocore/data/license-manager/2018-08-01/paginators-1.json' adding 'botocore/data/license-manager/2018-08-01/service-2.json' adding 'botocore/data/license-manager-linux-subscriptions/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/license-manager-linux-subscriptions/2018-05-10/paginators-1.json' adding 'botocore/data/license-manager-linux-subscriptions/2018-05-10/service-2.json' adding 'botocore/data/license-manager-user-subscriptions/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/license-manager-user-subscriptions/2018-05-10/paginators-1.json' adding 'botocore/data/license-manager-user-subscriptions/2018-05-10/service-2.json' adding 'botocore/data/license-manager-user-subscriptions/2018-05-10/waiters-2.json' adding 'botocore/data/lightsail/2016-11-28/endpoint-rule-set-1.json' adding 'botocore/data/lightsail/2016-11-28/examples-1.json' adding 'botocore/data/lightsail/2016-11-28/paginators-1.json' adding 'botocore/data/lightsail/2016-11-28/service-2.json' adding 'botocore/data/location/2020-11-19/endpoint-rule-set-1.json' adding 'botocore/data/location/2020-11-19/examples-1.json' adding 'botocore/data/location/2020-11-19/paginators-1.json' adding 'botocore/data/location/2020-11-19/paginators-1.sdk-extras.json' adding 'botocore/data/location/2020-11-19/service-2.json' adding 'botocore/data/location/2020-11-19/waiters-2.json' adding 'botocore/data/logs/2014-03-28/endpoint-rule-set-1.json' adding 'botocore/data/logs/2014-03-28/examples-1.json' adding 'botocore/data/logs/2014-03-28/paginators-1.json' adding 'botocore/data/logs/2014-03-28/paginators-1.sdk-extras.json' adding 'botocore/data/logs/2014-03-28/service-2.json' adding 'botocore/data/lookoutequipment/2020-12-15/endpoint-rule-set-1.json' adding 'botocore/data/lookoutequipment/2020-12-15/examples-1.json' adding 'botocore/data/lookoutequipment/2020-12-15/paginators-1.json' adding 'botocore/data/lookoutequipment/2020-12-15/service-2.json' adding 'botocore/data/m2/2021-04-28/endpoint-rule-set-1.json' adding 'botocore/data/m2/2021-04-28/paginators-1.json' adding 'botocore/data/m2/2021-04-28/service-2.json' adding 'botocore/data/machinelearning/2014-12-12/endpoint-rule-set-1.json' adding 'botocore/data/machinelearning/2014-12-12/examples-1.json' adding 'botocore/data/machinelearning/2014-12-12/paginators-1.json' adding 'botocore/data/machinelearning/2014-12-12/service-2.json' adding 'botocore/data/machinelearning/2014-12-12/waiters-2.json' adding 'botocore/data/macie2/2020-01-01/endpoint-rule-set-1.json' adding 'botocore/data/macie2/2020-01-01/paginators-1.json' adding 'botocore/data/macie2/2020-01-01/service-2.json' adding 'botocore/data/macie2/2020-01-01/waiters-2.json' adding 'botocore/data/mailmanager/2023-10-17/endpoint-rule-set-1.json' adding 'botocore/data/mailmanager/2023-10-17/paginators-1.json' adding 'botocore/data/mailmanager/2023-10-17/service-2.json' adding 'botocore/data/mailmanager/2023-10-17/waiters-2.json' adding 'botocore/data/managedblockchain/2018-09-24/endpoint-rule-set-1.json' adding 'botocore/data/managedblockchain/2018-09-24/examples-1.json' adding 'botocore/data/managedblockchain/2018-09-24/paginators-1.json' adding 'botocore/data/managedblockchain/2018-09-24/service-2.json' adding 'botocore/data/managedblockchain-query/2023-05-04/endpoint-rule-set-1.json' adding 'botocore/data/managedblockchain-query/2023-05-04/paginators-1.json' adding 'botocore/data/managedblockchain-query/2023-05-04/service-2.json' adding 'botocore/data/managedblockchain-query/2023-05-04/waiters-2.json' adding 'botocore/data/marketplace-agreement/2020-03-01/endpoint-rule-set-1.json' adding 'botocore/data/marketplace-agreement/2020-03-01/paginators-1.json' adding 'botocore/data/marketplace-agreement/2020-03-01/service-2.json' adding 'botocore/data/marketplace-agreement/2020-03-01/waiters-2.json' adding 'botocore/data/marketplace-catalog/2018-09-17/endpoint-rule-set-1.json' adding 'botocore/data/marketplace-catalog/2018-09-17/examples-1.json' adding 'botocore/data/marketplace-catalog/2018-09-17/paginators-1.json' adding 'botocore/data/marketplace-catalog/2018-09-17/service-2.json' adding 'botocore/data/marketplace-deployment/2023-01-25/endpoint-rule-set-1.json' adding 'botocore/data/marketplace-deployment/2023-01-25/paginators-1.json' adding 'botocore/data/marketplace-deployment/2023-01-25/service-2.json' adding 'botocore/data/marketplace-discovery/2026-02-05/endpoint-rule-set-1.json' adding 'botocore/data/marketplace-discovery/2026-02-05/paginators-1.json' adding 'botocore/data/marketplace-discovery/2026-02-05/paginators-1.sdk-extras.json' adding 'botocore/data/marketplace-discovery/2026-02-05/service-2.json' adding 'botocore/data/marketplace-discovery/2026-02-05/waiters-2.json' adding 'botocore/data/marketplace-entitlement/2017-01-11/endpoint-rule-set-1.json' adding 'botocore/data/marketplace-entitlement/2017-01-11/examples-1.json' adding 'botocore/data/marketplace-entitlement/2017-01-11/paginators-1.json' adding 'botocore/data/marketplace-entitlement/2017-01-11/service-2.json' adding 'botocore/data/marketplace-reporting/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/marketplace-reporting/2018-05-10/paginators-1.json' adding 'botocore/data/marketplace-reporting/2018-05-10/service-2.json' adding 'botocore/data/marketplace-reporting/2018-05-10/waiters-2.json' adding 'botocore/data/marketplacecommerceanalytics/2015-07-01/endpoint-rule-set-1.json' adding 'botocore/data/marketplacecommerceanalytics/2015-07-01/examples-1.json' adding 'botocore/data/marketplacecommerceanalytics/2015-07-01/paginators-1.json' adding 'botocore/data/marketplacecommerceanalytics/2015-07-01/service-2.json' adding 'botocore/data/mediaconnect/2018-11-14/endpoint-rule-set-1.json' adding 'botocore/data/mediaconnect/2018-11-14/paginators-1.json' adding 'botocore/data/mediaconnect/2018-11-14/service-2.json' adding 'botocore/data/mediaconnect/2018-11-14/waiters-2.json' adding 'botocore/data/mediaconvert/2017-08-29/endpoint-rule-set-1.json' adding 'botocore/data/mediaconvert/2017-08-29/paginators-1.json' adding 'botocore/data/mediaconvert/2017-08-29/paginators-1.sdk-extras.json' adding 'botocore/data/mediaconvert/2017-08-29/service-2.json' adding 'botocore/data/medialive/2017-10-14/endpoint-rule-set-1.json' adding 'botocore/data/medialive/2017-10-14/paginators-1.json' adding 'botocore/data/medialive/2017-10-14/service-2.json' adding 'botocore/data/medialive/2017-10-14/waiters-2.json' adding 'botocore/data/mediapackage/2017-10-12/endpoint-rule-set-1.json' adding 'botocore/data/mediapackage/2017-10-12/paginators-1.json' adding 'botocore/data/mediapackage/2017-10-12/service-2.json' adding 'botocore/data/mediapackage-vod/2018-11-07/endpoint-rule-set-1.json' adding 'botocore/data/mediapackage-vod/2018-11-07/paginators-1.json' adding 'botocore/data/mediapackage-vod/2018-11-07/service-2.json' adding 'botocore/data/mediapackagev2/2022-12-25/endpoint-rule-set-1.json' adding 'botocore/data/mediapackagev2/2022-12-25/paginators-1.json' adding 'botocore/data/mediapackagev2/2022-12-25/service-2.json' adding 'botocore/data/mediapackagev2/2022-12-25/waiters-2.json' adding 'botocore/data/mediastore/2017-09-01/endpoint-rule-set-1.json' adding 'botocore/data/mediastore/2017-09-01/examples-1.json' adding 'botocore/data/mediastore/2017-09-01/paginators-1.json' adding 'botocore/data/mediastore/2017-09-01/service-2.json' adding 'botocore/data/mediastore-data/2017-09-01/endpoint-rule-set-1.json' adding 'botocore/data/mediastore-data/2017-09-01/examples-1.json' adding 'botocore/data/mediastore-data/2017-09-01/paginators-1.json' adding 'botocore/data/mediastore-data/2017-09-01/service-2.json' adding 'botocore/data/mediatailor/2018-04-23/endpoint-rule-set-1.json' adding 'botocore/data/mediatailor/2018-04-23/paginators-1.json' adding 'botocore/data/mediatailor/2018-04-23/service-2.json' adding 'botocore/data/medical-imaging/2023-07-19/endpoint-rule-set-1.json' adding 'botocore/data/medical-imaging/2023-07-19/paginators-1.json' adding 'botocore/data/medical-imaging/2023-07-19/paginators-1.sdk-extras.json' adding 'botocore/data/medical-imaging/2023-07-19/service-2.json' adding 'botocore/data/medical-imaging/2023-07-19/waiters-2.json' adding 'botocore/data/memorydb/2021-01-01/endpoint-rule-set-1.json' adding 'botocore/data/memorydb/2021-01-01/examples-1.json' adding 'botocore/data/memorydb/2021-01-01/paginators-1.json' adding 'botocore/data/memorydb/2021-01-01/service-2.json' adding 'botocore/data/meteringmarketplace/2016-01-14/endpoint-rule-set-1.json' adding 'botocore/data/meteringmarketplace/2016-01-14/examples-1.json' adding 'botocore/data/meteringmarketplace/2016-01-14/paginators-1.json' adding 'botocore/data/meteringmarketplace/2016-01-14/service-2.json' adding 'botocore/data/mgh/2017-05-31/endpoint-rule-set-1.json' adding 'botocore/data/mgh/2017-05-31/examples-1.json' adding 'botocore/data/mgh/2017-05-31/paginators-1.json' adding 'botocore/data/mgh/2017-05-31/service-2.json' adding 'botocore/data/mgn/2020-02-26/endpoint-rule-set-1.json' adding 'botocore/data/mgn/2020-02-26/examples-1.json' adding 'botocore/data/mgn/2020-02-26/paginators-1.json' adding 'botocore/data/mgn/2020-02-26/service-2.json' adding 'botocore/data/mgn/2020-02-26/waiters-2.json' adding 'botocore/data/migration-hub-refactor-spaces/2021-10-26/endpoint-rule-set-1.json' adding 'botocore/data/migration-hub-refactor-spaces/2021-10-26/examples-1.json' adding 'botocore/data/migration-hub-refactor-spaces/2021-10-26/paginators-1.json' adding 'botocore/data/migration-hub-refactor-spaces/2021-10-26/service-2.json' adding 'botocore/data/migrationhub-config/2019-06-30/endpoint-rule-set-1.json' adding 'botocore/data/migrationhub-config/2019-06-30/examples-1.json' adding 'botocore/data/migrationhub-config/2019-06-30/paginators-1.json' adding 'botocore/data/migrationhub-config/2019-06-30/service-2.json' adding 'botocore/data/migrationhuborchestrator/2021-08-28/endpoint-rule-set-1.json' adding 'botocore/data/migrationhuborchestrator/2021-08-28/paginators-1.json' adding 'botocore/data/migrationhuborchestrator/2021-08-28/service-2.json' adding 'botocore/data/migrationhuborchestrator/2021-08-28/waiters-2.json' adding 'botocore/data/migrationhubstrategy/2020-02-19/endpoint-rule-set-1.json' adding 'botocore/data/migrationhubstrategy/2020-02-19/examples-1.json' adding 'botocore/data/migrationhubstrategy/2020-02-19/paginators-1.json' adding 'botocore/data/migrationhubstrategy/2020-02-19/paginators-1.sdk-extras.json' adding 'botocore/data/migrationhubstrategy/2020-02-19/service-2.json' adding 'botocore/data/mpa/2022-07-26/endpoint-rule-set-1.json' adding 'botocore/data/mpa/2022-07-26/paginators-1.json' adding 'botocore/data/mpa/2022-07-26/service-2.json' adding 'botocore/data/mpa/2022-07-26/waiters-2.json' adding 'botocore/data/mq/2017-11-27/endpoint-rule-set-1.json' adding 'botocore/data/mq/2017-11-27/paginators-1.json' adding 'botocore/data/mq/2017-11-27/service-2.json' adding 'botocore/data/mturk/2017-01-17/endpoint-rule-set-1.json' adding 'botocore/data/mturk/2017-01-17/examples-1.json' adding 'botocore/data/mturk/2017-01-17/paginators-1.json' adding 'botocore/data/mturk/2017-01-17/service-2.json' adding 'botocore/data/mwaa/2020-07-01/endpoint-rule-set-1.json' adding 'botocore/data/mwaa/2020-07-01/examples-1.json' adding 'botocore/data/mwaa/2020-07-01/paginators-1.json' adding 'botocore/data/mwaa/2020-07-01/service-2.json' adding 'botocore/data/mwaa-serverless/2024-07-26/endpoint-rule-set-1.json' adding 'botocore/data/mwaa-serverless/2024-07-26/paginators-1.json' adding 'botocore/data/mwaa-serverless/2024-07-26/service-2.json' adding 'botocore/data/mwaa-serverless/2024-07-26/waiters-2.json' adding 'botocore/data/neptune/2014-10-31/endpoint-rule-set-1.json' adding 'botocore/data/neptune/2014-10-31/examples-1.json' adding 'botocore/data/neptune/2014-10-31/paginators-1.json' adding 'botocore/data/neptune/2014-10-31/service-2.json' adding 'botocore/data/neptune/2014-10-31/service-2.sdk-extras.json' adding 'botocore/data/neptune/2014-10-31/waiters-2.json' adding 'botocore/data/neptune-graph/2023-11-29/endpoint-rule-set-1.json' adding 'botocore/data/neptune-graph/2023-11-29/paginators-1.json' adding 'botocore/data/neptune-graph/2023-11-29/service-2.json' adding 'botocore/data/neptune-graph/2023-11-29/waiters-2.json' adding 'botocore/data/neptunedata/2023-08-01/endpoint-rule-set-1.json' adding 'botocore/data/neptunedata/2023-08-01/paginators-1.json' adding 'botocore/data/neptunedata/2023-08-01/service-2.json' adding 'botocore/data/network-firewall/2020-11-12/endpoint-rule-set-1.json' adding 'botocore/data/network-firewall/2020-11-12/examples-1.json' adding 'botocore/data/network-firewall/2020-11-12/paginators-1.json' adding 'botocore/data/network-firewall/2020-11-12/paginators-1.sdk-extras.json' adding 'botocore/data/network-firewall/2020-11-12/service-2.json' adding 'botocore/data/networkflowmonitor/2023-04-19/endpoint-rule-set-1.json' adding 'botocore/data/networkflowmonitor/2023-04-19/paginators-1.json' adding 'botocore/data/networkflowmonitor/2023-04-19/paginators-1.sdk-extras.json' adding 'botocore/data/networkflowmonitor/2023-04-19/service-2.json' adding 'botocore/data/networkflowmonitor/2023-04-19/waiters-2.json' adding 'botocore/data/networkmanager/2019-07-05/endpoint-rule-set-1.json' adding 'botocore/data/networkmanager/2019-07-05/examples-1.json' adding 'botocore/data/networkmanager/2019-07-05/paginators-1.json' adding 'botocore/data/networkmanager/2019-07-05/service-2.json' adding 'botocore/data/networkmonitor/2023-08-01/endpoint-rule-set-1.json' adding 'botocore/data/networkmonitor/2023-08-01/paginators-1.json' adding 'botocore/data/networkmonitor/2023-08-01/service-2.json' adding 'botocore/data/networkmonitor/2023-08-01/waiters-2.json' adding 'botocore/data/notifications/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/notifications/2018-05-10/paginators-1.json' adding 'botocore/data/notifications/2018-05-10/service-2.json' adding 'botocore/data/notifications/2018-05-10/waiters-2.json' adding 'botocore/data/notificationscontacts/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/notificationscontacts/2018-05-10/paginators-1.json' adding 'botocore/data/notificationscontacts/2018-05-10/service-2.json' adding 'botocore/data/notificationscontacts/2018-05-10/waiters-2.json' adding 'botocore/data/nova-act/2025-08-22/endpoint-rule-set-1.json' adding 'botocore/data/nova-act/2025-08-22/paginators-1.json' adding 'botocore/data/nova-act/2025-08-22/service-2.json' adding 'botocore/data/nova-act/2025-08-22/waiters-2.json' adding 'botocore/data/oam/2022-06-10/endpoint-rule-set-1.json' adding 'botocore/data/oam/2022-06-10/paginators-1.json' adding 'botocore/data/oam/2022-06-10/service-2.json' adding 'botocore/data/observabilityadmin/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/observabilityadmin/2018-05-10/paginators-1.json' adding 'botocore/data/observabilityadmin/2018-05-10/service-2.json' adding 'botocore/data/observabilityadmin/2018-05-10/waiters-2.json' adding 'botocore/data/odb/2024-08-20/endpoint-rule-set-1.json' adding 'botocore/data/odb/2024-08-20/paginators-1.json' adding 'botocore/data/odb/2024-08-20/service-2.json' adding 'botocore/data/odb/2024-08-20/waiters-2.json' adding 'botocore/data/omics/2022-11-28/endpoint-rule-set-1.json' adding 'botocore/data/omics/2022-11-28/paginators-1.json' adding 'botocore/data/omics/2022-11-28/service-2.json' adding 'botocore/data/omics/2022-11-28/waiters-2.json' adding 'botocore/data/opensearch/2021-01-01/endpoint-rule-set-1.json' adding 'botocore/data/opensearch/2021-01-01/examples-1.json' adding 'botocore/data/opensearch/2021-01-01/paginators-1.json' adding 'botocore/data/opensearch/2021-01-01/service-2.json' adding 'botocore/data/opensearchserverless/2021-11-01/endpoint-rule-set-1.json' adding 'botocore/data/opensearchserverless/2021-11-01/paginators-1.json' adding 'botocore/data/opensearchserverless/2021-11-01/service-2.json' adding 'botocore/data/opensearchserverless/2021-11-01/waiters-2.json' adding 'botocore/data/organizations/2016-11-28/endpoint-rule-set-1.json' adding 'botocore/data/organizations/2016-11-28/examples-1.json' adding 'botocore/data/organizations/2016-11-28/paginators-1.json' adding 'botocore/data/organizations/2016-11-28/paginators-1.sdk-extras.json' adding 'botocore/data/organizations/2016-11-28/service-2.json' adding 'botocore/data/osis/2022-01-01/endpoint-rule-set-1.json' adding 'botocore/data/osis/2022-01-01/paginators-1.json' adding 'botocore/data/osis/2022-01-01/service-2.json' adding 'botocore/data/outposts/2019-12-03/endpoint-rule-set-1.json' adding 'botocore/data/outposts/2019-12-03/examples-1.json' adding 'botocore/data/outposts/2019-12-03/paginators-1.json' adding 'botocore/data/outposts/2019-12-03/paginators-1.sdk-extras.json' adding 'botocore/data/outposts/2019-12-03/service-2.json' adding 'botocore/data/panorama/2019-07-24/endpoint-rule-set-1.json' adding 'botocore/data/panorama/2019-07-24/examples-1.json' adding 'botocore/data/panorama/2019-07-24/paginators-1.json' adding 'botocore/data/panorama/2019-07-24/service-2.json' adding 'botocore/data/partnercentral-account/2025-04-04/endpoint-rule-set-1.json' adding 'botocore/data/partnercentral-account/2025-04-04/paginators-1.json' adding 'botocore/data/partnercentral-account/2025-04-04/service-2.json' adding 'botocore/data/partnercentral-account/2025-04-04/waiters-2.json' adding 'botocore/data/partnercentral-benefits/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/partnercentral-benefits/2018-05-10/paginators-1.json' adding 'botocore/data/partnercentral-benefits/2018-05-10/service-2.json' adding 'botocore/data/partnercentral-benefits/2018-05-10/waiters-2.json' adding 'botocore/data/partnercentral-channel/2024-03-18/endpoint-rule-set-1.json' adding 'botocore/data/partnercentral-channel/2024-03-18/paginators-1.json' adding 'botocore/data/partnercentral-channel/2024-03-18/service-2.json' adding 'botocore/data/partnercentral-channel/2024-03-18/waiters-2.json' adding 'botocore/data/partnercentral-selling/2022-07-26/endpoint-rule-set-1.json' adding 'botocore/data/partnercentral-selling/2022-07-26/paginators-1.json' adding 'botocore/data/partnercentral-selling/2022-07-26/service-2.json' adding 'botocore/data/partnercentral-selling/2022-07-26/waiters-2.json' adding 'botocore/data/payment-cryptography/2021-09-14/endpoint-rule-set-1.json' adding 'botocore/data/payment-cryptography/2021-09-14/paginators-1.json' adding 'botocore/data/payment-cryptography/2021-09-14/service-2.json' adding 'botocore/data/payment-cryptography/2021-09-14/waiters-2.json' adding 'botocore/data/payment-cryptography-data/2022-02-03/endpoint-rule-set-1.json' adding 'botocore/data/payment-cryptography-data/2022-02-03/paginators-1.json' adding 'botocore/data/payment-cryptography-data/2022-02-03/service-2.json' adding 'botocore/data/payment-cryptography-data/2022-02-03/waiters-2.json' adding 'botocore/data/pca-connector-ad/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/pca-connector-ad/2018-05-10/paginators-1.json' adding 'botocore/data/pca-connector-ad/2018-05-10/service-2.json' adding 'botocore/data/pca-connector-scep/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/pca-connector-scep/2018-05-10/paginators-1.json' adding 'botocore/data/pca-connector-scep/2018-05-10/service-2.json' adding 'botocore/data/pca-connector-scep/2018-05-10/waiters-2.json' adding 'botocore/data/pcs/2023-02-10/endpoint-rule-set-1.json' adding 'botocore/data/pcs/2023-02-10/paginators-1.json' adding 'botocore/data/pcs/2023-02-10/service-2.json' adding 'botocore/data/pcs/2023-02-10/waiters-2.json' adding 'botocore/data/personalize/2018-05-22/endpoint-rule-set-1.json' adding 'botocore/data/personalize/2018-05-22/examples-1.json' adding 'botocore/data/personalize/2018-05-22/paginators-1.json' adding 'botocore/data/personalize/2018-05-22/service-2.json' adding 'botocore/data/personalize-events/2018-03-22/endpoint-rule-set-1.json' adding 'botocore/data/personalize-events/2018-03-22/examples-1.json' adding 'botocore/data/personalize-events/2018-03-22/paginators-1.json' adding 'botocore/data/personalize-events/2018-03-22/service-2.json' adding 'botocore/data/personalize-runtime/2018-05-22/endpoint-rule-set-1.json' adding 'botocore/data/personalize-runtime/2018-05-22/examples-1.json' adding 'botocore/data/personalize-runtime/2018-05-22/paginators-1.json' adding 'botocore/data/personalize-runtime/2018-05-22/service-2.json' adding 'botocore/data/pi/2018-02-27/endpoint-rule-set-1.json' adding 'botocore/data/pi/2018-02-27/examples-1.json' adding 'botocore/data/pi/2018-02-27/paginators-1.json' adding 'botocore/data/pi/2018-02-27/service-2.json' adding 'botocore/data/pinpoint/2016-12-01/endpoint-rule-set-1.json' adding 'botocore/data/pinpoint/2016-12-01/examples-1.json' adding 'botocore/data/pinpoint/2016-12-01/service-2.json' adding 'botocore/data/pinpoint-email/2018-07-26/endpoint-rule-set-1.json' adding 'botocore/data/pinpoint-email/2018-07-26/examples-1.json' adding 'botocore/data/pinpoint-email/2018-07-26/paginators-1.json' adding 'botocore/data/pinpoint-email/2018-07-26/service-2.json' adding 'botocore/data/pinpoint-sms-voice/2018-09-05/endpoint-rule-set-1.json' adding 'botocore/data/pinpoint-sms-voice/2018-09-05/service-2.json' adding 'botocore/data/pinpoint-sms-voice-v2/2022-03-31/endpoint-rule-set-1.json' adding 'botocore/data/pinpoint-sms-voice-v2/2022-03-31/examples-1.json' adding 'botocore/data/pinpoint-sms-voice-v2/2022-03-31/paginators-1.json' adding 'botocore/data/pinpoint-sms-voice-v2/2022-03-31/paginators-1.sdk-extras.json' adding 'botocore/data/pinpoint-sms-voice-v2/2022-03-31/service-2.json' adding 'botocore/data/pinpoint-sms-voice-v2/2022-03-31/waiters-2.json' adding 'botocore/data/pipes/2015-10-07/endpoint-rule-set-1.json' adding 'botocore/data/pipes/2015-10-07/paginators-1.json' adding 'botocore/data/pipes/2015-10-07/service-2.json' adding 'botocore/data/pipes/2015-10-07/waiters-2.json' adding 'botocore/data/polly/2016-06-10/endpoint-rule-set-1.json' adding 'botocore/data/polly/2016-06-10/examples-1.json' adding 'botocore/data/polly/2016-06-10/paginators-1.json' adding 'botocore/data/polly/2016-06-10/service-2.json' adding 'botocore/data/pricing/2017-10-15/endpoint-rule-set-1.json' adding 'botocore/data/pricing/2017-10-15/examples-1.json' adding 'botocore/data/pricing/2017-10-15/paginators-1.json' adding 'botocore/data/pricing/2017-10-15/service-2.json' adding 'botocore/data/pricing/2017-10-15/waiters-2.json' adding 'botocore/data/proton/2020-07-20/endpoint-rule-set-1.json' adding 'botocore/data/proton/2020-07-20/examples-1.json' adding 'botocore/data/proton/2020-07-20/paginators-1.json' adding 'botocore/data/proton/2020-07-20/service-2.json' adding 'botocore/data/proton/2020-07-20/waiters-2.json' adding 'botocore/data/qapps/2023-11-27/endpoint-rule-set-1.json' adding 'botocore/data/qapps/2023-11-27/paginators-1.json' adding 'botocore/data/qapps/2023-11-27/service-2.json' adding 'botocore/data/qapps/2023-11-27/waiters-2.json' adding 'botocore/data/qbusiness/2023-11-27/endpoint-rule-set-1.json' adding 'botocore/data/qbusiness/2023-11-27/paginators-1.json' adding 'botocore/data/qbusiness/2023-11-27/paginators-1.sdk-extras.json' adding 'botocore/data/qbusiness/2023-11-27/service-2.json' adding 'botocore/data/qbusiness/2023-11-27/waiters-2.json' adding 'botocore/data/qconnect/2020-10-19/endpoint-rule-set-1.json' adding 'botocore/data/qconnect/2020-10-19/paginators-1.json' adding 'botocore/data/qconnect/2020-10-19/service-2.json' adding 'botocore/data/qconnect/2020-10-19/waiters-2.json' adding 'botocore/data/quicksight/2018-04-01/endpoint-rule-set-1.json' adding 'botocore/data/quicksight/2018-04-01/examples-1.json' adding 'botocore/data/quicksight/2018-04-01/paginators-1.json' adding 'botocore/data/quicksight/2018-04-01/paginators-1.sdk-extras.json' adding 'botocore/data/quicksight/2018-04-01/service-2.json' adding 'botocore/data/ram/2018-01-04/endpoint-rule-set-1.json' adding 'botocore/data/ram/2018-01-04/examples-1.json' adding 'botocore/data/ram/2018-01-04/paginators-1.json' adding 'botocore/data/ram/2018-01-04/service-2.json' adding 'botocore/data/rbin/2021-06-15/endpoint-rule-set-1.json' adding 'botocore/data/rbin/2021-06-15/examples-1.json' adding 'botocore/data/rbin/2021-06-15/paginators-1.json' adding 'botocore/data/rbin/2021-06-15/service-2.json' adding 'botocore/data/rds/2014-09-01/endpoint-rule-set-1.json' adding 'botocore/data/rds/2014-09-01/paginators-1.json' adding 'botocore/data/rds/2014-09-01/service-2.json' adding 'botocore/data/rds/2014-09-01/waiters-2.json' adding 'botocore/data/rds/2014-10-31/endpoint-rule-set-1.json' adding 'botocore/data/rds/2014-10-31/examples-1.json' adding 'botocore/data/rds/2014-10-31/paginators-1.json' adding 'botocore/data/rds/2014-10-31/paginators-1.sdk-extras.json' adding 'botocore/data/rds/2014-10-31/service-2.json' adding 'botocore/data/rds/2014-10-31/service-2.sdk-extras.json' adding 'botocore/data/rds/2014-10-31/waiters-2.json' adding 'botocore/data/rds-data/2018-08-01/endpoint-rule-set-1.json' adding 'botocore/data/rds-data/2018-08-01/examples-1.json' adding 'botocore/data/rds-data/2018-08-01/paginators-1.json' adding 'botocore/data/rds-data/2018-08-01/service-2.json' adding 'botocore/data/redshift/2012-12-01/endpoint-rule-set-1.json' adding 'botocore/data/redshift/2012-12-01/examples-1.json' adding 'botocore/data/redshift/2012-12-01/paginators-1.json' adding 'botocore/data/redshift/2012-12-01/service-2.json' adding 'botocore/data/redshift/2012-12-01/waiters-2.json' adding 'botocore/data/redshift-data/2019-12-20/endpoint-rule-set-1.json' adding 'botocore/data/redshift-data/2019-12-20/examples-1.json' adding 'botocore/data/redshift-data/2019-12-20/paginators-1.json' adding 'botocore/data/redshift-data/2019-12-20/paginators-1.sdk-extras.json' adding 'botocore/data/redshift-data/2019-12-20/service-2.json' adding 'botocore/data/redshift-serverless/2021-04-21/endpoint-rule-set-1.json' adding 'botocore/data/redshift-serverless/2021-04-21/paginators-1.json' adding 'botocore/data/redshift-serverless/2021-04-21/service-2.json' adding 'botocore/data/rekognition/2016-06-27/endpoint-rule-set-1.json' adding 'botocore/data/rekognition/2016-06-27/examples-1.json' adding 'botocore/data/rekognition/2016-06-27/paginators-1.json' adding 'botocore/data/rekognition/2016-06-27/service-2.json' adding 'botocore/data/rekognition/2016-06-27/waiters-2.json' adding 'botocore/data/repostspace/2022-05-13/endpoint-rule-set-1.json' adding 'botocore/data/repostspace/2022-05-13/paginators-1.json' adding 'botocore/data/repostspace/2022-05-13/service-2.json' adding 'botocore/data/repostspace/2022-05-13/waiters-2.json' adding 'botocore/data/resiliencehub/2020-04-30/endpoint-rule-set-1.json' adding 'botocore/data/resiliencehub/2020-04-30/examples-1.json' adding 'botocore/data/resiliencehub/2020-04-30/paginators-1.json' adding 'botocore/data/resiliencehub/2020-04-30/service-2.json' adding 'botocore/data/resource-explorer-2/2022-07-28/endpoint-rule-set-1.json' adding 'botocore/data/resource-explorer-2/2022-07-28/paginators-1.json' adding 'botocore/data/resource-explorer-2/2022-07-28/paginators-1.sdk-extras.json' adding 'botocore/data/resource-explorer-2/2022-07-28/service-2.json' adding 'botocore/data/resource-explorer-2/2022-07-28/waiters-2.json' adding 'botocore/data/resource-groups/2017-11-27/endpoint-rule-set-1.json' adding 'botocore/data/resource-groups/2017-11-27/examples-1.json' adding 'botocore/data/resource-groups/2017-11-27/paginators-1.json' adding 'botocore/data/resource-groups/2017-11-27/paginators-1.sdk-extras.json' adding 'botocore/data/resource-groups/2017-11-27/service-2.json' adding 'botocore/data/resourcegroupstaggingapi/2017-01-26/endpoint-rule-set-1.json' adding 'botocore/data/resourcegroupstaggingapi/2017-01-26/examples-1.json' adding 'botocore/data/resourcegroupstaggingapi/2017-01-26/paginators-1.json' adding 'botocore/data/resourcegroupstaggingapi/2017-01-26/service-2.json' adding 'botocore/data/rolesanywhere/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/rolesanywhere/2018-05-10/paginators-1.json' adding 'botocore/data/rolesanywhere/2018-05-10/service-2.json' adding 'botocore/data/rolesanywhere/2018-05-10/waiters-2.json' adding 'botocore/data/route53/2013-04-01/endpoint-rule-set-1.json' adding 'botocore/data/route53/2013-04-01/examples-1.json' adding 'botocore/data/route53/2013-04-01/paginators-1.json' adding 'botocore/data/route53/2013-04-01/service-2.json' adding 'botocore/data/route53/2013-04-01/waiters-2.json' adding 'botocore/data/route53-recovery-cluster/2019-12-02/endpoint-rule-set-1.json' adding 'botocore/data/route53-recovery-cluster/2019-12-02/examples-1.json' adding 'botocore/data/route53-recovery-cluster/2019-12-02/paginators-1.json' adding 'botocore/data/route53-recovery-cluster/2019-12-02/service-2.json' adding 'botocore/data/route53-recovery-control-config/2020-11-02/endpoint-rule-set-1.json' adding 'botocore/data/route53-recovery-control-config/2020-11-02/paginators-1.json' adding 'botocore/data/route53-recovery-control-config/2020-11-02/service-2.json' adding 'botocore/data/route53-recovery-control-config/2020-11-02/waiters-2.json' adding 'botocore/data/route53-recovery-readiness/2019-12-02/endpoint-rule-set-1.json' adding 'botocore/data/route53-recovery-readiness/2019-12-02/paginators-1.json' adding 'botocore/data/route53-recovery-readiness/2019-12-02/service-2.json' adding 'botocore/data/route53domains/2014-05-15/endpoint-rule-set-1.json' adding 'botocore/data/route53domains/2014-05-15/examples-1.json' adding 'botocore/data/route53domains/2014-05-15/paginators-1.json' adding 'botocore/data/route53domains/2014-05-15/service-2.json' adding 'botocore/data/route53globalresolver/2022-09-27/endpoint-rule-set-1.json' adding 'botocore/data/route53globalresolver/2022-09-27/paginators-1.json' adding 'botocore/data/route53globalresolver/2022-09-27/service-2.json' adding 'botocore/data/route53globalresolver/2022-09-27/waiters-2.json' adding 'botocore/data/route53profiles/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/route53profiles/2018-05-10/paginators-1.json' adding 'botocore/data/route53profiles/2018-05-10/service-2.json' adding 'botocore/data/route53resolver/2018-04-01/endpoint-rule-set-1.json' adding 'botocore/data/route53resolver/2018-04-01/examples-1.json' adding 'botocore/data/route53resolver/2018-04-01/paginators-1.json' adding 'botocore/data/route53resolver/2018-04-01/paginators-1.sdk-extras.json' adding 'botocore/data/route53resolver/2018-04-01/service-2.json' adding 'botocore/data/rtbfabric/2023-05-15/endpoint-rule-set-1.json' adding 'botocore/data/rtbfabric/2023-05-15/paginators-1.json' adding 'botocore/data/rtbfabric/2023-05-15/service-2.json' adding 'botocore/data/rtbfabric/2023-05-15/waiters-2.json' adding 'botocore/data/rum/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/rum/2018-05-10/examples-1.json' adding 'botocore/data/rum/2018-05-10/paginators-1.json' adding 'botocore/data/rum/2018-05-10/service-2.json' adding 'botocore/data/rum/2018-05-10/waiters-2.json' adding 'botocore/data/s3/2006-03-01/endpoint-rule-set-1.json' adding 'botocore/data/s3/2006-03-01/examples-1.json' adding 'botocore/data/s3/2006-03-01/paginators-1.json' adding 'botocore/data/s3/2006-03-01/paginators-1.sdk-extras.json' adding 'botocore/data/s3/2006-03-01/service-2.json' adding 'botocore/data/s3/2006-03-01/service-2.sdk-extras.json' adding 'botocore/data/s3/2006-03-01/waiters-2.json' adding 'botocore/data/s3control/2018-08-20/endpoint-rule-set-1.json' adding 'botocore/data/s3control/2018-08-20/examples-1.json' adding 'botocore/data/s3control/2018-08-20/paginators-1.json' adding 'botocore/data/s3control/2018-08-20/service-2.json' adding 'botocore/data/s3files/2025-05-05/endpoint-rule-set-1.json' adding 'botocore/data/s3files/2025-05-05/paginators-1.json' adding 'botocore/data/s3files/2025-05-05/service-2.json' adding 'botocore/data/s3files/2025-05-05/waiters-2.json' adding 'botocore/data/s3outposts/2017-07-25/endpoint-rule-set-1.json' adding 'botocore/data/s3outposts/2017-07-25/examples-1.json' adding 'botocore/data/s3outposts/2017-07-25/paginators-1.json' adding 'botocore/data/s3outposts/2017-07-25/service-2.json' adding 'botocore/data/s3tables/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/s3tables/2018-05-10/paginators-1.json' adding 'botocore/data/s3tables/2018-05-10/service-2.json' adding 'botocore/data/s3tables/2018-05-10/waiters-2.json' adding 'botocore/data/s3vectors/2025-07-15/endpoint-rule-set-1.json' adding 'botocore/data/s3vectors/2025-07-15/paginators-1.json' adding 'botocore/data/s3vectors/2025-07-15/service-2.json' adding 'botocore/data/s3vectors/2025-07-15/waiters-2.json' adding 'botocore/data/sagemaker/2017-07-24/endpoint-rule-set-1.json' adding 'botocore/data/sagemaker/2017-07-24/examples-1.json' adding 'botocore/data/sagemaker/2017-07-24/paginators-1.json' adding 'botocore/data/sagemaker/2017-07-24/paginators-1.sdk-extras.json' adding 'botocore/data/sagemaker/2017-07-24/service-2.json' adding 'botocore/data/sagemaker/2017-07-24/waiters-2.json' adding 'botocore/data/sagemaker-a2i-runtime/2019-11-07/endpoint-rule-set-1.json' adding 'botocore/data/sagemaker-a2i-runtime/2019-11-07/examples-1.json' adding 'botocore/data/sagemaker-a2i-runtime/2019-11-07/paginators-1.json' adding 'botocore/data/sagemaker-a2i-runtime/2019-11-07/service-2.json' adding 'botocore/data/sagemaker-edge/2020-09-23/endpoint-rule-set-1.json' adding 'botocore/data/sagemaker-edge/2020-09-23/examples-1.json' adding 'botocore/data/sagemaker-edge/2020-09-23/paginators-1.json' adding 'botocore/data/sagemaker-edge/2020-09-23/service-2.json' adding 'botocore/data/sagemaker-featurestore-runtime/2020-07-01/endpoint-rule-set-1.json' adding 'botocore/data/sagemaker-featurestore-runtime/2020-07-01/examples-1.json' adding 'botocore/data/sagemaker-featurestore-runtime/2020-07-01/paginators-1.json' adding 'botocore/data/sagemaker-featurestore-runtime/2020-07-01/service-2.json' adding 'botocore/data/sagemaker-geospatial/2020-05-27/endpoint-rule-set-1.json' adding 'botocore/data/sagemaker-geospatial/2020-05-27/paginators-1.json' adding 'botocore/data/sagemaker-geospatial/2020-05-27/service-2.json' adding 'botocore/data/sagemaker-metrics/2022-09-30/endpoint-rule-set-1.json' adding 'botocore/data/sagemaker-metrics/2022-09-30/paginators-1.json' adding 'botocore/data/sagemaker-metrics/2022-09-30/service-2.json' adding 'botocore/data/sagemaker-runtime/2017-05-13/endpoint-rule-set-1.json' adding 'botocore/data/sagemaker-runtime/2017-05-13/examples-1.json' adding 'botocore/data/sagemaker-runtime/2017-05-13/paginators-1.json' adding 'botocore/data/sagemaker-runtime/2017-05-13/service-2.json' adding 'botocore/data/savingsplans/2019-06-28/endpoint-rule-set-1.json' adding 'botocore/data/savingsplans/2019-06-28/examples-1.json' adding 'botocore/data/savingsplans/2019-06-28/paginators-1.json' adding 'botocore/data/savingsplans/2019-06-28/service-2.json' adding 'botocore/data/scheduler/2021-06-30/endpoint-rule-set-1.json' adding 'botocore/data/scheduler/2021-06-30/paginators-1.json' adding 'botocore/data/scheduler/2021-06-30/service-2.json' adding 'botocore/data/schemas/2019-12-02/endpoint-rule-set-1.json' adding 'botocore/data/schemas/2019-12-02/paginators-1.json' adding 'botocore/data/schemas/2019-12-02/service-2.json' adding 'botocore/data/schemas/2019-12-02/waiters-2.json' adding 'botocore/data/sdb/2009-04-15/endpoint-rule-set-1.json' adding 'botocore/data/sdb/2009-04-15/paginators-1.json' adding 'botocore/data/sdb/2009-04-15/service-2.json' adding 'botocore/data/secretsmanager/2017-10-17/endpoint-rule-set-1.json' adding 'botocore/data/secretsmanager/2017-10-17/examples-1.json' adding 'botocore/data/secretsmanager/2017-10-17/paginators-1.json' adding 'botocore/data/secretsmanager/2017-10-17/service-2.json' adding 'botocore/data/secretsmanager/2017-10-17/service-2.sdk-extras.json' adding 'botocore/data/security-ir/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/security-ir/2018-05-10/paginators-1.json' adding 'botocore/data/security-ir/2018-05-10/paginators-1.sdk-extras.json' adding 'botocore/data/security-ir/2018-05-10/service-2.json' adding 'botocore/data/security-ir/2018-05-10/waiters-2.json' adding 'botocore/data/securityagent/2025-09-06/endpoint-rule-set-1.json' adding 'botocore/data/securityagent/2025-09-06/paginators-1.json' adding 'botocore/data/securityagent/2025-09-06/service-2.json' adding 'botocore/data/securityagent/2025-09-06/waiters-2.json' adding 'botocore/data/securityhub/2018-10-26/endpoint-rule-set-1.json' adding 'botocore/data/securityhub/2018-10-26/examples-1.json' adding 'botocore/data/securityhub/2018-10-26/paginators-1.json' adding 'botocore/data/securityhub/2018-10-26/paginators-1.sdk-extras.json' adding 'botocore/data/securityhub/2018-10-26/service-2.json' adding 'botocore/data/securitylake/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/securitylake/2018-05-10/paginators-1.json' adding 'botocore/data/securitylake/2018-05-10/paginators-1.sdk-extras.json' adding 'botocore/data/securitylake/2018-05-10/service-2.json' adding 'botocore/data/serverlessrepo/2017-09-08/endpoint-rule-set-1.json' adding 'botocore/data/serverlessrepo/2017-09-08/paginators-1.json' adding 'botocore/data/serverlessrepo/2017-09-08/service-2.json' adding 'botocore/data/service-quotas/2019-06-24/endpoint-rule-set-1.json' adding 'botocore/data/service-quotas/2019-06-24/examples-1.json' adding 'botocore/data/service-quotas/2019-06-24/paginators-1.json' adding 'botocore/data/service-quotas/2019-06-24/service-2.json' adding 'botocore/data/servicecatalog/2015-12-10/endpoint-rule-set-1.json' adding 'botocore/data/servicecatalog/2015-12-10/examples-1.json' adding 'botocore/data/servicecatalog/2015-12-10/paginators-1.json' adding 'botocore/data/servicecatalog/2015-12-10/service-2.json' adding 'botocore/data/servicecatalog-appregistry/2020-06-24/endpoint-rule-set-1.json' adding 'botocore/data/servicecatalog-appregistry/2020-06-24/examples-1.json' adding 'botocore/data/servicecatalog-appregistry/2020-06-24/paginators-1.json' adding 'botocore/data/servicecatalog-appregistry/2020-06-24/service-2.json' adding 'botocore/data/servicediscovery/2017-03-14/endpoint-rule-set-1.json' adding 'botocore/data/servicediscovery/2017-03-14/examples-1.json' adding 'botocore/data/servicediscovery/2017-03-14/paginators-1.json' adding 'botocore/data/servicediscovery/2017-03-14/paginators-1.sdk-extras.json' adding 'botocore/data/servicediscovery/2017-03-14/service-2.json' adding 'botocore/data/ses/2010-12-01/endpoint-rule-set-1.json' adding 'botocore/data/ses/2010-12-01/examples-1.json' adding 'botocore/data/ses/2010-12-01/paginators-1.json' adding 'botocore/data/ses/2010-12-01/service-2.json' adding 'botocore/data/ses/2010-12-01/waiters-2.json' adding 'botocore/data/sesv2/2019-09-27/endpoint-rule-set-1.json' adding 'botocore/data/sesv2/2019-09-27/examples-1.json' adding 'botocore/data/sesv2/2019-09-27/paginators-1.json' adding 'botocore/data/sesv2/2019-09-27/service-2.json' adding 'botocore/data/shield/2016-06-02/endpoint-rule-set-1.json' adding 'botocore/data/shield/2016-06-02/examples-1.json' adding 'botocore/data/shield/2016-06-02/paginators-1.json' adding 'botocore/data/shield/2016-06-02/service-2.json' adding 'botocore/data/signer/2017-08-25/endpoint-rule-set-1.json' adding 'botocore/data/signer/2017-08-25/examples-1.json' adding 'botocore/data/signer/2017-08-25/paginators-1.json' adding 'botocore/data/signer/2017-08-25/service-2.json' adding 'botocore/data/signer/2017-08-25/waiters-2.json' adding 'botocore/data/signer-data/2017-08-25/endpoint-rule-set-1.json' adding 'botocore/data/signer-data/2017-08-25/paginators-1.json' adding 'botocore/data/signer-data/2017-08-25/service-2.json' adding 'botocore/data/signer-data/2017-08-25/waiters-2.json' adding 'botocore/data/signin/2023-01-01/endpoint-rule-set-1.json' adding 'botocore/data/signin/2023-01-01/paginators-1.json' adding 'botocore/data/signin/2023-01-01/service-2.json' adding 'botocore/data/simpledbv2/2025-09-26/endpoint-rule-set-1.json' adding 'botocore/data/simpledbv2/2025-09-26/paginators-1.json' adding 'botocore/data/simpledbv2/2025-09-26/service-2.json' adding 'botocore/data/simpledbv2/2025-09-26/waiters-2.json' adding 'botocore/data/simspaceweaver/2022-10-28/endpoint-rule-set-1.json' adding 'botocore/data/simspaceweaver/2022-10-28/paginators-1.json' adding 'botocore/data/simspaceweaver/2022-10-28/service-2.json' adding 'botocore/data/sms-voice/2018-09-05/endpoint-rule-set-1.json' adding 'botocore/data/sms-voice/2018-09-05/service-2.json' adding 'botocore/data/snow-device-management/2021-08-04/endpoint-rule-set-1.json' adding 'botocore/data/snow-device-management/2021-08-04/examples-1.json' adding 'botocore/data/snow-device-management/2021-08-04/paginators-1.json' adding 'botocore/data/snow-device-management/2021-08-04/service-2.json' adding 'botocore/data/snowball/2016-06-30/endpoint-rule-set-1.json' adding 'botocore/data/snowball/2016-06-30/examples-1.json' adding 'botocore/data/snowball/2016-06-30/paginators-1.json' adding 'botocore/data/snowball/2016-06-30/service-2.json' adding 'botocore/data/sns/2010-03-31/endpoint-rule-set-1.json' adding 'botocore/data/sns/2010-03-31/examples-1.json' adding 'botocore/data/sns/2010-03-31/paginators-1.json' adding 'botocore/data/sns/2010-03-31/service-2.json' adding 'botocore/data/socialmessaging/2024-01-01/endpoint-rule-set-1.json' adding 'botocore/data/socialmessaging/2024-01-01/paginators-1.json' adding 'botocore/data/socialmessaging/2024-01-01/service-2.json' adding 'botocore/data/sqs/2012-11-05/endpoint-rule-set-1.json' adding 'botocore/data/sqs/2012-11-05/examples-1.json' adding 'botocore/data/sqs/2012-11-05/paginators-1.json' adding 'botocore/data/sqs/2012-11-05/service-2.json' adding 'botocore/data/ssm/2014-11-06/endpoint-rule-set-1.json' adding 'botocore/data/ssm/2014-11-06/examples-1.json' adding 'botocore/data/ssm/2014-11-06/paginators-1.json' adding 'botocore/data/ssm/2014-11-06/service-2.json' adding 'botocore/data/ssm/2014-11-06/waiters-2.json' adding 'botocore/data/ssm-contacts/2021-05-03/endpoint-rule-set-1.json' adding 'botocore/data/ssm-contacts/2021-05-03/examples-1.json' adding 'botocore/data/ssm-contacts/2021-05-03/paginators-1.json' adding 'botocore/data/ssm-contacts/2021-05-03/service-2.json' adding 'botocore/data/ssm-guiconnect/2021-05-01/endpoint-rule-set-1.json' adding 'botocore/data/ssm-guiconnect/2021-05-01/paginators-1.json' adding 'botocore/data/ssm-guiconnect/2021-05-01/service-2.json' adding 'botocore/data/ssm-incidents/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/ssm-incidents/2018-05-10/examples-1.json' adding 'botocore/data/ssm-incidents/2018-05-10/paginators-1.json' adding 'botocore/data/ssm-incidents/2018-05-10/service-2.json' adding 'botocore/data/ssm-incidents/2018-05-10/waiters-2.json' adding 'botocore/data/ssm-quicksetup/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/ssm-quicksetup/2018-05-10/paginators-1.json' adding 'botocore/data/ssm-quicksetup/2018-05-10/service-2.json' adding 'botocore/data/ssm-sap/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/ssm-sap/2018-05-10/paginators-1.json' adding 'botocore/data/ssm-sap/2018-05-10/service-2.json' adding 'botocore/data/sso/2019-06-10/endpoint-rule-set-1.json' adding 'botocore/data/sso/2019-06-10/examples-1.json' adding 'botocore/data/sso/2019-06-10/paginators-1.json' adding 'botocore/data/sso/2019-06-10/service-2.json' adding 'botocore/data/sso-admin/2020-07-20/endpoint-rule-set-1.json' adding 'botocore/data/sso-admin/2020-07-20/examples-1.json' adding 'botocore/data/sso-admin/2020-07-20/paginators-1.json' adding 'botocore/data/sso-admin/2020-07-20/service-2.json' adding 'botocore/data/sso-admin/2020-07-20/waiters-2.json' adding 'botocore/data/sso-oidc/2019-06-10/endpoint-rule-set-1.json' adding 'botocore/data/sso-oidc/2019-06-10/examples-1.json' adding 'botocore/data/sso-oidc/2019-06-10/paginators-1.json' adding 'botocore/data/sso-oidc/2019-06-10/service-2.json' adding 'botocore/data/stepfunctions/2016-11-23/endpoint-rule-set-1.json' adding 'botocore/data/stepfunctions/2016-11-23/examples-1.json' adding 'botocore/data/stepfunctions/2016-11-23/paginators-1.json' adding 'botocore/data/stepfunctions/2016-11-23/service-2.json' adding 'botocore/data/storagegateway/2013-06-30/endpoint-rule-set-1.json' adding 'botocore/data/storagegateway/2013-06-30/examples-1.json' adding 'botocore/data/storagegateway/2013-06-30/paginators-1.json' adding 'botocore/data/storagegateway/2013-06-30/service-2.json' adding 'botocore/data/sts/2011-06-15/endpoint-rule-set-1.json' adding 'botocore/data/sts/2011-06-15/examples-1.json' adding 'botocore/data/sts/2011-06-15/paginators-1.json' adding 'botocore/data/sts/2011-06-15/service-2.json' adding 'botocore/data/supplychain/2024-01-01/endpoint-rule-set-1.json' adding 'botocore/data/supplychain/2024-01-01/paginators-1.json' adding 'botocore/data/supplychain/2024-01-01/service-2.json' adding 'botocore/data/support/2013-04-15/endpoint-rule-set-1.json' adding 'botocore/data/support/2013-04-15/examples-1.json' adding 'botocore/data/support/2013-04-15/paginators-1.json' adding 'botocore/data/support/2013-04-15/service-2.json' adding 'botocore/data/support-app/2021-08-20/endpoint-rule-set-1.json' adding 'botocore/data/support-app/2021-08-20/paginators-1.json' adding 'botocore/data/support-app/2021-08-20/service-2.json' adding 'botocore/data/sustainability/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/sustainability/2018-05-10/paginators-1.json' adding 'botocore/data/sustainability/2018-05-10/service-2.json' adding 'botocore/data/swf/2012-01-25/endpoint-rule-set-1.json' adding 'botocore/data/swf/2012-01-25/examples-1.json' adding 'botocore/data/swf/2012-01-25/paginators-1.json' adding 'botocore/data/swf/2012-01-25/service-2.json' adding 'botocore/data/synthetics/2017-10-11/endpoint-rule-set-1.json' adding 'botocore/data/synthetics/2017-10-11/examples-1.json' adding 'botocore/data/synthetics/2017-10-11/paginators-1.json' adding 'botocore/data/synthetics/2017-10-11/service-2.json' adding 'botocore/data/taxsettings/2018-05-10/endpoint-rule-set-1.json' adding 'botocore/data/taxsettings/2018-05-10/paginators-1.json' adding 'botocore/data/taxsettings/2018-05-10/service-2.json' adding 'botocore/data/textract/2018-06-27/endpoint-rule-set-1.json' adding 'botocore/data/textract/2018-06-27/examples-1.json' adding 'botocore/data/textract/2018-06-27/paginators-1.json' adding 'botocore/data/textract/2018-06-27/service-2.json' adding 'botocore/data/timestream-influxdb/2023-01-27/endpoint-rule-set-1.json' adding 'botocore/data/timestream-influxdb/2023-01-27/paginators-1.json' adding 'botocore/data/timestream-influxdb/2023-01-27/service-2.json' adding 'botocore/data/timestream-query/2018-11-01/endpoint-rule-set-1.json' adding 'botocore/data/timestream-query/2018-11-01/examples-1.json' adding 'botocore/data/timestream-query/2018-11-01/paginators-1.json' adding 'botocore/data/timestream-query/2018-11-01/service-2.json' adding 'botocore/data/timestream-write/2018-11-01/endpoint-rule-set-1.json' adding 'botocore/data/timestream-write/2018-11-01/examples-1.json' adding 'botocore/data/timestream-write/2018-11-01/paginators-1.json' adding 'botocore/data/timestream-write/2018-11-01/service-2.json' adding 'botocore/data/tnb/2008-10-21/endpoint-rule-set-1.json' adding 'botocore/data/tnb/2008-10-21/paginators-1.json' adding 'botocore/data/tnb/2008-10-21/service-2.json' adding 'botocore/data/transcribe/2017-10-26/endpoint-rule-set-1.json' adding 'botocore/data/transcribe/2017-10-26/examples-1.json' adding 'botocore/data/transcribe/2017-10-26/paginators-1.json' adding 'botocore/data/transcribe/2017-10-26/service-2.json' adding 'botocore/data/transcribe/2017-10-26/waiters-2.json' adding 'botocore/data/transfer/2018-11-05/endpoint-rule-set-1.json' adding 'botocore/data/transfer/2018-11-05/examples-1.json' adding 'botocore/data/transfer/2018-11-05/paginators-1.json' adding 'botocore/data/transfer/2018-11-05/service-2.json' adding 'botocore/data/transfer/2018-11-05/waiters-2.json' adding 'botocore/data/translate/2017-07-01/endpoint-rule-set-1.json' adding 'botocore/data/translate/2017-07-01/examples-1.json' adding 'botocore/data/translate/2017-07-01/paginators-1.json' adding 'botocore/data/translate/2017-07-01/service-2.json' adding 'botocore/data/trustedadvisor/2022-09-15/endpoint-rule-set-1.json' adding 'botocore/data/trustedadvisor/2022-09-15/paginators-1.json' adding 'botocore/data/trustedadvisor/2022-09-15/service-2.json' adding 'botocore/data/trustedadvisor/2022-09-15/waiters-2.json' adding 'botocore/data/uxc/2024-07-01/endpoint-rule-set-1.json' adding 'botocore/data/uxc/2024-07-01/paginators-1.json' adding 'botocore/data/uxc/2024-07-01/service-2.json' adding 'botocore/data/uxc/2024-07-01/waiters-2.json' adding 'botocore/data/verifiedpermissions/2021-12-01/endpoint-rule-set-1.json' adding 'botocore/data/verifiedpermissions/2021-12-01/paginators-1.json' adding 'botocore/data/verifiedpermissions/2021-12-01/service-2.json' adding 'botocore/data/verifiedpermissions/2021-12-01/waiters-2.json' adding 'botocore/data/voice-id/2021-09-27/endpoint-rule-set-1.json' adding 'botocore/data/voice-id/2021-09-27/examples-1.json' adding 'botocore/data/voice-id/2021-09-27/paginators-1.json' adding 'botocore/data/voice-id/2021-09-27/service-2.json' adding 'botocore/data/vpc-lattice/2022-11-30/endpoint-rule-set-1.json' adding 'botocore/data/vpc-lattice/2022-11-30/paginators-1.json' adding 'botocore/data/vpc-lattice/2022-11-30/service-2.json' adding 'botocore/data/vpc-lattice/2022-11-30/waiters-2.json' adding 'botocore/data/waf/2015-08-24/endpoint-rule-set-1.json' adding 'botocore/data/waf/2015-08-24/examples-1.json' adding 'botocore/data/waf/2015-08-24/paginators-1.json' adding 'botocore/data/waf/2015-08-24/service-2.json' adding 'botocore/data/waf-regional/2016-11-28/endpoint-rule-set-1.json' adding 'botocore/data/waf-regional/2016-11-28/examples-1.json' adding 'botocore/data/waf-regional/2016-11-28/paginators-1.json' adding 'botocore/data/waf-regional/2016-11-28/service-2.json' adding 'botocore/data/wafv2/2019-07-29/endpoint-rule-set-1.json' adding 'botocore/data/wafv2/2019-07-29/examples-1.json' adding 'botocore/data/wafv2/2019-07-29/paginators-1.json' adding 'botocore/data/wafv2/2019-07-29/service-2.json' adding 'botocore/data/wellarchitected/2020-03-31/endpoint-rule-set-1.json' adding 'botocore/data/wellarchitected/2020-03-31/examples-1.json' adding 'botocore/data/wellarchitected/2020-03-31/paginators-1.json' adding 'botocore/data/wellarchitected/2020-03-31/service-2.json' adding 'botocore/data/wickr/2024-02-01/endpoint-rule-set-1.json' adding 'botocore/data/wickr/2024-02-01/paginators-1.json' adding 'botocore/data/wickr/2024-02-01/service-2.json' adding 'botocore/data/wickr/2024-02-01/waiters-2.json' adding 'botocore/data/wisdom/2020-10-19/endpoint-rule-set-1.json' adding 'botocore/data/wisdom/2020-10-19/examples-1.json' adding 'botocore/data/wisdom/2020-10-19/paginators-1.json' adding 'botocore/data/wisdom/2020-10-19/service-2.json' adding 'botocore/data/workdocs/2016-05-01/endpoint-rule-set-1.json' adding 'botocore/data/workdocs/2016-05-01/examples-1.json' adding 'botocore/data/workdocs/2016-05-01/paginators-1.json' adding 'botocore/data/workdocs/2016-05-01/service-2.json' adding 'botocore/data/workmail/2017-10-01/endpoint-rule-set-1.json' adding 'botocore/data/workmail/2017-10-01/examples-1.json' adding 'botocore/data/workmail/2017-10-01/paginators-1.json' adding 'botocore/data/workmail/2017-10-01/service-2.json' adding 'botocore/data/workmailmessageflow/2019-05-01/endpoint-rule-set-1.json' adding 'botocore/data/workmailmessageflow/2019-05-01/examples-1.json' adding 'botocore/data/workmailmessageflow/2019-05-01/paginators-1.json' adding 'botocore/data/workmailmessageflow/2019-05-01/service-2.json' adding 'botocore/data/workspaces/2015-04-08/endpoint-rule-set-1.json' adding 'botocore/data/workspaces/2015-04-08/examples-1.json' adding 'botocore/data/workspaces/2015-04-08/paginators-1.json' adding 'botocore/data/workspaces/2015-04-08/service-2.json' adding 'botocore/data/workspaces-instances/2022-07-26/endpoint-rule-set-1.json' adding 'botocore/data/workspaces-instances/2022-07-26/paginators-1.json' adding 'botocore/data/workspaces-instances/2022-07-26/service-2.json' adding 'botocore/data/workspaces-instances/2022-07-26/waiters-2.json' adding 'botocore/data/workspaces-thin-client/2023-08-22/endpoint-rule-set-1.json' adding 'botocore/data/workspaces-thin-client/2023-08-22/paginators-1.json' adding 'botocore/data/workspaces-thin-client/2023-08-22/service-2.json' adding 'botocore/data/workspaces-web/2020-07-08/endpoint-rule-set-1.json' adding 'botocore/data/workspaces-web/2020-07-08/examples-1.json' adding 'botocore/data/workspaces-web/2020-07-08/paginators-1.json' adding 'botocore/data/workspaces-web/2020-07-08/service-2.json' adding 'botocore/data/workspaces-web/2020-07-08/waiters-2.json' adding 'botocore/data/xray/2016-04-12/endpoint-rule-set-1.json' adding 'botocore/data/xray/2016-04-12/examples-1.json' adding 'botocore/data/xray/2016-04-12/paginators-1.json' adding 'botocore/data/xray/2016-04-12/service-2.json' adding 'botocore/docs/__init__.py' adding 'botocore/docs/client.py' adding 'botocore/docs/docstring.py' adding 'botocore/docs/example.py' adding 'botocore/docs/method.py' adding 'botocore/docs/paginator.py' adding 'botocore/docs/params.py' adding 'botocore/docs/service.py' adding 'botocore/docs/shape.py' adding 'botocore/docs/sharedexample.py' adding 'botocore/docs/translator.py' adding 'botocore/docs/utils.py' adding 'botocore/docs/waiter.py' adding 'botocore/docs/bcdoc/__init__.py' adding 'botocore/docs/bcdoc/docstringparser.py' adding 'botocore/docs/bcdoc/restdoc.py' adding 'botocore/docs/bcdoc/style.py' adding 'botocore/retries/__init__.py' adding 'botocore/retries/adaptive.py' adding 'botocore/retries/base.py' adding 'botocore/retries/bucket.py' adding 'botocore/retries/quota.py' adding 'botocore/retries/special.py' adding 'botocore/retries/standard.py' adding 'botocore/retries/throttling.py' adding 'botocore/vendored/__init__.py' adding 'botocore/vendored/six.py' adding 'botocore/vendored/requests/__init__.py' adding 'botocore/vendored/requests/exceptions.py' adding 'botocore/vendored/requests/packages/__init__.py' adding 'botocore/vendored/requests/packages/urllib3/__init__.py' adding 'botocore/vendored/requests/packages/urllib3/exceptions.py' adding 'botocore-1.42.97.dist-info/LICENSE.txt' adding 'botocore-1.42.97.dist-info/METADATA' adding 'botocore-1.42.97.dist-info/NOTICE' adding 'botocore-1.42.97.dist-info/WHEEL' adding 'botocore-1.42.97.dist-info/top_level.txt' adding 'botocore-1.42.97.dist-info/RECORD' removing build/bdist.linux-aarch64/wheel Building wheel for botocore (pyproject.toml): finished with status 'done' Created wheel for botocore: filename=botocore-1.42.97-py3-none-any.whl size=14915249 sha256=16b1cdecdadbe2a1a9cf9e3c082c4e2ce1088be24d650ed501227f7060b7586d Stored in directory: /builddir/.cache/pip/wheels/3f/c9/ef/990bf44cbb9deea0d746b50aa30a9368f8424c6e879202d463 Successfully built botocore + RPM_EC=0 ++ jobs -p + exit 0 Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.5kL1Oc + umask 022 + cd /builddir/build/BUILD + '[' /builddir/build/BUILDROOT/python-botocore-1.42.97-1.an23.noarch '!=' / ']' + rm -rf /builddir/build/BUILDROOT/python-botocore-1.42.97-1.an23.noarch ++ dirname /builddir/build/BUILDROOT/python-botocore-1.42.97-1.an23.noarch + mkdir -p /builddir/build/BUILDROOT + mkdir /builddir/build/BUILDROOT/python-botocore-1.42.97-1.an23.noarch + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/gfortran/modules' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/gfortran/modules' + export FCFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/anolis/anolis-hardened-ld -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -Wl,--build-id=sha1 ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd botocore-1.42.97 ++ ls /builddir/build/BUILD/botocore-1.42.97/pyproject-wheeldir/botocore-1.42.97-py3-none-any.whl ++ xargs basename --multiple ++ sed -E 's/([^-]+)-([^-]+)-.+\.whl/\1==\2/' + specifier=botocore==1.42.97 + TMPDIR=/builddir/build/BUILD/botocore-1.42.97/.pyproject-builddir + /usr/bin/python3 -m pip install --root /builddir/build/BUILDROOT/python-botocore-1.42.97-1.an23.noarch --prefix /usr --no-deps --disable-pip-version-check --progress-bar off --verbose --ignore-installed --no-warn-script-location --no-index --no-cache-dir --find-links /builddir/build/BUILD/botocore-1.42.97/pyproject-wheeldir botocore==1.42.97 Using pip 23.3.1 from /usr/lib/python3.11/site-packages/pip (python 3.11) Looking in links: /builddir/build/BUILD/botocore-1.42.97/pyproject-wheeldir Processing ./pyproject-wheeldir/botocore-1.42.97-py3-none-any.whl Installing collected packages: botocore Successfully installed botocore-1.42.97 + '[' -d /builddir/build/BUILDROOT/python-botocore-1.42.97-1.an23.noarch/usr/bin ']' + rm -f /builddir/build/BUILD/python-botocore-1.42.97-1.an23.noarch-pyproject-ghost-distinfo + site_dirs=() + '[' -d /builddir/build/BUILDROOT/python-botocore-1.42.97-1.an23.noarch/usr/lib/python3.11/site-packages ']' + site_dirs+=("/usr/lib/python3.11/site-packages") + '[' /builddir/build/BUILDROOT/python-botocore-1.42.97-1.an23.noarch/usr/lib64/python3.11/site-packages '!=' /builddir/build/BUILDROOT/python-botocore-1.42.97-1.an23.noarch/usr/lib/python3.11/site-packages ']' + '[' -d /builddir/build/BUILDROOT/python-botocore-1.42.97-1.an23.noarch/usr/lib64/python3.11/site-packages ']' + for site_dir in ${site_dirs[@]} + for distinfo in /builddir/build/BUILDROOT/python-botocore-1.42.97-1.an23.noarch$site_dir/*.dist-info + echo '%ghost /usr/lib/python3.11/site-packages/botocore-1.42.97.dist-info' + sed -i s/pip/rpm/ /builddir/build/BUILDROOT/python-botocore-1.42.97-1.an23.noarch/usr/lib/python3.11/site-packages/botocore-1.42.97.dist-info/INSTALLER + PYTHONPATH=/usr/lib/rpm/anolis + /usr/bin/python3 -B /usr/lib/rpm/anolis/pyproject_preprocess_record.py --buildroot /builddir/build/BUILDROOT/python-botocore-1.42.97-1.an23.noarch --record /builddir/build/BUILDROOT/python-botocore-1.42.97-1.an23.noarch/usr/lib/python3.11/site-packages/botocore-1.42.97.dist-info/RECORD --output /builddir/build/BUILD/python-botocore-1.42.97-1.an23.noarch-pyproject-record + rm -fv /builddir/build/BUILDROOT/python-botocore-1.42.97-1.an23.noarch/usr/lib/python3.11/site-packages/botocore-1.42.97.dist-info/RECORD removed '/builddir/build/BUILDROOT/python-botocore-1.42.97-1.an23.noarch/usr/lib/python3.11/site-packages/botocore-1.42.97.dist-info/RECORD' + rm -fv /builddir/build/BUILDROOT/python-botocore-1.42.97-1.an23.noarch/usr/lib/python3.11/site-packages/botocore-1.42.97.dist-info/REQUESTED removed '/builddir/build/BUILDROOT/python-botocore-1.42.97-1.an23.noarch/usr/lib/python3.11/site-packages/botocore-1.42.97.dist-info/REQUESTED' ++ wc -l /builddir/build/BUILD/python-botocore-1.42.97-1.an23.noarch-pyproject-ghost-distinfo ++ cut -f1 '-d ' + lines=1 + '[' 1 -ne 1 ']' + RPM_PERCENTAGES_COUNT=8 + /usr/bin/python3 /usr/lib/rpm/anolis/pyproject_save_files.py --output-files /builddir/build/BUILD/python-botocore-1.42.97-1.an23.noarch-pyproject-files --output-modules /builddir/build/BUILD/python-botocore-1.42.97-1.an23.noarch-pyproject-modules --buildroot /builddir/build/BUILDROOT/python-botocore-1.42.97-1.an23.noarch --sitelib /usr/lib/python3.11/site-packages --sitearch /usr/lib64/python3.11/site-packages --python-version 3.11 --pyproject-record /builddir/build/BUILD/python-botocore-1.42.97-1.an23.noarch-pyproject-record --prefix /usr botocore + /usr/bin/find-debuginfo -j80 --strict-build-id -m -i --build-id-seed 1.42.97-1.an23 --unique-debug-suffix -1.42.97-1.an23.noarch --unique-debug-src-base python-botocore-1.42.97-1.an23.noarch --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 50000000 -S debugsourcefiles.list /builddir/build/BUILD/botocore-1.42.97 find-debuginfo: starting Extracting debug info from 0 files Creating .debug symlinks for symlinks to ELF files find: 'debug': No such file or directory find-debuginfo: done + /usr/lib/rpm/check-buildroot + /usr/lib/rpm/anolis/brp-ldconfig + COMPRESS='zstd -f --rm -19 -T0' + COMPRESS_EXT=.zst + /usr/lib/rpm/brp-compress + /usr/lib/rpm/anolis/brp-strip-lto /usr/bin/strip + /usr/lib/rpm/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/check-rpaths + /usr/lib/rpm/brp-remove-la-files + /usr/lib/rpm/anolis/clean_perl + /usr/lib/rpm/anolis/check_elf_files + /usr/lib/rpm/anolis/brp-mangle-shebangs + /usr/lib/rpm/anolis/remove-info-dir + /usr/lib/rpm/anolis/check-desktop-files + env -u SOURCE_DATE_EPOCH /usr/lib/rpm/anolis/brp-python-bytecompile '' 1 0 -j80 Bytecompiling .py files below /builddir/build/BUILDROOT/python-botocore-1.42.97-1.an23.noarch/usr/lib/python3.11 using python3.11 Not clamping source mtimes, $SOURCE_DATE_EPOCH not set + /usr/lib/rpm/anolis/brp-python-hardlink Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.f11xuF + umask 022 + cd /builddir/build/BUILD + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/gfortran/modules' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/gfortran/modules' + export FCFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/anolis/anolis-hardened-ld -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -Wl,--build-id=sha1 ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd botocore-1.42.97 + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/anolis/anolis-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/anolis/anolis-hardened-ld -specs=/usr/lib/rpm/anolis/anolis-annobin-cc1 -Wl,--build-id=sha1 ' + PATH=/builddir/build/BUILDROOT/python-botocore-1.42.97-1.an23.noarch/usr/bin:/usr/share/Modules/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/sbin + PYTHONPATH=/builddir/build/BUILDROOT/python-botocore-1.42.97-1.an23.noarch/usr/lib64/python3.11/site-packages:/builddir/build/BUILDROOT/python-botocore-1.42.97-1.an23.noarch/usr/lib/python3.11/site-packages + PYTHONDONTWRITEBYTECODE=1 + PYTEST_ADDOPTS=' --ignore=/builddir/build/BUILD/botocore-1.42.97/.pyproject-builddir' + PYTEST_XDIST_AUTO_NUM_WORKERS=80 + /usr/bin/pytest ============================= test session starts ============================== platform linux -- Python 3.11.6, pytest-7.3.1, pluggy-1.0.0 rootdir: /builddir/build/BUILD/botocore-1.42.97 configfile: pyproject.toml plugins: xdist-3.2.1 collected 59257 items tests/functional/test_account_id_endpoints.py ........ [ 0%] tests/functional/test_alias.py ...... [ 0%] tests/functional/test_apigateway.py . [ 0%] tests/functional/test_auth_config.py ................................... [ 0%] ........................................................................ [ 0%] ........................................................................ [ 0%] ........................................................................ [ 0%] ........................................................................ [ 0%] ........................................................................ [ 0%] ............................................... [ 0%] tests/functional/test_bearer_auth.py ............. [ 0%] tests/functional/test_bedrock_runtime.py . [ 0%] tests/functional/test_client.py .. [ 0%] tests/functional/test_client_class_names.py ............................ [ 0%] .................. [ 0%] tests/functional/test_client_metadata.py ...... [ 0%] tests/functional/test_cloudformation.py . [ 0%] tests/functional/test_cloudsearchdomain.py . [ 0%] tests/functional/test_cloudwatch.py ...... [ 0%] tests/functional/test_cognito_idp.py ............. [ 0%] tests/functional/test_compress.py ... [ 0%] tests/functional/test_config_provider.py ........... [ 0%] tests/functional/test_connecthealth.py . [ 0%] tests/functional/test_context_params.py ........................... [ 0%] tests/functional/test_credentials.py ................................... [ 1%] ........... [ 1%] tests/functional/test_disable_s3_express_auth.py .... [ 1%] tests/functional/test_discovery.py ........................ [ 1%] tests/functional/test_docdb.py .. [ 1%] tests/functional/test_dsql.py .... [ 1%] tests/functional/test_dynamodb.py ... [ 1%] tests/functional/test_ec2.py ... [ 1%] tests/functional/test_endpoint_rulesets.py ............................. [ 1%] ........................................................................ [ 1%] ........................................................................ [ 1%] ........................................................................ [ 1%] ........................................................................ [ 1%] ........................................................................ [ 1%] ........................................................................ [ 1%] ........................................................................ [ 2%] ........................................................................ [ 2%] ........................................................................ [ 2%] ........................................................................ [ 2%] ........................................................................ [ 2%] ........................................................................ [ 2%] ........................................................................ [ 2%] ........................................................................ [ 2%] ........................................................................ [ 3%] ........................................................................ [ 3%] ........................................................................ [ 3%] ........................................................................ [ 3%] ........................................................................ [ 3%] ........................................................................ [ 3%] ........................................................................ [ 3%] ........................................................................ [ 3%] ........................................................................ [ 3%] ........................................................................ [ 4%] ........................................................................ [ 4%] ........................................................................ [ 4%] ........................................................................ [ 4%] ........................................................................ [ 4%] ........................................................................ [ 4%] ........................................................................ [ 4%] ........................................................................ [ 4%] ........................................................................ [ 5%] ........................................................................ [ 5%] ........................................................................ [ 5%] ........................................................................ [ 5%] ........................................................................ [ 5%] ........................................................................ [ 5%] ........................................................................ [ 5%] ........................................................................ [ 5%] ........................................................................ [ 6%] ........................................................................ [ 6%] ........................................................................ [ 6%] ........................................................................ [ 6%] ........................................................................ [ 6%] ........................................................................ [ 6%] ........................................................................ [ 6%] ........................................................................ [ 6%] ........................................................................ [ 7%] ........................................................................ [ 7%] ........................................................................ [ 7%] ........................................................................ [ 7%] ........................................................................ [ 7%] ........................................................................ [ 7%] ........................................................................ [ 7%] ........................................................................ [ 7%] ........................................................................ [ 7%] ........................................................................ [ 8%] ........................................................................ [ 8%] ........................................................................ [ 8%] ........................................................................ [ 8%] ........................................................................ [ 8%] ........................................................................ [ 8%] ........................................................................ [ 8%] ........................................................................ [ 8%] ........................................................................ [ 9%] ........................................................................ [ 9%] ........................................................................ [ 9%] ........................................................................ [ 9%] ........................................................................ [ 9%] ........................................................................ [ 9%] ........................................................................ [ 9%] ........................................................................ [ 9%] ........................................................................ [ 10%] ........................................................................ [ 10%] ........................................................................ [ 10%] ........................................................................ [ 10%] ........................................................................ [ 10%] ........................................................................ [ 10%] ........................................................................ [ 10%] ........................................................................ [ 10%] ........................................................................ [ 11%] ........................................................................ [ 11%] ........................................................................ [ 11%] ........................................................................ [ 11%] ........................................................................ [ 11%] ........................................................................ [ 11%] ........................................................................ [ 11%] ........................................................................ [ 11%] ........................................................................ [ 12%] ........................................................................ [ 12%] ........................................................................ [ 12%] ........................................................................ [ 12%] ........................................................................ [ 12%] ........................................................................ [ 12%] ........................................................................ [ 12%] ........................................................................ [ 12%] ........................................................................ [ 12%] ........................................................................ [ 13%] ........................................................................ [ 13%] ........................................................................ [ 13%] ........................................................................ [ 13%] ........................................................................ [ 13%] ........................................................................ [ 13%] ........................................................................ [ 13%] ........................................................................ [ 13%] ........................................................................ [ 14%] ........................................................................ [ 14%] ........................................................................ [ 14%] ........................................................................ [ 14%] ........................................................................ [ 14%] ........................................................................ [ 14%] ........................................................................ [ 14%] ........................................................................ [ 14%] ........................................................................ [ 15%] ........................................................................ [ 15%] ........................................................................ [ 15%] ........................................................................ [ 15%] ........................................................................ [ 15%] ........................................................................ [ 15%] ........................................................................ [ 15%] ........................................................................ [ 15%] ........................................................................ [ 16%] ........................................................................ [ 16%] ........................................................................ [ 16%] ........................................................................ [ 16%] ........................................................................ [ 16%] ........................................................................ [ 16%] ........................................................................ [ 16%] ........................................................................ [ 16%] ........................................................................ [ 16%] ........................................................................ [ 17%] ........................................................................ [ 17%] ........................................................................ [ 17%] ........................................................................ [ 17%] ........................................................................ [ 17%] ........................................................................ [ 17%] ........................................................................ [ 17%] ........................................................................ [ 17%] ........................................................................ [ 18%] ........................................................................ [ 18%] ........................................................................ [ 18%] ........................................................................ [ 18%] ........................................................................ [ 18%] ........................................................................ [ 18%] ........................................................................ [ 18%] ........................................................................ [ 18%] ........................................................................ [ 19%] ........................................................................ [ 19%] ........................................................................ [ 19%] ........................................................................ [ 19%] ........................................................................ [ 19%] ........................................................................ [ 19%] ........................................................................ [ 19%] ........................................................................ [ 19%] ........................................................................ [ 20%] ........................................................................ [ 20%] ........................................................................ [ 20%] ........................................................................ [ 20%] ........................................................................ [ 20%] ........................................................................ [ 20%] ........................................................................ [ 20%] ........................................................................ [ 20%] ........................................................................ [ 20%] ........................................................................ [ 21%] ........................................................................ [ 21%] ........................................................................ [ 21%] ........................................................................ [ 21%] ........................................................................ [ 21%] ........................................................................ [ 21%] ........................................................................ [ 21%] ........................................................................ [ 21%] ........................................................................ [ 22%] ........................................................................ [ 22%] ........................................................................ [ 22%] ........................................................................ [ 22%] ........................................................................ [ 22%] ........................................................................ [ 22%] ........................................................................ [ 22%] ........................................................................ [ 22%] ........................................................................ [ 23%] ........................................................................ [ 23%] ........................................................................ [ 23%] ........................................................................ [ 23%] ........................................................................ [ 23%] ........................................................................ [ 23%] ........................................................................ [ 23%] ........................................................................ [ 23%] ........................................................................ [ 24%] ........................................................................ [ 24%] ........................................................................ [ 24%] ........................................................................ [ 24%] ........................................................................ [ 24%] ........................................................................ [ 24%] ........................................................................ [ 24%] ........................................................................ [ 24%] ........................................................................ [ 25%] ........................................................................ [ 25%] ........................................................................ [ 25%] ........................................................................ [ 25%] ........................................................................ [ 25%] ........................................................................ [ 25%] ........................................................................ [ 25%] ........................................................................ [ 25%] ........................................................................ [ 25%] ........................................................................ [ 26%] .............................................s.....s.................... [ 26%] ..........................s............................................. [ 26%] sssss................................................................... [ 26%] ........................................................................ [ 26%] ........................................................................ [ 26%] ........................................................................ [ 26%] ........................................................................ [ 26%] ...... [ 26%] tests/functional/test_endpoints.py ..................................... [ 27%] ........................................................................ [ 27%] ........................................................................ [ 27%] ........................................................................ [ 27%] ........................................................................ [ 27%] ........................................................................ [ 27%] ........................................................................ [ 27%] ........................................................................ [ 27%] ........................................................................ [ 27%] ........................................................................ [ 28%] ............................................... [ 28%] tests/functional/test_event_alias.py ................................... [ 28%] ........................................................................ [ 28%] ........................................................................ [ 28%] ........................................................................ [ 28%] ........................................................................ [ 28%] ...................................................................... [ 28%] tests/functional/test_eventbridge.py ss...ssss....sssss [ 28%] tests/functional/test_events.py .. [ 28%] tests/functional/test_glacier.py ....... [ 28%] tests/functional/test_h2_required.py s..... [ 28%] tests/functional/test_history.py .... [ 28%] tests/functional/test_httpchecksum.py ................................. [ 28%] tests/functional/test_importexport.py . [ 28%] tests/functional/test_iot_data.py .. [ 28%] tests/functional/test_kinesis.py ... [ 28%] tests/functional/test_lex.py .. [ 28%] tests/functional/test_loaders.py . [ 28%] tests/functional/test_machinelearning.py . [ 28%] tests/functional/test_model_backcompat.py . [ 28%] tests/functional/test_model_completeness.py ............................ [ 29%] ........................................................................ [ 29%] ........................................................................ [ 29%] ........................................................................ [ 29%] ........................................................................ [ 29%] ........................................................................ [ 29%] ........................................................................ [ 29%] .................. [ 29%] tests/functional/test_modeled_exceptions.py .... [ 29%] tests/functional/test_mturk.py . [ 29%] tests/functional/test_neptune.py .. [ 29%] tests/functional/test_paginate.py ......... [ 29%] tests/functional/test_paginator_config.py .............................. [ 29%] ........................................................................ [ 29%] ........................................................................ [ 30%] ........................................................................ [ 30%] ........................................................................ [ 30%] ........................................................................ [ 30%] ........................................................................ [ 30%] ........................................................................ [ 30%] ........................................................................ [ 30%] ........................................................................ [ 30%] ........................................................................ [ 31%] ........................................................................ [ 31%] ........................................................................ [ 31%] ........................................................................ [ 31%] ........................................................................ [ 31%] ........................................................................ [ 31%] ........................................................................ [ 31%] ........................................................................ [ 31%] ........................................................................ [ 32%] ........................................................................ [ 32%] ........................................................................ [ 32%] ........................................................................ [ 32%] ........................................................................ [ 32%] ........................................................................ [ 32%] ........................................................................ [ 32%] ........................................................................ [ 32%] ........................................................................ [ 33%] ........................................................................ [ 33%] ........................................................................ [ 33%] ........................................................................ [ 33%] ........................................................................ [ 33%] ........................................................................ [ 33%] ........................................................................ [ 33%] ........................................................................ [ 33%] ........................................................................ [ 34%] ........................................................................ [ 34%] ........................................................................ [ 34%] ........................................................................ [ 34%] ........................................................................ [ 34%] ........................................................................ [ 34%] ........................................................................ [ 34%] ........................................................................ [ 34%] ........................................................................ [ 34%] ........................... [ 35%] tests/functional/test_plugins.py .... [ 35%] tests/functional/test_polly.py . [ 35%] tests/functional/test_protocol_selection.py . [ 35%] tests/functional/test_public_apis.py ...... [ 35%] tests/functional/test_qbusiness.py . [ 35%] tests/functional/test_query_compatibility.py .. [ 35%] tests/functional/test_rds.py .... [ 35%] tests/functional/test_regions.py ....................................... [ 35%] ........................................................................ [ 35%] ........................................................................ [ 35%] ........................................................................ [ 35%] ........................................................................ [ 35%] ............................................. [ 35%] tests/functional/test_response_shadowing.py ............................ [ 35%] ........................................................................ [ 35%] ........................................................................ [ 35%] ........................................................................ [ 36%] ........................................................................ [ 36%] ........................................................................ [ 36%] ........................................................................ [ 36%] ........................................................................ [ 36%] ........................................................................ [ 36%] ........................................................................ [ 36%] ........................................................................ [ 36%] ........................................................................ [ 37%] ........................................................................ [ 37%] ........................................................................ [ 37%] ........................................................................ [ 37%] ........................................................................ [ 37%] ........................................................................ [ 37%] ........................................................................ [ 37%] ........................................................................ [ 37%] ........................................................................ [ 38%] ........................................................................ [ 38%] ........................................................................ [ 38%] ........................................................................ [ 38%] ........................................................................ [ 38%] ........................................................................ [ 38%] ........................................................................ [ 38%] ........................................................................ [ 38%] ........................................................................ [ 39%] ........................................................................ [ 39%] ........................................................................ [ 39%] ........................................................................ [ 39%] ........................................................................ [ 39%] ........................................................................ [ 39%] ........................................................................ [ 39%] ........................................................................ [ 39%] ........................................................................ [ 39%] ........................................................................ [ 40%] ........................................................................ [ 40%] ........................................................................ [ 40%] ........................................................................ [ 40%] ........................................................................ [ 40%] ........................................................................ [ 40%] ........................................................................ [ 40%] ........................................................................ [ 40%] ........................................................................ [ 41%] ........................................................................ [ 41%] ........................................................................ [ 41%] ........................................................................ [ 41%] ........................................................................ [ 41%] ........................................................................ [ 41%] ........................................................................ [ 41%] ........................................................................ [ 41%] ........................................................................ [ 42%] ........................................................................ [ 42%] ........................................................................ [ 42%] ........................................................................ [ 42%] ........................................................................ [ 42%] ........................................................................ [ 42%] ........................................................................ [ 42%] ........................................................................ [ 42%] ........................................................................ [ 43%] ........................................................................ [ 43%] ........................................................................ [ 43%] ........................................................................ [ 43%] ........................................................................ [ 43%] ........................................................................ [ 43%] ........................................................................ [ 43%] ........................................................................ [ 43%] ........................................................................ [ 43%] ........................................................................ [ 44%] ........................................................................ [ 44%] ........................................................................ [ 44%] ........................................................................ [ 44%] ........................................................................ [ 44%] ........................................................................ [ 44%] ........................................................................ [ 44%] ........................................................................ [ 44%] ........................................................................ [ 45%] ........................................................................ [ 45%] ........................................................................ [ 45%] ........................................................................ [ 45%] ........................................................................ [ 45%] ........................................................................ [ 45%] ........................................................................ [ 45%] ........................................................................ [ 45%] ........................................................................ [ 46%] ........................................................................ [ 46%] ........................................................................ [ 46%] ........................................................................ [ 46%] ........................................................................ [ 46%] ........................................................................ [ 46%] ........................................................................ [ 46%] ........................................................................ [ 46%] ........................................................................ [ 47%] ........................................................................ [ 47%] ........................................................................ [ 47%] ........................................................................ [ 47%] ........................................................................ [ 47%] ........................................................................ [ 47%] ........................................................................ [ 47%] ........................................................................ [ 47%] ........................................................................ [ 48%] ........................................................................ [ 48%] ........................................................................ [ 48%] ........................................................................ [ 48%] ........................................................................ [ 48%] ........................................................................ [ 48%] ........................................................................ [ 48%] ........................................................................ [ 48%] ........................................................................ [ 48%] ........................................................................ [ 49%] ........................................................................ [ 49%] ........................................................................ [ 49%] ........................................................................ [ 49%] ........................................................................ [ 49%] ........................................................................ [ 49%] ........................................................................ [ 49%] ........................................................................ [ 49%] ........................................................................ [ 50%] ........................................................................ [ 50%] ........................................................................ [ 50%] ........................................................................ [ 50%] ........................................................................ [ 50%] ........................................................................ [ 50%] ........................................................................ [ 50%] ........................................................................ [ 50%] ........................................................................ [ 51%] ........................................................................ [ 51%] ........................................................................ [ 51%] ........................................................................ [ 51%] ........................................................................ [ 51%] ........................................................................ [ 51%] ........................................................................ [ 51%] ........................................................................ [ 51%] ........................................................................ [ 52%] ........................................................................ [ 52%] ........................................................................ [ 52%] ........................................................................ [ 52%] ........................................................................ [ 52%] ........................................................................ [ 52%] ........................................................................ [ 52%] ........................................................................ [ 52%] ........................................................................ [ 52%] ........................................................................ [ 53%] ........................................................................ [ 53%] ........................................................................ [ 53%] ........................................................................ [ 53%] ........................................................................ [ 53%] ........................................................................ [ 53%] ........................................................................ [ 53%] ........................................................................ [ 53%] ........................................................................ [ 54%] ........................................................................ [ 54%] ........................................................................ [ 54%] ........................................................................ [ 54%] ........................................................................ [ 54%] ........................................................................ [ 54%] ........................................................................ [ 54%] ........................................................................ [ 54%] ........................................................................ [ 55%] ........................................................................ [ 55%] ........................................................................ [ 55%] ........................................................................ [ 55%] ........................................................................ [ 55%] ........................................................................ [ 55%] ........................................................................ [ 55%] ........................................................................ [ 55%] ........................................................................ [ 56%] ........................................................................ [ 56%] ........................................................................ [ 56%] ........................................................................ [ 56%] ........................................................................ [ 56%] ........................................................................ [ 56%] ........................................................................ [ 56%] ........................................................................ [ 56%] ........................................................................ [ 56%] ........................................................................ [ 57%] ........................................................................ [ 57%] ........................................................................ [ 57%] ........................................................................ [ 57%] ........................................................................ [ 57%] ........................................................................ [ 57%] ........................................................................ [ 57%] ........................................................................ [ 57%] ........................................................................ [ 58%] ........................................................................ [ 58%] ........................................................................ [ 58%] ........................................................................ [ 58%] ........................................................................ [ 58%] ........................................................................ [ 58%] ........................................................................ [ 58%] ........................................................................ [ 58%] ........................................................................ [ 59%] ........................................................................ [ 59%] ........................................................................ [ 59%] ........................................................................ [ 59%] ........................................................................ [ 59%] ........................................................................ [ 59%] ........................................................................ [ 59%] ........................................................................ [ 59%] ........................................................................ [ 60%] ........................................................................ [ 60%] ........................................................................ [ 60%] ........................................................................ [ 60%] ........................................................................ [ 60%] ........................................................................ [ 60%] ........................................................................ [ 60%] ........................................................................ [ 60%] ........................................................................ [ 61%] ........................................................................ [ 61%] ........................................................................ [ 61%] ........................................................................ [ 61%] ........................................................................ [ 61%] ........................................................................ [ 61%] ........................................................................ [ 61%] ........................................................................ [ 61%] ........................................................................ [ 61%] ........................................................................ [ 62%] ........................................................................ [ 62%] ........................................................................ [ 62%] ........................................................................ [ 62%] ........................................................................ [ 62%] ........................................................................ [ 62%] ........................................................................ [ 62%] ........................................................................ [ 62%] ........................................................................ [ 63%] ........................................................................ [ 63%] ........................................................................ [ 63%] ........................................................................ [ 63%] ........................................................................ [ 63%] ........................................................................ [ 63%] ........................................................................ [ 63%] ........................................................................ [ 63%] ........................................................................ [ 64%] ........................................................................ [ 64%] ........................................................................ [ 64%] ........................................................................ [ 64%] ........................................................................ [ 64%] ........................................................................ [ 64%] ........................................................................ [ 64%] ........................................................................ [ 64%] ........................................................................ [ 65%] ........................................................................ [ 65%] ........................................................................ [ 65%] ........................................................................ [ 65%] ........................................................................ [ 65%] ........................................................................ [ 65%] ........................................................................ [ 65%] ........................................................................ [ 65%] ........................................................................ [ 65%] ........................................................................ [ 66%] ........................................................................ [ 66%] ........................................................................ [ 66%] ........................................................................ [ 66%] ........................................................................ [ 66%] ........................................................................ [ 66%] ........................................................................ [ 66%] ........................................................................ [ 66%] ........................................................................ [ 67%] ........................................................................ [ 67%] ........................................................................ [ 67%] ........................................................................ [ 67%] ........................................................................ [ 67%] ........................................................................ [ 67%] ........................................................................ [ 67%] ........................................................................ [ 67%] ........................................................................ [ 68%] ........................................................................ [ 68%] ........................................................................ [ 68%] ........................................................................ [ 68%] ........................................................................ [ 68%] ........................................................................ [ 68%] ........................................................................ [ 68%] ........................................................................ [ 68%] ........................................................................ [ 69%] ........................................................................ [ 69%] ........................................................................ [ 69%] ........................................................................ [ 69%] ........................................................................ [ 69%] ........................................................................ [ 69%] ........................................................................ [ 69%] ........................................................................ [ 69%] ........................................................................ [ 69%] ........................................................................ [ 70%] ........................................................................ [ 70%] ........................................................................ [ 70%] ........................................................................ [ 70%] ........................................................................ [ 70%] ........................................................................ [ 70%] ........................................................................ [ 70%] ........................................................................ [ 70%] ........................................................................ [ 71%] ........................................................................ [ 71%] ........................................................................ [ 71%] ........................................................................ [ 71%] ........................................................................ [ 71%] ........................................................................ [ 71%] ........................................................................ [ 71%] ........................................................................ [ 71%] ........................................................................ [ 72%] ........................................................................ [ 72%] ........................................................................ [ 72%] ........................................................................ [ 72%] ........................................................................ [ 72%] ........................................................................ [ 72%] ........................................................................ [ 72%] ........................................................................ [ 72%] ........................................................................ [ 73%] ........................................................................ [ 73%] ........................................................................ [ 73%] ........................................................................ [ 73%] ........................................................................ [ 73%] ........................................................................ [ 73%] ........................................................................ [ 73%] ........................................................................ [ 73%] ........................................................................ [ 74%] ........................................................................ [ 74%] ........................................................................ [ 74%] ........................................................................ [ 74%] ........................................................................ [ 74%] ........................................................................ [ 74%] ........................................................................ [ 74%] ........................................................................ [ 74%] ........................................................................ [ 74%] ........................................................................ [ 75%] ........................................................................ [ 75%] ........................................................................ [ 75%] ........................................................................ [ 75%] ........................................................................ [ 75%] ........................................................................ [ 75%] ........................................................................ [ 75%] ........................................................................ [ 75%] ........................................................................ [ 76%] ........................................................................ [ 76%] ........................................................................ [ 76%] ........................................................................ [ 76%] ........................................................................ [ 76%] ........................................................................ [ 76%] ........................................................................ [ 76%] ........................................................................ [ 76%] ........................................................................ [ 77%] ........................................................................ [ 77%] ........................................................................ [ 77%] ........................................................................ [ 77%] ........................................................................ [ 77%] ........................................................................ [ 77%] ........................................................................ [ 77%] ........................................................................ [ 77%] ........................................................................ [ 78%] ........................................................................ [ 78%] ........................................................................ [ 78%] ........................................................................ [ 78%] ........................................................................ [ 78%] ........................................................................ [ 78%] ........................................................................ [ 78%] ........................................................................ [ 78%] ........................................................................ [ 78%] ........................................................................ [ 79%] ........................................................................ [ 79%] ........................................................................ [ 79%] ........................................................................ [ 79%] ........................................................................ [ 79%] ........................................................................ [ 79%] ........................................................................ [ 79%] ........................................................................ [ 79%] ........................................................................ [ 80%] ........................................................................ [ 80%] ........................................................................ [ 80%] ........................................................................ [ 80%] ........................................................................ [ 80%] ........................................................................ [ 80%] ........................................................................ [ 80%] ........................................................................ [ 80%] ........................................................................ [ 81%] ........................................................................ [ 81%] ........................................................................ [ 81%] ........................................................................ [ 81%] ........................................................................ [ 81%] ........................................................................ [ 81%] ........................................................................ [ 81%] ........................................................................ [ 81%] ........................................................................ [ 82%] ........................................................................ [ 82%] ........................................................................ [ 82%] ........................................................................ [ 82%] ........................................................................ [ 82%] ........................................................................ [ 82%] ........................................................................ [ 82%] ........................................................................ [ 82%] ........................................................................ [ 82%] ........................................................................ [ 83%] ........................................................................ [ 83%] ........................................................................ [ 83%] ........................................................................ [ 83%] ........................................................................ [ 83%] ........................................................................ [ 83%] ........................................................................ [ 83%] ........................................................................ [ 83%] ........................................................................ [ 84%] ........................................................................ [ 84%] ........................................................................ [ 84%] ........................................................................ [ 84%] ........................................................................ [ 84%] ........................................................................ [ 84%] ........................................................................ [ 84%] ........................................................................ [ 84%] ........................................................................ [ 85%] ........................................................................ [ 85%] ........................................................................ [ 85%] ........................................................................ [ 85%] ................................................ [ 85%] tests/functional/test_retry.py .................... [ 85%] tests/functional/test_route53.py .... [ 85%] tests/functional/test_rpc_v2_cbor.py . [ 85%] tests/functional/test_s3.py ............................................ [ 85%] ........s.......sssssssss............................................... [ 85%] ........................................................................ [ 85%] ........................................................................ [ 85%] ...................................... [ 86%] tests/functional/test_s3_control.py ... [ 86%] tests/functional/test_s3_control_redirects.py .......................... [ 86%] ........... [ 86%] tests/functional/test_s3express.py ......... [ 86%] tests/functional/test_sagemaker.py .. [ 86%] tests/functional/test_service_alias.py . [ 86%] tests/functional/test_service_names.py ................................. [ 86%] ........................................................................ [ 86%] ........................................................................ [ 86%] ........................................................................ [ 86%] ........................................................................ [ 86%] ........................................................................ [ 86%] ........................................................................ [ 86%] ........................................................................ [ 87%] ........................................................................ [ 87%] ........................................................................ [ 87%] ........................................................................ [ 87%] ........................................................................ [ 87%] ....................... [ 87%] tests/functional/test_session.py ....... [ 87%] tests/functional/test_six_imports.py ................................... [ 87%] .................................. [ 87%] tests/functional/test_six_threading.py . [ 87%] tests/functional/test_socialmessaging.py ................... [ 87%] tests/functional/test_sqs.py .. [ 87%] tests/functional/test_sts.py .......................... [ 87%] tests/functional/test_stub.py .......................... [ 87%] tests/functional/test_tagged_unions_unknown.py . [ 87%] tests/functional/test_useragent.py ..................................... [ 87%] ............................. [ 87%] tests/functional/test_utils.py ... [ 87%] tests/functional/test_waiter_config.py ................................. [ 87%] ..................FF.FFFF.F........FF.F...F......F.F..F......FF.......F. [ 88%] ...................F...FFFF..FF.......F...F..F.F.FF....... [ 88%] tests/functional/configured_endpoint_urls/test_configured_endpoint_url.py . [ 88%] ........................................................................ [ 88%] ........................................................................ [ 88%] ........................................................................ [ 88%] ........................................................................ [ 88%] ........................................................................ [ 88%] ........................................................................ [ 88%] ........................................................................ [ 89%] ........................................................................ [ 89%] ........................................................................ [ 89%] ........................................................................ [ 89%] ........................................................................ [ 89%] ........................................................................ [ 89%] ...................... [ 89%] tests/functional/csm/test_monitoring.py ..................... [ 89%] tests/functional/docs/test_alias.py . [ 89%] tests/functional/docs/test_autoscaling.py . [ 89%] tests/functional/docs/test_ec2.py .... [ 89%] tests/functional/docs/test_glacier.py .. [ 89%] tests/functional/docs/test_lex.py . [ 89%] tests/functional/docs/test_s3.py ........ [ 89%] tests/functional/docs/test_secretsmanager.py . [ 89%] tests/functional/docs/test_shared_example_config.py .................... [ 89%] ........................................................................ [ 89%] ........................................................................ [ 90%] ........................................................................ [ 90%] ........................................................................ [ 90%] ........................................................................ [ 90%] ........................................................................ [ 90%] ........................................................................ [ 90%] ........................................................................ [ 90%] ........................................................................ [ 90%] ........................................................................ [ 91%] ........................................................................ [ 91%] ........................................................................ [ 91%] ........................................................................ [ 91%] ........................................................................ [ 91%] ........................................................................ [ 91%] ........................................................................ [ 91%] ........................................................................ [ 91%] ........................................................................ [ 92%] ........................................................................ [ 92%] ........ [ 92%] tests/functional/docs/test_streaming_body.py . [ 92%] tests/functional/retries/test_bucket.py .. [ 92%] tests/functional/retries/test_quota.py . [ 92%] tests/unit/test_args.py ................................................ [ 92%] ..................................................... [ 92%] tests/unit/test_auth_bearer.py .... [ 92%] tests/unit/test_auth_sigv4.py .... [ 92%] tests/unit/test_awsrequest.py .......................................... [ 92%] ................. [ 92%] tests/unit/test_changelog.py s [ 92%] tests/unit/test_client.py .............................................. [ 92%] .........................................F.............................. [ 92%] ........................................................................ [ 92%] ................................................................. [ 92%] tests/unit/test_compat.py .............................................. [ 92%] ........................ [ 92%] tests/unit/test_compress.py .......................... [ 93%] tests/unit/test_config_provider.py ..................................... [ 93%] ................................................... [ 93%] tests/unit/test_configloader.py ................. [ 93%] tests/unit/test_context.py ........ [ 93%] tests/unit/test_credentials.py ......................................... [ 93%] ........................................................................ [ 93%] ........................................................................ [ 93%] .......sssssssssssss..ss [ 93%] tests/unit/test_decorators.py ......... [ 93%] tests/unit/test_discovery.py ................................. [ 93%] tests/unit/test_endpoint.py ............................ [ 93%] tests/unit/test_endpoint_provider.py ................................... [ 93%] ........................................................................ [ 93%] ..........s............................ [ 93%] tests/unit/test_errorfactory.py ......... [ 93%] tests/unit/test_eventstream.py ...................................... [ 94%] tests/unit/test_exceptions.py ........... [ 94%] tests/unit/test_handlers.py ............................................ [ 94%] ........................................................................ [ 94%] .....................................................s................. [ 94%] tests/unit/test_history.py ........ [ 94%] tests/unit/test_hooks.py ........................................... [ 94%] tests/unit/test_http_client_exception_mapping.py ..... [ 94%] tests/unit/test_http_session.py ........................................ [ 94%] ........... [ 94%] tests/unit/test_httpchecksum.py ........................................ [ 94%] ...ssssss......... [ 94%] tests/unit/test_idempotency.py .. [ 94%] tests/unit/test_loaders.py ................................ [ 94%] tests/unit/test_model.py ............................................... [ 94%] .............................................. [ 94%] tests/unit/test_monitoring.py .......................................... [ 94%] ....... [ 94%] tests/unit/test_paginate.py .......F....F..F....F..FF........FF......... [ 94%] .......FF.....FFFFFFFFF.....F. [ 95%] tests/unit/test_parsers.py ............................................. [ 95%] ...................................... [ 95%] tests/unit/test_plugin.py . [ 95%] tests/unit/test_protocols.py ........................................... [ 95%] ........................................................................ [ 95%] ........................................................................ [ 95%] ........................................................................ [ 95%] ........................................................................ [ 95%] ........................................................................ [ 95%] ........................................................................ [ 95%] ........................................................................ [ 96%] ........................................................................ [ 96%] ........................................................................ [ 96%] ........................................................................ [ 96%] ........................................................................ [ 96%] ........................................................................ [ 96%] ........ [ 96%] tests/unit/test_regions.py ............................................. [ 96%] .......................................................... [ 96%] tests/unit/test_response.py ................................ [ 96%] tests/unit/test_retryhandler.py ........................ [ 96%] tests/unit/test_s3_addressing.py ................ [ 97%] tests/unit/test_serialize.py ................................. [ 97%] tests/unit/test_session.py ...................................ss........ [ 97%] ............................................ [ 97%] tests/unit/test_session_legacy.py ...................................... [ 97%] ............................. [ 97%] tests/unit/test_signers.py ............................................. [ 97%] ............................ [ 97%] tests/unit/test_stub.py ............... [ 97%] tests/unit/test_tokens.py ....................... [ 97%] tests/unit/test_translate.py .... [ 97%] tests/unit/test_useragent.py ..................s......... [ 97%] tests/unit/test_utils.py ............................................... [ 97%] ........................................................................ [ 97%] ........................................................................ [ 97%] ........................................................................ [ 98%] ......................................................... [ 98%] tests/unit/test_validate.py ............................................ [ 98%] . [ 98%] tests/unit/test_waiters.py ..F.....F........F........................ [ 98%] tests/unit/auth/test_auth_trait.py .......... [ 98%] tests/unit/auth/test_signers.py ........................................ [ 98%] .................................. [ 98%] tests/unit/auth/test_sigv4.py .............................. [ 98%] tests/unit/cbor/test_cbor_decoding.py .................................. [ 98%] ........................................................................ [ 98%] ........................................................................ [ 98%] ................. [ 98%] tests/unit/crt/auth/test_crt_signers.py ................................ [ 98%] ......sssssssssssssssssssssssssssssssssssssss [ 98%] tests/unit/crt/auth/test_crt_sigv4.py ssssssssssssssssssssssssssssss [ 98%] tests/unit/docs/test_client.py .... [ 98%] tests/unit/docs/test_docs.py . [ 98%] tests/unit/docs/test_docstring.py ......... [ 98%] tests/unit/docs/test_example.py ...................... [ 99%] tests/unit/docs/test_method.py ................ [ 99%] tests/unit/docs/test_paginator.py .. [ 99%] tests/unit/docs/test_params.py .................. [ 99%] tests/unit/docs/test_service.py ..... [ 99%] tests/unit/docs/test_sharedexample.py ........... [ 99%] tests/unit/docs/test_utils.py .................................. [ 99%] tests/unit/docs/test_waiter.py . [ 99%] tests/unit/docs/bcdoc/test_docstringparser.py .......................... [ 99%] ......................................... [ 99%] tests/unit/docs/bcdoc/test_document.py ................ [ 99%] tests/unit/docs/bcdoc/test_style.py .................................... [ 99%] ....... [ 99%] tests/unit/response_parsing/test_response_parsing.py ................... [ 99%] ........................................................................ [ 99%] ........................................................................ [ 99%] ........................................................... [ 99%] tests/unit/retries/test_adaptive.py ........... [ 99%] tests/unit/retries/test_bucket.py ....... [ 99%] tests/unit/retries/test_quota.py ..... [ 99%] tests/unit/retries/test_special.py ....... [ 99%] tests/unit/retries/test_standard.py .................................... [ 99%] .................................................................... [ 99%] tests/unit/retries/test_throttling.py .... [100%] =================================== FAILURES =================================== ________ test_lint_waiter_configs[validator51-waiter_model51-client51] _________ client = waiter_name = 'daemon_deployment_stopped', service_model = ServiceModel(ecs) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value > acceptors = waiter.config.acceptors tests/functional/test_waiter_config.py:114: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = @property def acceptors(self): acceptors = [] for acceptor_config in self._config['acceptors']: > acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = config = OrderedDict([('matcher', 'pathAll'), ('argument', 'daemonDeployments[].status'), ('state', 'success'), ('expected', 'STOPPED')]) def __init__(self, config): self.state = config['state'] self.matcher = config['matcher'] self.expected = config['expected'] self.argument = config.get('argument') > self.matcher_func = self._create_matcher_func() botocore/waiter.py:178: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_matcher_func(self): # An acceptor function is a callable that takes a single value. The # parsed AWS response. Note that the parsed error response is also # provided in the case of errors, so it's entirely possible to # handle all the available matcher capabilities in the future. # There's only three supported matchers, so for now, this is all # contained to a single method. If this grows, we can expand this # out to separate methods or even objects. if self.matcher == 'path': return self._create_path_matcher() elif self.matcher == 'pathAll': > return self._create_path_all_matcher() botocore/waiter.py:213: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_path_all_matcher(self): > expression = jmespath.compile(self.argument) botocore/waiter.py:237: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ expression = 'daemonDeployments[].status' def compile(expression): > return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = expression = 'daemonDeployments[].status' def parse(self, expression): cached = self._CACHE.get(expression) if cached is not None: return cached parsed_result = self._do_parse(expression) self._CACHE[expression] = parsed_result if len(self._CACHE) > self._MAX_SIZE: > self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:91: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _free_cache_entries(self): > for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): /usr/lib/python3.11/site-packages/jmespath/parser.py:492: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...ons[].Status.Code', 'VpnConnections[].State', 'imageScanStatus.status', 'daemon.status', 'daemonDeployments[].status']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError During handling of the above exception, another exception occurred: validator = Draft4Validator(schema={'additionalProperties': False, 'properties': {'version': {'type': 'number'}, 'waiters': {'addi...', 'delay', 'maxAttempts', 'acceptors'], 'type': 'object'}, 'type': 'object'}}, 'type': 'object'}, format_checker=None) waiter_model = OrderedDict([('version', 2), ('waiters', OrderedDict([('DaemonActive', OrderedDict([('delay', 15), ('maxAttempts', 8),...([('matcher', 'pathAll'), ('argument', 'tasks[].lastStatus'), ('state', 'success'), ('expected', 'STOPPED')])])]))]))]) client = @pytest.mark.parametrize("validator, waiter_model, client", _waiter_configs()) def test_lint_waiter_configs(validator, waiter_model, client): _validate_schema(validator, waiter_model) for waiter_name in client.waiter_names: > _lint_single_waiter(client, waiter_name, client.meta.service_model) tests/functional/test_waiter_config.py:101: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ client = waiter_name = 'daemon_deployment_stopped', service_model = ServiceModel(ecs) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value acceptors = waiter.config.acceptors except Exception as e: > raise AssertionError(f"Could not create waiter '{waiter_name}': {e}") E AssertionError: Could not create waiter 'daemon_deployment_stopped': Population must be a sequence. For dicts or sets, use sorted(d). tests/functional/test_waiter_config.py:116: AssertionError ________ test_lint_waiter_configs[validator52-waiter_model52-client52] _________ client = waiter_name = 'addon_active', service_model = ServiceModel(eks) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value > acceptors = waiter.config.acceptors tests/functional/test_waiter_config.py:114: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = @property def acceptors(self): acceptors = [] for acceptor_config in self._config['acceptors']: > acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = config = OrderedDict([('expected', 'CREATE_FAILED'), ('matcher', 'path'), ('state', 'failure'), ('argument', 'addon.status')]) def __init__(self, config): self.state = config['state'] self.matcher = config['matcher'] self.expected = config['expected'] self.argument = config.get('argument') > self.matcher_func = self._create_matcher_func() botocore/waiter.py:178: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_matcher_func(self): # An acceptor function is a callable that takes a single value. The # parsed AWS response. Note that the parsed error response is also # provided in the case of errors, so it's entirely possible to # handle all the available matcher capabilities in the future. # There's only three supported matchers, so for now, this is all # contained to a single method. If this grows, we can expand this # out to separate methods or even objects. if self.matcher == 'path': > return self._create_path_matcher() botocore/waiter.py:211: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_path_matcher(self): > expression = jmespath.compile(self.argument) botocore/waiter.py:226: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ expression = 'addon.status' def compile(expression): > return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = expression = 'addon.status' def parse(self, expression): cached = self._CACHE.get(expression) if cached is not None: return cached parsed_result = self._do_parse(expression) self._CACHE[expression] = parsed_result if len(self._CACHE) > self._MAX_SIZE: > self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:91: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _free_cache_entries(self): > for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): /usr/lib/python3.11/site-packages/jmespath/parser.py:492: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...e', 'VpnConnections[].State', 'imageScanStatus.status', 'daemon.status', 'daemonDeployments[].status', 'addon.status']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError During handling of the above exception, another exception occurred: validator = Draft4Validator(schema={'additionalProperties': False, 'properties': {'version': {'type': 'number'}, 'waiters': {'addi...', 'delay', 'maxAttempts', 'acceptors'], 'type': 'object'}, 'type': 'object'}}, 'type': 'object'}, format_checker=None) waiter_model = OrderedDict([('version', 2), ('waiters', OrderedDict([('ClusterActive', OrderedDict([('delay', 30), ('operation', 'Des...tus')]), OrderedDict([('expected', 'ResourceNotFoundException'), ('matcher', 'error'), ('state', 'success')])])]))]))]) client = @pytest.mark.parametrize("validator, waiter_model, client", _waiter_configs()) def test_lint_waiter_configs(validator, waiter_model, client): _validate_schema(validator, waiter_model) for waiter_name in client.waiter_names: > _lint_single_waiter(client, waiter_name, client.meta.service_model) tests/functional/test_waiter_config.py:101: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ client = waiter_name = 'addon_active', service_model = ServiceModel(eks) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value acceptors = waiter.config.acceptors except Exception as e: > raise AssertionError(f"Could not create waiter '{waiter_name}': {e}") E AssertionError: Could not create waiter 'addon_active': Population must be a sequence. For dicts or sets, use sorted(d). tests/functional/test_waiter_config.py:116: AssertionError ________ test_lint_waiter_configs[validator54-waiter_model54-client54] _________ client = waiter_name = 'cache_cluster_available' service_model = ServiceModel(elasticache) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value > acceptors = waiter.config.acceptors tests/functional/test_waiter_config.py:114: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = @property def acceptors(self): acceptors = [] for acceptor_config in self._config['acceptors']: > acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = config = OrderedDict([('argument', 'CacheClusters[].CacheClusterStatus'), ('expected', 'available'), ('matcher', 'pathAll'), ('state', 'success')]) def __init__(self, config): self.state = config['state'] self.matcher = config['matcher'] self.expected = config['expected'] self.argument = config.get('argument') > self.matcher_func = self._create_matcher_func() botocore/waiter.py:178: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_matcher_func(self): # An acceptor function is a callable that takes a single value. The # parsed AWS response. Note that the parsed error response is also # provided in the case of errors, so it's entirely possible to # handle all the available matcher capabilities in the future. # There's only three supported matchers, so for now, this is all # contained to a single method. If this grows, we can expand this # out to separate methods or even objects. if self.matcher == 'path': return self._create_path_matcher() elif self.matcher == 'pathAll': > return self._create_path_all_matcher() botocore/waiter.py:213: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_path_all_matcher(self): > expression = jmespath.compile(self.argument) botocore/waiter.py:237: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ expression = 'CacheClusters[].CacheClusterStatus' def compile(expression): > return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = expression = 'CacheClusters[].CacheClusterStatus' def parse(self, expression): cached = self._CACHE.get(expression) if cached is not None: return cached parsed_result = self._do_parse(expression) self._CACHE[expression] = parsed_result if len(self._CACHE) > self._MAX_SIZE: > self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:91: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _free_cache_entries(self): > for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): /usr/lib/python3.11/site-packages/jmespath/parser.py:492: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...anStatus.status', 'daemon.status', 'daemonDeployments[].status', 'addon.status', 'CacheClusters[].CacheClusterStatus']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError During handling of the above exception, another exception occurred: validator = Draft4Validator(schema={'additionalProperties': False, 'properties': {'version': {'type': 'number'}, 'waiters': {'addi...', 'delay', 'maxAttempts', 'acceptors'], 'type': 'object'}, 'type': 'object'}}, 'type': 'object'}, format_checker=None) waiter_model = OrderedDict([('version', 2), ('waiters', OrderedDict([('CacheClusterAvailable', OrderedDict([('acceptors', [OrderedDic...il ElastiCache replication group is deleted.'), ('maxAttempts', 40), ('operation', 'DescribeReplicationGroups')]))]))]) client = @pytest.mark.parametrize("validator, waiter_model, client", _waiter_configs()) def test_lint_waiter_configs(validator, waiter_model, client): _validate_schema(validator, waiter_model) for waiter_name in client.waiter_names: > _lint_single_waiter(client, waiter_name, client.meta.service_model) tests/functional/test_waiter_config.py:101: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ client = waiter_name = 'cache_cluster_available' service_model = ServiceModel(elasticache) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value acceptors = waiter.config.acceptors except Exception as e: > raise AssertionError(f"Could not create waiter '{waiter_name}': {e}") E AssertionError: Could not create waiter 'cache_cluster_available': Population must be a sequence. For dicts or sets, use sorted(d). tests/functional/test_waiter_config.py:116: AssertionError ________ test_lint_waiter_configs[validator55-waiter_model55-client55] _________ client = waiter_name = 'environment_exists' service_model = ServiceModel(elasticbeanstalk) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value > acceptors = waiter.config.acceptors tests/functional/test_waiter_config.py:114: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = @property def acceptors(self): acceptors = [] for acceptor_config in self._config['acceptors']: > acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = config = OrderedDict([('state', 'success'), ('matcher', 'pathAll'), ('argument', 'Environments[].Status'), ('expected', 'Ready')]) def __init__(self, config): self.state = config['state'] self.matcher = config['matcher'] self.expected = config['expected'] self.argument = config.get('argument') > self.matcher_func = self._create_matcher_func() botocore/waiter.py:178: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_matcher_func(self): # An acceptor function is a callable that takes a single value. The # parsed AWS response. Note that the parsed error response is also # provided in the case of errors, so it's entirely possible to # handle all the available matcher capabilities in the future. # There's only three supported matchers, so for now, this is all # contained to a single method. If this grows, we can expand this # out to separate methods or even objects. if self.matcher == 'path': return self._create_path_matcher() elif self.matcher == 'pathAll': > return self._create_path_all_matcher() botocore/waiter.py:213: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_path_all_matcher(self): > expression = jmespath.compile(self.argument) botocore/waiter.py:237: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ expression = 'Environments[].Status' def compile(expression): > return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = expression = 'Environments[].Status' def parse(self, expression): cached = self._CACHE.get(expression) if cached is not None: return cached parsed_result = self._do_parse(expression) self._CACHE[expression] = parsed_result if len(self._CACHE) > self._MAX_SIZE: > self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:91: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _free_cache_entries(self): > for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): /usr/lib/python3.11/site-packages/jmespath/parser.py:492: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok....status', 'daemonDeployments[].status', 'addon.status', 'CacheClusters[].CacheClusterStatus', 'Environments[].Status']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError During handling of the above exception, another exception occurred: validator = Draft4Validator(schema={'additionalProperties': False, 'properties': {'version': {'type': 'number'}, 'waiters': {'addi...', 'delay', 'maxAttempts', 'acceptors'], 'type': 'object'}, 'type': 'object'}}, 'type': 'object'}, format_checker=None) waiter_model = OrderedDict([('version', 2), ('waiters', OrderedDict([('EnvironmentExists', OrderedDict([('delay', 20), ('maxAttempts'...tate', 'retry'), ('matcher', 'pathAll'), ('argument', 'Environments[].Status'), ('expected', 'Terminating')])])]))]))]) client = @pytest.mark.parametrize("validator, waiter_model, client", _waiter_configs()) def test_lint_waiter_configs(validator, waiter_model, client): _validate_schema(validator, waiter_model) for waiter_name in client.waiter_names: > _lint_single_waiter(client, waiter_name, client.meta.service_model) tests/functional/test_waiter_config.py:101: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ client = waiter_name = 'environment_exists' service_model = ServiceModel(elasticbeanstalk) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value acceptors = waiter.config.acceptors except Exception as e: > raise AssertionError(f"Could not create waiter '{waiter_name}': {e}") E AssertionError: Could not create waiter 'environment_exists': Population must be a sequence. For dicts or sets, use sorted(d). tests/functional/test_waiter_config.py:116: AssertionError ________ test_lint_waiter_configs[validator56-waiter_model56-client56] _________ client = waiter_name = 'any_instance_in_service', service_model = ServiceModel(elb) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value > acceptors = waiter.config.acceptors tests/functional/test_waiter_config.py:114: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = @property def acceptors(self): acceptors = [] for acceptor_config in self._config['acceptors']: > acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = config = OrderedDict([('argument', 'InstanceStates[].State'), ('expected', 'InService'), ('matcher', 'pathAny'), ('state', 'success')]) def __init__(self, config): self.state = config['state'] self.matcher = config['matcher'] self.expected = config['expected'] self.argument = config.get('argument') > self.matcher_func = self._create_matcher_func() botocore/waiter.py:178: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_matcher_func(self): # An acceptor function is a callable that takes a single value. The # parsed AWS response. Note that the parsed error response is also # provided in the case of errors, so it's entirely possible to # handle all the available matcher capabilities in the future. # There's only three supported matchers, so for now, this is all # contained to a single method. If this grows, we can expand this # out to separate methods or even objects. if self.matcher == 'path': return self._create_path_matcher() elif self.matcher == 'pathAll': return self._create_path_all_matcher() elif self.matcher == 'pathAny': > return self._create_path_any_matcher() botocore/waiter.py:215: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_path_any_matcher(self): > expression = jmespath.compile(self.argument) botocore/waiter.py:258: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ expression = 'InstanceStates[].State' def compile(expression): > return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = expression = 'InstanceStates[].State' def parse(self, expression): cached = self._CACHE.get(expression) if cached is not None: return cached parsed_result = self._do_parse(expression) self._CACHE[expression] = parsed_result if len(self._CACHE) > self._MAX_SIZE: > self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:91: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _free_cache_entries(self): > for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): /usr/lib/python3.11/site-packages/jmespath/parser.py:492: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...ts[].status', 'addon.status', 'CacheClusters[].CacheClusterStatus', 'Environments[].Status', 'InstanceStates[].State']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError During handling of the above exception, another exception occurred: validator = Draft4Validator(schema={'additionalProperties': False, 'properties': {'version': {'type': 'number'}, 'waiters': {'addi...', 'delay', 'maxAttempts', 'acceptors'], 'type': 'object'}, 'type': 'object'}}, 'type': 'object'}, format_checker=None) waiter_model = OrderedDict([('version', 2), ('waiters', OrderedDict([('InstanceDeregistered', OrderedDict([('delay', 15), ('operation...Instance'), ('state', 'retry')])]), ('delay', 15), ('maxAttempts', 40), ('operation', 'DescribeInstanceHealth')]))]))]) client = @pytest.mark.parametrize("validator, waiter_model, client", _waiter_configs()) def test_lint_waiter_configs(validator, waiter_model, client): _validate_schema(validator, waiter_model) for waiter_name in client.waiter_names: > _lint_single_waiter(client, waiter_name, client.meta.service_model) tests/functional/test_waiter_config.py:101: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ client = waiter_name = 'any_instance_in_service', service_model = ServiceModel(elb) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value acceptors = waiter.config.acceptors except Exception as e: > raise AssertionError(f"Could not create waiter '{waiter_name}': {e}") E AssertionError: Could not create waiter 'any_instance_in_service': Population must be a sequence. For dicts or sets, use sorted(d). tests/functional/test_waiter_config.py:116: AssertionError ________ test_lint_waiter_configs[validator57-waiter_model57-client57] _________ client = waiter_name = 'load_balancer_available', service_model = ServiceModel(elbv2) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value > acceptors = waiter.config.acceptors tests/functional/test_waiter_config.py:114: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = @property def acceptors(self): acceptors = [] for acceptor_config in self._config['acceptors']: > acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = config = OrderedDict([('state', 'success'), ('matcher', 'pathAll'), ('argument', 'LoadBalancers[].State.Code'), ('expected', 'active')]) def __init__(self, config): self.state = config['state'] self.matcher = config['matcher'] self.expected = config['expected'] self.argument = config.get('argument') > self.matcher_func = self._create_matcher_func() botocore/waiter.py:178: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_matcher_func(self): # An acceptor function is a callable that takes a single value. The # parsed AWS response. Note that the parsed error response is also # provided in the case of errors, so it's entirely possible to # handle all the available matcher capabilities in the future. # There's only three supported matchers, so for now, this is all # contained to a single method. If this grows, we can expand this # out to separate methods or even objects. if self.matcher == 'path': return self._create_path_matcher() elif self.matcher == 'pathAll': > return self._create_path_all_matcher() botocore/waiter.py:213: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_path_all_matcher(self): > expression = jmespath.compile(self.argument) botocore/waiter.py:237: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ expression = 'LoadBalancers[].State.Code' def compile(expression): > return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = expression = 'LoadBalancers[].State.Code' def parse(self, expression): cached = self._CACHE.get(expression) if cached is not None: return cached parsed_result = self._do_parse(expression) self._CACHE[expression] = parsed_result if len(self._CACHE) > self._MAX_SIZE: > self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:91: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _free_cache_entries(self): > for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): /usr/lib/python3.11/site-packages/jmespath/parser.py:492: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...'CacheClusters[].CacheClusterStatus', 'Environments[].Status', 'InstanceStates[].State', 'LoadBalancers[].State.Code']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError During handling of the above exception, another exception occurred: validator = Draft4Validator(schema={'additionalProperties': False, 'properties': {'version': {'type': 'number'}, 'waiters': {'addi...', 'delay', 'maxAttempts', 'acceptors'], 'type': 'object'}, 'type': 'object'}}, 'type': 'object'}, format_checker=None) waiter_model = OrderedDict([('version', 2), ('waiters', OrderedDict([('LoadBalancerExists', OrderedDict([('delay', 15), ('operation',...thDescriptions[].TargetHealth.State'), ('expected', 'unused'), ('matcher', 'pathAll'), ('state', 'success')])])]))]))]) client = @pytest.mark.parametrize("validator, waiter_model, client", _waiter_configs()) def test_lint_waiter_configs(validator, waiter_model, client): _validate_schema(validator, waiter_model) for waiter_name in client.waiter_names: > _lint_single_waiter(client, waiter_name, client.meta.service_model) tests/functional/test_waiter_config.py:101: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ client = waiter_name = 'load_balancer_available', service_model = ServiceModel(elbv2) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value acceptors = waiter.config.acceptors except Exception as e: > raise AssertionError(f"Could not create waiter '{waiter_name}': {e}") E AssertionError: Could not create waiter 'load_balancer_available': Population must be a sequence. For dicts or sets, use sorted(d). tests/functional/test_waiter_config.py:116: AssertionError ________ test_lint_waiter_configs[validator59-waiter_model59-client59] _________ client = waiter_name = 'cluster_running', service_model = ServiceModel(emr) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value > acceptors = waiter.config.acceptors tests/functional/test_waiter_config.py:114: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = @property def acceptors(self): acceptors = [] for acceptor_config in self._config['acceptors']: > acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = config = OrderedDict([('state', 'success'), ('matcher', 'path'), ('argument', 'Cluster.Status.State'), ('expected', 'RUNNING')]) def __init__(self, config): self.state = config['state'] self.matcher = config['matcher'] self.expected = config['expected'] self.argument = config.get('argument') > self.matcher_func = self._create_matcher_func() botocore/waiter.py:178: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_matcher_func(self): # An acceptor function is a callable that takes a single value. The # parsed AWS response. Note that the parsed error response is also # provided in the case of errors, so it's entirely possible to # handle all the available matcher capabilities in the future. # There's only three supported matchers, so for now, this is all # contained to a single method. If this grows, we can expand this # out to separate methods or even objects. if self.matcher == 'path': > return self._create_path_matcher() botocore/waiter.py:211: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_path_matcher(self): > expression = jmespath.compile(self.argument) botocore/waiter.py:226: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ expression = 'Cluster.Status.State' def compile(expression): > return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = expression = 'Cluster.Status.State' def parse(self, expression): cached = self._CACHE.get(expression) if cached is not None: return cached parsed_result = self._do_parse(expression) self._CACHE[expression] = parsed_result if len(self._CACHE) > self._MAX_SIZE: > self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:91: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _free_cache_entries(self): > for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): /usr/lib/python3.11/site-packages/jmespath/parser.py:492: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...usterStatus', 'Environments[].Status', 'InstanceStates[].State', 'LoadBalancers[].State.Code', 'Cluster.Status.State']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError During handling of the above exception, another exception occurred: validator = Draft4Validator(schema={'additionalProperties': False, 'properties': {'version': {'type': 'number'}, 'waiters': {'addi...', 'delay', 'maxAttempts', 'acceptors'], 'type': 'object'}, 'type': 'object'}}, 'type': 'object'}, format_checker=None) waiter_model = OrderedDict([('version', 2), ('waiters', OrderedDict([('ClusterRunning', OrderedDict([('delay', 30), ('operation', 'De...ailure'), ('matcher', 'path'), ('argument', 'Cluster.Status.State'), ('expected', 'TERMINATED_WITH_ERRORS')])])]))]))]) client = @pytest.mark.parametrize("validator, waiter_model, client", _waiter_configs()) def test_lint_waiter_configs(validator, waiter_model, client): _validate_schema(validator, waiter_model) for waiter_name in client.waiter_names: > _lint_single_waiter(client, waiter_name, client.meta.service_model) tests/functional/test_waiter_config.py:101: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ client = waiter_name = 'cluster_running', service_model = ServiceModel(emr) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value acceptors = waiter.config.acceptors except Exception as e: > raise AssertionError(f"Could not create waiter '{waiter_name}': {e}") E AssertionError: Could not create waiter 'cluster_running': Population must be a sequence. For dicts or sets, use sorted(d). tests/functional/test_waiter_config.py:116: AssertionError ________ test_lint_waiter_configs[validator68-waiter_model68-client68] _________ client = waiter_name = 'contact_scheduled', service_model = ServiceModel(groundstation) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value > acceptors = waiter.config.acceptors tests/functional/test_waiter_config.py:114: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = @property def acceptors(self): acceptors = [] for acceptor_config in self._config['acceptors']: > acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = config = OrderedDict([('matcher', 'path'), ('argument', 'contactStatus'), ('state', 'failure'), ('expected', 'FAILED_TO_SCHEDULE')]) def __init__(self, config): self.state = config['state'] self.matcher = config['matcher'] self.expected = config['expected'] self.argument = config.get('argument') > self.matcher_func = self._create_matcher_func() botocore/waiter.py:178: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_matcher_func(self): # An acceptor function is a callable that takes a single value. The # parsed AWS response. Note that the parsed error response is also # provided in the case of errors, so it's entirely possible to # handle all the available matcher capabilities in the future. # There's only three supported matchers, so for now, this is all # contained to a single method. If this grows, we can expand this # out to separate methods or even objects. if self.matcher == 'path': > return self._create_path_matcher() botocore/waiter.py:211: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_path_matcher(self): > expression = jmespath.compile(self.argument) botocore/waiter.py:226: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ expression = 'contactStatus' def compile(expression): > return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = expression = 'contactStatus' def parse(self, expression): cached = self._CACHE.get(expression) if cached is not None: return cached parsed_result = self._do_parse(expression) self._CACHE[expression] = parsed_result if len(self._CACHE) > self._MAX_SIZE: > self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:91: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _free_cache_entries(self): > for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): /usr/lib/python3.11/site-packages/jmespath/parser.py:492: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...vironments[].Status', 'InstanceStates[].State', 'LoadBalancers[].State.Code', 'Cluster.Status.State', 'contactStatus']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError During handling of the above exception, another exception occurred: validator = Draft4Validator(schema={'additionalProperties': False, 'properties': {'version': {'type': 'number'}, 'waiters': {'addi...', 'delay', 'maxAttempts', 'acceptors'], 'type': 'object'}, 'type': 'object'}}, 'type': 'object'}, format_checker=None) waiter_model = OrderedDict([('version', 2), ('waiters', OrderedDict([('ContactScheduled', OrderedDict([('description', 'Waits until a...eredDict([('matcher', 'path'), ('argument', 'version.status'), ('state', 'success'), ('expected', 'ACTIVE')])])]))]))]) client = @pytest.mark.parametrize("validator, waiter_model, client", _waiter_configs()) def test_lint_waiter_configs(validator, waiter_model, client): _validate_schema(validator, waiter_model) for waiter_name in client.waiter_names: > _lint_single_waiter(client, waiter_name, client.meta.service_model) tests/functional/test_waiter_config.py:101: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ client = waiter_name = 'contact_scheduled', service_model = ServiceModel(groundstation) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value acceptors = waiter.config.acceptors except Exception as e: > raise AssertionError(f"Could not create waiter '{waiter_name}': {e}") E AssertionError: Could not create waiter 'contact_scheduled': Population must be a sequence. For dicts or sets, use sorted(d). tests/functional/test_waiter_config.py:116: AssertionError ________ test_lint_waiter_configs[validator69-waiter_model69-client69] _________ client = waiter_name = 'fhir_datastore_active', service_model = ServiceModel(healthlake) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value > acceptors = waiter.config.acceptors tests/functional/test_waiter_config.py:114: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = @property def acceptors(self): acceptors = [] for acceptor_config in self._config['acceptors']: > acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = config = OrderedDict([('state', 'success'), ('matcher', 'path'), ('argument', 'DatastoreProperties.DatastoreStatus'), ('expected', 'ACTIVE')]) def __init__(self, config): self.state = config['state'] self.matcher = config['matcher'] self.expected = config['expected'] self.argument = config.get('argument') > self.matcher_func = self._create_matcher_func() botocore/waiter.py:178: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_matcher_func(self): # An acceptor function is a callable that takes a single value. The # parsed AWS response. Note that the parsed error response is also # provided in the case of errors, so it's entirely possible to # handle all the available matcher capabilities in the future. # There's only three supported matchers, so for now, this is all # contained to a single method. If this grows, we can expand this # out to separate methods or even objects. if self.matcher == 'path': > return self._create_path_matcher() botocore/waiter.py:211: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_path_matcher(self): > expression = jmespath.compile(self.argument) botocore/waiter.py:226: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ expression = 'DatastoreProperties.DatastoreStatus' def compile(expression): > return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = expression = 'DatastoreProperties.DatastoreStatus' def parse(self, expression): cached = self._CACHE.get(expression) if cached is not None: return cached parsed_result = self._do_parse(expression) self._CACHE[expression] = parsed_result if len(self._CACHE) > self._MAX_SIZE: > self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:91: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _free_cache_entries(self): > for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): /usr/lib/python3.11/site-packages/jmespath/parser.py:492: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok....State', 'LoadBalancers[].State.Code', 'Cluster.Status.State', 'contactStatus', 'DatastoreProperties.DatastoreStatus']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError During handling of the above exception, another exception occurred: validator = Draft4Validator(schema={'additionalProperties': False, 'properties': {'version': {'type': 'number'}, 'waiters': {'addi...', 'delay', 'maxAttempts', 'acceptors'], 'type': 'object'}, 'type': 'object'}}, 'type': 'object'}, format_checker=None) waiter_model = OrderedDict([('version', 2), ('waiters', OrderedDict([('FHIRDatastoreActive', OrderedDict([('operation', 'DescribeFHIR...te', 'failure'), ('matcher', 'path'), ('argument', 'ImportJobProperties.JobStatus'), ('expected', 'FAILED')])])]))]))]) client = @pytest.mark.parametrize("validator, waiter_model, client", _waiter_configs()) def test_lint_waiter_configs(validator, waiter_model, client): _validate_schema(validator, waiter_model) for waiter_name in client.waiter_names: > _lint_single_waiter(client, waiter_name, client.meta.service_model) tests/functional/test_waiter_config.py:101: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ client = waiter_name = 'fhir_datastore_active', service_model = ServiceModel(healthlake) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value acceptors = waiter.config.acceptors except Exception as e: > raise AssertionError(f"Could not create waiter '{waiter_name}': {e}") E AssertionError: Could not create waiter 'fhir_datastore_active': Population must be a sequence. For dicts or sets, use sorted(d). tests/functional/test_waiter_config.py:116: AssertionError ________ test_lint_waiter_configs[validator71-waiter_model71-client71] _________ client = waiter_name = 'connection_available', service_model = ServiceModel(interconnect) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value > acceptors = waiter.config.acceptors tests/functional/test_waiter_config.py:114: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = @property def acceptors(self): acceptors = [] for acceptor_config in self._config['acceptors']: > acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = config = OrderedDict([('matcher', 'path'), ('argument', 'connection.state'), ('state', 'success'), ('expected', 'available')]) def __init__(self, config): self.state = config['state'] self.matcher = config['matcher'] self.expected = config['expected'] self.argument = config.get('argument') > self.matcher_func = self._create_matcher_func() botocore/waiter.py:178: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_matcher_func(self): # An acceptor function is a callable that takes a single value. The # parsed AWS response. Note that the parsed error response is also # provided in the case of errors, so it's entirely possible to # handle all the available matcher capabilities in the future. # There's only three supported matchers, so for now, this is all # contained to a single method. If this grows, we can expand this # out to separate methods or even objects. if self.matcher == 'path': > return self._create_path_matcher() botocore/waiter.py:211: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_path_matcher(self): > expression = jmespath.compile(self.argument) botocore/waiter.py:226: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ expression = 'connection.state' def compile(expression): > return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = expression = 'connection.state' def parse(self, expression): cached = self._CACHE.get(expression) if cached is not None: return cached parsed_result = self._do_parse(expression) self._CACHE[expression] = parsed_result if len(self._CACHE) > self._MAX_SIZE: > self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:91: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _free_cache_entries(self): > for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): /usr/lib/python3.11/site-packages/jmespath/parser.py:492: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...ers[].State.Code', 'Cluster.Status.State', 'contactStatus', 'DatastoreProperties.DatastoreStatus', 'connection.state']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError During handling of the above exception, another exception occurred: validator = Draft4Validator(schema={'additionalProperties': False, 'properties': {'version': {'type': 'number'}, 'waiters': {'addi...', 'delay', 'maxAttempts', 'acceptors'], 'type': 'object'}, 'type': 'object'}}, 'type': 'object'}, format_checker=None) waiter_model = OrderedDict([('version', 2), ('waiters', OrderedDict([('ConnectionAvailable', OrderedDict([('delay', 30), ('maxAttempt...dDict([('matcher', 'path'), ('argument', 'connection.state'), ('state', 'success'), ('expected', 'deleted')])])]))]))]) client = @pytest.mark.parametrize("validator, waiter_model, client", _waiter_configs()) def test_lint_waiter_configs(validator, waiter_model, client): _validate_schema(validator, waiter_model) for waiter_name in client.waiter_names: > _lint_single_waiter(client, waiter_name, client.meta.service_model) tests/functional/test_waiter_config.py:101: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ client = waiter_name = 'connection_available', service_model = ServiceModel(interconnect) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value acceptors = waiter.config.acceptors except Exception as e: > raise AssertionError(f"Could not create waiter '{waiter_name}': {e}") E AssertionError: Could not create waiter 'connection_available': Population must be a sequence. For dicts or sets, use sorted(d). tests/functional/test_waiter_config.py:116: AssertionError ________ test_lint_waiter_configs[validator75-waiter_model75-client75] _________ client = waiter_name = 'asset_active', service_model = ServiceModel(iotsitewise) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value > acceptors = waiter.config.acceptors tests/functional/test_waiter_config.py:114: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = @property def acceptors(self): acceptors = [] for acceptor_config in self._config['acceptors']: > acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = config = OrderedDict([('state', 'success'), ('matcher', 'path'), ('argument', 'assetStatus.state'), ('expected', 'ACTIVE')]) def __init__(self, config): self.state = config['state'] self.matcher = config['matcher'] self.expected = config['expected'] self.argument = config.get('argument') > self.matcher_func = self._create_matcher_func() botocore/waiter.py:178: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_matcher_func(self): # An acceptor function is a callable that takes a single value. The # parsed AWS response. Note that the parsed error response is also # provided in the case of errors, so it's entirely possible to # handle all the available matcher capabilities in the future. # There's only three supported matchers, so for now, this is all # contained to a single method. If this grows, we can expand this # out to separate methods or even objects. if self.matcher == 'path': > return self._create_path_matcher() botocore/waiter.py:211: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_path_matcher(self): > expression = jmespath.compile(self.argument) botocore/waiter.py:226: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ expression = 'assetStatus.state' def compile(expression): > return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = expression = 'assetStatus.state' def parse(self, expression): cached = self._CACHE.get(expression) if cached is not None: return cached parsed_result = self._do_parse(expression) self._CACHE[expression] = parsed_result if len(self._CACHE) > self._MAX_SIZE: > self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:91: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _free_cache_entries(self): > for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): /usr/lib/python3.11/site-packages/jmespath/parser.py:492: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...luster.Status.State', 'contactStatus', 'DatastoreProperties.DatastoreStatus', 'connection.state', 'assetStatus.state']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError During handling of the above exception, another exception occurred: validator = Draft4Validator(schema={'additionalProperties': False, 'properties': {'version': {'type': 'number'}, 'waiters': {'addi...', 'delay', 'maxAttempts', 'acceptors'], 'type': 'object'}, 'type': 'object'}}, 'type': 'object'}, format_checker=None) waiter_model = OrderedDict([('version', 2), ('waiters', OrderedDict([('AssetModelNotExists', OrderedDict([('delay', 3), ('maxAttempts...Dict([('state', 'success'), ('matcher', 'path'), ('argument', 'portalStatus.state'), ('expected', 'ACTIVE')])])]))]))]) client = @pytest.mark.parametrize("validator, waiter_model, client", _waiter_configs()) def test_lint_waiter_configs(validator, waiter_model, client): _validate_schema(validator, waiter_model) for waiter_name in client.waiter_names: > _lint_single_waiter(client, waiter_name, client.meta.service_model) tests/functional/test_waiter_config.py:101: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ client = waiter_name = 'asset_active', service_model = ServiceModel(iotsitewise) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value acceptors = waiter.config.acceptors except Exception as e: > raise AssertionError(f"Could not create waiter '{waiter_name}': {e}") E AssertionError: Could not create waiter 'asset_active': Population must be a sequence. For dicts or sets, use sorted(d). tests/functional/test_waiter_config.py:116: AssertionError ________ test_lint_waiter_configs[validator82-waiter_model82-client82] _________ client = waiter_name = 'function_active_v2', service_model = ServiceModel(lambda) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value > acceptors = waiter.config.acceptors tests/functional/test_waiter_config.py:114: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = @property def acceptors(self): acceptors = [] for acceptor_config in self._config['acceptors']: > acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = config = OrderedDict([('matcher', 'path'), ('argument', 'Configuration.State'), ('state', 'success'), ('expected', 'Active')]) def __init__(self, config): self.state = config['state'] self.matcher = config['matcher'] self.expected = config['expected'] self.argument = config.get('argument') > self.matcher_func = self._create_matcher_func() botocore/waiter.py:178: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_matcher_func(self): # An acceptor function is a callable that takes a single value. The # parsed AWS response. Note that the parsed error response is also # provided in the case of errors, so it's entirely possible to # handle all the available matcher capabilities in the future. # There's only three supported matchers, so for now, this is all # contained to a single method. If this grows, we can expand this # out to separate methods or even objects. if self.matcher == 'path': > return self._create_path_matcher() botocore/waiter.py:211: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_path_matcher(self): > expression = jmespath.compile(self.argument) botocore/waiter.py:226: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ expression = 'Configuration.State' def compile(expression): > return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = expression = 'Configuration.State' def parse(self, expression): cached = self._CACHE.get(expression) if cached is not None: return cached parsed_result = self._do_parse(expression) self._CACHE[expression] = parsed_result if len(self._CACHE) > self._MAX_SIZE: > self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:91: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _free_cache_entries(self): > for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): /usr/lib/python3.11/site-packages/jmespath/parser.py:492: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...contactStatus', 'DatastoreProperties.DatastoreStatus', 'connection.state', 'assetStatus.state', 'Configuration.State']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError During handling of the above exception, another exception occurred: validator = Draft4Validator(schema={'additionalProperties': False, 'properties': {'version': {'type': 'number'}, 'waiters': {'addi...', 'delay', 'maxAttempts', 'acceptors'], 'type': 'object'}, 'type': 'object'}}, 'type': 'object'}, format_checker=None) waiter_model = OrderedDict([('version', 2), ('waiters', OrderedDict([('FunctionActive', OrderedDict([('description', "Waits for the f...d')]), OrderedDict([('matcher', 'path'), ('argument', 'State'), ('state', 'retry'), ('expected', 'Pending')])])]))]))]) client = @pytest.mark.parametrize("validator, waiter_model, client", _waiter_configs()) def test_lint_waiter_configs(validator, waiter_model, client): _validate_schema(validator, waiter_model) for waiter_name in client.waiter_names: > _lint_single_waiter(client, waiter_name, client.meta.service_model) tests/functional/test_waiter_config.py:101: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ client = waiter_name = 'function_active_v2', service_model = ServiceModel(lambda) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value acceptors = waiter.config.acceptors except Exception as e: > raise AssertionError(f"Could not create waiter '{waiter_name}': {e}") E AssertionError: Could not create waiter 'function_active_v2': Population must be a sequence. For dicts or sets, use sorted(d). tests/functional/test_waiter_config.py:116: AssertionError ________ test_lint_waiter_configs[validator84-waiter_model84-client84] _________ client = waiter_name = 'bot_alias_available', service_model = ServiceModel(lexv2-models) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value > acceptors = waiter.config.acceptors tests/functional/test_waiter_config.py:114: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = @property def acceptors(self): acceptors = [] for acceptor_config in self._config['acceptors']: > acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = config = OrderedDict([('expected', 'Available'), ('matcher', 'path'), ('state', 'success'), ('argument', 'botAliasStatus')]) def __init__(self, config): self.state = config['state'] self.matcher = config['matcher'] self.expected = config['expected'] self.argument = config.get('argument') > self.matcher_func = self._create_matcher_func() botocore/waiter.py:178: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_matcher_func(self): # An acceptor function is a callable that takes a single value. The # parsed AWS response. Note that the parsed error response is also # provided in the case of errors, so it's entirely possible to # handle all the available matcher capabilities in the future. # There's only three supported matchers, so for now, this is all # contained to a single method. If this grows, we can expand this # out to separate methods or even objects. if self.matcher == 'path': > return self._create_path_matcher() botocore/waiter.py:211: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_path_matcher(self): > expression = jmespath.compile(self.argument) botocore/waiter.py:226: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ expression = 'botAliasStatus' def compile(expression): > return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = expression = 'botAliasStatus' def parse(self, expression): cached = self._CACHE.get(expression) if cached is not None: return cached parsed_result = self._do_parse(expression) self._CACHE[expression] = parsed_result if len(self._CACHE) > self._MAX_SIZE: > self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:91: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _free_cache_entries(self): > for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): /usr/lib/python3.11/site-packages/jmespath/parser.py:492: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...atastoreProperties.DatastoreStatus', 'connection.state', 'assetStatus.state', 'Configuration.State', 'botAliasStatus']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError During handling of the above exception, another exception occurred: validator = Draft4Validator(schema={'additionalProperties': False, 'properties': {'version': {'type': 'number'}, 'waiters': {'addi...', 'delay', 'maxAttempts', 'acceptors'], 'type': 'object'}, 'type': 'object'}}, 'type': 'object'}, format_checker=None) waiter_model = OrderedDict([('version', 2), ('waiters', OrderedDict([('BotAvailable', OrderedDict([('delay', 10), ('operation', 'Desc...redDict([('expected', 'Failed'), ('matcher', 'path'), ('state', 'failure'), ('argument', 'botLocaleStatus')])])]))]))]) client = @pytest.mark.parametrize("validator, waiter_model, client", _waiter_configs()) def test_lint_waiter_configs(validator, waiter_model, client): _validate_schema(validator, waiter_model) for waiter_name in client.waiter_names: > _lint_single_waiter(client, waiter_name, client.meta.service_model) tests/functional/test_waiter_config.py:101: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ client = waiter_name = 'bot_alias_available', service_model = ServiceModel(lexv2-models) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value acceptors = waiter.config.acceptors except Exception as e: > raise AssertionError(f"Could not create waiter '{waiter_name}': {e}") E AssertionError: Could not create waiter 'bot_alias_available': Population must be a sequence. For dicts or sets, use sorted(d). tests/functional/test_waiter_config.py:116: AssertionError ________ test_lint_waiter_configs[validator87-waiter_model87-client87] _________ client = waiter_name = 'batch_prediction_available' service_model = ServiceModel(machinelearning) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value > acceptors = waiter.config.acceptors tests/functional/test_waiter_config.py:114: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = @property def acceptors(self): acceptors = [] for acceptor_config in self._config['acceptors']: > acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = config = OrderedDict([('expected', 'COMPLETED'), ('matcher', 'pathAll'), ('state', 'success'), ('argument', 'Results[].Status')]) def __init__(self, config): self.state = config['state'] self.matcher = config['matcher'] self.expected = config['expected'] self.argument = config.get('argument') > self.matcher_func = self._create_matcher_func() botocore/waiter.py:178: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_matcher_func(self): # An acceptor function is a callable that takes a single value. The # parsed AWS response. Note that the parsed error response is also # provided in the case of errors, so it's entirely possible to # handle all the available matcher capabilities in the future. # There's only three supported matchers, so for now, this is all # contained to a single method. If this grows, we can expand this # out to separate methods or even objects. if self.matcher == 'path': return self._create_path_matcher() elif self.matcher == 'pathAll': > return self._create_path_all_matcher() botocore/waiter.py:213: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_path_all_matcher(self): > expression = jmespath.compile(self.argument) botocore/waiter.py:237: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ expression = 'Results[].Status' def compile(expression): > return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = expression = 'Results[].Status' def parse(self, expression): cached = self._CACHE.get(expression) if cached is not None: return cached parsed_result = self._do_parse(expression) self._CACHE[expression] = parsed_result if len(self._CACHE) > self._MAX_SIZE: > self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:91: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _free_cache_entries(self): > for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): /usr/lib/python3.11/site-packages/jmespath/parser.py:492: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...atastoreStatus', 'connection.state', 'assetStatus.state', 'Configuration.State', 'botAliasStatus', 'Results[].Status']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError During handling of the above exception, another exception occurred: validator = Draft4Validator(schema={'additionalProperties': False, 'properties': {'version': {'type': 'number'}, 'waiters': {'addi...', 'delay', 'maxAttempts', 'acceptors'], 'type': 'object'}, 'type': 'object'}}, 'type': 'object'}, format_checker=None) waiter_model = OrderedDict([('version', 2), ('waiters', OrderedDict([('DataSourceAvailable', OrderedDict([('delay', 30), ('operation'...ict([('expected', 'FAILED'), ('matcher', 'pathAny'), ('state', 'failure'), ('argument', 'Results[].Status')])])]))]))]) client = @pytest.mark.parametrize("validator, waiter_model, client", _waiter_configs()) def test_lint_waiter_configs(validator, waiter_model, client): _validate_schema(validator, waiter_model) for waiter_name in client.waiter_names: > _lint_single_waiter(client, waiter_name, client.meta.service_model) tests/functional/test_waiter_config.py:101: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ client = waiter_name = 'batch_prediction_available' service_model = ServiceModel(machinelearning) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value acceptors = waiter.config.acceptors except Exception as e: > raise AssertionError(f"Could not create waiter '{waiter_name}': {e}") E AssertionError: Could not create waiter 'batch_prediction_available': Population must be a sequence. For dicts or sets, use sorted(d). tests/functional/test_waiter_config.py:116: AssertionError ________ test_lint_waiter_configs[validator94-waiter_model94-client94] _________ client = waiter_name = 'flow_active', service_model = ServiceModel(mediaconnect) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value > acceptors = waiter.config.acceptors tests/functional/test_waiter_config.py:114: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = @property def acceptors(self): acceptors = [] for acceptor_config in self._config['acceptors']: > acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = config = OrderedDict([('matcher', 'path'), ('argument', 'Flow.Status'), ('state', 'success'), ('expected', 'ACTIVE')]) def __init__(self, config): self.state = config['state'] self.matcher = config['matcher'] self.expected = config['expected'] self.argument = config.get('argument') > self.matcher_func = self._create_matcher_func() botocore/waiter.py:178: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_matcher_func(self): # An acceptor function is a callable that takes a single value. The # parsed AWS response. Note that the parsed error response is also # provided in the case of errors, so it's entirely possible to # handle all the available matcher capabilities in the future. # There's only three supported matchers, so for now, this is all # contained to a single method. If this grows, we can expand this # out to separate methods or even objects. if self.matcher == 'path': > return self._create_path_matcher() botocore/waiter.py:211: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_path_matcher(self): > expression = jmespath.compile(self.argument) botocore/waiter.py:226: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ expression = 'Flow.Status' def compile(expression): > return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = expression = 'Flow.Status' def parse(self, expression): cached = self._CACHE.get(expression) if cached is not None: return cached parsed_result = self._do_parse(expression) self._CACHE[expression] = parsed_result if len(self._CACHE) > self._MAX_SIZE: > self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:91: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _free_cache_entries(self): > for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): /usr/lib/python3.11/site-packages/jmespath/parser.py:492: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok..., 'connection.state', 'assetStatus.state', 'Configuration.State', 'botAliasStatus', 'Results[].Status', 'Flow.Status']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError During handling of the above exception, another exception occurred: validator = Draft4Validator(schema={'additionalProperties': False, 'properties': {'version': {'type': 'number'}, 'waiters': {'addi...', 'delay', 'maxAttempts', 'acceptors'], 'type': 'object'}, 'type': 'object'}}, 'type': 'object'}, format_checker=None) waiter_model = OrderedDict([('version', 2), ('waiters', OrderedDict([('FlowActive', OrderedDict([('description', 'Wait until a flow i...ion')]), OrderedDict([('matcher', 'error'), ('state', 'retry'), ('expected', 'ServiceUnavailableException')])])]))]))]) client = @pytest.mark.parametrize("validator, waiter_model, client", _waiter_configs()) def test_lint_waiter_configs(validator, waiter_model, client): _validate_schema(validator, waiter_model) for waiter_name in client.waiter_names: > _lint_single_waiter(client, waiter_name, client.meta.service_model) tests/functional/test_waiter_config.py:101: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ client = waiter_name = 'flow_active', service_model = ServiceModel(mediaconnect) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value acceptors = waiter.config.acceptors except Exception as e: > raise AssertionError(f"Could not create waiter '{waiter_name}': {e}") E AssertionError: Could not create waiter 'flow_active': Population must be a sequence. For dicts or sets, use sorted(d). tests/functional/test_waiter_config.py:116: AssertionError ________ test_lint_waiter_configs[validator95-waiter_model95-client95] _________ client = waiter_name = 'signal_map_monitor_deleted' service_model = ServiceModel(medialive) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value > acceptors = waiter.config.acceptors tests/functional/test_waiter_config.py:114: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = @property def acceptors(self): acceptors = [] for acceptor_config in self._config['acceptors']: > acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = config = OrderedDict([('matcher', 'path'), ('argument', 'MonitorDeployment.Status'), ('state', 'success'), ('expected', 'DELETE_COMPLETE')]) def __init__(self, config): self.state = config['state'] self.matcher = config['matcher'] self.expected = config['expected'] self.argument = config.get('argument') > self.matcher_func = self._create_matcher_func() botocore/waiter.py:178: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_matcher_func(self): # An acceptor function is a callable that takes a single value. The # parsed AWS response. Note that the parsed error response is also # provided in the case of errors, so it's entirely possible to # handle all the available matcher capabilities in the future. # There's only three supported matchers, so for now, this is all # contained to a single method. If this grows, we can expand this # out to separate methods or even objects. if self.matcher == 'path': > return self._create_path_matcher() botocore/waiter.py:211: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_path_matcher(self): > expression = jmespath.compile(self.argument) botocore/waiter.py:226: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ expression = 'MonitorDeployment.Status' def compile(expression): > return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = expression = 'MonitorDeployment.Status' def parse(self, expression): cached = self._CACHE.get(expression) if cached is not None: return cached parsed_result = self._do_parse(expression) self._CACHE[expression] = parsed_result if len(self._CACHE) > self._MAX_SIZE: > self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:91: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _free_cache_entries(self): > for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): /usr/lib/python3.11/site-packages/jmespath/parser.py:492: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...Status.state', 'Configuration.State', 'botAliasStatus', 'Results[].Status', 'Flow.Status', 'MonitorDeployment.Status']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError During handling of the above exception, another exception occurred: validator = Draft4Validator(schema={'additionalProperties': False, 'properties': {'version': {'type': 'number'}, 'waiters': {'addi...', 'delay', 'maxAttempts', 'acceptors'], 'type': 'object'}, 'type': 'object'}}, 'type': 'object'}, format_checker=None) waiter_model = OrderedDict([('version', 2), ('waiters', OrderedDict([('ChannelCreated', OrderedDict([('description', 'Wait until a ch...te'), ('expected', 'DELETING')]), OrderedDict([('state', 'retry'), ('matcher', 'status'), ('expected', 500)])])]))]))]) client = @pytest.mark.parametrize("validator, waiter_model, client", _waiter_configs()) def test_lint_waiter_configs(validator, waiter_model, client): _validate_schema(validator, waiter_model) for waiter_name in client.waiter_names: > _lint_single_waiter(client, waiter_name, client.meta.service_model) tests/functional/test_waiter_config.py:101: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ client = waiter_name = 'signal_map_monitor_deleted' service_model = ServiceModel(medialive) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value acceptors = waiter.config.acceptors except Exception as e: > raise AssertionError(f"Could not create waiter '{waiter_name}': {e}") E AssertionError: Could not create waiter 'signal_map_monitor_deleted': Population must be a sequence. For dicts or sets, use sorted(d). tests/functional/test_waiter_config.py:116: AssertionError _______ test_lint_waiter_configs[validator103-waiter_model103-client103] _______ client = waiter_name = 'export_task_cancelled' service_model = ServiceModel(neptune-graph) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value > acceptors = waiter.config.acceptors tests/functional/test_waiter_config.py:114: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = @property def acceptors(self): acceptors = [] for acceptor_config in self._config['acceptors']: > acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = config = OrderedDict([('matcher', 'path'), ('argument', "status != 'CANCELLING' && status != 'CANCELLED'"), ('state', 'failure'), ('expected', True)]) def __init__(self, config): self.state = config['state'] self.matcher = config['matcher'] self.expected = config['expected'] self.argument = config.get('argument') > self.matcher_func = self._create_matcher_func() botocore/waiter.py:178: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_matcher_func(self): # An acceptor function is a callable that takes a single value. The # parsed AWS response. Note that the parsed error response is also # provided in the case of errors, so it's entirely possible to # handle all the available matcher capabilities in the future. # There's only three supported matchers, so for now, this is all # contained to a single method. If this grows, we can expand this # out to separate methods or even objects. if self.matcher == 'path': > return self._create_path_matcher() botocore/waiter.py:211: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_path_matcher(self): > expression = jmespath.compile(self.argument) botocore/waiter.py:226: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ expression = "status != 'CANCELLING' && status != 'CANCELLED'" def compile(expression): > return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = expression = "status != 'CANCELLING' && status != 'CANCELLED'" def parse(self, expression): cached = self._CACHE.get(expression) if cached is not None: return cached parsed_result = self._do_parse(expression) self._CACHE[expression] = parsed_result if len(self._CACHE) > self._MAX_SIZE: > self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:91: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _free_cache_entries(self): > for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): /usr/lib/python3.11/site-packages/jmespath/parser.py:492: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...us', 'Results[].Status', 'Flow.Status', 'MonitorDeployment.Status', "status != 'CANCELLING' && status != 'CANCELLED'"]) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError During handling of the above exception, another exception occurred: validator = Draft4Validator(schema={'additionalProperties': False, 'properties': {'version': {'type': 'number'}, 'waiters': {'addi...', 'delay', 'maxAttempts', 'acceptors'], 'type': 'object'}, 'type': 'object'}}, 'type': 'object'}, format_checker=None) waiter_model = OrderedDict([('version', 2), ('waiters', OrderedDict([('ExportTaskCancelled', OrderedDict([('description', 'Wait until...True)]), OrderedDict([('matcher', 'error'), ('state', 'success'), ('expected', 'ResourceNotFoundException')])])]))]))]) client = @pytest.mark.parametrize("validator, waiter_model, client", _waiter_configs()) def test_lint_waiter_configs(validator, waiter_model, client): _validate_schema(validator, waiter_model) for waiter_name in client.waiter_names: > _lint_single_waiter(client, waiter_name, client.meta.service_model) tests/functional/test_waiter_config.py:101: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ client = waiter_name = 'export_task_cancelled' service_model = ServiceModel(neptune-graph) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value acceptors = waiter.config.acceptors except Exception as e: > raise AssertionError(f"Could not create waiter '{waiter_name}': {e}") E AssertionError: Could not create waiter 'export_task_cancelled': Population must be a sequence. For dicts or sets, use sorted(d). tests/functional/test_waiter_config.py:116: AssertionError _______ test_lint_waiter_configs[validator124-waiter_model124-client124] _______ client = waiter_name = 'component_deleted', service_model = ServiceModel(proton) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value > acceptors = waiter.config.acceptors tests/functional/test_waiter_config.py:114: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = @property def acceptors(self): acceptors = [] for acceptor_config in self._config['acceptors']: > acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = config = OrderedDict([('matcher', 'path'), ('argument', 'component.deploymentStatus'), ('state', 'failure'), ('expected', 'DELETE_FAILED')]) def __init__(self, config): self.state = config['state'] self.matcher = config['matcher'] self.expected = config['expected'] self.argument = config.get('argument') > self.matcher_func = self._create_matcher_func() botocore/waiter.py:178: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_matcher_func(self): # An acceptor function is a callable that takes a single value. The # parsed AWS response. Note that the parsed error response is also # provided in the case of errors, so it's entirely possible to # handle all the available matcher capabilities in the future. # There's only three supported matchers, so for now, this is all # contained to a single method. If this grows, we can expand this # out to separate methods or even objects. if self.matcher == 'path': > return self._create_path_matcher() botocore/waiter.py:211: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_path_matcher(self): > expression = jmespath.compile(self.argument) botocore/waiter.py:226: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ expression = 'component.deploymentStatus' def compile(expression): > return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = expression = 'component.deploymentStatus' def parse(self, expression): cached = self._CACHE.get(expression) if cached is not None: return cached parsed_result = self._do_parse(expression) self._CACHE[expression] = parsed_result if len(self._CACHE) > self._MAX_SIZE: > self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:91: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _free_cache_entries(self): > for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): /usr/lib/python3.11/site-packages/jmespath/parser.py:492: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok....Status', 'MonitorDeployment.Status', "status != 'CANCELLING' && status != 'CANCELLED'", 'component.deploymentStatus']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError During handling of the above exception, another exception occurred: validator = Draft4Validator(schema={'additionalProperties': False, 'properties': {'version': {'type': 'number'}, 'waiters': {'addi...', 'delay', 'maxAttempts', 'acceptors'], 'type': 'object'}, 'type': 'object'}}, 'type': 'object'}, format_checker=None) waiter_model = OrderedDict([('version', 2), ('waiters', OrderedDict([('ComponentDeleted', OrderedDict([('description', 'Wait until a ...ath'), ('argument', 'service.status'), ('state', 'failure'), ('expected', 'UPDATE_COMPLETE_CLEANUP_FAILED')])])]))]))]) client = @pytest.mark.parametrize("validator, waiter_model, client", _waiter_configs()) def test_lint_waiter_configs(validator, waiter_model, client): _validate_schema(validator, waiter_model) for waiter_name in client.waiter_names: > _lint_single_waiter(client, waiter_name, client.meta.service_model) tests/functional/test_waiter_config.py:101: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ client = waiter_name = 'component_deleted', service_model = ServiceModel(proton) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value acceptors = waiter.config.acceptors except Exception as e: > raise AssertionError(f"Could not create waiter '{waiter_name}': {e}") E AssertionError: Could not create waiter 'component_deleted': Population must be a sequence. For dicts or sets, use sorted(d). tests/functional/test_waiter_config.py:116: AssertionError _______ test_lint_waiter_configs[validator128-waiter_model128-client128] _______ client = waiter_name = 'db_cluster_available', service_model = ServiceModel(rds) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value > acceptors = waiter.config.acceptors tests/functional/test_waiter_config.py:114: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = @property def acceptors(self): acceptors = [] for acceptor_config in self._config['acceptors']: > acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = config = OrderedDict([('matcher', 'pathAll'), ('argument', 'DBClusters[].Status'), ('state', 'success'), ('expected', 'available')]) def __init__(self, config): self.state = config['state'] self.matcher = config['matcher'] self.expected = config['expected'] self.argument = config.get('argument') > self.matcher_func = self._create_matcher_func() botocore/waiter.py:178: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_matcher_func(self): # An acceptor function is a callable that takes a single value. The # parsed AWS response. Note that the parsed error response is also # provided in the case of errors, so it's entirely possible to # handle all the available matcher capabilities in the future. # There's only three supported matchers, so for now, this is all # contained to a single method. If this grows, we can expand this # out to separate methods or even objects. if self.matcher == 'path': return self._create_path_matcher() elif self.matcher == 'pathAll': > return self._create_path_all_matcher() botocore/waiter.py:213: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_path_all_matcher(self): > expression = jmespath.compile(self.argument) botocore/waiter.py:237: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ expression = 'DBClusters[].Status' def compile(expression): > return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = expression = 'DBClusters[].Status' def parse(self, expression): cached = self._CACHE.get(expression) if cached is not None: return cached parsed_result = self._do_parse(expression) self._CACHE[expression] = parsed_result if len(self._CACHE) > self._MAX_SIZE: > self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:91: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _free_cache_entries(self): > for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): /usr/lib/python3.11/site-packages/jmespath/parser.py:492: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...yment.Status', "status != 'CANCELLING' && status != 'CANCELLED'", 'component.deploymentStatus', 'DBClusters[].Status']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError During handling of the above exception, another exception occurred: validator = Draft4Validator(schema={'additionalProperties': False, 'properties': {'version': {'type': 'number'}, 'waiters': {'addi...', 'delay', 'maxAttempts', 'acceptors'], 'type': 'object'}, 'type': 'object'}}, 'type': 'object'}, format_checker=None) waiter_model = OrderedDict([('version', 2), ('waiters', OrderedDict([('DBClusterAvailable', OrderedDict([('delay', 30), ('maxAttempts...expected', 'available'), ('matcher', 'pathAll'), ('state', 'success'), ('argument', 'DBSnapshots[].Status')])])]))]))]) client = @pytest.mark.parametrize("validator, waiter_model, client", _waiter_configs()) def test_lint_waiter_configs(validator, waiter_model, client): _validate_schema(validator, waiter_model) for waiter_name in client.waiter_names: > _lint_single_waiter(client, waiter_name, client.meta.service_model) tests/functional/test_waiter_config.py:101: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ client = waiter_name = 'db_cluster_available', service_model = ServiceModel(rds) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value acceptors = waiter.config.acceptors except Exception as e: > raise AssertionError(f"Could not create waiter '{waiter_name}': {e}") E AssertionError: Could not create waiter 'db_cluster_available': Population must be a sequence. For dicts or sets, use sorted(d). tests/functional/test_waiter_config.py:116: AssertionError _______ test_lint_waiter_configs[validator129-waiter_model129-client129] _______ client = waiter_name = 'cluster_available', service_model = ServiceModel(redshift) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value > acceptors = waiter.config.acceptors tests/functional/test_waiter_config.py:114: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = @property def acceptors(self): acceptors = [] for acceptor_config in self._config['acceptors']: > acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = config = OrderedDict([('expected', 'available'), ('matcher', 'pathAll'), ('state', 'success'), ('argument', 'Clusters[].ClusterStatus')]) def __init__(self, config): self.state = config['state'] self.matcher = config['matcher'] self.expected = config['expected'] self.argument = config.get('argument') > self.matcher_func = self._create_matcher_func() botocore/waiter.py:178: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_matcher_func(self): # An acceptor function is a callable that takes a single value. The # parsed AWS response. Note that the parsed error response is also # provided in the case of errors, so it's entirely possible to # handle all the available matcher capabilities in the future. # There's only three supported matchers, so for now, this is all # contained to a single method. If this grows, we can expand this # out to separate methods or even objects. if self.matcher == 'path': return self._create_path_matcher() elif self.matcher == 'pathAll': > return self._create_path_all_matcher() botocore/waiter.py:213: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_path_all_matcher(self): > expression = jmespath.compile(self.argument) botocore/waiter.py:237: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ expression = 'Clusters[].ClusterStatus' def compile(expression): > return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = expression = 'Clusters[].ClusterStatus' def parse(self, expression): cached = self._CACHE.get(expression) if cached is not None: return cached parsed_result = self._do_parse(expression) self._CACHE[expression] = parsed_result if len(self._CACHE) > self._MAX_SIZE: > self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:91: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _free_cache_entries(self): > for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): /usr/lib/python3.11/site-packages/jmespath/parser.py:492: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...ANCELLING' && status != 'CANCELLED'", 'component.deploymentStatus', 'DBClusters[].Status', 'Clusters[].ClusterStatus']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError During handling of the above exception, another exception occurred: validator = Draft4Validator(schema={'additionalProperties': False, 'properties': {'version': {'type': 'number'}, 'waiters': {'addi...', 'delay', 'maxAttempts', 'acceptors'], 'type': 'object'}, 'type': 'object'}}, 'type': 'object'}, format_checker=None) waiter_model = OrderedDict([('version', 2), ('waiters', OrderedDict([('ClusterAvailable', OrderedDict([('delay', 60), ('operation', '...([('expected', 'deleted'), ('matcher', 'pathAny'), ('state', 'failure'), ('argument', 'Snapshots[].Status')])])]))]))]) client = @pytest.mark.parametrize("validator, waiter_model, client", _waiter_configs()) def test_lint_waiter_configs(validator, waiter_model, client): _validate_schema(validator, waiter_model) for waiter_name in client.waiter_names: > _lint_single_waiter(client, waiter_name, client.meta.service_model) tests/functional/test_waiter_config.py:101: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ client = waiter_name = 'cluster_available', service_model = ServiceModel(redshift) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value acceptors = waiter.config.acceptors except Exception as e: > raise AssertionError(f"Could not create waiter '{waiter_name}': {e}") E AssertionError: Could not create waiter 'cluster_available': Population must be a sequence. For dicts or sets, use sorted(d). tests/functional/test_waiter_config.py:116: AssertionError _______ test_lint_waiter_configs[validator130-waiter_model130-client130] _______ client = waiter_name = 'project_version_running' service_model = ServiceModel(rekognition) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value > acceptors = waiter.config.acceptors tests/functional/test_waiter_config.py:114: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = @property def acceptors(self): acceptors = [] for acceptor_config in self._config['acceptors']: > acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = config = OrderedDict([('state', 'success'), ('matcher', 'pathAll'), ('argument', 'ProjectVersionDescriptions[].Status'), ('expected', 'RUNNING')]) def __init__(self, config): self.state = config['state'] self.matcher = config['matcher'] self.expected = config['expected'] self.argument = config.get('argument') > self.matcher_func = self._create_matcher_func() botocore/waiter.py:178: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_matcher_func(self): # An acceptor function is a callable that takes a single value. The # parsed AWS response. Note that the parsed error response is also # provided in the case of errors, so it's entirely possible to # handle all the available matcher capabilities in the future. # There's only three supported matchers, so for now, this is all # contained to a single method. If this grows, we can expand this # out to separate methods or even objects. if self.matcher == 'path': return self._create_path_matcher() elif self.matcher == 'pathAll': > return self._create_path_all_matcher() botocore/waiter.py:213: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_path_all_matcher(self): > expression = jmespath.compile(self.argument) botocore/waiter.py:237: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ expression = 'ProjectVersionDescriptions[].Status' def compile(expression): > return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = expression = 'ProjectVersionDescriptions[].Status' def parse(self, expression): cached = self._CACHE.get(expression) if cached is not None: return cached parsed_result = self._do_parse(expression) self._CACHE[expression] = parsed_result if len(self._CACHE) > self._MAX_SIZE: > self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:91: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _free_cache_entries(self): > for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): /usr/lib/python3.11/site-packages/jmespath/parser.py:492: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...component.deploymentStatus', 'DBClusters[].Status', 'Clusters[].ClusterStatus', 'ProjectVersionDescriptions[].Status']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError During handling of the above exception, another exception occurred: validator = Draft4Validator(schema={'additionalProperties': False, 'properties': {'version': {'type': 'number'}, 'waiters': {'addi...', 'delay', 'maxAttempts', 'acceptors'], 'type': 'object'}, 'type': 'object'}}, 'type': 'object'}, format_checker=None) waiter_model = OrderedDict([('version', 2), ('waiters', OrderedDict([('ProjectVersionTrainingCompleted', OrderedDict([('description',...lure'), ('matcher', 'pathAny'), ('argument', 'ProjectVersionDescriptions[].Status'), ('expected', 'FAILED')])])]))]))]) client = @pytest.mark.parametrize("validator, waiter_model, client", _waiter_configs()) def test_lint_waiter_configs(validator, waiter_model, client): _validate_schema(validator, waiter_model) for waiter_name in client.waiter_names: > _lint_single_waiter(client, waiter_name, client.meta.service_model) tests/functional/test_waiter_config.py:101: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ client = waiter_name = 'project_version_running' service_model = ServiceModel(rekognition) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value acceptors = waiter.config.acceptors except Exception as e: > raise AssertionError(f"Could not create waiter '{waiter_name}': {e}") E AssertionError: Could not create waiter 'project_version_running': Population must be a sequence. For dicts or sets, use sorted(d). tests/functional/test_waiter_config.py:116: AssertionError _______ test_lint_waiter_configs[validator131-waiter_model131-client131] _______ client = waiter_name = 'channel_created', service_model = ServiceModel(repostspace) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value > acceptors = waiter.config.acceptors tests/functional/test_waiter_config.py:114: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = @property def acceptors(self): acceptors = [] for acceptor_config in self._config['acceptors']: > acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = config = OrderedDict([('matcher', 'path'), ('argument', 'channelStatus'), ('state', 'success'), ('expected', 'CREATED')]) def __init__(self, config): self.state = config['state'] self.matcher = config['matcher'] self.expected = config['expected'] self.argument = config.get('argument') > self.matcher_func = self._create_matcher_func() botocore/waiter.py:178: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_matcher_func(self): # An acceptor function is a callable that takes a single value. The # parsed AWS response. Note that the parsed error response is also # provided in the case of errors, so it's entirely possible to # handle all the available matcher capabilities in the future. # There's only three supported matchers, so for now, this is all # contained to a single method. If this grows, we can expand this # out to separate methods or even objects. if self.matcher == 'path': > return self._create_path_matcher() botocore/waiter.py:211: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_path_matcher(self): > expression = jmespath.compile(self.argument) botocore/waiter.py:226: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ expression = 'channelStatus' def compile(expression): > return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = expression = 'channelStatus' def parse(self, expression): cached = self._CACHE.get(expression) if cached is not None: return cached parsed_result = self._do_parse(expression) self._CACHE[expression] = parsed_result if len(self._CACHE) > self._MAX_SIZE: > self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:91: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _free_cache_entries(self): > for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): /usr/lib/python3.11/site-packages/jmespath/parser.py:492: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...entStatus', 'DBClusters[].Status', 'Clusters[].ClusterStatus', 'ProjectVersionDescriptions[].Status', 'channelStatus']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError During handling of the above exception, another exception occurred: validator = Draft4Validator(schema={'additionalProperties': False, 'properties': {'version': {'type': 'number'}, 'waiters': {'addi...', 'delay', 'maxAttempts', 'acceptors'], 'type': 'object'}, 'type': 'object'}}, 'type': 'object'}, format_checker=None) waiter_model = OrderedDict([('version', 2), ('waiters', OrderedDict([('ChannelCreated', OrderedDict([('delay', 2), ('maxAttempts', 60...)]), OrderedDict([('matcher', 'path'), ('argument', 'status'), ('state', 'retry'), ('expected', 'DELETING')])])]))]))]) client = @pytest.mark.parametrize("validator, waiter_model, client", _waiter_configs()) def test_lint_waiter_configs(validator, waiter_model, client): _validate_schema(validator, waiter_model) for waiter_name in client.waiter_names: > _lint_single_waiter(client, waiter_name, client.meta.service_model) tests/functional/test_waiter_config.py:101: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ client = waiter_name = 'channel_created', service_model = ServiceModel(repostspace) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value acceptors = waiter.config.acceptors except Exception as e: > raise AssertionError(f"Could not create waiter '{waiter_name}': {e}") E AssertionError: Could not create waiter 'channel_created': Population must be a sequence. For dicts or sets, use sorted(d). tests/functional/test_waiter_config.py:116: AssertionError _______ test_lint_waiter_configs[validator134-waiter_model134-client134] _______ client = waiter_name = 'resource_record_sets_changed' service_model = ServiceModel(route53) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value > acceptors = waiter.config.acceptors tests/functional/test_waiter_config.py:114: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = @property def acceptors(self): acceptors = [] for acceptor_config in self._config['acceptors']: > acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = config = OrderedDict([('matcher', 'path'), ('expected', 'INSYNC'), ('argument', 'ChangeInfo.Status'), ('state', 'success')]) def __init__(self, config): self.state = config['state'] self.matcher = config['matcher'] self.expected = config['expected'] self.argument = config.get('argument') > self.matcher_func = self._create_matcher_func() botocore/waiter.py:178: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_matcher_func(self): # An acceptor function is a callable that takes a single value. The # parsed AWS response. Note that the parsed error response is also # provided in the case of errors, so it's entirely possible to # handle all the available matcher capabilities in the future. # There's only three supported matchers, so for now, this is all # contained to a single method. If this grows, we can expand this # out to separate methods or even objects. if self.matcher == 'path': > return self._create_path_matcher() botocore/waiter.py:211: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_path_matcher(self): > expression = jmespath.compile(self.argument) botocore/waiter.py:226: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ expression = 'ChangeInfo.Status' def compile(expression): > return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = expression = 'ChangeInfo.Status' def parse(self, expression): cached = self._CACHE.get(expression) if cached is not None: return cached parsed_result = self._do_parse(expression) self._CACHE[expression] = parsed_result if len(self._CACHE) > self._MAX_SIZE: > self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:91: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _free_cache_entries(self): > for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): /usr/lib/python3.11/site-packages/jmespath/parser.py:492: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...rs[].Status', 'Clusters[].ClusterStatus', 'ProjectVersionDescriptions[].Status', 'channelStatus', 'ChangeInfo.Status']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError During handling of the above exception, another exception occurred: validator = Draft4Validator(schema={'additionalProperties': False, 'properties': {'version': {'type': 'number'}, 'waiters': {'addi...', 'delay', 'maxAttempts', 'acceptors'], 'type': 'object'}, 'type': 'object'}}, 'type': 'object'}, format_checker=None) waiter_model = OrderedDict([('version', 2), ('waiters', OrderedDict([('ResourceRecordSetsChanged', OrderedDict([('delay', 30), ('maxA...dDict([('matcher', 'path'), ('expected', 'INSYNC'), ('argument', 'ChangeInfo.Status'), ('state', 'success')])])]))]))]) client = @pytest.mark.parametrize("validator, waiter_model, client", _waiter_configs()) def test_lint_waiter_configs(validator, waiter_model, client): _validate_schema(validator, waiter_model) for waiter_name in client.waiter_names: > _lint_single_waiter(client, waiter_name, client.meta.service_model) tests/functional/test_waiter_config.py:101: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ client = waiter_name = 'resource_record_sets_changed' service_model = ServiceModel(route53) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value acceptors = waiter.config.acceptors except Exception as e: > raise AssertionError(f"Could not create waiter '{waiter_name}': {e}") E AssertionError: Could not create waiter 'resource_record_sets_changed': Population must be a sequence. For dicts or sets, use sorted(d). tests/functional/test_waiter_config.py:116: AssertionError _______ test_lint_waiter_configs[validator135-waiter_model135-client135] _______ client = waiter_name = 'cluster_created' service_model = ServiceModel(route53-recovery-control-config) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value > acceptors = waiter.config.acceptors tests/functional/test_waiter_config.py:114: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = @property def acceptors(self): acceptors = [] for acceptor_config in self._config['acceptors']: > acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = config = OrderedDict([('state', 'success'), ('matcher', 'path'), ('argument', 'Cluster.Status'), ('expected', 'DEPLOYED')]) def __init__(self, config): self.state = config['state'] self.matcher = config['matcher'] self.expected = config['expected'] self.argument = config.get('argument') > self.matcher_func = self._create_matcher_func() botocore/waiter.py:178: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_matcher_func(self): # An acceptor function is a callable that takes a single value. The # parsed AWS response. Note that the parsed error response is also # provided in the case of errors, so it's entirely possible to # handle all the available matcher capabilities in the future. # There's only three supported matchers, so for now, this is all # contained to a single method. If this grows, we can expand this # out to separate methods or even objects. if self.matcher == 'path': > return self._create_path_matcher() botocore/waiter.py:211: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_path_matcher(self): > expression = jmespath.compile(self.argument) botocore/waiter.py:226: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ expression = 'Cluster.Status' def compile(expression): > return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = expression = 'Cluster.Status' def parse(self, expression): cached = self._CACHE.get(expression) if cached is not None: return cached parsed_result = self._do_parse(expression) self._CACHE[expression] = parsed_result if len(self._CACHE) > self._MAX_SIZE: > self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:91: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _free_cache_entries(self): > for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): /usr/lib/python3.11/site-packages/jmespath/parser.py:492: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...sters[].ClusterStatus', 'ProjectVersionDescriptions[].Status', 'channelStatus', 'ChangeInfo.Status', 'Cluster.Status']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError During handling of the above exception, another exception occurred: validator = Draft4Validator(schema={'additionalProperties': False, 'properties': {'version': {'type': 'number'}, 'waiters': {'addi...', 'delay', 'maxAttempts', 'acceptors'], 'type': 'object'}, 'type': 'object'}}, 'type': 'object'}, format_checker=None) waiter_model = OrderedDict([('version', 2), ('waiters', OrderedDict([('ClusterCreated', OrderedDict([('description', 'Wait until a cl...expected', 'PENDING_DELETION')]), OrderedDict([('state', 'retry'), ('matcher', 'status'), ('expected', 500)])])]))]))]) client = @pytest.mark.parametrize("validator, waiter_model, client", _waiter_configs()) def test_lint_waiter_configs(validator, waiter_model, client): _validate_schema(validator, waiter_model) for waiter_name in client.waiter_names: > _lint_single_waiter(client, waiter_name, client.meta.service_model) tests/functional/test_waiter_config.py:101: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ client = waiter_name = 'cluster_created' service_model = ServiceModel(route53-recovery-control-config) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value acceptors = waiter.config.acceptors except Exception as e: > raise AssertionError(f"Could not create waiter '{waiter_name}': {e}") E AssertionError: Could not create waiter 'cluster_created': Population must be a sequence. For dicts or sets, use sorted(d). tests/functional/test_waiter_config.py:116: AssertionError _______ test_lint_waiter_configs[validator143-waiter_model143-client143] _______ client = waiter_name = 'endpoint_deleted', service_model = ServiceModel(sagemaker) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value > acceptors = waiter.config.acceptors tests/functional/test_waiter_config.py:114: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = @property def acceptors(self): acceptors = [] for acceptor_config in self._config['acceptors']: > acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = config = OrderedDict([('matcher', 'path'), ('argument', 'EndpointStatus'), ('state', 'failure'), ('expected', 'Failed')]) def __init__(self, config): self.state = config['state'] self.matcher = config['matcher'] self.expected = config['expected'] self.argument = config.get('argument') > self.matcher_func = self._create_matcher_func() botocore/waiter.py:178: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_matcher_func(self): # An acceptor function is a callable that takes a single value. The # parsed AWS response. Note that the parsed error response is also # provided in the case of errors, so it's entirely possible to # handle all the available matcher capabilities in the future. # There's only three supported matchers, so for now, this is all # contained to a single method. If this grows, we can expand this # out to separate methods or even objects. if self.matcher == 'path': > return self._create_path_matcher() botocore/waiter.py:211: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_path_matcher(self): > expression = jmespath.compile(self.argument) botocore/waiter.py:226: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ expression = 'EndpointStatus' def compile(expression): > return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = expression = 'EndpointStatus' def parse(self, expression): cached = self._CACHE.get(expression) if cached is not None: return cached parsed_result = self._do_parse(expression) self._CACHE[expression] = parsed_result if len(self._CACHE) > self._MAX_SIZE: > self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:91: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _free_cache_entries(self): > for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): /usr/lib/python3.11/site-packages/jmespath/parser.py:492: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...tus', 'ProjectVersionDescriptions[].Status', 'channelStatus', 'ChangeInfo.Status', 'Cluster.Status', 'EndpointStatus']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError During handling of the above exception, another exception occurred: validator = Draft4Validator(schema={'additionalProperties': False, 'properties': {'version': {'type': 'number'}, 'waiters': {'addi...', 'delay', 'maxAttempts', 'acceptors'], 'type': 'object'}, 'type': 'object'}}, 'type': 'object'}, format_checker=None) waiter_model = OrderedDict([('version', 2), ('waiters', OrderedDict([('EndpointDeleted', OrderedDict([('delay', 30), ('maxAttempts', ..., 'Failed')]), OrderedDict([('matcher', 'error'), ('state', 'failure'), ('expected', 'ValidationException')])])]))]))]) client = @pytest.mark.parametrize("validator, waiter_model, client", _waiter_configs()) def test_lint_waiter_configs(validator, waiter_model, client): _validate_schema(validator, waiter_model) for waiter_name in client.waiter_names: > _lint_single_waiter(client, waiter_name, client.meta.service_model) tests/functional/test_waiter_config.py:101: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ client = waiter_name = 'endpoint_deleted', service_model = ServiceModel(sagemaker) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value acceptors = waiter.config.acceptors except Exception as e: > raise AssertionError(f"Could not create waiter '{waiter_name}': {e}") E AssertionError: Could not create waiter 'endpoint_deleted': Population must be a sequence. For dicts or sets, use sorted(d). tests/functional/test_waiter_config.py:116: AssertionError _______ test_lint_waiter_configs[validator147-waiter_model147-client147] _______ client = waiter_name = 'identity_exists', service_model = ServiceModel(ses) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value > acceptors = waiter.config.acceptors tests/functional/test_waiter_config.py:114: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = @property def acceptors(self): acceptors = [] for acceptor_config in self._config['acceptors']: > acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = config = OrderedDict([('expected', 'Success'), ('matcher', 'pathAll'), ('state', 'success'), ('argument', 'VerificationAttributes.*.VerificationStatus')]) def __init__(self, config): self.state = config['state'] self.matcher = config['matcher'] self.expected = config['expected'] self.argument = config.get('argument') > self.matcher_func = self._create_matcher_func() botocore/waiter.py:178: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_matcher_func(self): # An acceptor function is a callable that takes a single value. The # parsed AWS response. Note that the parsed error response is also # provided in the case of errors, so it's entirely possible to # handle all the available matcher capabilities in the future. # There's only three supported matchers, so for now, this is all # contained to a single method. If this grows, we can expand this # out to separate methods or even objects. if self.matcher == 'path': return self._create_path_matcher() elif self.matcher == 'pathAll': > return self._create_path_all_matcher() botocore/waiter.py:213: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_path_all_matcher(self): > expression = jmespath.compile(self.argument) botocore/waiter.py:237: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ expression = 'VerificationAttributes.*.VerificationStatus' def compile(expression): > return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = expression = 'VerificationAttributes.*.VerificationStatus' def parse(self, expression): cached = self._CACHE.get(expression) if cached is not None: return cached parsed_result = self._do_parse(expression) self._CACHE[expression] = parsed_result if len(self._CACHE) > self._MAX_SIZE: > self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:91: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _free_cache_entries(self): > for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): /usr/lib/python3.11/site-packages/jmespath/parser.py:492: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...hannelStatus', 'ChangeInfo.Status', 'Cluster.Status', 'EndpointStatus', 'VerificationAttributes.*.VerificationStatus']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError During handling of the above exception, another exception occurred: validator = Draft4Validator(schema={'additionalProperties': False, 'properties': {'version': {'type': 'number'}, 'waiters': {'addi...', 'delay', 'maxAttempts', 'acceptors'], 'type': 'object'}, 'type': 'object'}}, 'type': 'object'}, format_checker=None) waiter_model = OrderedDict([('version', 2), ('waiters', OrderedDict([('IdentityExists', OrderedDict([('delay', 3), ('operation', 'Get..., ('matcher', 'pathAll'), ('state', 'success'), ('argument', 'VerificationAttributes.*.VerificationStatus')])])]))]))]) client = @pytest.mark.parametrize("validator, waiter_model, client", _waiter_configs()) def test_lint_waiter_configs(validator, waiter_model, client): _validate_schema(validator, waiter_model) for waiter_name in client.waiter_names: > _lint_single_waiter(client, waiter_name, client.meta.service_model) tests/functional/test_waiter_config.py:101: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ client = waiter_name = 'identity_exists', service_model = ServiceModel(ses) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value acceptors = waiter.config.acceptors except Exception as e: > raise AssertionError(f"Could not create waiter '{waiter_name}': {e}") E AssertionError: Could not create waiter 'identity_exists': Population must be a sequence. For dicts or sets, use sorted(d). tests/functional/test_waiter_config.py:116: AssertionError _______ test_lint_waiter_configs[validator150-waiter_model150-client150] _______ client = waiter_name = 'export_succeeded', service_model = ServiceModel(simpledbv2) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value > acceptors = waiter.config.acceptors tests/functional/test_waiter_config.py:114: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = @property def acceptors(self): acceptors = [] for acceptor_config in self._config['acceptors']: > acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = config = OrderedDict([('matcher', 'path'), ('argument', 'exportStatus'), ('state', 'success'), ('expected', 'SUCCEEDED')]) def __init__(self, config): self.state = config['state'] self.matcher = config['matcher'] self.expected = config['expected'] self.argument = config.get('argument') > self.matcher_func = self._create_matcher_func() botocore/waiter.py:178: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_matcher_func(self): # An acceptor function is a callable that takes a single value. The # parsed AWS response. Note that the parsed error response is also # provided in the case of errors, so it's entirely possible to # handle all the available matcher capabilities in the future. # There's only three supported matchers, so for now, this is all # contained to a single method. If this grows, we can expand this # out to separate methods or even objects. if self.matcher == 'path': > return self._create_path_matcher() botocore/waiter.py:211: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_path_matcher(self): > expression = jmespath.compile(self.argument) botocore/waiter.py:226: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ expression = 'exportStatus' def compile(expression): > return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = expression = 'exportStatus' def parse(self, expression): cached = self._CACHE.get(expression) if cached is not None: return cached parsed_result = self._do_parse(expression) self._CACHE[expression] = parsed_result if len(self._CACHE) > self._MAX_SIZE: > self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:91: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _free_cache_entries(self): > for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): /usr/lib/python3.11/site-packages/jmespath/parser.py:492: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...ChangeInfo.Status', 'Cluster.Status', 'EndpointStatus', 'VerificationAttributes.*.VerificationStatus', 'exportStatus']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError During handling of the above exception, another exception occurred: validator = Draft4Validator(schema={'additionalProperties': False, 'properties': {'version': {'type': 'number'}, 'waiters': {'addi...', 'delay', 'maxAttempts', 'acceptors'], 'type': 'object'}, 'type': 'object'}}, 'type': 'object'}, format_checker=None) waiter_model = OrderedDict([('version', 2), ('waiters', OrderedDict([('ExportSucceeded', OrderedDict([('delay', 30), ('maxAttempts', ...rderedDict([('matcher', 'path'), ('argument', 'exportStatus'), ('state', 'failure'), ('expected', 'FAILED')])])]))]))]) client = @pytest.mark.parametrize("validator, waiter_model, client", _waiter_configs()) def test_lint_waiter_configs(validator, waiter_model, client): _validate_schema(validator, waiter_model) for waiter_name in client.waiter_names: > _lint_single_waiter(client, waiter_name, client.meta.service_model) tests/functional/test_waiter_config.py:101: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ client = waiter_name = 'export_succeeded', service_model = ServiceModel(simpledbv2) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value acceptors = waiter.config.acceptors except Exception as e: > raise AssertionError(f"Could not create waiter '{waiter_name}': {e}") E AssertionError: Could not create waiter 'export_succeeded': Population must be a sequence. For dicts or sets, use sorted(d). tests/functional/test_waiter_config.py:116: AssertionError _______ test_lint_waiter_configs[validator152-waiter_model152-client152] _______ client = waiter_name = 'wait_for_replication_set_active' service_model = ServiceModel(ssm-incidents) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value > acceptors = waiter.config.acceptors tests/functional/test_waiter_config.py:114: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = @property def acceptors(self): acceptors = [] for acceptor_config in self._config['acceptors']: > acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = config = OrderedDict([('matcher', 'path'), ('argument', 'replicationSet.status'), ('state', 'success'), ('expected', 'ACTIVE')]) def __init__(self, config): self.state = config['state'] self.matcher = config['matcher'] self.expected = config['expected'] self.argument = config.get('argument') > self.matcher_func = self._create_matcher_func() botocore/waiter.py:178: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_matcher_func(self): # An acceptor function is a callable that takes a single value. The # parsed AWS response. Note that the parsed error response is also # provided in the case of errors, so it's entirely possible to # handle all the available matcher capabilities in the future. # There's only three supported matchers, so for now, this is all # contained to a single method. If this grows, we can expand this # out to separate methods or even objects. if self.matcher == 'path': > return self._create_path_matcher() botocore/waiter.py:211: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_path_matcher(self): > expression = jmespath.compile(self.argument) botocore/waiter.py:226: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ expression = 'replicationSet.status' def compile(expression): > return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = expression = 'replicationSet.status' def parse(self, expression): cached = self._CACHE.get(expression) if cached is not None: return cached parsed_result = self._do_parse(expression) self._CACHE[expression] = parsed_result if len(self._CACHE) > self._MAX_SIZE: > self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:91: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _free_cache_entries(self): > for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): /usr/lib/python3.11/site-packages/jmespath/parser.py:492: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...ter.Status', 'EndpointStatus', 'VerificationAttributes.*.VerificationStatus', 'exportStatus', 'replicationSet.status']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError During handling of the above exception, another exception occurred: validator = Draft4Validator(schema={'additionalProperties': False, 'properties': {'version': {'type': 'number'}, 'waiters': {'addi...', 'delay', 'maxAttempts', 'acceptors'], 'type': 'object'}, 'type': 'object'}}, 'type': 'object'}, format_checker=None) waiter_model = OrderedDict([('version', 2), ('waiters', OrderedDict([('WaitForReplicationSetActive', OrderedDict([('description', 'Wa...t([('matcher', 'path'), ('argument', 'replicationSet.status'), ('state', 'failure'), ('expected', 'FAILED')])])]))]))]) client = @pytest.mark.parametrize("validator, waiter_model, client", _waiter_configs()) def test_lint_waiter_configs(validator, waiter_model, client): _validate_schema(validator, waiter_model) for waiter_name in client.waiter_names: > _lint_single_waiter(client, waiter_name, client.meta.service_model) tests/functional/test_waiter_config.py:101: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ client = waiter_name = 'wait_for_replication_set_active' service_model = ServiceModel(ssm-incidents) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value acceptors = waiter.config.acceptors except Exception as e: > raise AssertionError(f"Could not create waiter '{waiter_name}': {e}") E AssertionError: Could not create waiter 'wait_for_replication_set_active': Population must be a sequence. For dicts or sets, use sorted(d). tests/functional/test_waiter_config.py:116: AssertionError _______ test_lint_waiter_configs[validator154-waiter_model154-client154] _______ client = waiter_name = 'call_analytics_job_completed' service_model = ServiceModel(transcribe) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value > acceptors = waiter.config.acceptors tests/functional/test_waiter_config.py:114: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = @property def acceptors(self): acceptors = [] for acceptor_config in self._config['acceptors']: > acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = config = OrderedDict([('state', 'success'), ('matcher', 'path'), ('argument', 'CallAnalyticsJob.CallAnalyticsJobStatus'), ('expected', 'COMPLETED')]) def __init__(self, config): self.state = config['state'] self.matcher = config['matcher'] self.expected = config['expected'] self.argument = config.get('argument') > self.matcher_func = self._create_matcher_func() botocore/waiter.py:178: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_matcher_func(self): # An acceptor function is a callable that takes a single value. The # parsed AWS response. Note that the parsed error response is also # provided in the case of errors, so it's entirely possible to # handle all the available matcher capabilities in the future. # There's only three supported matchers, so for now, this is all # contained to a single method. If this grows, we can expand this # out to separate methods or even objects. if self.matcher == 'path': > return self._create_path_matcher() botocore/waiter.py:211: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_path_matcher(self): > expression = jmespath.compile(self.argument) botocore/waiter.py:226: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ expression = 'CallAnalyticsJob.CallAnalyticsJobStatus' def compile(expression): > return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = expression = 'CallAnalyticsJob.CallAnalyticsJobStatus' def parse(self, expression): cached = self._CACHE.get(expression) if cached is not None: return cached parsed_result = self._do_parse(expression) self._CACHE[expression] = parsed_result if len(self._CACHE) > self._MAX_SIZE: > self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:91: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _free_cache_entries(self): > for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): /usr/lib/python3.11/site-packages/jmespath/parser.py:492: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...nAttributes.*.VerificationStatus', 'exportStatus', 'replicationSet.status', 'CallAnalyticsJob.CallAnalyticsJobStatus']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError During handling of the above exception, another exception occurred: validator = Draft4Validator(schema={'additionalProperties': False, 'properties': {'version': {'type': 'number'}, 'waiters': {'addi...', 'delay', 'maxAttempts', 'acceptors'], 'type': 'object'}, 'type': 'object'}}, 'type': 'object'}, format_checker=None) waiter_model = OrderedDict([('version', 2), ('waiters', OrderedDict([('CallAnalyticsJobCompleted', OrderedDict([('operation', 'GetCal...redDict([('state', 'failure'), ('matcher', 'path'), ('argument', 'VocabularyState'), ('expected', 'FAILED')])])]))]))]) client = @pytest.mark.parametrize("validator, waiter_model, client", _waiter_configs()) def test_lint_waiter_configs(validator, waiter_model, client): _validate_schema(validator, waiter_model) for waiter_name in client.waiter_names: > _lint_single_waiter(client, waiter_name, client.meta.service_model) tests/functional/test_waiter_config.py:101: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ client = waiter_name = 'call_analytics_job_completed' service_model = ServiceModel(transcribe) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value acceptors = waiter.config.acceptors except Exception as e: > raise AssertionError(f"Could not create waiter '{waiter_name}': {e}") E AssertionError: Could not create waiter 'call_analytics_job_completed': Population must be a sequence. For dicts or sets, use sorted(d). tests/functional/test_waiter_config.py:116: AssertionError _______ test_lint_waiter_configs[validator155-waiter_model155-client155] _______ client = waiter_name = 'server_offline', service_model = ServiceModel(transfer) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value > acceptors = waiter.config.acceptors tests/functional/test_waiter_config.py:114: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = @property def acceptors(self): acceptors = [] for acceptor_config in self._config['acceptors']: > acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:167: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = config = OrderedDict([('matcher', 'path'), ('argument', 'Server.State'), ('state', 'success'), ('expected', 'OFFLINE')]) def __init__(self, config): self.state = config['state'] self.matcher = config['matcher'] self.expected = config['expected'] self.argument = config.get('argument') > self.matcher_func = self._create_matcher_func() botocore/waiter.py:178: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_matcher_func(self): # An acceptor function is a callable that takes a single value. The # parsed AWS response. Note that the parsed error response is also # provided in the case of errors, so it's entirely possible to # handle all the available matcher capabilities in the future. # There's only three supported matchers, so for now, this is all # contained to a single method. If this grows, we can expand this # out to separate methods or even objects. if self.matcher == 'path': > return self._create_path_matcher() botocore/waiter.py:211: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _create_path_matcher(self): > expression = jmespath.compile(self.argument) botocore/waiter.py:226: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ expression = 'Server.State' def compile(expression): > return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = expression = 'Server.State' def parse(self, expression): cached = self._CACHE.get(expression) if cached is not None: return cached parsed_result = self._do_parse(expression) self._CACHE[expression] = parsed_result if len(self._CACHE) > self._MAX_SIZE: > self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:91: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def _free_cache_entries(self): > for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): /usr/lib/python3.11/site-packages/jmespath/parser.py:492: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...rificationStatus', 'exportStatus', 'replicationSet.status', 'CallAnalyticsJob.CallAnalyticsJobStatus', 'Server.State']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError During handling of the above exception, another exception occurred: validator = Draft4Validator(schema={'additionalProperties': False, 'properties': {'version': {'type': 'number'}, 'waiters': {'addi...', 'delay', 'maxAttempts', 'acceptors'], 'type': 'object'}, 'type': 'object'}}, 'type': 'object'}, format_checker=None) waiter_model = OrderedDict([('version', 2), ('waiters', OrderedDict([('ServerOffline', OrderedDict([('delay', 30), ('maxAttempts', 12...Dict([('matcher', 'path'), ('argument', 'Server.State'), ('state', 'failure'), ('expected', 'START_FAILED')])])]))]))]) client = @pytest.mark.parametrize("validator, waiter_model, client", _waiter_configs()) def test_lint_waiter_configs(validator, waiter_model, client): _validate_schema(validator, waiter_model) for waiter_name in client.waiter_names: > _lint_single_waiter(client, waiter_name, client.meta.service_model) tests/functional/test_waiter_config.py:101: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ client = waiter_name = 'server_offline', service_model = ServiceModel(transfer) def _lint_single_waiter(client, waiter_name, service_model): try: waiter = client.get_waiter(waiter_name) # The 'acceptors' property is dynamic and will create # the acceptor configs when first accessed. This is still # considered a failure to construct the waiter which is # why it's in this try/except block. # This catches things like: # * jmespath expression compiles # * matcher has a known value acceptors = waiter.config.acceptors except Exception as e: > raise AssertionError(f"Could not create waiter '{waiter_name}': {e}") E AssertionError: Could not create waiter 'server_offline': Population must be a sequence. For dicts or sets, use sorted(d). tests/functional/test_waiter_config.py:116: AssertionError ________ TestAutoGeneratedClient.test_paginator_class_name_from_client _________ self = def test_paginator_class_name_from_client(self): pagination_config = { 'pagination': { 'TestOperation': { "input_token": "Marker", "output_token": "Marker", "more_results": "IsTruncated", "limit_key": "MaxItems", "result_key": "Users", } } } self.loader.load_service_model.side_effect = [ self.service_description, self.endpoint_ruleset, pagination_config, ] creator = self.create_client_creator() service_client = creator.create_client('myservice', 'us-west-2') > paginator = service_client.get_paginator('test_operation') tests/unit/test_client.py:1191: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ botocore/client.py:1272: in get_paginator paginator = documented_paginator_cls( botocore/paginate.py:612: in __init__ self._result_keys = self._get_result_keys(self._pagination_cfg) botocore/paginate.py:650: in _get_result_keys result_key = [jmespath.compile(rk) for rk in result_key] botocore/paginate.py:650: in result_key = [jmespath.compile(rk) for rk in result_key] /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: in compile return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/parser.py:91: in parse self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:492: in _free_cache_entries for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...nStatus', 'exportStatus', 'replicationSet.status', 'CallAnalyticsJob.CallAnalyticsJobStatus', 'Server.State', 'Users']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError ____________ TestPagination.test_any_passed_in_args_are_unmodified _____________ self = def setUp(self): self.method = mock.Mock() self.model = mock.Mock() self.paginate_config = { 'output_token': 'NextToken', 'input_token': 'NextToken', 'result_key': 'Foo', } > self.paginator = Paginator( self.method, self.paginate_config, self.model ) tests/unit/test_paginate.py:107: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ botocore/paginate.py:612: in __init__ self._result_keys = self._get_result_keys(self._pagination_cfg) botocore/paginate.py:650: in _get_result_keys result_key = [jmespath.compile(rk) for rk in result_key] botocore/paginate.py:650: in result_key = [jmespath.compile(rk) for rk in result_key] /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: in compile return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/parser.py:91: in parse self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:492: in _free_cache_entries for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...', 'exportStatus', 'replicationSet.status', 'CallAnalyticsJob.CallAnalyticsJobStatus', 'Server.State', 'Users', 'Foo']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError ______________ TestPagination.test_more_tokens_is_path_expression ______________ self = def test_more_tokens_is_path_expression(self): self.paginate_config = { 'more_results': 'Foo.IsTruncated', 'output_token': 'NextToken', 'input_token': 'NextToken', 'result_key': 'Bar', } > self.paginator = Paginator( self.method, self.paginate_config, self.model ) tests/unit/test_paginate.py:259: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ botocore/paginate.py:608: in __init__ self._more_results = self._get_more_results_token(self._pagination_cfg) botocore/paginate.py:643: in _get_more_results_token return jmespath.compile(more_results) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: in compile return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/parser.py:91: in parse self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:492: in _free_cache_entries for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...'replicationSet.status', 'CallAnalyticsJob.CallAnalyticsJobStatus', 'Server.State', 'Users', 'Foo', 'Foo.IsTruncated']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError ______________ TestPagination.test_next_token_with_or_expression _______________ self = def test_next_token_with_or_expression(self): self.pagination_config = { 'output_token': 'NextToken || NextToken2', 'input_token': 'NextToken', 'result_key': 'Foo', } > self.paginator = Paginator( self.method, self.pagination_config, self.model ) tests/unit/test_paginate.py:197: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ botocore/paginate.py:606: in __init__ self._output_token = self._get_output_tokens(self._pagination_cfg) botocore/paginate.py:631: in _get_output_tokens output.append(jmespath.compile(config)) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: in compile return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/parser.py:91: in parse self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:492: in _free_cache_entries for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...allAnalyticsJob.CallAnalyticsJobStatus', 'Server.State', 'Users', 'Foo', 'Foo.IsTruncated', 'NextToken || NextToken2']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError ___________________ TestPaginatorPageSize.test_no_page_size ____________________ self = def setUp(self): self.method = mock.Mock() self.model = mock.Mock() self.paginate_config = { "output_token": "Marker", "input_token": "Marker", "result_key": ["Users", "Groups"], 'limit_key': 'MaxKeys', } > self.paginator = Paginator( self.method, self.paginate_config, self.model ) tests/unit/test_paginate.py:390: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ botocore/paginate.py:612: in __init__ self._result_keys = self._get_result_keys(self._pagination_cfg) botocore/paginate.py:650: in _get_result_keys result_key = [jmespath.compile(rk) for rk in result_key] botocore/paginate.py:650: in result_key = [jmespath.compile(rk) for rk in result_key] /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: in compile return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/parser.py:91: in parse self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:492: in _free_cache_entries for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...csJob.CallAnalyticsJobStatus', 'Server.State', 'Users', 'Foo', 'Foo.IsTruncated', 'NextToken || NextToken2', 'Groups']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError _________ TestPaginatorWithPathExpressions.test_s3_list_object_complex _________ self = def setUp(self): self.method = mock.Mock() self.model = mock.Mock() # This is something we'd see in s3 pagination. self.paginate_config = { 'output_token': [ 'NextMarker || ListBucketResult.Contents[-1].Key' ], 'input_token': 'next_marker', 'result_key': 'Contents', } > self.paginator = Paginator( self.method, self.paginate_config, self.model ) tests/unit/test_paginate.py:441: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ botocore/paginate.py:606: in __init__ self._output_token = self._get_output_tokens(self._pagination_cfg) botocore/paginate.py:631: in _get_output_tokens output.append(jmespath.compile(config)) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: in compile return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/parser.py:91: in parse self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:492: in _free_cache_entries for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...rs', 'Foo', 'Foo.IsTruncated', 'NextToken || NextToken2', 'Groups', 'NextMarker || ListBucketResult.Contents[-1].Key']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError ____________ TestPaginatorWithPathExpressions.test_s3_list_objects _____________ self = def setUp(self): self.method = mock.Mock() self.model = mock.Mock() # This is something we'd see in s3 pagination. self.paginate_config = { 'output_token': [ 'NextMarker || ListBucketResult.Contents[-1].Key' ], 'input_token': 'next_marker', 'result_key': 'Contents', } > self.paginator = Paginator( self.method, self.paginate_config, self.model ) tests/unit/test_paginate.py:441: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ botocore/paginate.py:612: in __init__ self._result_keys = self._get_result_keys(self._pagination_cfg) botocore/paginate.py:650: in _get_result_keys result_key = [jmespath.compile(rk) for rk in result_key] botocore/paginate.py:650: in result_key = [jmespath.compile(rk) for rk in result_key] /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: in compile return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/parser.py:91: in parse self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:492: in _free_cache_entries for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...'Foo.IsTruncated', 'NextToken || NextToken2', 'Groups', 'NextMarker || ListBucketResult.Contents[-1].Key', 'Contents']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError ______________ TestMultipleTokens.test_s3_list_multipart_uploads _______________ self = def setUp(self): self.method = mock.Mock() self.model = mock.Mock() # This is something we'd see in s3 pagination. self.paginate_config = { "output_token": [ "ListBucketResults.NextKeyMarker", "ListBucketResults.NextUploadIdMarker", ], "input_token": ["key_marker", "upload_id_marker"], "result_key": 'Foo', } > self.paginator = Paginator( self.method, self.paginate_config, self.model ) tests/unit/test_paginate.py:684: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ botocore/paginate.py:606: in __init__ self._output_token = self._get_output_tokens(self._pagination_cfg) botocore/paginate.py:631: in _get_output_tokens output.append(jmespath.compile(config)) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: in compile return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/parser.py:91: in parse self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:492: in _free_cache_entries for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...xtToken2', 'Groups', 'NextMarker || ListBucketResult.Contents[-1].Key', 'Contents', 'ListBucketResults.NextKeyMarker']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError _____________________ TestOptionalTokens.test_clean_token ______________________ self = def setUp(self): self.method = mock.Mock() self.model = mock.Mock() # This is based on Route53 pagination. self.paginate_config = { "output_token": [ "NextRecordName", "NextRecordType", "NextRecordIdentifier", ], "input_token": [ "StartRecordName", "StartRecordType", "StartRecordIdentifier", ], "result_key": 'Foo', } > self.paginator = Paginator( self.method, self.paginate_config, self.model ) tests/unit/test_paginate.py:753: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ botocore/paginate.py:606: in __init__ self._output_token = self._get_output_tokens(self._pagination_cfg) botocore/paginate.py:631: in _get_output_tokens output.append(jmespath.compile(config)) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: in compile return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/parser.py:91: in parse self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:492: in _free_cache_entries for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...', 'NextMarker || ListBucketResult.Contents[-1].Key', 'Contents', 'ListBucketResults.NextKeyMarker', 'NextRecordName']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError ____ TestMultipleInputKeys.test_build_full_result_with_multiple_input_keys _____ self = def setUp(self): self.method = mock.Mock() self.model = mock.Mock() # Probably the most complicated example we'll see: # multiple input/output/result keys. self.paginate_config = { "output_token": ["Marker1", "Marker2"], "input_token": ["InMarker1", "InMarker2"], "result_key": ["Users", "Groups"], } > self.paginator = Paginator( self.method, self.paginate_config, self.model ) tests/unit/test_paginate.py:1116: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ botocore/paginate.py:606: in __init__ self._output_token = self._get_output_tokens(self._pagination_cfg) botocore/paginate.py:631: in _get_output_tokens output.append(jmespath.compile(config)) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: in compile return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/parser.py:91: in parse self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:492: in _free_cache_entries for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...ker || ListBucketResult.Contents[-1].Key', 'Contents', 'ListBucketResults.NextKeyMarker', 'NextRecordName', 'Marker1']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError ________ TestMultipleInputKeys.test_result_key_exposed_on_page_iterator ________ self = def setUp(self): self.method = mock.Mock() self.model = mock.Mock() # Probably the most complicated example we'll see: # multiple input/output/result keys. self.paginate_config = { "output_token": ["Marker1", "Marker2"], "input_token": ["InMarker1", "InMarker2"], "result_key": ["Users", "Groups"], } > self.paginator = Paginator( self.method, self.paginate_config, self.model ) tests/unit/test_paginate.py:1116: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ botocore/paginate.py:606: in __init__ self._output_token = self._get_output_tokens(self._pagination_cfg) botocore/paginate.py:631: in _get_output_tokens output.append(jmespath.compile(config)) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: in compile return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/parser.py:91: in parse self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:492: in _free_cache_entries for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...BucketResult.Contents[-1].Key', 'Contents', 'ListBucketResults.NextKeyMarker', 'NextRecordName', 'Marker1', 'Marker2']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError ___________ TestIncludeResultKeys.test_different_kinds_of_result_key ___________ self = def setUp(self): self.method = mock.Mock() self.model = mock.Mock() self.paginate_config = { 'output_token': 'Marker', 'input_token': 'Marker', 'result_key': ['ResultKey', 'Count', 'Log'], } > self.paginator = Paginator( self.method, self.paginate_config, self.model ) tests/unit/test_paginate.py:1258: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ botocore/paginate.py:612: in __init__ self._result_keys = self._get_result_keys(self._pagination_cfg) botocore/paginate.py:650: in _get_result_keys result_key = [jmespath.compile(rk) for rk in result_key] botocore/paginate.py:650: in result_key = [jmespath.compile(rk) for rk in result_key] /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: in compile return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/parser.py:91: in parse self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:492: in _free_cache_entries for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...Contents[-1].Key', 'Contents', 'ListBucketResults.NextKeyMarker', 'NextRecordName', 'Marker1', 'Marker2', 'ResultKey']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError _______________ TestIncludeResultKeys.test_result_key_is_missing _______________ self = def setUp(self): self.method = mock.Mock() self.model = mock.Mock() self.paginate_config = { 'output_token': 'Marker', 'input_token': 'Marker', 'result_key': ['ResultKey', 'Count', 'Log'], } > self.paginator = Paginator( self.method, self.paginate_config, self.model ) tests/unit/test_paginate.py:1258: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ botocore/paginate.py:612: in __init__ self._result_keys = self._get_result_keys(self._pagination_cfg) botocore/paginate.py:650: in _get_result_keys result_key = [jmespath.compile(rk) for rk in result_key] botocore/paginate.py:650: in result_key = [jmespath.compile(rk) for rk in result_key] /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: in compile return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/parser.py:91: in parse self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:492: in _free_cache_entries for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...-1].Key', 'Contents', 'ListBucketResults.NextKeyMarker', 'NextRecordName', 'Marker1', 'Marker2', 'ResultKey', 'Count']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError ___________ TestIncludeNonResultKeys.test_include_non_aggregate_keys ___________ self = def setUp(self): self.method = mock.Mock() self.model = mock.Mock() self.paginate_config = { 'output_token': 'NextToken', 'input_token': 'NextToken', 'result_key': 'ResultKey', 'non_aggregate_keys': ['NotResultKey'], } > self.paginator = Paginator( self.method, self.paginate_config, self.model ) tests/unit/test_paginate.py:1299: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ botocore/paginate.py:609: in __init__ self._non_aggregate_keys = self._get_non_aggregate_keys( botocore/paginate.py:622: in _get_non_aggregate_keys keys.append(jmespath.compile(key)) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: in compile return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/parser.py:91: in parse self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:492: in _free_cache_entries for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...nts', 'ListBucketResults.NextKeyMarker', 'NextRecordName', 'Marker1', 'Marker2', 'ResultKey', 'Count', 'NotResultKey']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError _______ TestIncludeNonResultKeys.test_include_with_multiple_result_keys ________ self = def test_include_with_multiple_result_keys(self): self.paginate_config['result_key'] = ['ResultKey1', 'ResultKey2'] > self.paginator = Paginator( self.method, self.paginate_config, self.model ) tests/unit/test_paginate.py:1320: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ botocore/paginate.py:612: in __init__ self._result_keys = self._get_result_keys(self._pagination_cfg) botocore/paginate.py:650: in _get_result_keys result_key = [jmespath.compile(rk) for rk in result_key] botocore/paginate.py:650: in result_key = [jmespath.compile(rk) for rk in result_key] /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: in compile return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/parser.py:91: in parse self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:492: in _free_cache_entries for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...ketResults.NextKeyMarker', 'NextRecordName', 'Marker1', 'Marker2', 'ResultKey', 'Count', 'NotResultKey', 'ResultKey1']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError ________ TestIncludeNonResultKeys.test_include_with_nested_result_keys _________ self = def test_include_with_nested_result_keys(self): self.paginate_config['result_key'] = 'Result.Key' self.paginate_config['non_aggregate_keys'] = [ 'Outer', 'Result.Inner', ] > self.paginator = Paginator( self.method, self.paginate_config, self.model ) tests/unit/test_paginate.py:1357: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ botocore/paginate.py:609: in __init__ self._non_aggregate_keys = self._get_non_aggregate_keys( botocore/paginate.py:622: in _get_non_aggregate_keys keys.append(jmespath.compile(key)) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: in compile return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/parser.py:91: in parse self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:492: in _free_cache_entries for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...s.NextKeyMarker', 'NextRecordName', 'Marker1', 'Marker2', 'ResultKey', 'Count', 'NotResultKey', 'ResultKey1', 'Outer']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError ________________ TestSearchOverResults.test_empty_when_no_match ________________ self = def test_empty_when_no_match(self): > result = list(self.paginator.paginate().search('Foo[].qux')) tests/unit/test_paginate.py:1428: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ botocore/paginate.py:349: in search compiled = jmespath.compile(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: in compile return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/parser.py:91: in parse self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:492: in _free_cache_entries for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...er', 'NextRecordName', 'Marker1', 'Marker2', 'ResultKey', 'Count', 'NotResultKey', 'ResultKey1', 'Outer', 'Foo[].qux']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError __________ TestSearchOverResults.test_no_yield_when_no_match_on_page ___________ self = def test_no_yield_when_no_match_on_page(self): > result = list(self.paginator.paginate().search('Foo[].b')) tests/unit/test_paginate.py:1432: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ botocore/paginate.py:349: in search compiled = jmespath.compile(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: in compile return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/parser.py:91: in parse self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:492: in _free_cache_entries for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...ecordName', 'Marker1', 'Marker2', 'ResultKey', 'Count', 'NotResultKey', 'ResultKey1', 'Outer', 'Foo[].qux', 'Foo[].b']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError ___________ TestSearchOverResults.test_yields_individual_list_values ___________ self = def test_yields_individual_list_values(self): > result = list(self.paginator.paginate().search('Foo[].*[]')) tests/unit/test_paginate.py:1424: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ botocore/paginate.py:349: in search compiled = jmespath.compile(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: in compile return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/parser.py:91: in parse self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:492: in _free_cache_entries for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...Marker1', 'Marker2', 'ResultKey', 'Count', 'NotResultKey', 'ResultKey1', 'Outer', 'Foo[].qux', 'Foo[].b', 'Foo[].*[]']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError ______________ TestSearchOverResults.test_yields_non_list_values _______________ self = def test_yields_non_list_values(self): > result = list(self.paginator.paginate().search('Foo[0].a')) tests/unit/test_paginate.py:1420: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ botocore/paginate.py:349: in search compiled = jmespath.compile(expression) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: in compile return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/parser.py:91: in parse self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:492: in _free_cache_entries for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...arker2', 'ResultKey', 'Count', 'NotResultKey', 'ResultKey1', 'Outer', 'Foo[].qux', 'Foo[].b', 'Foo[].*[]', 'Foo[0].a']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError ____________________ TestStringPageSize.test_int_page_size _____________________ self = def setUp(self): self.service_model = { 'metadata': {'protocol': 'query', 'endpointPrefix': 'prefix'}, 'documentation': 'best service ever', 'operations': { 'ListStuff': { 'name': 'ListStuff', 'http': {'method': 'GET', 'requestUri': '/things'}, 'input': {'shape': 'ListStuffInputShape'}, 'output': {'shape': 'ListStuffOutputShape'}, 'errors': [], 'documentation': 'Lists stuff', } }, 'shapes': { 'String': {'type': 'string'}, 'ListOfStuff': {'type': 'list', 'member': {'type': 'string'}}, 'ListStuffInputShape': { 'type': 'structure', 'required': [], 'members': { 'NextToken': {'shape': 'String'}, 'MaxItems': {'shape': 'String'}, }, }, 'ListStuffOutputShape': { 'type': 'structure', 'required': [], 'members': { 'NextToken': {'shape': 'String'}, 'Stuff': {'shape': 'ListOfStuff'}, 'IsTruncated': {'type': 'boolean'}, }, }, }, } self.paginate_config = { 'input_token': 'NextToken', 'output_token': 'NextToken', 'limit_key': 'MaxItems', 'result_key': 'Stuff', } self.service = model.ServiceModel(self.service_model) self.model = self.service.operation_model('ListStuff') self.method = mock.Mock() self.method.side_effect = [{}] > self.paginator = Paginator( self.method, self.paginate_config, self.model ) tests/unit/test_paginate.py:1610: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ botocore/paginate.py:612: in __init__ self._result_keys = self._get_result_keys(self._pagination_cfg) botocore/paginate.py:650: in _get_result_keys result_key = [jmespath.compile(rk) for rk in result_key] botocore/paginate.py:650: in result_key = [jmespath.compile(rk) for rk in result_key] /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: in compile return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/parser.py:91: in parse self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:492: in _free_cache_entries for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...'ResultKey', 'Count', 'NotResultKey', 'ResultKey1', 'Outer', 'Foo[].qux', 'Foo[].b', 'Foo[].*[]', 'Foo[0].a', 'Stuff']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError _________ TestWaiterModel.test_path_all_matcher_does_not_receive_list __________ self = def test_path_all_matcher_does_not_receive_list(self): > matches = self.create_acceptor_function( for_config={ 'state': 'success', 'matcher': 'pathAll', 'argument': 'Tables[].State', 'expected': 'GOOD', } ) tests/unit/test_waiters.py:343: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ tests/unit/test_waiters.py:43: in create_acceptor_function return config.acceptors[0].matcher_func botocore/waiter.py:167: in acceptors acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:178: in __init__ self.matcher_func = self._create_matcher_func() botocore/waiter.py:213: in _create_matcher_func return self._create_path_all_matcher() botocore/waiter.py:237: in _create_path_all_matcher expression = jmespath.compile(self.argument) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: in compile return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/parser.py:91: in parse self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:492: in _free_cache_entries for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...t', 'NotResultKey', 'ResultKey1', 'Outer', 'Foo[].qux', 'Foo[].b', 'Foo[].*[]', 'Foo[0].a', 'Stuff', 'Tables[].State']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError _________ TestWaiterModel.test_single_waiter_supports_all_three_states _________ self = def test_single_waiter_supports_all_three_states(self): single_waiter = { 'acceptors': [ { 'state': 'success', 'matcher': 'error', 'expected': 'DoesNotExistError', }, {'state': 'success', 'matcher': 'status', 'expected': 200}, { 'state': 'success', 'matcher': 'path', 'argument': 'Foo.Bar', 'expected': 'baz', }, ], } single_waiter.update(self.boiler_plate_config) config = SingleWaiterConfig(single_waiter) > acceptors = config.acceptors tests/unit/test_waiters.py:372: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ botocore/waiter.py:167: in acceptors acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:178: in __init__ self.matcher_func = self._create_matcher_func() botocore/waiter.py:211: in _create_matcher_func return self._create_path_matcher() botocore/waiter.py:226: in _create_path_matcher expression = jmespath.compile(self.argument) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: in compile return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/parser.py:91: in parse self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:492: in _free_cache_entries for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...ultKey', 'ResultKey1', 'Outer', 'Foo[].qux', 'Foo[].b', 'Foo[].*[]', 'Foo[0].a', 'Stuff', 'Tables[].State', 'Foo.Bar']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError ____ TestWaiterModel.test_waiter_handles_error_responses_with_path_matchers ____ self = def test_waiter_handles_error_responses_with_path_matchers(self): > path_any = self.create_acceptor_function( for_config={ 'state': 'success', 'matcher': 'pathAny', 'argument': 'length(Tables) > `0`', 'expected': True, } ) tests/unit/test_waiters.py:269: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ tests/unit/test_waiters.py:43: in create_acceptor_function return config.acceptors[0].matcher_func botocore/waiter.py:167: in acceptors acceptor = AcceptorConfig(acceptor_config) botocore/waiter.py:178: in __init__ self.matcher_func = self._create_matcher_func() botocore/waiter.py:215: in _create_matcher_func return self._create_path_any_matcher() botocore/waiter.py:258: in _create_path_any_matcher expression = jmespath.compile(self.argument) /usr/lib/python3.11/site-packages/jmespath/__init__.py:19: in compile return parser.Parser().parse(expression) /usr/lib/python3.11/site-packages/jmespath/parser.py:91: in parse self._free_cache_entries() /usr/lib/python3.11/site-packages/jmespath/parser.py:492: in _free_cache_entries for key in random.sample(self._CACHE.keys(), int(self._MAX_SIZE / 2)): _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = population = dict_keys(['keys(RequestItems)', 'Marker', 'AdditionalDataPending', 'LogFileData', 'NextToken', 'Activities', 'nextTok...Outer', 'Foo[].qux', 'Foo[].b', 'Foo[].*[]', 'Foo[0].a', 'Stuff', 'Tables[].State', 'Foo.Bar', 'length(Tables) > `0`']) k = 64 def sample(self, population, k, *, counts=None): """Chooses k unique random elements from a population sequence. Returns a new list containing elements from the population while leaving the original population unchanged. The resulting list is in selection order so that all sub-slices will also be valid random samples. This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices). Members of the population need not be hashable or unique. If the population contains repeats, then each occurrence is a possible selection in the sample. Repeated elements can be specified one at a time or with the optional counts parameter. For example: sample(['red', 'blue'], counts=[4, 2], k=5) is equivalent to: sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5) To choose a sample from a range of integers, use range() for the population argument. This is especially fast and space efficient for sampling from a large population: sample(range(10000000), 60) """ # Sampling without replacement entails tracking either potential # selections (the pool) in a list or previous selections in a set. # When the number of selections is small compared to the # population, then tracking selections is efficient, requiring # only a small set and an occasional reselection. For # a larger number of selections, the pool tracking method is # preferred since the list takes less space than the # set and it doesn't suffer from frequent reselections. # The number of calls to _randbelow() is kept at or near k, the # theoretical minimum. This is important because running time # is dominated by _randbelow() and because it extracts the # least entropy from the underlying random number generators. # Memory requirements are kept to the smaller of a k-length # set or an n-length list. # There are other sampling algorithms that do not require # auxiliary memory, but they were rejected because they made # too many calls to _randbelow(), making them slower and # causing them to eat more entropy than necessary. if not isinstance(population, _Sequence): > raise TypeError("Population must be a sequence. " "For dicts or sets, use sorted(d).") E TypeError: Population must be a sequence. For dicts or sets, use sorted(d). /usr/lib64/python3.11/random.py:439: TypeError =============================== warnings summary =============================== tests/functional/docs/test_shared_example_config.py::test_lint_shared_example_configs[DescribeStream-example_config232-service_model232] /usr/lib/python3.11/site-packages/dateutil/parser/_parser.py:1207: UnknownTimezoneWarning: tzname PDT identified but not understood. Pass `tzinfos` argument in order to correctly return a timezone-aware datetime. In a future version, this will raise an exception. warnings.warn("tzname {tzname} identified but not understood. " -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html =========================== short test summary info ============================ FAILED tests/functional/test_waiter_config.py::test_lint_waiter_configs[validator51-waiter_model51-client51] FAILED tests/functional/test_waiter_config.py::test_lint_waiter_configs[validator52-waiter_model52-client52] FAILED tests/functional/test_waiter_config.py::test_lint_waiter_configs[validator54-waiter_model54-client54] FAILED tests/functional/test_waiter_config.py::test_lint_waiter_configs[validator55-waiter_model55-client55] FAILED tests/functional/test_waiter_config.py::test_lint_waiter_configs[validator56-waiter_model56-client56] FAILED tests/functional/test_waiter_config.py::test_lint_waiter_configs[validator57-waiter_model57-client57] FAILED tests/functional/test_waiter_config.py::test_lint_waiter_configs[validator59-waiter_model59-client59] FAILED tests/functional/test_waiter_config.py::test_lint_waiter_configs[validator68-waiter_model68-client68] FAILED tests/functional/test_waiter_config.py::test_lint_waiter_configs[validator69-waiter_model69-client69] FAILED tests/functional/test_waiter_config.py::test_lint_waiter_configs[validator71-waiter_model71-client71] FAILED tests/functional/test_waiter_config.py::test_lint_waiter_configs[validator75-waiter_model75-client75] FAILED tests/functional/test_waiter_config.py::test_lint_waiter_configs[validator82-waiter_model82-client82] FAILED tests/functional/test_waiter_config.py::test_lint_waiter_configs[validator84-waiter_model84-client84] FAILED tests/functional/test_waiter_config.py::test_lint_waiter_configs[validator87-waiter_model87-client87] FAILED tests/functional/test_waiter_config.py::test_lint_waiter_configs[validator94-waiter_model94-client94] FAILED tests/functional/test_waiter_config.py::test_lint_waiter_configs[validator95-waiter_model95-client95] FAILED tests/functional/test_waiter_config.py::test_lint_waiter_configs[validator103-waiter_model103-client103] FAILED tests/functional/test_waiter_config.py::test_lint_waiter_configs[validator124-waiter_model124-client124] FAILED tests/functional/test_waiter_config.py::test_lint_waiter_configs[validator128-waiter_model128-client128] FAILED tests/functional/test_waiter_config.py::test_lint_waiter_configs[validator129-waiter_model129-client129] FAILED tests/functional/test_waiter_config.py::test_lint_waiter_configs[validator130-waiter_model130-client130] FAILED tests/functional/test_waiter_config.py::test_lint_waiter_configs[validator131-waiter_model131-client131] FAILED tests/functional/test_waiter_config.py::test_lint_waiter_configs[validator134-waiter_model134-client134] FAILED tests/functional/test_waiter_config.py::test_lint_waiter_configs[validator135-waiter_model135-client135] FAILED tests/functional/test_waiter_config.py::test_lint_waiter_configs[validator143-waiter_model143-client143] FAILED tests/functional/test_waiter_config.py::test_lint_waiter_configs[validator147-waiter_model147-client147] FAILED tests/functional/test_waiter_config.py::test_lint_waiter_configs[validator150-waiter_model150-client150] FAILED tests/functional/test_waiter_config.py::test_lint_waiter_configs[validator152-waiter_model152-client152] FAILED tests/functional/test_waiter_config.py::test_lint_waiter_configs[validator154-waiter_model154-client154] FAILED tests/functional/test_waiter_config.py::test_lint_waiter_configs[validator155-waiter_model155-client155] FAILED tests/unit/test_client.py::TestAutoGeneratedClient::test_paginator_class_name_from_client FAILED tests/unit/test_paginate.py::TestPagination::test_any_passed_in_args_are_unmodified FAILED tests/unit/test_paginate.py::TestPagination::test_more_tokens_is_path_expression FAILED tests/unit/test_paginate.py::TestPagination::test_next_token_with_or_expression FAILED tests/unit/test_paginate.py::TestPaginatorPageSize::test_no_page_size FAILED tests/unit/test_paginate.py::TestPaginatorWithPathExpressions::test_s3_list_object_complex FAILED tests/unit/test_paginate.py::TestPaginatorWithPathExpressions::test_s3_list_objects FAILED tests/unit/test_paginate.py::TestMultipleTokens::test_s3_list_multipart_uploads FAILED tests/unit/test_paginate.py::TestOptionalTokens::test_clean_token - Ty... FAILED tests/unit/test_paginate.py::TestMultipleInputKeys::test_build_full_result_with_multiple_input_keys FAILED tests/unit/test_paginate.py::TestMultipleInputKeys::test_result_key_exposed_on_page_iterator FAILED tests/unit/test_paginate.py::TestIncludeResultKeys::test_different_kinds_of_result_key FAILED tests/unit/test_paginate.py::TestIncludeResultKeys::test_result_key_is_missing FAILED tests/unit/test_paginate.py::TestIncludeNonResultKeys::test_include_non_aggregate_keys FAILED tests/unit/test_paginate.py::TestIncludeNonResultKeys::test_include_with_multiple_result_keys FAILED tests/unit/test_paginate.py::TestIncludeNonResultKeys::test_include_with_nested_result_keys FAILED tests/unit/test_paginate.py::TestSearchOverResults::test_empty_when_no_match FAILED tests/unit/test_paginate.py::TestSearchOverResults::test_no_yield_when_no_match_on_page FAILED tests/unit/test_paginate.py::TestSearchOverResults::test_yields_individual_list_values FAILED tests/unit/test_paginate.py::TestSearchOverResults::test_yields_non_list_values FAILED tests/unit/test_paginate.py::TestStringPageSize::test_int_page_size - ... FAILED tests/unit/test_waiters.py::TestWaiterModel::test_path_all_matcher_does_not_receive_list FAILED tests/unit/test_waiters.py::TestWaiterModel::test_single_waiter_supports_all_three_states FAILED tests/unit/test_waiters.py::TestWaiterModel::test_waiter_handles_error_responses_with_path_matchers ==== 54 failed, 59077 passed, 126 skipped, 1 warning in 1494.36s (0:24:54) ===== error: Bad exit status from /var/tmp/rpm-tmp.f11xuF (%check) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.f11xuF (%check) Child return code was: 1 EXCEPTION: [Error("Command failed: \n # bash --login -c '/usr/bin/rpmbuild -ba --noprep --noclean --target noarch /builddir/build/SPECS/python-botocore.spec'\n", 1)] Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/mockbuild/trace_decorator.py", line 93, in trace result = func(*args, **kw) File "/usr/lib/python3.6/site-packages/mockbuild/util.py", line 610, in do_with_status raise exception.Error("Command failed: \n # %s\n%s" % (cmd_pretty(command, env), output), child.returncode) mockbuild.exception.Error: Command failed: # bash --login -c '/usr/bin/rpmbuild -ba --noprep --noclean --target noarch /builddir/build/SPECS/python-botocore.spec'