<86>Apr 29 06:26:38 userdel[2553319]: delete user 'rooter' <86>Apr 29 06:26:38 userdel[2553319]: removed group 'rooter' owned by 'rooter' <86>Apr 29 06:26:38 userdel[2553319]: removed shadow group 'rooter' owned by 'rooter' <86>Apr 29 06:26:38 groupadd[2553329]: group added to /etc/group: name=rooter, GID=711 <86>Apr 29 06:26:38 groupadd[2553329]: group added to /etc/gshadow: name=rooter <86>Apr 29 06:26:38 groupadd[2553329]: new group: name=rooter, GID=711 useradd warning: rooter's uid 711 outside of the UID_MIN 1000 and UID_MAX 60000 range. <86>Apr 29 06:26:38 useradd[2553335]: new user: name=rooter, UID=711, GID=711, home=/root, shell=/bin/bash, from=none <86>Apr 29 06:26:38 userdel[2553348]: delete user 'builder' <86>Apr 29 06:26:38 userdel[2553348]: removed group 'builder' owned by 'builder' <86>Apr 29 06:26:38 userdel[2553348]: removed shadow group 'builder' owned by 'builder' <86>Apr 29 06:26:39 groupadd[2553357]: group added to /etc/group: name=builder, GID=712 <86>Apr 29 06:26:39 groupadd[2553357]: group added to /etc/gshadow: name=builder <86>Apr 29 06:26:39 groupadd[2553357]: new group: name=builder, GID=712 useradd warning: builder's uid 712 outside of the UID_MIN 1000 and UID_MAX 60000 range. <86>Apr 29 06:26:39 useradd[2553363]: new user: name=builder, UID=712, GID=712, home=/usr/src, shell=/bin/bash, from=none <13>Apr 29 06:26:41 rpmi: libmpdec3-2.5.1-alt3 sisyphus+314490.500.5.1 1675432033 installed <13>Apr 29 06:26:41 rpmi: libgdbm-1.8.3-alt10 sisyphus+278100.1600.1.1 1626059138 installed <13>Apr 29 06:26:41 rpmi: libexpat-2.5.0-alt1 sisyphus+309227.100.1.1 1667075766 installed <13>Apr 29 06:26:41 rpmi: libp11-kit-0.24.1-alt1 sisyphus+293720.100.1.1 1642535281 installed <13>Apr 29 06:26:41 rpmi: libtasn1-4.19.0-alt1 sisyphus+305700.100.1.1 1661359628 installed <13>Apr 29 06:26:41 rpmi: rpm-macros-alternatives-0.5.2-alt2 sisyphus+315270.200.2.1 1676457367 installed <13>Apr 29 06:26:41 rpmi: alternatives-0.5.2-alt2 sisyphus+315270.200.2.1 1676457367 installed <13>Apr 29 06:26:41 rpmi: ca-certificates-2022.12.14-alt1 sisyphus+311754.200.1.1 1671046143 installed <13>Apr 29 06:26:41 rpmi: ca-trust-0.1.4-alt1 sisyphus+308690.100.1.1 1666182992 installed <13>Apr 29 06:26:41 rpmi: p11-kit-trust-0.24.1-alt1 sisyphus+293720.100.1.1 1642535281 installed <13>Apr 29 06:26:41 rpmi: libcrypto1.1-1.1.1t-alt1 sisyphus+314824.100.2.2 1675799073 installed <13>Apr 29 06:26:41 rpmi: libssl1.1-1.1.1t-alt1 sisyphus+314824.100.2.2 1675799073 installed <13>Apr 29 06:26:41 rpmi: python3-3.10.8-alt1.1 sisyphus+311926.100.2.1 1671363746 installed <13>Apr 29 06:26:42 rpmi: python3-base-3.10.8-alt1.1 sisyphus+311926.100.2.1 1671363746 installed <13>Apr 29 06:26:42 rpmi: tests-for-installed-python3-pkgs-0.1.22-alt1 sisyphus+319076.100.3.1 1682536051 installed <13>Apr 29 06:26:42 rpmi: rpm-build-python3-0.1.22-alt1 sisyphus+319076.100.3.1 1682536051 installed <13>Apr 29 06:26:47 rpmi: python3-module-six-1.16.0-alt1 sisyphus+283489.100.2.1 1629527308 installed <13>Apr 29 06:26:47 rpmi: python3-module-attrs-22.2.0-alt1 sisyphus+313134.100.1.1 1673363066 installed <13>Apr 29 06:26:47 rpmi: python3-module-packaging-23.0-alt1 sisyphus+314493.40.11.1 1676633541 installed <13>Apr 29 06:26:47 rpmi: python3-module-pkg_resources-1:67.7.2-alt1 sisyphus+319053.1300.6.1 1682668497 installed <13>Apr 29 06:26:47 rpmi: python3-module-idna-3.4-alt1 sisyphus+307942.100.1.1 1665051373 installed <13>Apr 29 06:26:47 rpmi: python3-module-mypy_extensions-1.0.0-alt1 sisyphus+316350.100.2.1 1678357948 installed <13>Apr 29 06:26:47 rpmi: python3-module-zope.interface-5.4.0-alt2 sisyphus+291245.43540.56.1 1643371192 installed <13>Apr 29 06:26:47 rpmi: perl-HTTP-Date-6.05-alt1 sisyphus+258981.100.1.1 1601542386 installed <13>Apr 29 06:26:47 rpmi: python3-module-dateutil-2.8.2-alt1 sisyphus+282710.100.1.1 1628976583 installed <13>Apr 29 06:26:47 rpmi: python3-module-typing_extensions-4.5.0-alt1 sisyphus+315274.100.1.1 1676455261 installed <13>Apr 29 06:26:47 rpmi: python3-module-pytz-1:2022.6-alt1 sisyphus+311396.200.1.1 1670517427 installed <13>Apr 29 06:26:47 rpmi: python3-module-tomli-2.0.1-alt2 sisyphus+305000.3300.2.1 1660575675 installed <13>Apr 29 06:26:47 rpmi: python3-module-greenlet-1.1.2-alt1 sisyphus+291245.12740.54.1 1643302800 installed <13>Apr 29 06:26:47 rpmi: python3-module-exceptiongroup-1.1.1-alt1 sisyphus+318894.100.2.1 1682414107 installed <13>Apr 29 06:26:47 rpmi: libopenblas-0.3.19-alt1.2 sisyphus+318600.100.1.1 1681692065 installed <13>Apr 29 06:26:47 rpmi: libwayland-client-1.22.0-alt1.1 sisyphus+318010.100.1.1 1680606300 installed <13>Apr 29 06:26:47 rpmi: liblcms2-2.15-alt1 sisyphus+316039.100.1.1 1677666336 installed <13>Apr 29 06:26:47 rpmi: perl-XML-NamespaceSupport-1.12-alt1 1491296348 installed <13>Apr 29 06:26:47 rpmi: libpng16-1.6.39-alt1 sisyphus+310490.100.1.1 1669195208 installed <13>Apr 29 06:26:47 rpmi: libjpeg-2:2.1.2-alt1.2 sisyphus+300827.100.2.1 1653916654 installed <13>Apr 29 06:26:47 rpmi: libkmod-30-alt1 sisyphus+307195.200.2.1 1663842346 installed <13>Apr 29 06:26:47 rpmi: libatk-2.48.0-alt1 sisyphus+317076.400.1.1 1679344534 installed <13>Apr 29 06:26:47 rpmi: liblz4-1:1.9.4-alt1 sisyphus+309416.100.1.1 1667413000 installed <13>Apr 29 06:26:47 rpmi: libsystemd-1:252.7-alt1 sisyphus+316321.100.1.1 1678130459 installed <13>Apr 29 06:26:47 rpmi: libdbus-1.14.6-alt1 sisyphus+315497.100.1.1 1676874448 installed <13>Apr 29 06:26:47 rpmi: python3-module-markupsafe-1:2.1.2-alt1 sisyphus+313626.100.1.1 1674030215 installed <13>Apr 29 06:26:47 rpmi: python3-module-jinja2-3.1.2-alt1 sisyphus+303664.100.1.1 1657809843 installed <13>Apr 29 06:26:47 rpmi: python3-module-multidict-6.0.4-alt1 sisyphus+313390.100.1.1 1673619403 installed <13>Apr 29 06:26:47 rpmi: python3-module-click-8.1.3-alt2 sisyphus+318894.300.3.1 1682420471 installed <13>Apr 29 06:26:47 rpmi: python3-module-appdirs-1.4.4-alt1 sisyphus+267613.300.2.1 1620039159 installed <13>Apr 29 06:26:47 rpmi: python3-module-sortedcontainers-2.4.0-alt1 sisyphus+272042.100.1.1 1621262424 installed <13>Apr 29 06:26:47 rpmi: python3-module-frozenlist-1.3.3-alt1 sisyphus+314063.100.1.1 1674563222 installed <13>Apr 29 06:26:47 rpmi: python3-module-charset-normalizer-2.1.1-alt1 sisyphus+311047.100.1.1 1669992940 installed <13>Apr 29 06:26:47 rpmi: libsqlite3-3.41.2-alt1 sisyphus+318245.100.1.1 1680943749 installed <13>Apr 29 06:26:47 rpmi: python3-modules-sqlite3-3.10.8-alt1.1 sisyphus+311926.100.2.1 1671363746 installed <13>Apr 29 06:26:47 rpmi: libfribidi-1.0.12-alt1 sisyphus+298746.100.1.1 1650435950 installed <13>Apr 29 06:26:47 rpmi: libusb-1.0.26-alt2 sisyphus+305525.100.1.1 1660924428 installed <13>Apr 29 06:26:47 rpmi: libcares-1.19.0-alt2 sisyphus+318319.40.19.1 1681776144 installed <13>Apr 29 06:26:47 rpmi: perl-LWP-MediaTypes-6.04-alt1 sisyphus+225468.100.1.1 1553186684 installed <13>Apr 29 06:26:47 rpmi: perl-Compress-Raw-Zlib-2.204-alt1 sisyphus+314931.100.1.1 1675930919 installed <13>Apr 29 06:26:47 rpmi: perl-libnet-1:3.15-alt1 sisyphus+317310.100.1.1 1679580208 installed <13>Apr 29 06:26:47 rpmi: perl-XML-SAX-Base-1.09-alt1 1494364363 installed <13>Apr 29 06:26:47 rpmi: libwebp7-1.3.0-alt1 sisyphus+313492.100.1.1 1673749692 installed <13>Apr 29 06:26:48 rpmi: libhidapi-0.12.0-alt1_1 sisyphus+303213.100.1.1 1657034193 installed <13>Apr 29 06:26:48 rpmi: python3-module-cython-hidapi-0.13.1-alt1 sisyphus+316627.100.1.1 1678653691 installed <13>Apr 29 06:26:48 rpmi: python3-module-serial-3.5-alt2 sisyphus+281995.100.1.1 1628172783 installed <13>Apr 29 06:26:48 rpmi: python3-module-coverage-6.5.0-alt1 sisyphus+319144.100.1.1 1682257465 installed <13>Apr 29 06:26:48 rpmi: python3-module-Cython-0.29.34-alt1 sisyphus+317941.200.2.1 1682342273 installed <13>Apr 29 06:26:48 rpmi: python3-module-aiosignal-1.3.1-alt1 sisyphus+314057.100.1.1 1674561191 installed <13>Apr 29 06:26:48 rpmi: python3-module-fs-2.4.16-alt1 sisyphus+299491.100.1.1 1651737114 installed <13>Apr 29 06:26:48 rpmi: python3-module-incremental-22.10.0-alt1 sisyphus+312706.100.1.1 1672404273 installed <13>Apr 29 06:26:48 rpmi: python3-module-yarl-1.8.1-alt1 sisyphus+309642.100.1.1 1667832284 installed <13>Apr 29 06:26:48 rpmi: libavahi-0.8-alt2 sisyphus+279391.100.1.2 1626530700 installed <13>Apr 29 06:26:48 rpmi: libblosc-1.21.1-alt1 sisyphus+304120.100.1.1 1658481162 installed <13>Apr 29 06:26:48 rpmi: libblosc2-2.8.0-alt1 sisyphus+317488.300.3.1 1679813153 installed <13>Apr 29 06:26:48 rpmi: kmod-30-alt1 sisyphus+307195.200.2.1 1663842346 installed <13>Apr 29 06:26:48 rpmi: libwayland-cursor-1.22.0-alt1.1 sisyphus+318010.100.1.1 1680606300 installed <13>Apr 29 06:26:48 rpmi: libwayland-egl-4:18.1.0-alt1.1 sisyphus+318010.100.1.1 1680606300 installed <13>Apr 29 06:26:48 rpmi: python3-module-mypy-1.2.0-alt1 sisyphus+319309.100.2.1 1682496138 installed <13>Apr 29 06:26:48 rpmi: python3-module-sqlalchemy-2.0.4-alt1 sisyphus+316295.100.2.1 1678458456 installed <13>Apr 29 06:26:48 rpmi: python3-module-typing-inspect-0.8.0-alt1 sisyphus+306830.400.1.1 1663349697 installed <13>Apr 29 06:26:48 rpmi: perl-File-Listing-6.15-alt1 sisyphus+298606.100.1.1 1650203737 installed <13>Apr 29 06:26:48 rpmi: python3-module-idna_ssl-1.1.0-alt2 sisyphus+272418.100.1.1 1621876529 installed <13>Apr 29 06:26:48 rpmi: python3-module-hyperlink-21.0.0-alt1.1 sisyphus+304836.100.1.1 1659710964 installed <13>Apr 29 06:26:48 rpmi: python3-module-outcome-1.2.0-alt2 sisyphus+318894.1400.3.1 1682420792 installed <13>Apr 29 06:26:48 rpmi: python3-module-genshi-0.7.7-alt1 sisyphus+299111.100.1.1 1651061011 installed <13>Apr 29 06:26:48 rpmi: python3-module-pyrsistent-0.19.3-alt1 sisyphus+313910.100.1.1 1674348735 installed <13>Apr 29 06:26:49 rpmi: python3-module-redis-py-3.4.1-alt2 sisyphus+280723.100.1.1 1627279044 installed <13>Apr 29 06:26:49 rpmi: python3-module-xlwt-1.3.0-alt2 sisyphus+276024.100.1.1 1624812681 installed <13>Apr 29 06:26:49 rpmi: python3-module-xlsxwriter-3.1.0-alt1 sisyphus+318699.100.1.1 1681793160 installed <13>Apr 29 06:26:49 rpmi: python3-module-jdcal-1.4.1-alt1 sisyphus+302206.100.1.1 1655392673 installed <13>Apr 29 06:26:49 rpmi: python3-module-xlrd-2.0.1-alt2.1 sisyphus+274166.200.2.1 1623321346 installed <13>Apr 29 06:26:49 rpmi: python3-module-mpmath-1.2.1-alt1 sisyphus+277364.40.2.1 1625515359 installed <13>Apr 29 06:26:49 rpmi: python3-module-matplotlib-data-3.7.0-alt1 sisyphus+315348.200.2.1 1676627496 installed <13>Apr 29 06:26:49 rpmi: python3-module-railroad-diagrams-1.1.1-alt1 sisyphus+294587.100.1.1 1643813088 installed <13>Apr 29 06:26:49 rpmi: python3-module-pyparsing-3.0.9-alt2 sisyphus+309123.700.4.1 1668095436 installed <13>Apr 29 06:26:49 rpmi: python3-module-kiwisolver-1.4.4-alt1 sisyphus+301961.300.3.1 1658144000 installed <13>Apr 29 06:26:49 rpmi: python3-module-lark-parser-0.11.3-alt1 sisyphus+273965.100.1.1 1623099891 installed <13>Apr 29 06:26:49 rpmi: python3-module-et_xmlfile-1.1.0-alt1 sisyphus+300537.100.1.1 1653384154 installed <13>Apr 29 06:26:49 rpmi: python3-module-openpyxl-3.0.10-alt1 sisyphus+313035.100.1.1 1673263148 installed <13>Apr 29 06:26:49 rpmi: python3-module-sqlparse-0.4.4-alt1 sisyphus+319188.100.1.1 1682328039 installed <13>Apr 29 06:26:49 rpmi: python3-module-cycler-0.11.0-alt2 sisyphus+318170.100.1.1 1680850132 installed <13>Apr 29 06:26:49 rpmi: python3-module-cpuinfo-8.0.0-alt1 sisyphus+288179.100.1.1 1635239235 installed <13>Apr 29 06:26:49 rpmi: python3-module-platformdirs-3.2.0-alt1 sisyphus+319053.700.6.1 1682668363 installed <13>Apr 29 06:26:49 rpmi: python3-module-pathspec-0.11.1-alt1 sisyphus+318744.100.3.1 1681891000 installed <13>Apr 29 06:26:49 rpmi: python3-module-webencodings-0.5.1-alt2 sisyphus+276020.100.1.1 1624812421 installed <13>Apr 29 06:26:49 rpmi: python3-module-pluggy-1.0.0-alt1 sisyphus+284853.100.1.1 1631109373 installed <13>Apr 29 06:26:49 rpmi: python3-module-iniconfig-2.0.0-alt1 sisyphus+314076.200.3.1 1674737275 installed <13>Apr 29 06:26:49 rpmi: python3-module-pytest-7.3.1-alt1 sisyphus+318894.200.2.1 1682414249 installed <13>Apr 29 06:26:49 rpmi: python3-module-asgiref-3.4.1-alt1 sisyphus+283297.40.2.1 1629315886 installed <13>Apr 29 06:26:49 rpmi: python3-module-olefile-0.46-alt2 sisyphus+288126.100.1.1 1635163866 installed <13>Apr 29 06:26:49 rpmi: python3-module-constantly-15.1.0-alt6 sisyphus+284854.100.1.1 1631108193 installed <13>Apr 29 06:26:49 rpmi: python3-module-pygobject-2.28.6-alt12 sisyphus+291245.50660.59.1 1643601090 installed <13>Apr 29 06:26:49 rpmi: python3-module-certifi-2021.5.30-alt1 sisyphus+286375.2700.3.1 1633434210 installed <13>Apr 29 06:26:49 rpmi: python3-module-openid-3.2.0-alt1 sisyphus+278049.100.2.1 1625998936 installed <13>Apr 29 06:26:49 rpmi: python3-module-z3c-3.0.0-alt4 sisyphus+284857.200.1.1 1631109149 installed <13>Apr 29 06:26:49 rpmi: python3-module-zc-1.0.0-alt7 sisyphus+284857.100.1.1 1631109117 installed <13>Apr 29 06:26:49 rpmi: python3-module-zope-3.3.0-alt9 sisyphus+281937.200.4.1 1628175910 installed <13>Apr 29 06:26:49 rpmi: python3-module-zope.event-4.4-alt2 sisyphus+281937.400.4.1 1628175946 installed <13>Apr 29 06:26:49 rpmi: python3-module-pycparser-2.21-alt1.1 sisyphus+309935.7300.4.1 1668527005 installed <13>Apr 29 06:26:49 rpmi: python3-module-cffi-1.15.1-alt1 sisyphus+308243.100.2.1 1665650136 installed <13>Apr 29 06:26:49 rpmi: python3-module-cryptography-40.0.2-alt1 sisyphus+318920.100.1.1 1681998103 installed <13>Apr 29 06:26:49 rpmi: python3-module-openssl-23.1.1-alt2 sisyphus+319053.1700.6.1 1682668601 installed <13>Apr 29 06:26:49 rpmi: python3-module-automat-20.2.0-alt3 sisyphus+307208.340.3.1 1663936206 installed <13>Apr 29 06:26:49 rpmi: python3-module-twisted-logger-20.3.0-alt3 sisyphus+291245.44300.56.1 1643371531 installed <13>Apr 29 06:26:50 rpmi: python3-module-twisted-words-20.3.0-alt3 sisyphus+291245.44300.56.1 1643371531 installed <13>Apr 29 06:26:50 rpmi: python3-module-twisted-core-20.3.0-alt3 sisyphus+291245.44300.56.1 1643371531 installed <13>Apr 29 06:26:50 rpmi: python3-module-twisted-names-20.3.0-alt3 sisyphus+291245.44300.56.1 1643371531 installed <13>Apr 29 06:26:50 rpmi: python3-module-urllib3-2:1.26.14-alt2 sisyphus+318352.100.1.1 1681194106 installed <13>Apr 29 06:26:50 rpmi: python3-module-requests-2.28.2-alt1 sisyphus+313963.100.2.1 1674508765 installed <13>Apr 29 06:26:50 rpmi: python3-module-pycares-4.1.2-alt1 sisyphus+301090.100.1.1 1654174980 installed <13>Apr 29 06:26:50 rpmi: python3-module-tornado-6.3.1-alt1 sisyphus+319366.100.1.1 1682516456 installed <13>Apr 29 06:26:50 rpmi: python3-module-astor-0.8.1-alt1.1 sisyphus+315877.100.1.1 1677481862 installed <13>Apr 29 06:26:50 rpmi: python3-module-sniffio-1.2.0-alt1 sisyphus+295017.1600.2.1 1644498020 installed <13>Apr 29 06:26:50 rpmi: python3-module-async_generator-1.10-alt3 sisyphus+319053.1600.6.1 1682668582 installed <13>Apr 29 06:26:50 rpmi: python3-module-trio-0.22.0-alt3 sisyphus+319053.2100.6.1 1682668663 installed <13>Apr 29 06:26:50 rpmi: python3-module-dns-1:2.2.0-alt1 sisyphus+294114.1200.10.1 1646418229 installed <13>Apr 29 06:26:50 rpmi: python3-module-async-timeout-4.0.2-alt1 sisyphus+295017.1100.2.1 1644497909 installed <13>Apr 29 06:26:50 rpmi: python3-module-Cheetah-3.3.1-alt1 sisyphus+312482.100.1.1 1672048795 installed <13>Apr 29 06:26:50 rpmi: python3-module-paste-3.5.0-alt1.1 sisyphus+309935.6500.4.1 1668526794 installed <13>Apr 29 06:26:50 rpmi: python3-module-PasteDeploy-1:3.0.1-alt1 sisyphus+308592.100.1.1 1666070463 installed <13>Apr 29 06:26:50 rpmi: python3-module-PasteScript-1:2.0.2-alt2 sisyphus+272468.100.1.1 1621939313 installed <13>Apr 29 06:26:50 rpmi: libyaml2-0.2.5-alt1 sisyphus+278391.100.1.1 1626094932 installed <13>Apr 29 06:26:50 rpmi: python3-module-yaml-6.0-alt2 sisyphus+318894.440.3.1 1682420505 installed <13>Apr 29 06:26:50 rpmi: python3-module-libcst-0.4.7-alt1 sisyphus+306830.500.1.1 1663349904 installed <13>Apr 29 06:26:50 rpmi: libxslt-1.1.37-alt1 sisyphus+307481.100.1.1 1664360525 installed <13>Apr 29 06:26:50 rpmi: python3-module-html5lib-1:1.1-alt1 sisyphus+278096.120.5.1 1626086978 installed <13>Apr 29 06:26:51 rpmi: python3-module-lxml-4.9.2-alt2 sisyphus+319423.100.1.1 1682592963 installed <13>Apr 29 06:26:51 rpmi: python3-module-soupsieve-2.3.1-alt1 sisyphus+297886.100.1.1 1649153481 installed <13>Apr 29 06:26:51 rpmi: python3-module-beautifulsoup4-4.11.2-alt1 sisyphus+316622.100.1.1 1678651404 installed <13>Apr 29 06:26:51 rpmi: libuv-1.44.2-alt1 sisyphus+303845.100.1.1 1658053887 installed <13>Apr 29 06:26:51 rpmi: libqhull-2020.2-alt1 sisyphus+279488.100.1.2 1626573478 installed <13>Apr 29 06:26:51 rpmi: libpython3-3.10.8-alt1.1 sisyphus+311926.100.2.1 1671363746 installed <13>Apr 29 06:26:51 rpmi: libopenjpeg2.0-2.5.0-alt1 sisyphus+299926.300.3.1 1652478844 installed <13>Apr 29 06:26:51 rpmi: libncurses-6.3.20220618-alt1 sisyphus+302449.100.1.1 1655835262 installed <13>Apr 29 06:26:51 rpmi: libtinfo-devel-6.3.20220618-alt1 sisyphus+302449.100.1.1 1655835262 installed <13>Apr 29 06:26:51 rpmi: libncurses-devel-6.3.20220618-alt1 sisyphus+302449.100.1.1 1655835262 installed <13>Apr 29 06:26:52 rpmi: python3-dev-3.10.8-alt1.1 sisyphus+311926.100.2.1 1671363746 installed <13>Apr 29 06:26:52 rpmi: python3-module-setuptools-1:67.7.2-alt1 sisyphus+319053.1300.6.1 1682668497 installed <13>Apr 29 06:26:52 rpmi: libmaxminddb-1.7.1-alt1 sisyphus+310839.100.1.1 1669722011 installed <13>Apr 29 06:26:52 rpmi: python3-module-MaxMindDB-2.2.0-alt1 sisyphus+291245.47100.56.1 1643373899 installed <13>Apr 29 06:26:52 rpmi: liblzo2-2.10-alt2 sisyphus+283836.100.1.1 1629977730 installed <13>Apr 29 06:26:52 rpmi: openldap-common-2.6.4-alt1 sisyphus+317419.100.1.1 1679684487 installed <13>Apr 29 06:26:52 rpmi: libxblas-1.0.248-alt2 sisyphus+285045.40.2.1 1631388462 installed <13>Apr 29 06:26:52 rpmi: libhdf5-103-1.10.6-alt2 sisyphus+271925.100.1.1 1621108484 installed <13>Apr 29 06:26:52 rpmi: libxkbcommon-1.5.0-alt1 sisyphus+312911.100.1.1 1673035570 installed <13>Apr 29 06:26:52 rpmi: libgudev-1:237-alt1 sisyphus+282754.100.1.1 1629006690 installed <13>Apr 29 06:26:52 rpmi: libgomp1-12.2.1-alt2 sisyphus+317777.100.2.2 1682563133 installed <13>Apr 29 06:26:52 rpmi: libimagequant-2.17.0-alt1_1 sisyphus+291138.100.1.1 1638394107 installed <13>Apr 29 06:26:52 rpmi: libquadmath0-12.2.1-alt2 sisyphus+317777.100.2.2 1682563133 installed <13>Apr 29 06:26:52 rpmi: libgfortran5-12.2.1-alt2 sisyphus+317777.100.2.2 1682563133 installed <13>Apr 29 06:26:52 rpmi: liblapack-1:3.8.0-alt7 sisyphus+293726.100.1.1 1642544503 installed <13>Apr 29 06:26:53 rpmi: python3-module-numpy-1:1.22.1-alt3 sisyphus+294708.100.1.1 1643971588 installed <13>Apr 29 06:26:53 rpmi: python3-module-numexpr-1:2.8.3-alt1 sisyphus+303891.100.2.3 1658110787 installed <13>Apr 29 06:26:53 rpmi: python3-module-tables-1:3.8.0-alt3 sisyphus+318923.100.1.1 1682002425 installed <13>Apr 29 06:26:53 rpmi: libev4-4.33-alt2 sisyphus+286828.100.2.3 1634005210 installed <13>Apr 29 06:26:53 rpmi: python3-module-gevent-22.10.1-alt1 sisyphus+316634.100.1.1 1678655455 installed <13>Apr 29 06:26:53 rpmi: libepoxy-1.5.10-alt1 sisyphus+296853.200.2.1 1647631868 installed <13>Apr 29 06:26:53 rpmi: libdatrie-0.2.13-alt1_2 sisyphus+285649.100.1.1 1632260805 installed <13>Apr 29 06:26:53 rpmi: libthai-0.1.29-alt1_1 sisyphus+292947.100.1.1 1641111918 installed <13>Apr 29 06:26:53 rpmi: libverto-0.3.2-alt1_1 sisyphus+279289.100.1.3 1626493872 installed <13>Apr 29 06:26:53 rpmi: liblmdb-0.9.29-alt1.1 sisyphus+306630.100.1.1 1663072361 installed <13>Apr 29 06:26:53 rpmi: libkeyutils-1.6.3-alt1 sisyphus+266061.100.1.1 1612919567 installed <13>Apr 29 06:26:53 rpmi: libcom_err-1.46.4.0.5.4cda-alt1 sisyphus+283826.100.1.1 1629975361 installed <86>Apr 29 06:26:53 groupadd[2563091]: group added to /etc/group: name=_keytab, GID=999 <86>Apr 29 06:26:53 groupadd[2563091]: group added to /etc/gshadow: name=_keytab <86>Apr 29 06:26:53 groupadd[2563091]: new group: name=_keytab, GID=999 <13>Apr 29 06:26:53 rpmi: libkrb5-1.20.1-alt1 sisyphus+306946.1000.5.2 1677793939 installed <13>Apr 29 06:26:53 rpmi: libcups-2.4.2-alt2 sisyphus+318635.100.1.1 1681738783 installed <86>Apr 29 06:26:53 groupadd[2563160]: group added to /etc/group: name=sasl, GID=998 <86>Apr 29 06:26:53 groupadd[2563160]: group added to /etc/gshadow: name=sasl <86>Apr 29 06:26:53 groupadd[2563160]: new group: name=sasl, GID=998 <13>Apr 29 06:26:53 rpmi: libsasl2-3-2.1.27-alt2.2 sisyphus+306372.1000.8.1 1663097332 installed <13>Apr 29 06:26:53 rpmi: libldap2-2.6.4-alt1 sisyphus+317419.100.1.1 1679684507 installed <13>Apr 29 06:26:53 rpmi: libpq5-15.2-alt3 sisyphus+319036.200.1.1 1682108382 installed <13>Apr 29 06:26:53 rpmi: python3-module-psycopg2-2.9.5-alt1 sisyphus+309059.100.1.1 1666861313 installed <13>Apr 29 06:26:53 rpmi: python3-module-eventlet-0.33.3-alt2 sisyphus+318403.100.1.1 1681290339 installed <13>Apr 29 06:26:53 rpmi: python3-module-gunicorn-20.1.0-alt2 sisyphus+297766.100.1.1 1649054912 installed <13>Apr 29 06:26:53 rpmi: python3-module-aiohttp-3.8.3-alt1 sisyphus+313861.40.1.1 1674314145 installed <13>Apr 29 06:26:53 rpmi: python3-module-GeoIP2-4.6.0-alt1 sisyphus+301702.500.2.1 1656091709 installed <13>Apr 29 06:26:54 rpmi: python3-module-django-3.2.18-alt1 sisyphus+317426.100.1.1 1679687773 installed <13>Apr 29 06:26:54 rpmi: python3-module-black-23.3.0-alt2 sisyphus+319053.1500.6.1 1682668557 installed <13>Apr 29 06:26:54 rpmi: usbids-20230428-alt1 sisyphus+319523.100.1.1 1682723593 installed <13>Apr 29 06:26:54 rpmi: libpixman-3:0.42.2-alt1 sisyphus+309549.100.1.1 1667649379 installed <13>Apr 29 06:26:54 rpmi: libbrotlicommon-1.0.9-alt2 sisyphus+278430.100.1.2 1626213212 installed <13>Apr 29 06:26:54 rpmi: libbrotlidec-1.0.9-alt2 sisyphus+278430.100.1.2 1626213212 installed <13>Apr 29 06:26:54 rpmi: libgraphite2-1.3.14-alt2.1 sisyphus+279571.100.1.2 1626605157 installed <13>Apr 29 06:26:54 rpmi: libharfbuzz-7.0.1-alt1 sisyphus+318888.200.2.1 1682012447 installed <13>Apr 29 06:26:54 rpmi: libfreetype-2.13.0-alt1 sisyphus+315092.100.1.1 1676198645 installed <13>Apr 29 06:26:54 rpmi: libfontconfig1-2.14.2-alt7 sisyphus+319291.100.1.1 1682426301 installed <13>Apr 29 06:26:54 rpmi: python3-module-freetype-2.1.0.post1-alt2 sisyphus+249972.100.1.1 1586875515 installed <13>Apr 29 06:26:54 rpmi: libharfbuzz-gobject-7.0.1-alt1 sisyphus+318888.200.2.1 1682012447 installed <13>Apr 29 06:26:54 rpmi: perl-Try-Tiny-0.31-alt1 sisyphus+290597.100.1.1 1637915507 installed <13>Apr 29 06:26:54 rpmi: perl-IO-Socket-IP-0.41-alt1 sisyphus+259012.100.1.2 1601553446 installed <13>Apr 29 06:26:54 rpmi: perl-Compress-Raw-Bzip2-2.204-alt1 sisyphus+314930.100.1.1 1675930902 installed <13>Apr 29 06:26:54 rpmi: perl-IO-Compress-Brotli-2:0.004001-alt3 sisyphus+302124.100.1.1 1655283098 installed <13>Apr 29 06:26:54 rpmi: perl-Clone-0.46-alt1 sisyphus+308850.100.1.3 1666451819 installed <13>Apr 29 06:26:54 rpmi: perl-HTML-Tagset-3.20-alt2 1317725093 installed <13>Apr 29 06:26:54 rpmi: perl-Term-ANSIColor-5.01-alt1 sisyphus+244783.100.1.2 1579747505 installed <13>Apr 29 06:26:54 rpmi: perl-Data-Dump-1.25-alt1 sisyphus+276551.100.1.1 1625126880 installed <13>Apr 29 06:26:54 rpmi: perl-Filter-1.64-alt1 sisyphus+305464.100.1.1 1660815328 installed <13>Apr 29 06:26:54 rpmi: perl-Encode-3.19-alt1 sisyphus+304776.100.1.1 1659623414 installed <13>Apr 29 06:26:54 rpmi: perl-URI-5.17-alt1 sisyphus+310739.100.1.1 1669616836 installed <13>Apr 29 06:26:54 rpmi: perl-IO-Compress-2.204-alt1 sisyphus+315114.100.1.1 1676225908 installed <13>Apr 29 06:26:54 rpmi: perl-Net-HTTP-6.22-alt1 sisyphus+294185.100.1.1 1643275428 installed <13>Apr 29 06:26:54 rpmi: perl-HTML-Parser-3.81-alt1 sisyphus+314462.100.1.1 1675193797 installed <13>Apr 29 06:26:54 rpmi: perl-WWW-RobotRules-6.02-alt1 1329756211 installed <13>Apr 29 06:26:54 rpmi: perl-Encode-Locale-1.05-alt1 1444608613 installed <13>Apr 29 06:26:54 rpmi: perl-IO-HTML-1.004-alt1 sisyphus+258983.100.1.1 1601542619 installed <13>Apr 29 06:26:54 rpmi: perl-HTTP-Message-6.44-alt1 sisyphus+309106.100.1.1 1666913573 installed <13>Apr 29 06:26:54 rpmi: perl-HTTP-Cookies-6.10-alt1 sisyphus+264349.100.1.1 1609891183 installed <13>Apr 29 06:26:54 rpmi: perl-HTTP-Negotiate-6.01-alt1 1329760563 installed <13>Apr 29 06:26:54 rpmi: perl-libwww-6.68-alt1 sisyphus+316051.100.1.1 1677673156 installed <13>Apr 29 06:26:54 rpmi: perl-XML-LibXML-2.0208-alt3 sisyphus+319374.100.1.1 1682520584 installed <13>Apr 29 06:26:54 rpmi: perl-XML-SAX-1.02-alt1 sisyphus+232322.100.1.1 1560758406 installed <13>Apr 29 06:26:54 rpmi: perl-XML-Simple-2.25-alt2 sisyphus+257498.100.1.1 1599324034 installed <13>Apr 29 06:26:54 rpmi: icon-naming-utils-0.8.90-alt1 sisyphus+276851.100.1.1 1625243947 installed <13>Apr 29 06:26:54 rpmi: icon-theme-adwaita-44.0-alt1 sisyphus+317076.600.1.1 1679344664 installed <13>Apr 29 06:26:54 rpmi: libjbig-2.1-alt1 sisyphus+276068.100.1.1 1624815406 installed <13>Apr 29 06:26:54 rpmi: libdeflate-1.18-alt1 sisyphus+317484.100.1.1 1679768614 installed <13>Apr 29 06:26:55 rpmi: libtiff5-4.4.0-alt3 sisyphus+316986.100.1.1 1679241635 installed <13>Apr 29 06:26:55 rpmi: libgdk-pixbuf-locales-2.42.10-alt1 sisyphus+308991.100.1.1 1666721198 installed <13>Apr 29 06:26:55 rpmi: gtk+3-themes-incompatible-3.20-alt3 1461944560 installed <13>Apr 29 06:26:55 rpmi: libdevmapper-1.02.193-alt1 sisyphus+317421.100.1.1 1679684422 installed <13>Apr 29 06:26:55 rpmi: mount-2.38.1-alt1 sisyphus+308470.100.1.1 1665845352 installed <13>Apr 29 06:26:55 rpmi: losetup-2.38.1-alt1 sisyphus+308470.100.1.1 1665845352 installed <13>Apr 29 06:26:55 rpmi: lsblk-2.38.1-alt1 sisyphus+308470.100.1.1 1665845352 installed <13>Apr 29 06:26:55 rpmi: dmsetup-1.02.193-alt1 sisyphus+317421.100.1.1 1679684422 installed <86>Apr 29 06:26:55 groupadd[2563463]: group added to /etc/group: name=tape, GID=997 <86>Apr 29 06:26:55 groupadd[2563463]: group added to /etc/gshadow: name=tape <86>Apr 29 06:26:55 groupadd[2563463]: new group: name=tape, GID=997 <86>Apr 29 06:26:55 groupadd[2563472]: group added to /etc/group: name=dialout, GID=996 <86>Apr 29 06:26:55 groupadd[2563472]: group added to /etc/gshadow: name=dialout <86>Apr 29 06:26:55 groupadd[2563472]: new group: name=dialout, GID=996 <86>Apr 29 06:26:55 groupadd[2563480]: group added to /etc/group: name=input, GID=995 <86>Apr 29 06:26:55 groupadd[2563480]: group added to /etc/gshadow: name=input <86>Apr 29 06:26:55 groupadd[2563480]: new group: name=input, GID=995 <86>Apr 29 06:26:55 groupadd[2563488]: group added to /etc/group: name=video, GID=994 <86>Apr 29 06:26:55 groupadd[2563488]: group added to /etc/gshadow: name=video <86>Apr 29 06:26:55 groupadd[2563488]: new group: name=video, GID=994 <86>Apr 29 06:26:55 groupadd[2563495]: group added to /etc/group: name=render, GID=993 <86>Apr 29 06:26:55 groupadd[2563495]: group added to /etc/gshadow: name=render <86>Apr 29 06:26:55 groupadd[2563495]: new group: name=render, GID=993 <86>Apr 29 06:26:55 groupadd[2563502]: group added to /etc/group: name=sgx, GID=992 <86>Apr 29 06:26:55 groupadd[2563502]: group added to /etc/gshadow: name=sgx <86>Apr 29 06:26:55 groupadd[2563502]: new group: name=sgx, GID=992 <13>Apr 29 06:26:55 rpmi: udev-1:252.7-alt1 sisyphus+316321.100.1.1 1678130459 installed <13>Apr 29 06:26:55 rpmi: desktop-file-utils-0.26-alt3 sisyphus+297027.100.1.1 1648023316 installed <13>Apr 29 06:26:55 rpmi: shared-mime-info-2.2-alt1 sisyphus+297388.100.1.1 1648466617 installed <13>Apr 29 06:26:55 rpmi: gsettings-desktop-schemas-data-44.0-alt1 sisyphus+317076.300.1.1 1679344430 installed <13>Apr 29 06:26:56 rpmi: libgio-2.76.2-alt1 sisyphus+319162.100.1.1 1682278235 installed <13>Apr 29 06:26:56 rpmi: gsettings-desktop-schemas-44.0-alt1 sisyphus+317076.300.1.1 1679344454 installed <13>Apr 29 06:26:56 rpmi: gobject-introspection-1.76.1-alt1 sisyphus+317264.100.1.1 1679555251 installed <13>Apr 29 06:26:56 rpmi: libgdk-pixbuf-2.42.10-alt1 sisyphus+308991.100.1.1 1666721201 installed <13>Apr 29 06:26:56 rpmi: gobject-introspection-x11-1.76.1-alt1 sisyphus+317264.100.1.1 1679555251 installed <13>Apr 29 06:26:56 rpmi: gtk4-update-icon-cache-4.10.3-alt1 sisyphus+319162.200.1.1 1682278544 installed <13>Apr 29 06:26:56 rpmi: libgdk-pixbuf-gir-2.42.10-alt1 sisyphus+308991.100.1.1 1666721201 installed <13>Apr 29 06:26:56 rpmi: libatk-gir-2.48.0-alt1 sisyphus+317076.400.1.1 1679344534 installed <13>Apr 29 06:26:56 rpmi: libharfbuzz-gir-7.0.1-alt1 sisyphus+318888.200.2.1 1682012447 installed <13>Apr 29 06:26:56 rpmi: libdconf-0.40.0-alt1 sisyphus+279299.100.1.2 1626495975 installed <13>Apr 29 06:26:56 rpmi: libjson-glib-1.6.6-alt1 sisyphus+299768.200.2.1 1652264095 installed <13>Apr 29 06:26:56 rpmi: libgusb-0.4.5-alt1 sisyphus+314918.100.1.1 1675925446 installed <13>Apr 29 06:26:56 rpmi: libcolord-1.4.6-alt1 sisyphus+296000.100.1.1 1646050423 installed <13>Apr 29 06:26:56 rpmi: libpolkit-0.120-alt1.qa2 sisyphus+296007.100.1.1 1646053433 installed <86>Apr 29 06:26:56 groupadd[2563625]: group added to /etc/group: name=colord, GID=991 <86>Apr 29 06:26:56 groupadd[2563625]: group added to /etc/gshadow: name=colord <86>Apr 29 06:26:56 groupadd[2563625]: new group: name=colord, GID=991 <86>Apr 29 06:26:56 useradd[2563631]: new user: name=colord, UID=999, GID=991, home=/var/colord, shell=/dev/null, from=none <13>Apr 29 06:26:56 rpmi: colord-1.4.6-alt1 sisyphus+296000.100.1.1 1646050423 installed <13>Apr 29 06:26:56 rpmi: systemd-modules-common-1:252.7-alt1 sisyphus+316321.100.1.1 1678130436 installed <13>Apr 29 06:26:56 rpmi: systemd-sysctl-common-1:252.7-alt1 sisyphus+316321.100.1.1 1678130459 installed <13>Apr 29 06:26:56 rpmi: systemd-tmpfiles-common-1:252.7-alt1 sisyphus+316321.100.1.1 1678130436 installed <13>Apr 29 06:26:56 rpmi: systemd-utils-filetriggers-1:252.7-alt1 sisyphus+316321.100.1.1 1678130436 installed <13>Apr 29 06:26:56 rpmi: systemd-utils-standalone-1:252.7-alt1 sisyphus+316321.100.1.1 1678130459 installed <13>Apr 29 06:26:56 rpmi: dbus-tools-1.14.6-alt1 sisyphus+315497.100.1.1 1676874448 installed <86>Apr 29 06:26:56 groupadd[2563654]: group added to /etc/group: name=messagebus, GID=990 <86>Apr 29 06:26:56 groupadd[2563654]: group added to /etc/gshadow: name=messagebus <86>Apr 29 06:26:56 groupadd[2563654]: new group: name=messagebus, GID=990 <86>Apr 29 06:26:56 useradd[2563660]: new user: name=messagebus, UID=998, GID=990, home=/run/dbus, shell=/dev/null, from=none <13>Apr 29 06:26:56 rpmi: dbus-1.14.6-alt1 sisyphus+315497.100.1.1 1676874448 installed <13>Apr 29 06:26:56 rpmi: dconf-0.40.0-alt1 sisyphus+279299.100.1.2 1626495975 installed <13>Apr 29 06:26:56 rpmi: libgtk+3-schemas-3.24.37-alt1 sisyphus+316153.100.1.1 1677835525 installed <13>Apr 29 06:26:56 rpmi: libX11-locales-3:1.8.4-alt1 sisyphus+314722.100.1.1 1675664300 installed <13>Apr 29 06:26:56 rpmi: libXdmcp-1.1.4-alt1 sisyphus+311188.1000.1.1 1670233860 installed <13>Apr 29 06:26:56 rpmi: libXau-1.0.11-alt1 sisyphus+311428.100.1.1 1670577440 installed <13>Apr 29 06:26:56 rpmi: libxcb-1.15-alt1 sisyphus+299436.300.1.1 1651655490 installed <13>Apr 29 06:26:56 rpmi: libX11-3:1.8.4-alt1 sisyphus+314722.100.1.1 1675664302 installed <13>Apr 29 06:26:56 rpmi: libXext-1.3.5-alt1 sisyphus+309285.100.1.1 1667212413 installed <13>Apr 29 06:26:56 rpmi: libXrender-0.9.11-alt1 sisyphus+308841.100.1.1 1666436131 installed <13>Apr 29 06:26:56 rpmi: libcairo-1:1.16.0-alt2 sisyphus+312186.100.1.1 1671693945 installed <13>Apr 29 06:26:56 rpmi: libcairo-gobject-1:1.16.0-alt2 sisyphus+312186.100.1.1 1671693945 installed <13>Apr 29 06:26:56 rpmi: libXi-1.8-alt1 sisyphus+285490.200.1.1 1632124180 installed <13>Apr 29 06:26:56 rpmi: libXfixes-6.0.0-alt1 sisyphus+284644.300.1.1 1630910333 installed <13>Apr 29 06:26:56 rpmi: python3-module-Pillow-9.4.0-alt2 sisyphus+318894.500.3.1 1682420627 installed <13>Apr 29 06:26:56 rpmi: python3-module-Reportlab-3.6.12-alt1 sisyphus+315569.100.1.1 1676963239 installed <13>Apr 29 06:26:56 rpmi: python3-module-fonttools-4.39.3-alt1 sisyphus+319145.100.1.1 1682259296 installed <13>Apr 29 06:26:56 rpmi: libXcursor-1.2.1-alt1 sisyphus+297765.200.1.1 1649053934 installed <13>Apr 29 06:26:56 rpmi: libat-spi2-core-2.48.0-alt1 sisyphus+317076.400.1.1 1679344534 installed <13>Apr 29 06:26:57 rpmi: at-spi2-atk-2.48.0-alt1 sisyphus+317076.400.1.1 1679344534 installed <13>Apr 29 06:26:57 rpmi: python3-module-pycairo-1.23.0-alt1.1 sisyphus+319444.100.1.1 1682610076 installed <13>Apr 29 06:26:57 rpmi: libXft-2.3.7-alt1 sisyphus+310164.100.1.1 1668680609 installed <13>Apr 29 06:26:57 rpmi: libpango-1.50.14-alt1 sisyphus+316117.100.1.1 1677780554 installed <13>Apr 29 06:26:57 rpmi: libpango-gir-1.50.14-alt1 sisyphus+316117.100.1.1 1677780554 installed <13>Apr 29 06:26:57 rpmi: libXrandr-1.5.3-alt1 sisyphus+310375.100.1.1 1669010698 installed <13>Apr 29 06:26:57 rpmi: libXinerama-1.1.5-alt1 sisyphus+309287.100.1.1 1667213209 installed <13>Apr 29 06:26:57 rpmi: libXcomposite-0.4.6-alt1 sisyphus+311188.200.1.1 1670233684 installed <13>Apr 29 06:26:57 rpmi: libXdamage-1.1.6-alt1 sisyphus+311188.300.1.1 1670233713 installed <13>Apr 29 06:26:57 rpmi: libgtk+3-3.24.37-alt1 sisyphus+316153.100.1.1 1677835558 installed <13>Apr 29 06:26:57 rpmi: libgtk+3-gir-3.24.37-alt1 sisyphus+316153.100.1.1 1677835558 installed <13>Apr 29 06:26:57 rpmi: python3-module-pygobject3-3.44.1-alt1 sisyphus+317423.100.1.1 1679685690 installed <13>Apr 29 06:26:57 rpmi: python3-module-mpl_toolkits-3.7.0-alt1 sisyphus+315348.200.2.1 1676627515 installed <13>Apr 29 06:26:57 rpmi: python3-module-matplotlib-cairo-3.7.0-alt1 sisyphus+315348.200.2.1 1676627515 installed <13>Apr 29 06:26:57 rpmi: python3-module-matplotlib-gtk3-3.7.0-alt1 sisyphus+315348.200.2.1 1676627515 installed <13>Apr 29 06:26:58 rpmi: python3-module-matplotlib-3.7.0-alt1 sisyphus+315348.200.2.1 1676627515 installed <13>Apr 29 06:26:59 rpmi: python3-module-scipy-1.10.1-alt1 sisyphus+315992.100.1.1 1677594052 installed <13>Apr 29 06:27:00 rpmi: python3-module-pandas-1.3.1-alt3 sisyphus+291245.63600.59.1 1643609234 installed <13>Apr 29 06:27:00 rpmi: python3-module-hypothesis-6.68.1-alt1 sisyphus+314493.4040.14.1 1676642460 installed <13>Apr 29 06:27:00 rpmi: python3-module-jsonschema-4.17.3-alt2 sisyphus+314007.100.1.1 1674488080 installed <13>Apr 29 06:27:00 rpmi: python3-module-wheel-0.40.0-alt1 sisyphus+318890.200.2.1 1682002149 installed <13>Apr 29 06:27:00 rpmi: python3-module-jmespath-1.0.1-alt1 sisyphus+317988.100.2.1 1680612150 installed Building target platforms: i586 Building for target i586 Wrote: /usr/src/in/nosrpm/python3-module-botocore-1.27.90-alt1.nosrc.rpm (w1.gzdio) <13>Apr 29 06:27:05 rpmi: python3-module-system-seed-wheels-0.0.1-alt1 sisyphus+270533.400.6.1 1619683380 installed <13>Apr 29 06:27:05 rpmi: python3-module-filelock-3.12.0-alt1 sisyphus+319053.100.6.1 1682668225 installed <13>Apr 29 06:27:05 rpmi: python3-module-pip-wheel-23.1.1-alt1 sisyphus+319202.100.1.1 1682337693 installed <13>Apr 29 06:27:05 rpmi: python3-module-setuptools-wheel-1:67.7.2-alt1 sisyphus+319053.1300.6.1 1682668497 installed <13>Apr 29 06:27:05 rpmi: python3-module-wheel-wheel-0.40.0-alt1 sisyphus+318890.200.2.1 1682002149 installed <13>Apr 29 06:27:05 rpmi: python3-module-system-seed-wheels-wheels-0.0.1-alt1 sisyphus+270533.400.6.1 1619683380 installed <13>Apr 29 06:27:05 rpmi: python3-module-distlib-0.3.6-alt1 sisyphus+306796.100.1.1 1663166230 installed <13>Apr 29 06:27:05 rpmi: python3-module-virtualenv-20.20.0-alt1 sisyphus+316023.100.2.1 1677667762 installed <13>Apr 29 06:27:05 rpmi: python3-module-apipkg-1.5-alt1 sisyphus+275892.100.2.1 1624872742 installed <13>Apr 29 06:27:05 rpmi: python3-module-py-1.11.0-alt1 sisyphus+295927.100.2.1 1646050822 installed <13>Apr 29 06:27:05 rpmi: python3-module-tox-3.27.1-alt1 sisyphus+309865.500.3.1 1668591286 installed <13>Apr 29 06:27:05 rpmi: python3-module-tox-console-scripts-0.3.2-alt1 sisyphus+301745.100.2.1 1655211258 installed <13>Apr 29 06:27:05 rpmi: python3-module-tox-no-deps-0.2.0-alt1 sisyphus+301745.200.2.1 1655211304 installed <13>Apr 29 06:27:05 rpmi: python3-module-pyproject-installer-0.5.0-alt1 sisyphus+318506.100.1.1 1681480777 installed Installing python3-module-botocore-1.27.90-alt1.src.rpm Building target platforms: i586 Building for target i586 Executing(%prep): /bin/sh -e /usr/src/tmp/rpm-tmp.93531 + umask 022 + /bin/mkdir -p /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + rm -rf python3-module-botocore-1.27.90 + echo 'Source #0 (python3-module-botocore-1.27.90.tar):' Source #0 (python3-module-botocore-1.27.90.tar): + /bin/tar -xf /usr/src/RPM/SOURCES/python3-module-botocore-1.27.90.tar + cd python3-module-botocore-1.27.90 + /bin/chmod -c -Rf u+rwX,go-w . + echo 'Patch #0 (python3-module-botocore-1.27.90-alt.patch):' Patch #0 (python3-module-botocore-1.27.90-alt.patch): + /usr/bin/patch -p1 patching file botocore/httpsession.py patching file tox.ini + rm botocore/cacert.pem + VENDORED_PATH=botocore/vendored + UNVENDORED_PATH=botocore/vendored/__init__.py + rm -r botocore/vendored + mkdir botocore/vendored + cp /usr/src/RPM/SOURCES/debundler.py.in botocore/vendored/__init__.py + sed -i -e 's/@VENDORED_ROOT@/"botocore.vendored"/' -e 's/@VENDORED_FAKE_PACKAGES@/{"requests.packages"}/' botocore/vendored/__init__.py + exit 0 Executing(%build): /bin/sh -e /usr/src/tmp/rpm-tmp.7522 + umask 022 + /bin/mkdir -p /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + cd python3-module-botocore-1.27.90 + export 'CFLAGS=-pipe -frecord-gcc-switches -Wall -g -O2 -flto=auto -march=i586 -mtune=generic' + CFLAGS='-pipe -frecord-gcc-switches -Wall -g -O2 -flto=auto -march=i586 -mtune=generic' + export 'CXXFLAGS=-pipe -frecord-gcc-switches -Wall -g -O2 -flto=auto -march=i586 -mtune=generic' + CXXFLAGS='-pipe -frecord-gcc-switches -Wall -g -O2 -flto=auto -march=i586 -mtune=generic' + export 'FFLAGS=-pipe -frecord-gcc-switches -Wall -g -O2 -flto=auto -march=i586 -mtune=generic' + FFLAGS='-pipe -frecord-gcc-switches -Wall -g -O2 -flto=auto -march=i586 -mtune=generic' + /usr/bin/python3 -m pyproject_installer -v build INFO : pyproject_installer.build_cmd._build : Building wheel INFO : pyproject_installer.build_cmd._build : Source tree: /usr/src/RPM/BUILD/python3-module-botocore-1.27.90 INFO : pyproject_installer.build_cmd._build : Output dir: /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/dist DEBUG : pyproject_installer.lib.build_backend : Validating source path DEBUG : pyproject_installer.lib.build_backend : Checking for PEP517 spec DEBUG : pyproject_installer.lib.build_backend : Parsing configuration file: /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/pyproject.toml INFO : pyproject_installer.lib.build_backend : build-system was not found, using defaults INFO : backend_caller.py : Calling hook build_wheel in subprocess INFO : backend_caller.py : Build backend: setuptools.build_meta:__legacy__ INFO : backend_caller.py : Hook args: ['/usr/src/RPM/BUILD/python3-module-botocore-1.27.90/dist'] INFO : backend_caller.py : Hook kwargs: {'config_settings': None} INFO : root : running bdist_wheel INFO : root : running build INFO : root : running build_py INFO : root : creating build INFO : root : creating build/lib INFO : root : creating build/lib/botocore INFO : root : copying botocore/httpsession.py -> build/lib/botocore INFO : root : copying botocore/waiter.py -> build/lib/botocore INFO : root : copying botocore/validate.py -> build/lib/botocore INFO : root : copying botocore/utils.py -> build/lib/botocore INFO : root : copying botocore/translate.py -> build/lib/botocore INFO : root : copying botocore/tokens.py -> build/lib/botocore INFO : root : copying botocore/stub.py -> build/lib/botocore INFO : root : copying botocore/signers.py -> build/lib/botocore INFO : root : copying botocore/session.py -> build/lib/botocore INFO : root : copying botocore/serialize.py -> build/lib/botocore INFO : root : copying botocore/retryhandler.py -> build/lib/botocore INFO : root : copying botocore/response.py -> build/lib/botocore INFO : root : copying botocore/regions.py -> build/lib/botocore INFO : root : copying botocore/parsers.py -> build/lib/botocore INFO : root : copying botocore/paginate.py -> build/lib/botocore INFO : root : copying botocore/monitoring.py -> build/lib/botocore INFO : root : copying botocore/model.py -> build/lib/botocore INFO : root : copying botocore/loaders.py -> build/lib/botocore INFO : root : copying botocore/httpchecksum.py -> build/lib/botocore INFO : root : copying botocore/hooks.py -> build/lib/botocore INFO : root : copying botocore/history.py -> build/lib/botocore INFO : root : copying botocore/handlers.py -> build/lib/botocore INFO : root : copying botocore/exceptions.py -> build/lib/botocore INFO : root : copying botocore/eventstream.py -> build/lib/botocore INFO : root : copying botocore/errorfactory.py -> build/lib/botocore INFO : root : copying botocore/endpoint_provider.py -> build/lib/botocore INFO : root : copying botocore/endpoint.py -> build/lib/botocore INFO : root : copying botocore/discovery.py -> build/lib/botocore INFO : root : copying botocore/credentials.py -> build/lib/botocore INFO : root : copying botocore/configprovider.py -> build/lib/botocore INFO : root : copying botocore/configloader.py -> build/lib/botocore INFO : root : copying botocore/config.py -> build/lib/botocore INFO : root : copying botocore/compat.py -> build/lib/botocore INFO : root : copying botocore/client.py -> build/lib/botocore INFO : root : copying botocore/awsrequest.py -> build/lib/botocore INFO : root : copying botocore/auth.py -> build/lib/botocore INFO : root : copying botocore/args.py -> build/lib/botocore INFO : root : copying botocore/__init__.py -> build/lib/botocore INFO : root : creating build/lib/botocore/vendored INFO : root : copying botocore/vendored/__init__.py -> build/lib/botocore/vendored INFO : root : creating build/lib/botocore/retries INFO : root : copying botocore/retries/throttling.py -> build/lib/botocore/retries INFO : root : copying botocore/retries/standard.py -> build/lib/botocore/retries INFO : root : copying botocore/retries/special.py -> build/lib/botocore/retries INFO : root : copying botocore/retries/quota.py -> build/lib/botocore/retries INFO : root : copying botocore/retries/bucket.py -> build/lib/botocore/retries INFO : root : copying botocore/retries/base.py -> build/lib/botocore/retries INFO : root : copying botocore/retries/adaptive.py -> build/lib/botocore/retries INFO : root : copying botocore/retries/__init__.py -> build/lib/botocore/retries INFO : root : creating build/lib/botocore/docs INFO : root : copying botocore/docs/waiter.py -> build/lib/botocore/docs INFO : root : copying botocore/docs/utils.py -> build/lib/botocore/docs INFO : root : copying botocore/docs/sharedexample.py -> build/lib/botocore/docs INFO : root : copying botocore/docs/shape.py -> build/lib/botocore/docs INFO : root : copying botocore/docs/service.py -> build/lib/botocore/docs INFO : root : copying botocore/docs/params.py -> build/lib/botocore/docs INFO : root : copying botocore/docs/paginator.py -> build/lib/botocore/docs INFO : root : copying botocore/docs/method.py -> build/lib/botocore/docs INFO : root : copying botocore/docs/example.py -> build/lib/botocore/docs INFO : root : copying botocore/docs/docstring.py -> build/lib/botocore/docs INFO : root : copying botocore/docs/client.py -> build/lib/botocore/docs INFO : root : copying botocore/docs/__init__.py -> build/lib/botocore/docs INFO : root : creating build/lib/botocore/crt INFO : root : copying botocore/crt/auth.py -> build/lib/botocore/crt INFO : root : copying botocore/crt/__init__.py -> build/lib/botocore/crt INFO : root : creating build/lib/botocore/docs/bcdoc INFO : root : copying botocore/docs/bcdoc/style.py -> build/lib/botocore/docs/bcdoc INFO : root : copying botocore/docs/bcdoc/restdoc.py -> build/lib/botocore/docs/bcdoc INFO : root : copying botocore/docs/bcdoc/docstringparser.py -> build/lib/botocore/docs/bcdoc INFO : root : copying botocore/docs/bcdoc/__init__.py -> build/lib/botocore/docs/bcdoc INFO : root : running egg_info INFO : root : creating botocore.egg-info INFO : root : writing botocore.egg-info/PKG-INFO INFO : root : writing dependency_links to botocore.egg-info/dependency_links.txt INFO : root : writing requirements to botocore.egg-info/requires.txt INFO : root : writing top-level names to botocore.egg-info/top_level.txt INFO : root : writing manifest file 'botocore.egg-info/SOURCES.txt' INFO : root : reading manifest file 'botocore.egg-info/SOURCES.txt' INFO : root : reading manifest template 'MANIFEST.in' WARNING : root : warning: no files found matching 'botocore/cacert.pem' WARNING : root : warning: no files found matching 'botocore/vendored/requests/cacert.pem' WARNING : root : no previously-included directories found matching 'docs/build' INFO : root : adding license file 'LICENSE.txt' INFO : root : adding license file 'NOTICE' INFO : root : writing manifest file 'botocore.egg-info/SOURCES.txt' /usr/lib/python3/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/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/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/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/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.alexaforbusiness' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.alexaforbusiness' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.alexaforbusiness' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.alexaforbusiness' to be distributed and are already explicitly excluding 'botocore.data.alexaforbusiness' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.backupstorage' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.backupstorage' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.backupstorage' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.backupstorage' to be distributed and are already explicitly excluding 'botocore.data.backupstorage' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.codestar' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.codestar' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.codestar' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.codestar' to be distributed and are already explicitly excluding 'botocore.data.codestar' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.elastictranscoder' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.elastictranscoder' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.elastictranscoder' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.elastictranscoder' to be distributed and are already explicitly excluding 'botocore.data.elastictranscoder' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/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/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/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/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/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/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.evidently' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.evidently' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.evidently' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.evidently' to be distributed and are already explicitly excluding 'botocore.data.evidently' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/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/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/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/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/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/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/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/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/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/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.gamesparks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.gamesparks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.gamesparks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.gamesparks' to be distributed and are already explicitly excluding 'botocore.data.gamesparks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/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/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/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/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/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/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/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/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/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/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/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.honeycode' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.honeycode' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.honeycode' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.honeycode' to be distributed and are already explicitly excluding 'botocore.data.honeycode' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/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/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/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/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/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/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/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/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.iotanalytics' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.iotanalytics' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.iotanalytics' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.iotanalytics' to be distributed and are already explicitly excluding 'botocore.data.iotanalytics' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/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/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/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.iotfleethub' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.iotfleethub' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.iotfleethub' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.iotfleethub' to be distributed and are already explicitly excluding 'botocore.data.iotfleethub' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.lookoutmetrics' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.lookoutmetrics' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.lookoutmetrics' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.lookoutmetrics' to be distributed and are already explicitly excluding 'botocore.data.lookoutmetrics' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.lookoutvision' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.lookoutvision' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.lookoutvision' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.lookoutvision' to be distributed and are already explicitly excluding 'botocore.data.lookoutvision' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/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/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/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.macie' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.macie' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.macie' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.macie' to be distributed and are already explicitly excluding 'botocore.data.macie' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.mobile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.mobile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.mobile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.mobile' to be distributed and are already explicitly excluding 'botocore.data.mobile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/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/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/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/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/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/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.nimble' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.nimble' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.nimble' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.nimble' to be distributed and are already explicitly excluding 'botocore.data.nimble' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/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/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.opsworks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.opsworks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.opsworks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.opsworks' to be distributed and are already explicitly excluding 'botocore.data.opsworks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.opsworkscm' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.opsworkscm' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.opsworkscm' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.opsworkscm' to be distributed and are already explicitly excluding 'botocore.data.opsworkscm' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/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/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/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/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/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/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/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/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/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.privatenetworks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.privatenetworks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.privatenetworks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.privatenetworks' to be distributed and are already explicitly excluding 'botocore.data.privatenetworks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/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/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.qldb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.qldb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.qldb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.qldb' to be distributed and are already explicitly excluding 'botocore.data.qldb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/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/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/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/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/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/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/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/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/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.robomaker' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.robomaker' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.robomaker' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.robomaker' to be distributed and are already explicitly excluding 'botocore.data.robomaker' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.sms' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.sms' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.sms' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.sms' to be distributed and are already explicitly excluding 'botocore.data.sms' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'botocore.data.worklink' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'botocore.data.worklink' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'botocore.data.worklink' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'botocore.data.worklink' to be distributed and are already explicitly excluding 'botocore.data.worklink' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/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/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/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/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) INFO : root : creating build/lib/botocore/data INFO : root : copying botocore/data/_retry.json -> build/lib/botocore/data INFO : root : copying botocore/data/endpoints.json -> build/lib/botocore/data INFO : root : copying botocore/data/partitions.json -> build/lib/botocore/data INFO : root : copying botocore/data/sdk-default-configuration.json -> build/lib/botocore/data INFO : root : creating build/lib/botocore/data/accessanalyzer INFO : root : creating build/lib/botocore/data/accessanalyzer/2019-11-01 INFO : root : copying botocore/data/accessanalyzer/2019-11-01/examples-1.json -> build/lib/botocore/data/accessanalyzer/2019-11-01 INFO : root : copying botocore/data/accessanalyzer/2019-11-01/paginators-1.json -> build/lib/botocore/data/accessanalyzer/2019-11-01 INFO : root : copying botocore/data/accessanalyzer/2019-11-01/service-2.json -> build/lib/botocore/data/accessanalyzer/2019-11-01 INFO : root : creating build/lib/botocore/data/account INFO : root : creating build/lib/botocore/data/account/2021-02-01 INFO : root : copying botocore/data/account/2021-02-01/examples-1.json -> build/lib/botocore/data/account/2021-02-01 INFO : root : copying botocore/data/account/2021-02-01/paginators-1.json -> build/lib/botocore/data/account/2021-02-01 INFO : root : copying botocore/data/account/2021-02-01/service-2.json -> build/lib/botocore/data/account/2021-02-01 INFO : root : creating build/lib/botocore/data/acm-pca INFO : root : creating build/lib/botocore/data/acm-pca/2017-08-22 INFO : root : copying botocore/data/acm-pca/2017-08-22/examples-1.json -> build/lib/botocore/data/acm-pca/2017-08-22 INFO : root : copying botocore/data/acm-pca/2017-08-22/paginators-1.json -> build/lib/botocore/data/acm-pca/2017-08-22 INFO : root : copying botocore/data/acm-pca/2017-08-22/service-2.json -> build/lib/botocore/data/acm-pca/2017-08-22 INFO : root : copying botocore/data/acm-pca/2017-08-22/waiters-2.json -> build/lib/botocore/data/acm-pca/2017-08-22 INFO : root : creating build/lib/botocore/data/acm INFO : root : creating build/lib/botocore/data/acm/2015-12-08 INFO : root : copying botocore/data/acm/2015-12-08/examples-1.json -> build/lib/botocore/data/acm/2015-12-08 INFO : root : copying botocore/data/acm/2015-12-08/paginators-1.json -> build/lib/botocore/data/acm/2015-12-08 INFO : root : copying botocore/data/acm/2015-12-08/service-2.json -> build/lib/botocore/data/acm/2015-12-08 INFO : root : copying botocore/data/acm/2015-12-08/waiters-2.json -> build/lib/botocore/data/acm/2015-12-08 INFO : root : creating build/lib/botocore/data/alexaforbusiness INFO : root : creating build/lib/botocore/data/alexaforbusiness/2017-11-09 INFO : root : copying botocore/data/alexaforbusiness/2017-11-09/examples-1.json -> build/lib/botocore/data/alexaforbusiness/2017-11-09 INFO : root : copying botocore/data/alexaforbusiness/2017-11-09/paginators-1.json -> build/lib/botocore/data/alexaforbusiness/2017-11-09 INFO : root : copying botocore/data/alexaforbusiness/2017-11-09/service-2.json -> build/lib/botocore/data/alexaforbusiness/2017-11-09 INFO : root : creating build/lib/botocore/data/amp INFO : root : creating build/lib/botocore/data/amp/2020-08-01 INFO : root : copying botocore/data/amp/2020-08-01/examples-1.json -> build/lib/botocore/data/amp/2020-08-01 INFO : root : copying botocore/data/amp/2020-08-01/paginators-1.json -> build/lib/botocore/data/amp/2020-08-01 INFO : root : copying botocore/data/amp/2020-08-01/service-2.json -> build/lib/botocore/data/amp/2020-08-01 INFO : root : copying botocore/data/amp/2020-08-01/waiters-2.json -> build/lib/botocore/data/amp/2020-08-01 INFO : root : creating build/lib/botocore/data/amplify INFO : root : creating build/lib/botocore/data/amplify/2017-07-25 INFO : root : copying botocore/data/amplify/2017-07-25/examples-1.json -> build/lib/botocore/data/amplify/2017-07-25 INFO : root : copying botocore/data/amplify/2017-07-25/paginators-1.json -> build/lib/botocore/data/amplify/2017-07-25 INFO : root : copying botocore/data/amplify/2017-07-25/service-2.json -> build/lib/botocore/data/amplify/2017-07-25 INFO : root : creating build/lib/botocore/data/amplifybackend INFO : root : creating build/lib/botocore/data/amplifybackend/2020-08-11 INFO : root : copying botocore/data/amplifybackend/2020-08-11/paginators-1.json -> build/lib/botocore/data/amplifybackend/2020-08-11 INFO : root : copying botocore/data/amplifybackend/2020-08-11/service-2.json -> build/lib/botocore/data/amplifybackend/2020-08-11 INFO : root : creating build/lib/botocore/data/amplifyuibuilder INFO : root : creating build/lib/botocore/data/amplifyuibuilder/2021-08-11 INFO : root : copying botocore/data/amplifyuibuilder/2021-08-11/examples-1.json -> build/lib/botocore/data/amplifyuibuilder/2021-08-11 INFO : root : copying botocore/data/amplifyuibuilder/2021-08-11/paginators-1.json -> build/lib/botocore/data/amplifyuibuilder/2021-08-11 INFO : root : copying botocore/data/amplifyuibuilder/2021-08-11/service-2.json -> build/lib/botocore/data/amplifyuibuilder/2021-08-11 INFO : root : creating build/lib/botocore/data/apigateway INFO : root : creating build/lib/botocore/data/apigateway/2015-07-09 INFO : root : copying botocore/data/apigateway/2015-07-09/examples-1.json -> build/lib/botocore/data/apigateway/2015-07-09 INFO : root : copying botocore/data/apigateway/2015-07-09/paginators-1.json -> build/lib/botocore/data/apigateway/2015-07-09 INFO : root : copying botocore/data/apigateway/2015-07-09/service-2.json -> build/lib/botocore/data/apigateway/2015-07-09 INFO : root : creating build/lib/botocore/data/apigatewaymanagementapi INFO : root : creating build/lib/botocore/data/apigatewaymanagementapi/2018-11-29 INFO : root : copying botocore/data/apigatewaymanagementapi/2018-11-29/paginators-1.json -> build/lib/botocore/data/apigatewaymanagementapi/2018-11-29 INFO : root : copying botocore/data/apigatewaymanagementapi/2018-11-29/service-2.json -> build/lib/botocore/data/apigatewaymanagementapi/2018-11-29 INFO : root : creating build/lib/botocore/data/apigatewayv2 INFO : root : creating build/lib/botocore/data/apigatewayv2/2018-11-29 INFO : root : copying botocore/data/apigatewayv2/2018-11-29/paginators-1.json -> build/lib/botocore/data/apigatewayv2/2018-11-29 INFO : root : copying botocore/data/apigatewayv2/2018-11-29/service-2.json -> build/lib/botocore/data/apigatewayv2/2018-11-29 INFO : root : creating build/lib/botocore/data/appconfig INFO : root : creating build/lib/botocore/data/appconfig/2019-10-09 INFO : root : copying botocore/data/appconfig/2019-10-09/examples-1.json -> build/lib/botocore/data/appconfig/2019-10-09 INFO : root : copying botocore/data/appconfig/2019-10-09/paginators-1.json -> build/lib/botocore/data/appconfig/2019-10-09 INFO : root : copying botocore/data/appconfig/2019-10-09/service-2.json -> build/lib/botocore/data/appconfig/2019-10-09 INFO : root : creating build/lib/botocore/data/appconfigdata INFO : root : creating build/lib/botocore/data/appconfigdata/2021-11-11 INFO : root : copying botocore/data/appconfigdata/2021-11-11/examples-1.json -> build/lib/botocore/data/appconfigdata/2021-11-11 INFO : root : copying botocore/data/appconfigdata/2021-11-11/paginators-1.json -> build/lib/botocore/data/appconfigdata/2021-11-11 INFO : root : copying botocore/data/appconfigdata/2021-11-11/service-2.json -> build/lib/botocore/data/appconfigdata/2021-11-11 INFO : root : creating build/lib/botocore/data/appflow INFO : root : creating build/lib/botocore/data/appflow/2020-08-23 INFO : root : copying botocore/data/appflow/2020-08-23/examples-1.json -> build/lib/botocore/data/appflow/2020-08-23 INFO : root : copying botocore/data/appflow/2020-08-23/paginators-1.json -> build/lib/botocore/data/appflow/2020-08-23 INFO : root : copying botocore/data/appflow/2020-08-23/service-2.json -> build/lib/botocore/data/appflow/2020-08-23 INFO : root : creating build/lib/botocore/data/appintegrations INFO : root : creating build/lib/botocore/data/appintegrations/2020-07-29 INFO : root : copying botocore/data/appintegrations/2020-07-29/examples-1.json -> build/lib/botocore/data/appintegrations/2020-07-29 INFO : root : copying botocore/data/appintegrations/2020-07-29/paginators-1.json -> build/lib/botocore/data/appintegrations/2020-07-29 INFO : root : copying botocore/data/appintegrations/2020-07-29/service-2.json -> build/lib/botocore/data/appintegrations/2020-07-29 INFO : root : creating build/lib/botocore/data/application-autoscaling INFO : root : creating build/lib/botocore/data/application-autoscaling/2016-02-06 INFO : root : copying botocore/data/application-autoscaling/2016-02-06/examples-1.json -> build/lib/botocore/data/application-autoscaling/2016-02-06 INFO : root : copying botocore/data/application-autoscaling/2016-02-06/paginators-1.json -> build/lib/botocore/data/application-autoscaling/2016-02-06 INFO : root : copying botocore/data/application-autoscaling/2016-02-06/service-2.json -> build/lib/botocore/data/application-autoscaling/2016-02-06 INFO : root : creating build/lib/botocore/data/application-insights INFO : root : creating build/lib/botocore/data/application-insights/2018-11-25 INFO : root : copying botocore/data/application-insights/2018-11-25/examples-1.json -> build/lib/botocore/data/application-insights/2018-11-25 INFO : root : copying botocore/data/application-insights/2018-11-25/paginators-1.json -> build/lib/botocore/data/application-insights/2018-11-25 INFO : root : copying botocore/data/application-insights/2018-11-25/service-2.json -> build/lib/botocore/data/application-insights/2018-11-25 INFO : root : creating build/lib/botocore/data/applicationcostprofiler INFO : root : creating build/lib/botocore/data/applicationcostprofiler/2020-09-10 INFO : root : copying botocore/data/applicationcostprofiler/2020-09-10/examples-1.json -> build/lib/botocore/data/applicationcostprofiler/2020-09-10 INFO : root : copying botocore/data/applicationcostprofiler/2020-09-10/paginators-1.json -> build/lib/botocore/data/applicationcostprofiler/2020-09-10 INFO : root : copying botocore/data/applicationcostprofiler/2020-09-10/service-2.json -> build/lib/botocore/data/applicationcostprofiler/2020-09-10 INFO : root : creating build/lib/botocore/data/appmesh INFO : root : creating build/lib/botocore/data/appmesh/2018-10-01 INFO : root : copying botocore/data/appmesh/2018-10-01/examples-1.json -> build/lib/botocore/data/appmesh/2018-10-01 INFO : root : copying botocore/data/appmesh/2018-10-01/paginators-1.json -> build/lib/botocore/data/appmesh/2018-10-01 INFO : root : copying botocore/data/appmesh/2018-10-01/service-2.json -> build/lib/botocore/data/appmesh/2018-10-01 INFO : root : creating build/lib/botocore/data/appmesh/2019-01-25 INFO : root : copying botocore/data/appmesh/2019-01-25/examples-1.json -> build/lib/botocore/data/appmesh/2019-01-25 INFO : root : copying botocore/data/appmesh/2019-01-25/paginators-1.json -> build/lib/botocore/data/appmesh/2019-01-25 INFO : root : copying botocore/data/appmesh/2019-01-25/service-2.json -> build/lib/botocore/data/appmesh/2019-01-25 INFO : root : creating build/lib/botocore/data/apprunner INFO : root : creating build/lib/botocore/data/apprunner/2020-05-15 INFO : root : copying botocore/data/apprunner/2020-05-15/examples-1.json -> build/lib/botocore/data/apprunner/2020-05-15 INFO : root : copying botocore/data/apprunner/2020-05-15/paginators-1.json -> build/lib/botocore/data/apprunner/2020-05-15 INFO : root : copying botocore/data/apprunner/2020-05-15/service-2.json -> build/lib/botocore/data/apprunner/2020-05-15 INFO : root : creating build/lib/botocore/data/appstream INFO : root : creating build/lib/botocore/data/appstream/2016-12-01 INFO : root : copying botocore/data/appstream/2016-12-01/examples-1.json -> build/lib/botocore/data/appstream/2016-12-01 INFO : root : copying botocore/data/appstream/2016-12-01/paginators-1.json -> build/lib/botocore/data/appstream/2016-12-01 INFO : root : copying botocore/data/appstream/2016-12-01/service-2.json -> build/lib/botocore/data/appstream/2016-12-01 INFO : root : copying botocore/data/appstream/2016-12-01/waiters-2.json -> build/lib/botocore/data/appstream/2016-12-01 INFO : root : creating build/lib/botocore/data/appsync INFO : root : creating build/lib/botocore/data/appsync/2017-07-25 INFO : root : copying botocore/data/appsync/2017-07-25/examples-1.json -> build/lib/botocore/data/appsync/2017-07-25 INFO : root : copying botocore/data/appsync/2017-07-25/paginators-1.json -> build/lib/botocore/data/appsync/2017-07-25 INFO : root : copying botocore/data/appsync/2017-07-25/service-2.json -> build/lib/botocore/data/appsync/2017-07-25 INFO : root : creating build/lib/botocore/data/athena INFO : root : creating build/lib/botocore/data/athena/2017-05-18 INFO : root : copying botocore/data/athena/2017-05-18/examples-1.json -> build/lib/botocore/data/athena/2017-05-18 INFO : root : copying botocore/data/athena/2017-05-18/paginators-1.json -> build/lib/botocore/data/athena/2017-05-18 INFO : root : copying botocore/data/athena/2017-05-18/service-2.json -> build/lib/botocore/data/athena/2017-05-18 INFO : root : creating build/lib/botocore/data/auditmanager INFO : root : creating build/lib/botocore/data/auditmanager/2017-07-25 INFO : root : copying botocore/data/auditmanager/2017-07-25/examples-1.json -> build/lib/botocore/data/auditmanager/2017-07-25 INFO : root : copying botocore/data/auditmanager/2017-07-25/paginators-1.json -> build/lib/botocore/data/auditmanager/2017-07-25 INFO : root : copying botocore/data/auditmanager/2017-07-25/service-2.json -> build/lib/botocore/data/auditmanager/2017-07-25 INFO : root : creating build/lib/botocore/data/autoscaling-plans INFO : root : creating build/lib/botocore/data/autoscaling-plans/2018-01-06 INFO : root : copying botocore/data/autoscaling-plans/2018-01-06/examples-1.json -> build/lib/botocore/data/autoscaling-plans/2018-01-06 INFO : root : copying botocore/data/autoscaling-plans/2018-01-06/paginators-1.json -> build/lib/botocore/data/autoscaling-plans/2018-01-06 INFO : root : copying botocore/data/autoscaling-plans/2018-01-06/service-2.json -> build/lib/botocore/data/autoscaling-plans/2018-01-06 INFO : root : creating build/lib/botocore/data/autoscaling INFO : root : creating build/lib/botocore/data/autoscaling/2011-01-01 INFO : root : copying botocore/data/autoscaling/2011-01-01/examples-1.json -> build/lib/botocore/data/autoscaling/2011-01-01 INFO : root : copying botocore/data/autoscaling/2011-01-01/paginators-1.json -> build/lib/botocore/data/autoscaling/2011-01-01 INFO : root : copying botocore/data/autoscaling/2011-01-01/service-2.json -> build/lib/botocore/data/autoscaling/2011-01-01 INFO : root : creating build/lib/botocore/data/backup-gateway INFO : root : creating build/lib/botocore/data/backup-gateway/2021-01-01 INFO : root : copying botocore/data/backup-gateway/2021-01-01/examples-1.json -> build/lib/botocore/data/backup-gateway/2021-01-01 INFO : root : copying botocore/data/backup-gateway/2021-01-01/paginators-1.json -> build/lib/botocore/data/backup-gateway/2021-01-01 INFO : root : copying botocore/data/backup-gateway/2021-01-01/service-2.json -> build/lib/botocore/data/backup-gateway/2021-01-01 INFO : root : creating build/lib/botocore/data/backup INFO : root : creating build/lib/botocore/data/backup/2018-11-15 INFO : root : copying botocore/data/backup/2018-11-15/examples-1.json -> build/lib/botocore/data/backup/2018-11-15 INFO : root : copying botocore/data/backup/2018-11-15/paginators-1.json -> build/lib/botocore/data/backup/2018-11-15 INFO : root : copying botocore/data/backup/2018-11-15/service-2.json -> build/lib/botocore/data/backup/2018-11-15 INFO : root : creating build/lib/botocore/data/backupstorage INFO : root : creating build/lib/botocore/data/backupstorage/2018-04-10 INFO : root : copying botocore/data/backupstorage/2018-04-10/paginators-1.json -> build/lib/botocore/data/backupstorage/2018-04-10 INFO : root : copying botocore/data/backupstorage/2018-04-10/service-2.json -> build/lib/botocore/data/backupstorage/2018-04-10 INFO : root : creating build/lib/botocore/data/batch INFO : root : creating build/lib/botocore/data/batch/2016-08-10 INFO : root : copying botocore/data/batch/2016-08-10/examples-1.json -> build/lib/botocore/data/batch/2016-08-10 INFO : root : copying botocore/data/batch/2016-08-10/paginators-1.json -> build/lib/botocore/data/batch/2016-08-10 INFO : root : copying botocore/data/batch/2016-08-10/service-2.json -> build/lib/botocore/data/batch/2016-08-10 INFO : root : creating build/lib/botocore/data/billingconductor INFO : root : creating build/lib/botocore/data/billingconductor/2021-07-30 INFO : root : copying botocore/data/billingconductor/2021-07-30/examples-1.json -> build/lib/botocore/data/billingconductor/2021-07-30 INFO : root : copying botocore/data/billingconductor/2021-07-30/paginators-1.json -> build/lib/botocore/data/billingconductor/2021-07-30 INFO : root : copying botocore/data/billingconductor/2021-07-30/service-2.json -> build/lib/botocore/data/billingconductor/2021-07-30 INFO : root : copying botocore/data/billingconductor/2021-07-30/waiters-2.json -> build/lib/botocore/data/billingconductor/2021-07-30 INFO : root : creating build/lib/botocore/data/braket INFO : root : creating build/lib/botocore/data/braket/2019-09-01 INFO : root : copying botocore/data/braket/2019-09-01/examples-1.json -> build/lib/botocore/data/braket/2019-09-01 INFO : root : copying botocore/data/braket/2019-09-01/paginators-1.json -> build/lib/botocore/data/braket/2019-09-01 INFO : root : copying botocore/data/braket/2019-09-01/service-2.json -> build/lib/botocore/data/braket/2019-09-01 INFO : root : creating build/lib/botocore/data/budgets INFO : root : creating build/lib/botocore/data/budgets/2016-10-20 INFO : root : copying botocore/data/budgets/2016-10-20/examples-1.json -> build/lib/botocore/data/budgets/2016-10-20 INFO : root : copying botocore/data/budgets/2016-10-20/paginators-1.json -> build/lib/botocore/data/budgets/2016-10-20 INFO : root : copying botocore/data/budgets/2016-10-20/service-2.json -> build/lib/botocore/data/budgets/2016-10-20 INFO : root : creating build/lib/botocore/data/ce INFO : root : creating build/lib/botocore/data/ce/2017-10-25 INFO : root : copying botocore/data/ce/2017-10-25/examples-1.json -> build/lib/botocore/data/ce/2017-10-25 INFO : root : copying botocore/data/ce/2017-10-25/paginators-1.json -> build/lib/botocore/data/ce/2017-10-25 INFO : root : copying botocore/data/ce/2017-10-25/service-2.json -> build/lib/botocore/data/ce/2017-10-25 INFO : root : creating build/lib/botocore/data/chime-sdk-identity INFO : root : creating build/lib/botocore/data/chime-sdk-identity/2021-04-20 INFO : root : copying botocore/data/chime-sdk-identity/2021-04-20/examples-1.json -> build/lib/botocore/data/chime-sdk-identity/2021-04-20 INFO : root : copying botocore/data/chime-sdk-identity/2021-04-20/paginators-1.json -> build/lib/botocore/data/chime-sdk-identity/2021-04-20 INFO : root : copying botocore/data/chime-sdk-identity/2021-04-20/service-2.json -> build/lib/botocore/data/chime-sdk-identity/2021-04-20 INFO : root : creating build/lib/botocore/data/chime-sdk-media-pipelines INFO : root : creating build/lib/botocore/data/chime-sdk-media-pipelines/2021-07-15 INFO : root : copying botocore/data/chime-sdk-media-pipelines/2021-07-15/paginators-1.json -> build/lib/botocore/data/chime-sdk-media-pipelines/2021-07-15 INFO : root : copying botocore/data/chime-sdk-media-pipelines/2021-07-15/service-2.json -> build/lib/botocore/data/chime-sdk-media-pipelines/2021-07-15 INFO : root : creating build/lib/botocore/data/chime-sdk-meetings INFO : root : creating build/lib/botocore/data/chime-sdk-meetings/2021-07-15 INFO : root : copying botocore/data/chime-sdk-meetings/2021-07-15/examples-1.json -> build/lib/botocore/data/chime-sdk-meetings/2021-07-15 INFO : root : copying botocore/data/chime-sdk-meetings/2021-07-15/paginators-1.json -> build/lib/botocore/data/chime-sdk-meetings/2021-07-15 INFO : root : copying botocore/data/chime-sdk-meetings/2021-07-15/service-2.json -> build/lib/botocore/data/chime-sdk-meetings/2021-07-15 INFO : root : creating build/lib/botocore/data/chime-sdk-messaging INFO : root : creating build/lib/botocore/data/chime-sdk-messaging/2021-05-15 INFO : root : copying botocore/data/chime-sdk-messaging/2021-05-15/examples-1.json -> build/lib/botocore/data/chime-sdk-messaging/2021-05-15 INFO : root : copying botocore/data/chime-sdk-messaging/2021-05-15/paginators-1.json -> build/lib/botocore/data/chime-sdk-messaging/2021-05-15 INFO : root : copying botocore/data/chime-sdk-messaging/2021-05-15/service-2.json -> build/lib/botocore/data/chime-sdk-messaging/2021-05-15 INFO : root : creating build/lib/botocore/data/chime INFO : root : creating build/lib/botocore/data/chime/2018-05-01 INFO : root : copying botocore/data/chime/2018-05-01/examples-1.json -> build/lib/botocore/data/chime/2018-05-01 INFO : root : copying botocore/data/chime/2018-05-01/paginators-1.json -> build/lib/botocore/data/chime/2018-05-01 INFO : root : copying botocore/data/chime/2018-05-01/service-2.json -> build/lib/botocore/data/chime/2018-05-01 INFO : root : creating build/lib/botocore/data/cloud9 INFO : root : creating build/lib/botocore/data/cloud9/2017-09-23 INFO : root : copying botocore/data/cloud9/2017-09-23/examples-1.json -> build/lib/botocore/data/cloud9/2017-09-23 INFO : root : copying botocore/data/cloud9/2017-09-23/paginators-1.json -> build/lib/botocore/data/cloud9/2017-09-23 INFO : root : copying botocore/data/cloud9/2017-09-23/service-2.json -> build/lib/botocore/data/cloud9/2017-09-23 INFO : root : creating build/lib/botocore/data/cloudcontrol INFO : root : creating build/lib/botocore/data/cloudcontrol/2021-09-30 INFO : root : copying botocore/data/cloudcontrol/2021-09-30/examples-1.json -> build/lib/botocore/data/cloudcontrol/2021-09-30 INFO : root : copying botocore/data/cloudcontrol/2021-09-30/paginators-1.json -> build/lib/botocore/data/cloudcontrol/2021-09-30 INFO : root : copying botocore/data/cloudcontrol/2021-09-30/paginators-1.sdk-extras.json -> build/lib/botocore/data/cloudcontrol/2021-09-30 INFO : root : copying botocore/data/cloudcontrol/2021-09-30/service-2.json -> build/lib/botocore/data/cloudcontrol/2021-09-30 INFO : root : copying botocore/data/cloudcontrol/2021-09-30/waiters-2.json -> build/lib/botocore/data/cloudcontrol/2021-09-30 INFO : root : creating build/lib/botocore/data/clouddirectory INFO : root : creating build/lib/botocore/data/clouddirectory/2016-05-10 INFO : root : copying botocore/data/clouddirectory/2016-05-10/examples-1.json -> build/lib/botocore/data/clouddirectory/2016-05-10 INFO : root : copying botocore/data/clouddirectory/2016-05-10/paginators-1.json -> build/lib/botocore/data/clouddirectory/2016-05-10 INFO : root : copying botocore/data/clouddirectory/2016-05-10/service-2.json -> build/lib/botocore/data/clouddirectory/2016-05-10 INFO : root : creating build/lib/botocore/data/clouddirectory/2017-01-11 INFO : root : copying botocore/data/clouddirectory/2017-01-11/examples-1.json -> build/lib/botocore/data/clouddirectory/2017-01-11 INFO : root : copying botocore/data/clouddirectory/2017-01-11/paginators-1.json -> build/lib/botocore/data/clouddirectory/2017-01-11 INFO : root : copying botocore/data/clouddirectory/2017-01-11/service-2.json -> build/lib/botocore/data/clouddirectory/2017-01-11 INFO : root : creating build/lib/botocore/data/cloudformation INFO : root : creating build/lib/botocore/data/cloudformation/2010-05-15 INFO : root : copying botocore/data/cloudformation/2010-05-15/examples-1.json -> build/lib/botocore/data/cloudformation/2010-05-15 INFO : root : copying botocore/data/cloudformation/2010-05-15/paginators-1.json -> build/lib/botocore/data/cloudformation/2010-05-15 INFO : root : copying botocore/data/cloudformation/2010-05-15/service-2.json -> build/lib/botocore/data/cloudformation/2010-05-15 INFO : root : copying botocore/data/cloudformation/2010-05-15/waiters-2.json -> build/lib/botocore/data/cloudformation/2010-05-15 INFO : root : creating build/lib/botocore/data/cloudfront INFO : root : creating build/lib/botocore/data/cloudfront/2014-05-31 INFO : root : copying botocore/data/cloudfront/2014-05-31/paginators-1.json -> build/lib/botocore/data/cloudfront/2014-05-31 INFO : root : copying botocore/data/cloudfront/2014-05-31/service-2.json -> build/lib/botocore/data/cloudfront/2014-05-31 INFO : root : copying botocore/data/cloudfront/2014-05-31/waiters-2.json -> build/lib/botocore/data/cloudfront/2014-05-31 INFO : root : creating build/lib/botocore/data/cloudfront/2014-10-21 INFO : root : copying botocore/data/cloudfront/2014-10-21/paginators-1.json -> build/lib/botocore/data/cloudfront/2014-10-21 INFO : root : copying botocore/data/cloudfront/2014-10-21/service-2.json -> build/lib/botocore/data/cloudfront/2014-10-21 INFO : root : copying botocore/data/cloudfront/2014-10-21/waiters-2.json -> build/lib/botocore/data/cloudfront/2014-10-21 INFO : root : creating build/lib/botocore/data/cloudfront/2014-11-06 INFO : root : copying botocore/data/cloudfront/2014-11-06/paginators-1.json -> build/lib/botocore/data/cloudfront/2014-11-06 INFO : root : copying botocore/data/cloudfront/2014-11-06/service-2.json -> build/lib/botocore/data/cloudfront/2014-11-06 INFO : root : copying botocore/data/cloudfront/2014-11-06/waiters-2.json -> build/lib/botocore/data/cloudfront/2014-11-06 INFO : root : creating build/lib/botocore/data/cloudfront/2015-04-17 INFO : root : copying botocore/data/cloudfront/2015-04-17/paginators-1.json -> build/lib/botocore/data/cloudfront/2015-04-17 INFO : root : copying botocore/data/cloudfront/2015-04-17/service-2.json -> build/lib/botocore/data/cloudfront/2015-04-17 INFO : root : copying botocore/data/cloudfront/2015-04-17/waiters-2.json -> build/lib/botocore/data/cloudfront/2015-04-17 INFO : root : creating build/lib/botocore/data/cloudfront/2015-07-27 INFO : root : copying botocore/data/cloudfront/2015-07-27/paginators-1.json -> build/lib/botocore/data/cloudfront/2015-07-27 INFO : root : copying botocore/data/cloudfront/2015-07-27/service-2.json -> build/lib/botocore/data/cloudfront/2015-07-27 INFO : root : copying botocore/data/cloudfront/2015-07-27/waiters-2.json -> build/lib/botocore/data/cloudfront/2015-07-27 INFO : root : creating build/lib/botocore/data/cloudfront/2015-09-17 INFO : root : copying botocore/data/cloudfront/2015-09-17/paginators-1.json -> build/lib/botocore/data/cloudfront/2015-09-17 INFO : root : copying botocore/data/cloudfront/2015-09-17/service-2.json -> build/lib/botocore/data/cloudfront/2015-09-17 INFO : root : copying botocore/data/cloudfront/2015-09-17/waiters-2.json -> build/lib/botocore/data/cloudfront/2015-09-17 INFO : root : creating build/lib/botocore/data/cloudfront/2016-01-13 INFO : root : copying botocore/data/cloudfront/2016-01-13/paginators-1.json -> build/lib/botocore/data/cloudfront/2016-01-13 INFO : root : copying botocore/data/cloudfront/2016-01-13/service-2.json -> build/lib/botocore/data/cloudfront/2016-01-13 INFO : root : copying botocore/data/cloudfront/2016-01-13/waiters-2.json -> build/lib/botocore/data/cloudfront/2016-01-13 INFO : root : creating build/lib/botocore/data/cloudfront/2016-01-28 INFO : root : copying botocore/data/cloudfront/2016-01-28/examples-1.json -> build/lib/botocore/data/cloudfront/2016-01-28 INFO : root : copying botocore/data/cloudfront/2016-01-28/paginators-1.json -> build/lib/botocore/data/cloudfront/2016-01-28 INFO : root : copying botocore/data/cloudfront/2016-01-28/service-2.json -> build/lib/botocore/data/cloudfront/2016-01-28 INFO : root : copying botocore/data/cloudfront/2016-01-28/waiters-2.json -> build/lib/botocore/data/cloudfront/2016-01-28 INFO : root : creating build/lib/botocore/data/cloudfront/2016-08-01 INFO : root : copying botocore/data/cloudfront/2016-08-01/examples-1.json -> build/lib/botocore/data/cloudfront/2016-08-01 INFO : root : copying botocore/data/cloudfront/2016-08-01/paginators-1.json -> build/lib/botocore/data/cloudfront/2016-08-01 INFO : root : copying botocore/data/cloudfront/2016-08-01/service-2.json -> build/lib/botocore/data/cloudfront/2016-08-01 INFO : root : copying botocore/data/cloudfront/2016-08-01/waiters-2.json -> build/lib/botocore/data/cloudfront/2016-08-01 INFO : root : creating build/lib/botocore/data/cloudfront/2016-08-20 INFO : root : copying botocore/data/cloudfront/2016-08-20/paginators-1.json -> build/lib/botocore/data/cloudfront/2016-08-20 INFO : root : copying botocore/data/cloudfront/2016-08-20/service-2.json -> build/lib/botocore/data/cloudfront/2016-08-20 INFO : root : copying botocore/data/cloudfront/2016-08-20/waiters-2.json -> build/lib/botocore/data/cloudfront/2016-08-20 INFO : root : creating build/lib/botocore/data/cloudfront/2016-09-07 INFO : root : copying botocore/data/cloudfront/2016-09-07/examples-1.json -> build/lib/botocore/data/cloudfront/2016-09-07 INFO : root : copying botocore/data/cloudfront/2016-09-07/paginators-1.json -> build/lib/botocore/data/cloudfront/2016-09-07 INFO : root : copying botocore/data/cloudfront/2016-09-07/service-2.json -> build/lib/botocore/data/cloudfront/2016-09-07 INFO : root : copying botocore/data/cloudfront/2016-09-07/waiters-2.json -> build/lib/botocore/data/cloudfront/2016-09-07 INFO : root : creating build/lib/botocore/data/cloudfront/2016-09-29 INFO : root : copying botocore/data/cloudfront/2016-09-29/examples-1.json -> build/lib/botocore/data/cloudfront/2016-09-29 INFO : root : copying botocore/data/cloudfront/2016-09-29/paginators-1.json -> build/lib/botocore/data/cloudfront/2016-09-29 INFO : root : copying botocore/data/cloudfront/2016-09-29/service-2.json -> build/lib/botocore/data/cloudfront/2016-09-29 INFO : root : copying botocore/data/cloudfront/2016-09-29/waiters-2.json -> build/lib/botocore/data/cloudfront/2016-09-29 INFO : root : creating build/lib/botocore/data/cloudfront/2016-11-25 INFO : root : copying botocore/data/cloudfront/2016-11-25/examples-1.json -> build/lib/botocore/data/cloudfront/2016-11-25 INFO : root : copying botocore/data/cloudfront/2016-11-25/paginators-1.json -> build/lib/botocore/data/cloudfront/2016-11-25 INFO : root : copying botocore/data/cloudfront/2016-11-25/service-2.json -> build/lib/botocore/data/cloudfront/2016-11-25 INFO : root : copying botocore/data/cloudfront/2016-11-25/waiters-2.json -> build/lib/botocore/data/cloudfront/2016-11-25 INFO : root : creating build/lib/botocore/data/cloudfront/2017-03-25 INFO : root : copying botocore/data/cloudfront/2017-03-25/paginators-1.json -> build/lib/botocore/data/cloudfront/2017-03-25 INFO : root : copying botocore/data/cloudfront/2017-03-25/service-2.json -> build/lib/botocore/data/cloudfront/2017-03-25 INFO : root : copying botocore/data/cloudfront/2017-03-25/waiters-2.json -> build/lib/botocore/data/cloudfront/2017-03-25 INFO : root : creating build/lib/botocore/data/cloudfront/2017-10-30 INFO : root : copying botocore/data/cloudfront/2017-10-30/examples-1.json -> build/lib/botocore/data/cloudfront/2017-10-30 INFO : root : copying botocore/data/cloudfront/2017-10-30/paginators-1.json -> build/lib/botocore/data/cloudfront/2017-10-30 INFO : root : copying botocore/data/cloudfront/2017-10-30/service-2.json -> build/lib/botocore/data/cloudfront/2017-10-30 INFO : root : copying botocore/data/cloudfront/2017-10-30/waiters-2.json -> build/lib/botocore/data/cloudfront/2017-10-30 INFO : root : creating build/lib/botocore/data/cloudfront/2018-06-18 INFO : root : copying botocore/data/cloudfront/2018-06-18/examples-1.json -> build/lib/botocore/data/cloudfront/2018-06-18 INFO : root : copying botocore/data/cloudfront/2018-06-18/paginators-1.json -> build/lib/botocore/data/cloudfront/2018-06-18 INFO : root : copying botocore/data/cloudfront/2018-06-18/service-2.json -> build/lib/botocore/data/cloudfront/2018-06-18 INFO : root : copying botocore/data/cloudfront/2018-06-18/waiters-2.json -> build/lib/botocore/data/cloudfront/2018-06-18 INFO : root : creating build/lib/botocore/data/cloudfront/2018-11-05 INFO : root : copying botocore/data/cloudfront/2018-11-05/examples-1.json -> build/lib/botocore/data/cloudfront/2018-11-05 INFO : root : copying botocore/data/cloudfront/2018-11-05/paginators-1.json -> build/lib/botocore/data/cloudfront/2018-11-05 INFO : root : copying botocore/data/cloudfront/2018-11-05/service-2.json -> build/lib/botocore/data/cloudfront/2018-11-05 INFO : root : copying botocore/data/cloudfront/2018-11-05/waiters-2.json -> build/lib/botocore/data/cloudfront/2018-11-05 INFO : root : creating build/lib/botocore/data/cloudfront/2019-03-26 INFO : root : copying botocore/data/cloudfront/2019-03-26/examples-1.json -> build/lib/botocore/data/cloudfront/2019-03-26 INFO : root : copying botocore/data/cloudfront/2019-03-26/paginators-1.json -> build/lib/botocore/data/cloudfront/2019-03-26 INFO : root : copying botocore/data/cloudfront/2019-03-26/service-2.json -> build/lib/botocore/data/cloudfront/2019-03-26 INFO : root : copying botocore/data/cloudfront/2019-03-26/waiters-2.json -> build/lib/botocore/data/cloudfront/2019-03-26 INFO : root : creating build/lib/botocore/data/cloudfront/2020-05-31 INFO : root : copying botocore/data/cloudfront/2020-05-31/examples-1.json -> build/lib/botocore/data/cloudfront/2020-05-31 INFO : root : copying botocore/data/cloudfront/2020-05-31/paginators-1.json -> build/lib/botocore/data/cloudfront/2020-05-31 INFO : root : copying botocore/data/cloudfront/2020-05-31/service-2.json -> build/lib/botocore/data/cloudfront/2020-05-31 INFO : root : copying botocore/data/cloudfront/2020-05-31/waiters-2.json -> build/lib/botocore/data/cloudfront/2020-05-31 INFO : root : creating build/lib/botocore/data/cloudhsm INFO : root : creating build/lib/botocore/data/cloudhsm/2014-05-30 INFO : root : copying botocore/data/cloudhsm/2014-05-30/examples-1.json -> build/lib/botocore/data/cloudhsm/2014-05-30 INFO : root : copying botocore/data/cloudhsm/2014-05-30/paginators-1.json -> build/lib/botocore/data/cloudhsm/2014-05-30 INFO : root : copying botocore/data/cloudhsm/2014-05-30/service-2.json -> build/lib/botocore/data/cloudhsm/2014-05-30 INFO : root : creating build/lib/botocore/data/cloudhsmv2 INFO : root : creating build/lib/botocore/data/cloudhsmv2/2017-04-28 INFO : root : copying botocore/data/cloudhsmv2/2017-04-28/examples-1.json -> build/lib/botocore/data/cloudhsmv2/2017-04-28 INFO : root : copying botocore/data/cloudhsmv2/2017-04-28/paginators-1.json -> build/lib/botocore/data/cloudhsmv2/2017-04-28 INFO : root : copying botocore/data/cloudhsmv2/2017-04-28/service-2.json -> build/lib/botocore/data/cloudhsmv2/2017-04-28 INFO : root : creating build/lib/botocore/data/cloudsearch INFO : root : creating build/lib/botocore/data/cloudsearch/2011-02-01 INFO : root : copying botocore/data/cloudsearch/2011-02-01/service-2.json -> build/lib/botocore/data/cloudsearch/2011-02-01 INFO : root : creating build/lib/botocore/data/cloudsearch/2013-01-01 INFO : root : copying botocore/data/cloudsearch/2013-01-01/examples-1.json -> build/lib/botocore/data/cloudsearch/2013-01-01 INFO : root : copying botocore/data/cloudsearch/2013-01-01/paginators-1.json -> build/lib/botocore/data/cloudsearch/2013-01-01 INFO : root : copying botocore/data/cloudsearch/2013-01-01/service-2.json -> build/lib/botocore/data/cloudsearch/2013-01-01 INFO : root : creating build/lib/botocore/data/cloudsearchdomain INFO : root : creating build/lib/botocore/data/cloudsearchdomain/2013-01-01 INFO : root : copying botocore/data/cloudsearchdomain/2013-01-01/examples-1.json -> build/lib/botocore/data/cloudsearchdomain/2013-01-01 INFO : root : copying botocore/data/cloudsearchdomain/2013-01-01/service-2.json -> build/lib/botocore/data/cloudsearchdomain/2013-01-01 INFO : root : creating build/lib/botocore/data/cloudtrail INFO : root : creating build/lib/botocore/data/cloudtrail/2013-11-01 INFO : root : copying botocore/data/cloudtrail/2013-11-01/examples-1.json -> build/lib/botocore/data/cloudtrail/2013-11-01 INFO : root : copying botocore/data/cloudtrail/2013-11-01/paginators-1.json -> build/lib/botocore/data/cloudtrail/2013-11-01 INFO : root : copying botocore/data/cloudtrail/2013-11-01/service-2.json -> build/lib/botocore/data/cloudtrail/2013-11-01 INFO : root : creating build/lib/botocore/data/cloudwatch INFO : root : creating build/lib/botocore/data/cloudwatch/2010-08-01 INFO : root : copying botocore/data/cloudwatch/2010-08-01/examples-1.json -> build/lib/botocore/data/cloudwatch/2010-08-01 INFO : root : copying botocore/data/cloudwatch/2010-08-01/paginators-1.json -> build/lib/botocore/data/cloudwatch/2010-08-01 INFO : root : copying botocore/data/cloudwatch/2010-08-01/service-2.json -> build/lib/botocore/data/cloudwatch/2010-08-01 INFO : root : copying botocore/data/cloudwatch/2010-08-01/waiters-2.json -> build/lib/botocore/data/cloudwatch/2010-08-01 INFO : root : creating build/lib/botocore/data/codeartifact INFO : root : creating build/lib/botocore/data/codeartifact/2018-09-22 INFO : root : copying botocore/data/codeartifact/2018-09-22/examples-1.json -> build/lib/botocore/data/codeartifact/2018-09-22 INFO : root : copying botocore/data/codeartifact/2018-09-22/paginators-1.json -> build/lib/botocore/data/codeartifact/2018-09-22 INFO : root : copying botocore/data/codeartifact/2018-09-22/paginators-1.sdk-extras.json -> build/lib/botocore/data/codeartifact/2018-09-22 INFO : root : copying botocore/data/codeartifact/2018-09-22/service-2.json -> build/lib/botocore/data/codeartifact/2018-09-22 INFO : root : creating build/lib/botocore/data/codebuild INFO : root : creating build/lib/botocore/data/codebuild/2016-10-06 INFO : root : copying botocore/data/codebuild/2016-10-06/examples-1.json -> build/lib/botocore/data/codebuild/2016-10-06 INFO : root : copying botocore/data/codebuild/2016-10-06/paginators-1.json -> build/lib/botocore/data/codebuild/2016-10-06 INFO : root : copying botocore/data/codebuild/2016-10-06/service-2.json -> build/lib/botocore/data/codebuild/2016-10-06 INFO : root : creating build/lib/botocore/data/codecommit INFO : root : creating build/lib/botocore/data/codecommit/2015-04-13 INFO : root : copying botocore/data/codecommit/2015-04-13/examples-1.json -> build/lib/botocore/data/codecommit/2015-04-13 INFO : root : copying botocore/data/codecommit/2015-04-13/paginators-1.json -> build/lib/botocore/data/codecommit/2015-04-13 INFO : root : copying botocore/data/codecommit/2015-04-13/service-2.json -> build/lib/botocore/data/codecommit/2015-04-13 INFO : root : creating build/lib/botocore/data/codedeploy INFO : root : creating build/lib/botocore/data/codedeploy/2014-10-06 INFO : root : copying botocore/data/codedeploy/2014-10-06/examples-1.json -> build/lib/botocore/data/codedeploy/2014-10-06 INFO : root : copying botocore/data/codedeploy/2014-10-06/paginators-1.json -> build/lib/botocore/data/codedeploy/2014-10-06 INFO : root : copying botocore/data/codedeploy/2014-10-06/service-2.json -> build/lib/botocore/data/codedeploy/2014-10-06 INFO : root : copying botocore/data/codedeploy/2014-10-06/waiters-2.json -> build/lib/botocore/data/codedeploy/2014-10-06 INFO : root : creating build/lib/botocore/data/codeguru-reviewer INFO : root : creating build/lib/botocore/data/codeguru-reviewer/2019-09-19 INFO : root : copying botocore/data/codeguru-reviewer/2019-09-19/examples-1.json -> build/lib/botocore/data/codeguru-reviewer/2019-09-19 INFO : root : copying botocore/data/codeguru-reviewer/2019-09-19/paginators-1.json -> build/lib/botocore/data/codeguru-reviewer/2019-09-19 INFO : root : copying botocore/data/codeguru-reviewer/2019-09-19/service-2.json -> build/lib/botocore/data/codeguru-reviewer/2019-09-19 INFO : root : copying botocore/data/codeguru-reviewer/2019-09-19/waiters-2.json -> build/lib/botocore/data/codeguru-reviewer/2019-09-19 INFO : root : creating build/lib/botocore/data/codeguruprofiler INFO : root : creating build/lib/botocore/data/codeguruprofiler/2019-07-18 INFO : root : copying botocore/data/codeguruprofiler/2019-07-18/examples-1.json -> build/lib/botocore/data/codeguruprofiler/2019-07-18 INFO : root : copying botocore/data/codeguruprofiler/2019-07-18/paginators-1.json -> build/lib/botocore/data/codeguruprofiler/2019-07-18 INFO : root : copying botocore/data/codeguruprofiler/2019-07-18/service-2.json -> build/lib/botocore/data/codeguruprofiler/2019-07-18 INFO : root : creating build/lib/botocore/data/codepipeline INFO : root : creating build/lib/botocore/data/codepipeline/2015-07-09 INFO : root : copying botocore/data/codepipeline/2015-07-09/examples-1.json -> build/lib/botocore/data/codepipeline/2015-07-09 INFO : root : copying botocore/data/codepipeline/2015-07-09/paginators-1.json -> build/lib/botocore/data/codepipeline/2015-07-09 INFO : root : copying botocore/data/codepipeline/2015-07-09/service-2.json -> build/lib/botocore/data/codepipeline/2015-07-09 INFO : root : creating build/lib/botocore/data/codestar-connections INFO : root : creating build/lib/botocore/data/codestar-connections/2019-12-01 INFO : root : copying botocore/data/codestar-connections/2019-12-01/examples-1.json -> build/lib/botocore/data/codestar-connections/2019-12-01 INFO : root : copying botocore/data/codestar-connections/2019-12-01/paginators-1.json -> build/lib/botocore/data/codestar-connections/2019-12-01 INFO : root : copying botocore/data/codestar-connections/2019-12-01/service-2.json -> build/lib/botocore/data/codestar-connections/2019-12-01 INFO : root : creating build/lib/botocore/data/codestar-notifications INFO : root : creating build/lib/botocore/data/codestar-notifications/2019-10-15 INFO : root : copying botocore/data/codestar-notifications/2019-10-15/examples-1.json -> build/lib/botocore/data/codestar-notifications/2019-10-15 INFO : root : copying botocore/data/codestar-notifications/2019-10-15/paginators-1.json -> build/lib/botocore/data/codestar-notifications/2019-10-15 INFO : root : copying botocore/data/codestar-notifications/2019-10-15/service-2.json -> build/lib/botocore/data/codestar-notifications/2019-10-15 INFO : root : creating build/lib/botocore/data/codestar INFO : root : creating build/lib/botocore/data/codestar/2017-04-19 INFO : root : copying botocore/data/codestar/2017-04-19/examples-1.json -> build/lib/botocore/data/codestar/2017-04-19 INFO : root : copying botocore/data/codestar/2017-04-19/paginators-1.json -> build/lib/botocore/data/codestar/2017-04-19 INFO : root : copying botocore/data/codestar/2017-04-19/service-2.json -> build/lib/botocore/data/codestar/2017-04-19 INFO : root : creating build/lib/botocore/data/cognito-identity INFO : root : creating build/lib/botocore/data/cognito-identity/2014-06-30 INFO : root : copying botocore/data/cognito-identity/2014-06-30/examples-1.json -> build/lib/botocore/data/cognito-identity/2014-06-30 INFO : root : copying botocore/data/cognito-identity/2014-06-30/paginators-1.json -> build/lib/botocore/data/cognito-identity/2014-06-30 INFO : root : copying botocore/data/cognito-identity/2014-06-30/service-2.json -> build/lib/botocore/data/cognito-identity/2014-06-30 INFO : root : creating build/lib/botocore/data/cognito-idp INFO : root : creating build/lib/botocore/data/cognito-idp/2016-04-18 INFO : root : copying botocore/data/cognito-idp/2016-04-18/examples-1.json -> build/lib/botocore/data/cognito-idp/2016-04-18 INFO : root : copying botocore/data/cognito-idp/2016-04-18/paginators-1.json -> build/lib/botocore/data/cognito-idp/2016-04-18 INFO : root : copying botocore/data/cognito-idp/2016-04-18/service-2.json -> build/lib/botocore/data/cognito-idp/2016-04-18 INFO : root : creating build/lib/botocore/data/cognito-sync INFO : root : creating build/lib/botocore/data/cognito-sync/2014-06-30 INFO : root : copying botocore/data/cognito-sync/2014-06-30/examples-1.json -> build/lib/botocore/data/cognito-sync/2014-06-30 INFO : root : copying botocore/data/cognito-sync/2014-06-30/paginators-1.json -> build/lib/botocore/data/cognito-sync/2014-06-30 INFO : root : copying botocore/data/cognito-sync/2014-06-30/service-2.json -> build/lib/botocore/data/cognito-sync/2014-06-30 INFO : root : creating build/lib/botocore/data/comprehend INFO : root : creating build/lib/botocore/data/comprehend/2017-11-27 INFO : root : copying botocore/data/comprehend/2017-11-27/examples-1.json -> build/lib/botocore/data/comprehend/2017-11-27 INFO : root : copying botocore/data/comprehend/2017-11-27/paginators-1.json -> build/lib/botocore/data/comprehend/2017-11-27 INFO : root : copying botocore/data/comprehend/2017-11-27/service-2.json -> build/lib/botocore/data/comprehend/2017-11-27 INFO : root : creating build/lib/botocore/data/comprehendmedical INFO : root : creating build/lib/botocore/data/comprehendmedical/2018-10-30 INFO : root : copying botocore/data/comprehendmedical/2018-10-30/examples-1.json -> build/lib/botocore/data/comprehendmedical/2018-10-30 INFO : root : copying botocore/data/comprehendmedical/2018-10-30/paginators-1.json -> build/lib/botocore/data/comprehendmedical/2018-10-30 INFO : root : copying botocore/data/comprehendmedical/2018-10-30/service-2.json -> build/lib/botocore/data/comprehendmedical/2018-10-30 INFO : root : creating build/lib/botocore/data/compute-optimizer INFO : root : creating build/lib/botocore/data/compute-optimizer/2019-11-01 INFO : root : copying botocore/data/compute-optimizer/2019-11-01/examples-1.json -> build/lib/botocore/data/compute-optimizer/2019-11-01 INFO : root : copying botocore/data/compute-optimizer/2019-11-01/paginators-1.json -> build/lib/botocore/data/compute-optimizer/2019-11-01 INFO : root : copying botocore/data/compute-optimizer/2019-11-01/service-2.json -> build/lib/botocore/data/compute-optimizer/2019-11-01 INFO : root : creating build/lib/botocore/data/config INFO : root : creating build/lib/botocore/data/config/2014-11-12 INFO : root : copying botocore/data/config/2014-11-12/examples-1.json -> build/lib/botocore/data/config/2014-11-12 INFO : root : copying botocore/data/config/2014-11-12/paginators-1.json -> build/lib/botocore/data/config/2014-11-12 INFO : root : copying botocore/data/config/2014-11-12/service-2.json -> build/lib/botocore/data/config/2014-11-12 INFO : root : creating build/lib/botocore/data/connect-contact-lens INFO : root : creating build/lib/botocore/data/connect-contact-lens/2020-08-21 INFO : root : copying botocore/data/connect-contact-lens/2020-08-21/examples-1.json -> build/lib/botocore/data/connect-contact-lens/2020-08-21 INFO : root : copying botocore/data/connect-contact-lens/2020-08-21/paginators-1.json -> build/lib/botocore/data/connect-contact-lens/2020-08-21 INFO : root : copying botocore/data/connect-contact-lens/2020-08-21/service-2.json -> build/lib/botocore/data/connect-contact-lens/2020-08-21 INFO : root : creating build/lib/botocore/data/connect INFO : root : creating build/lib/botocore/data/connect/2017-08-08 INFO : root : copying botocore/data/connect/2017-08-08/examples-1.json -> build/lib/botocore/data/connect/2017-08-08 INFO : root : copying botocore/data/connect/2017-08-08/paginators-1.json -> build/lib/botocore/data/connect/2017-08-08 INFO : root : copying botocore/data/connect/2017-08-08/service-2.json -> build/lib/botocore/data/connect/2017-08-08 INFO : root : creating build/lib/botocore/data/connectcampaigns INFO : root : creating build/lib/botocore/data/connectcampaigns/2021-01-30 INFO : root : copying botocore/data/connectcampaigns/2021-01-30/paginators-1.json -> build/lib/botocore/data/connectcampaigns/2021-01-30 INFO : root : copying botocore/data/connectcampaigns/2021-01-30/service-2.json -> build/lib/botocore/data/connectcampaigns/2021-01-30 INFO : root : creating build/lib/botocore/data/connectcases INFO : root : creating build/lib/botocore/data/connectcases/2022-10-03 INFO : root : copying botocore/data/connectcases/2022-10-03/paginators-1.json -> build/lib/botocore/data/connectcases/2022-10-03 INFO : root : copying botocore/data/connectcases/2022-10-03/service-2.json -> build/lib/botocore/data/connectcases/2022-10-03 INFO : root : creating build/lib/botocore/data/connectparticipant INFO : root : creating build/lib/botocore/data/connectparticipant/2018-09-07 INFO : root : copying botocore/data/connectparticipant/2018-09-07/examples-1.json -> build/lib/botocore/data/connectparticipant/2018-09-07 INFO : root : copying botocore/data/connectparticipant/2018-09-07/paginators-1.json -> build/lib/botocore/data/connectparticipant/2018-09-07 INFO : root : copying botocore/data/connectparticipant/2018-09-07/service-2.json -> build/lib/botocore/data/connectparticipant/2018-09-07 INFO : root : creating build/lib/botocore/data/controltower INFO : root : creating build/lib/botocore/data/controltower/2018-05-10 INFO : root : copying botocore/data/controltower/2018-05-10/paginators-1.json -> build/lib/botocore/data/controltower/2018-05-10 INFO : root : copying botocore/data/controltower/2018-05-10/service-2.json -> build/lib/botocore/data/controltower/2018-05-10 INFO : root : creating build/lib/botocore/data/cur INFO : root : creating build/lib/botocore/data/cur/2017-01-06 INFO : root : copying botocore/data/cur/2017-01-06/examples-1.json -> build/lib/botocore/data/cur/2017-01-06 INFO : root : copying botocore/data/cur/2017-01-06/paginators-1.json -> build/lib/botocore/data/cur/2017-01-06 INFO : root : copying botocore/data/cur/2017-01-06/service-2.json -> build/lib/botocore/data/cur/2017-01-06 INFO : root : creating build/lib/botocore/data/customer-profiles INFO : root : creating build/lib/botocore/data/customer-profiles/2020-08-15 INFO : root : copying botocore/data/customer-profiles/2020-08-15/examples-1.json -> build/lib/botocore/data/customer-profiles/2020-08-15 INFO : root : copying botocore/data/customer-profiles/2020-08-15/paginators-1.json -> build/lib/botocore/data/customer-profiles/2020-08-15 INFO : root : copying botocore/data/customer-profiles/2020-08-15/service-2.json -> build/lib/botocore/data/customer-profiles/2020-08-15 INFO : root : creating build/lib/botocore/data/databrew INFO : root : creating build/lib/botocore/data/databrew/2017-07-25 INFO : root : copying botocore/data/databrew/2017-07-25/examples-1.json -> build/lib/botocore/data/databrew/2017-07-25 INFO : root : copying botocore/data/databrew/2017-07-25/paginators-1.json -> build/lib/botocore/data/databrew/2017-07-25 INFO : root : copying botocore/data/databrew/2017-07-25/service-2.json -> build/lib/botocore/data/databrew/2017-07-25 INFO : root : creating build/lib/botocore/data/dataexchange INFO : root : creating build/lib/botocore/data/dataexchange/2017-07-25 INFO : root : copying botocore/data/dataexchange/2017-07-25/paginators-1.json -> build/lib/botocore/data/dataexchange/2017-07-25 INFO : root : copying botocore/data/dataexchange/2017-07-25/service-2.json -> build/lib/botocore/data/dataexchange/2017-07-25 INFO : root : copying botocore/data/dataexchange/2017-07-25/waiters-2.json -> build/lib/botocore/data/dataexchange/2017-07-25 INFO : root : creating build/lib/botocore/data/datapipeline INFO : root : creating build/lib/botocore/data/datapipeline/2012-10-29 INFO : root : copying botocore/data/datapipeline/2012-10-29/examples-1.json -> build/lib/botocore/data/datapipeline/2012-10-29 INFO : root : copying botocore/data/datapipeline/2012-10-29/paginators-1.json -> build/lib/botocore/data/datapipeline/2012-10-29 INFO : root : copying botocore/data/datapipeline/2012-10-29/service-2.json -> build/lib/botocore/data/datapipeline/2012-10-29 INFO : root : creating build/lib/botocore/data/datasync INFO : root : creating build/lib/botocore/data/datasync/2018-11-09 INFO : root : copying botocore/data/datasync/2018-11-09/examples-1.json -> build/lib/botocore/data/datasync/2018-11-09 INFO : root : copying botocore/data/datasync/2018-11-09/paginators-1.json -> build/lib/botocore/data/datasync/2018-11-09 INFO : root : copying botocore/data/datasync/2018-11-09/service-2.json -> build/lib/botocore/data/datasync/2018-11-09 INFO : root : creating build/lib/botocore/data/dax INFO : root : creating build/lib/botocore/data/dax/2017-04-19 INFO : root : copying botocore/data/dax/2017-04-19/examples-1.json -> build/lib/botocore/data/dax/2017-04-19 INFO : root : copying botocore/data/dax/2017-04-19/paginators-1.json -> build/lib/botocore/data/dax/2017-04-19 INFO : root : copying botocore/data/dax/2017-04-19/service-2.json -> build/lib/botocore/data/dax/2017-04-19 INFO : root : creating build/lib/botocore/data/detective INFO : root : creating build/lib/botocore/data/detective/2018-10-26 INFO : root : copying botocore/data/detective/2018-10-26/examples-1.json -> build/lib/botocore/data/detective/2018-10-26 INFO : root : copying botocore/data/detective/2018-10-26/paginators-1.json -> build/lib/botocore/data/detective/2018-10-26 INFO : root : copying botocore/data/detective/2018-10-26/service-2.json -> build/lib/botocore/data/detective/2018-10-26 INFO : root : creating build/lib/botocore/data/devicefarm INFO : root : creating build/lib/botocore/data/devicefarm/2015-06-23 INFO : root : copying botocore/data/devicefarm/2015-06-23/examples-1.json -> build/lib/botocore/data/devicefarm/2015-06-23 INFO : root : copying botocore/data/devicefarm/2015-06-23/paginators-1.json -> build/lib/botocore/data/devicefarm/2015-06-23 INFO : root : copying botocore/data/devicefarm/2015-06-23/service-2.json -> build/lib/botocore/data/devicefarm/2015-06-23 INFO : root : creating build/lib/botocore/data/devops-guru INFO : root : creating build/lib/botocore/data/devops-guru/2020-12-01 INFO : root : copying botocore/data/devops-guru/2020-12-01/examples-1.json -> build/lib/botocore/data/devops-guru/2020-12-01 INFO : root : copying botocore/data/devops-guru/2020-12-01/paginators-1.json -> build/lib/botocore/data/devops-guru/2020-12-01 INFO : root : copying botocore/data/devops-guru/2020-12-01/service-2.json -> build/lib/botocore/data/devops-guru/2020-12-01 INFO : root : creating build/lib/botocore/data/directconnect INFO : root : creating build/lib/botocore/data/directconnect/2012-10-25 INFO : root : copying botocore/data/directconnect/2012-10-25/examples-1.json -> build/lib/botocore/data/directconnect/2012-10-25 INFO : root : copying botocore/data/directconnect/2012-10-25/paginators-1.json -> build/lib/botocore/data/directconnect/2012-10-25 INFO : root : copying botocore/data/directconnect/2012-10-25/service-2.json -> build/lib/botocore/data/directconnect/2012-10-25 INFO : root : creating build/lib/botocore/data/discovery INFO : root : creating build/lib/botocore/data/discovery/2015-11-01 INFO : root : copying botocore/data/discovery/2015-11-01/examples-1.json -> build/lib/botocore/data/discovery/2015-11-01 INFO : root : copying botocore/data/discovery/2015-11-01/paginators-1.json -> build/lib/botocore/data/discovery/2015-11-01 INFO : root : copying botocore/data/discovery/2015-11-01/service-2.json -> build/lib/botocore/data/discovery/2015-11-01 INFO : root : creating build/lib/botocore/data/dlm INFO : root : creating build/lib/botocore/data/dlm/2018-01-12 INFO : root : copying botocore/data/dlm/2018-01-12/examples-1.json -> build/lib/botocore/data/dlm/2018-01-12 INFO : root : copying botocore/data/dlm/2018-01-12/paginators-1.json -> build/lib/botocore/data/dlm/2018-01-12 INFO : root : copying botocore/data/dlm/2018-01-12/service-2.json -> build/lib/botocore/data/dlm/2018-01-12 INFO : root : creating build/lib/botocore/data/dms INFO : root : creating build/lib/botocore/data/dms/2016-01-01 INFO : root : copying botocore/data/dms/2016-01-01/examples-1.json -> build/lib/botocore/data/dms/2016-01-01 INFO : root : copying botocore/data/dms/2016-01-01/paginators-1.json -> build/lib/botocore/data/dms/2016-01-01 INFO : root : copying botocore/data/dms/2016-01-01/service-2.json -> build/lib/botocore/data/dms/2016-01-01 INFO : root : copying botocore/data/dms/2016-01-01/waiters-2.json -> build/lib/botocore/data/dms/2016-01-01 INFO : root : creating build/lib/botocore/data/docdb INFO : root : creating build/lib/botocore/data/docdb/2014-10-31 INFO : root : copying botocore/data/docdb/2014-10-31/examples-1.json -> build/lib/botocore/data/docdb/2014-10-31 INFO : root : copying botocore/data/docdb/2014-10-31/paginators-1.json -> build/lib/botocore/data/docdb/2014-10-31 INFO : root : copying botocore/data/docdb/2014-10-31/service-2.json -> build/lib/botocore/data/docdb/2014-10-31 INFO : root : copying botocore/data/docdb/2014-10-31/service-2.sdk-extras.json -> build/lib/botocore/data/docdb/2014-10-31 INFO : root : copying botocore/data/docdb/2014-10-31/waiters-2.json -> build/lib/botocore/data/docdb/2014-10-31 INFO : root : creating build/lib/botocore/data/drs INFO : root : creating build/lib/botocore/data/drs/2020-02-26 INFO : root : copying botocore/data/drs/2020-02-26/examples-1.json -> build/lib/botocore/data/drs/2020-02-26 INFO : root : copying botocore/data/drs/2020-02-26/paginators-1.json -> build/lib/botocore/data/drs/2020-02-26 INFO : root : copying botocore/data/drs/2020-02-26/service-2.json -> build/lib/botocore/data/drs/2020-02-26 INFO : root : creating build/lib/botocore/data/ds INFO : root : creating build/lib/botocore/data/ds/2015-04-16 INFO : root : copying botocore/data/ds/2015-04-16/examples-1.json -> build/lib/botocore/data/ds/2015-04-16 INFO : root : copying botocore/data/ds/2015-04-16/paginators-1.json -> build/lib/botocore/data/ds/2015-04-16 INFO : root : copying botocore/data/ds/2015-04-16/service-2.json -> build/lib/botocore/data/ds/2015-04-16 INFO : root : creating build/lib/botocore/data/dynamodb INFO : root : creating build/lib/botocore/data/dynamodb/2011-12-05 INFO : root : copying botocore/data/dynamodb/2011-12-05/examples-1.json -> build/lib/botocore/data/dynamodb/2011-12-05 INFO : root : creating build/lib/botocore/data/dynamodb/2012-08-10 INFO : root : copying botocore/data/dynamodb/2012-08-10/examples-1.json -> build/lib/botocore/data/dynamodb/2012-08-10 INFO : root : copying botocore/data/dynamodb/2012-08-10/paginators-1.json -> build/lib/botocore/data/dynamodb/2012-08-10 INFO : root : copying botocore/data/dynamodb/2012-08-10/service-2.json -> build/lib/botocore/data/dynamodb/2012-08-10 INFO : root : copying botocore/data/dynamodb/2012-08-10/waiters-2.json -> build/lib/botocore/data/dynamodb/2012-08-10 INFO : root : creating build/lib/botocore/data/dynamodbstreams INFO : root : creating build/lib/botocore/data/dynamodbstreams/2012-08-10 INFO : root : copying botocore/data/dynamodbstreams/2012-08-10/examples-1.json -> build/lib/botocore/data/dynamodbstreams/2012-08-10 INFO : root : copying botocore/data/dynamodbstreams/2012-08-10/paginators-1.json -> build/lib/botocore/data/dynamodbstreams/2012-08-10 INFO : root : copying botocore/data/dynamodbstreams/2012-08-10/service-2.json -> build/lib/botocore/data/dynamodbstreams/2012-08-10 INFO : root : creating build/lib/botocore/data/ebs INFO : root : creating build/lib/botocore/data/ebs/2019-11-02 INFO : root : copying botocore/data/ebs/2019-11-02/examples-1.json -> build/lib/botocore/data/ebs/2019-11-02 INFO : root : copying botocore/data/ebs/2019-11-02/paginators-1.json -> build/lib/botocore/data/ebs/2019-11-02 INFO : root : copying botocore/data/ebs/2019-11-02/service-2.json -> build/lib/botocore/data/ebs/2019-11-02 INFO : root : creating build/lib/botocore/data/ec2-instance-connect INFO : root : creating build/lib/botocore/data/ec2-instance-connect/2018-04-02 INFO : root : copying botocore/data/ec2-instance-connect/2018-04-02/examples-1.json -> build/lib/botocore/data/ec2-instance-connect/2018-04-02 INFO : root : copying botocore/data/ec2-instance-connect/2018-04-02/paginators-1.json -> build/lib/botocore/data/ec2-instance-connect/2018-04-02 INFO : root : copying botocore/data/ec2-instance-connect/2018-04-02/service-2.json -> build/lib/botocore/data/ec2-instance-connect/2018-04-02 INFO : root : creating build/lib/botocore/data/ec2 INFO : root : creating build/lib/botocore/data/ec2/2014-09-01 INFO : root : copying botocore/data/ec2/2014-09-01/paginators-1.json -> build/lib/botocore/data/ec2/2014-09-01 INFO : root : copying botocore/data/ec2/2014-09-01/service-2.json -> build/lib/botocore/data/ec2/2014-09-01 INFO : root : copying botocore/data/ec2/2014-09-01/waiters-2.json -> build/lib/botocore/data/ec2/2014-09-01 INFO : root : creating build/lib/botocore/data/ec2/2014-10-01 INFO : root : copying botocore/data/ec2/2014-10-01/paginators-1.json -> build/lib/botocore/data/ec2/2014-10-01 INFO : root : copying botocore/data/ec2/2014-10-01/service-2.json -> build/lib/botocore/data/ec2/2014-10-01 INFO : root : copying botocore/data/ec2/2014-10-01/waiters-2.json -> build/lib/botocore/data/ec2/2014-10-01 INFO : root : creating build/lib/botocore/data/ec2/2015-03-01 INFO : root : copying botocore/data/ec2/2015-03-01/paginators-1.json -> build/lib/botocore/data/ec2/2015-03-01 INFO : root : copying botocore/data/ec2/2015-03-01/service-2.json -> build/lib/botocore/data/ec2/2015-03-01 INFO : root : copying botocore/data/ec2/2015-03-01/waiters-2.json -> build/lib/botocore/data/ec2/2015-03-01 INFO : root : creating build/lib/botocore/data/ec2/2015-04-15 INFO : root : copying botocore/data/ec2/2015-04-15/paginators-1.json -> build/lib/botocore/data/ec2/2015-04-15 INFO : root : copying botocore/data/ec2/2015-04-15/service-2.json -> build/lib/botocore/data/ec2/2015-04-15 INFO : root : copying botocore/data/ec2/2015-04-15/waiters-2.json -> build/lib/botocore/data/ec2/2015-04-15 INFO : root : creating build/lib/botocore/data/ec2/2015-10-01 INFO : root : copying botocore/data/ec2/2015-10-01/examples-1.json -> build/lib/botocore/data/ec2/2015-10-01 INFO : root : copying botocore/data/ec2/2015-10-01/paginators-1.json -> build/lib/botocore/data/ec2/2015-10-01 INFO : root : copying botocore/data/ec2/2015-10-01/service-2.json -> build/lib/botocore/data/ec2/2015-10-01 INFO : root : copying botocore/data/ec2/2015-10-01/waiters-2.json -> build/lib/botocore/data/ec2/2015-10-01 INFO : root : creating build/lib/botocore/data/ec2/2016-04-01 INFO : root : copying botocore/data/ec2/2016-04-01/examples-1.json -> build/lib/botocore/data/ec2/2016-04-01 INFO : root : copying botocore/data/ec2/2016-04-01/paginators-1.json -> build/lib/botocore/data/ec2/2016-04-01 INFO : root : copying botocore/data/ec2/2016-04-01/service-2.json -> build/lib/botocore/data/ec2/2016-04-01 INFO : root : copying botocore/data/ec2/2016-04-01/waiters-2.json -> build/lib/botocore/data/ec2/2016-04-01 INFO : root : creating build/lib/botocore/data/ec2/2016-09-15 INFO : root : copying botocore/data/ec2/2016-09-15/examples-1.json -> build/lib/botocore/data/ec2/2016-09-15 INFO : root : copying botocore/data/ec2/2016-09-15/paginators-1.json -> build/lib/botocore/data/ec2/2016-09-15 INFO : root : copying botocore/data/ec2/2016-09-15/service-2.json -> build/lib/botocore/data/ec2/2016-09-15 INFO : root : copying botocore/data/ec2/2016-09-15/waiters-2.json -> build/lib/botocore/data/ec2/2016-09-15 INFO : root : creating build/lib/botocore/data/ec2/2016-11-15 INFO : root : copying botocore/data/ec2/2016-11-15/examples-1.json -> build/lib/botocore/data/ec2/2016-11-15 INFO : root : copying botocore/data/ec2/2016-11-15/paginators-1.json -> build/lib/botocore/data/ec2/2016-11-15 INFO : root : copying botocore/data/ec2/2016-11-15/service-2.json -> build/lib/botocore/data/ec2/2016-11-15 INFO : root : copying botocore/data/ec2/2016-11-15/waiters-2.json -> build/lib/botocore/data/ec2/2016-11-15 INFO : root : creating build/lib/botocore/data/ecr-public INFO : root : creating build/lib/botocore/data/ecr-public/2020-10-30 INFO : root : copying botocore/data/ecr-public/2020-10-30/examples-1.json -> build/lib/botocore/data/ecr-public/2020-10-30 INFO : root : copying botocore/data/ecr-public/2020-10-30/paginators-1.json -> build/lib/botocore/data/ecr-public/2020-10-30 INFO : root : copying botocore/data/ecr-public/2020-10-30/service-2.json -> build/lib/botocore/data/ecr-public/2020-10-30 INFO : root : creating build/lib/botocore/data/ecr INFO : root : creating build/lib/botocore/data/ecr/2015-09-21 INFO : root : copying botocore/data/ecr/2015-09-21/examples-1.json -> build/lib/botocore/data/ecr/2015-09-21 INFO : root : copying botocore/data/ecr/2015-09-21/paginators-1.json -> build/lib/botocore/data/ecr/2015-09-21 INFO : root : copying botocore/data/ecr/2015-09-21/service-2.json -> build/lib/botocore/data/ecr/2015-09-21 INFO : root : copying botocore/data/ecr/2015-09-21/waiters-2.json -> build/lib/botocore/data/ecr/2015-09-21 INFO : root : creating build/lib/botocore/data/ecs INFO : root : creating build/lib/botocore/data/ecs/2014-11-13 INFO : root : copying botocore/data/ecs/2014-11-13/examples-1.json -> build/lib/botocore/data/ecs/2014-11-13 INFO : root : copying botocore/data/ecs/2014-11-13/paginators-1.json -> build/lib/botocore/data/ecs/2014-11-13 INFO : root : copying botocore/data/ecs/2014-11-13/service-2.json -> build/lib/botocore/data/ecs/2014-11-13 INFO : root : copying botocore/data/ecs/2014-11-13/waiters-2.json -> build/lib/botocore/data/ecs/2014-11-13 INFO : root : creating build/lib/botocore/data/efs INFO : root : creating build/lib/botocore/data/efs/2015-02-01 INFO : root : copying botocore/data/efs/2015-02-01/examples-1.json -> build/lib/botocore/data/efs/2015-02-01 INFO : root : copying botocore/data/efs/2015-02-01/paginators-1.json -> build/lib/botocore/data/efs/2015-02-01 INFO : root : copying botocore/data/efs/2015-02-01/service-2.json -> build/lib/botocore/data/efs/2015-02-01 INFO : root : creating build/lib/botocore/data/eks INFO : root : creating build/lib/botocore/data/eks/2017-11-01 INFO : root : copying botocore/data/eks/2017-11-01/examples-1.json -> build/lib/botocore/data/eks/2017-11-01 INFO : root : copying botocore/data/eks/2017-11-01/paginators-1.json -> build/lib/botocore/data/eks/2017-11-01 INFO : root : copying botocore/data/eks/2017-11-01/service-2.json -> build/lib/botocore/data/eks/2017-11-01 INFO : root : copying botocore/data/eks/2017-11-01/service-2.sdk-extras.json -> build/lib/botocore/data/eks/2017-11-01 INFO : root : copying botocore/data/eks/2017-11-01/waiters-2.json -> build/lib/botocore/data/eks/2017-11-01 INFO : root : creating build/lib/botocore/data/elastic-inference INFO : root : creating build/lib/botocore/data/elastic-inference/2017-07-25 INFO : root : copying botocore/data/elastic-inference/2017-07-25/examples-1.json -> build/lib/botocore/data/elastic-inference/2017-07-25 INFO : root : copying botocore/data/elastic-inference/2017-07-25/paginators-1.json -> build/lib/botocore/data/elastic-inference/2017-07-25 INFO : root : copying botocore/data/elastic-inference/2017-07-25/service-2.json -> build/lib/botocore/data/elastic-inference/2017-07-25 INFO : root : creating build/lib/botocore/data/elasticache INFO : root : creating build/lib/botocore/data/elasticache/2014-09-30 INFO : root : copying botocore/data/elasticache/2014-09-30/paginators-1.json -> build/lib/botocore/data/elasticache/2014-09-30 INFO : root : copying botocore/data/elasticache/2014-09-30/service-2.json -> build/lib/botocore/data/elasticache/2014-09-30 INFO : root : copying botocore/data/elasticache/2014-09-30/waiters-2.json -> build/lib/botocore/data/elasticache/2014-09-30 INFO : root : creating build/lib/botocore/data/elasticache/2015-02-02 INFO : root : copying botocore/data/elasticache/2015-02-02/examples-1.json -> build/lib/botocore/data/elasticache/2015-02-02 INFO : root : copying botocore/data/elasticache/2015-02-02/paginators-1.json -> build/lib/botocore/data/elasticache/2015-02-02 INFO : root : copying botocore/data/elasticache/2015-02-02/service-2.json -> build/lib/botocore/data/elasticache/2015-02-02 INFO : root : copying botocore/data/elasticache/2015-02-02/waiters-2.json -> build/lib/botocore/data/elasticache/2015-02-02 INFO : root : creating build/lib/botocore/data/elasticbeanstalk INFO : root : creating build/lib/botocore/data/elasticbeanstalk/2010-12-01 INFO : root : copying botocore/data/elasticbeanstalk/2010-12-01/examples-1.json -> build/lib/botocore/data/elasticbeanstalk/2010-12-01 INFO : root : copying botocore/data/elasticbeanstalk/2010-12-01/paginators-1.json -> build/lib/botocore/data/elasticbeanstalk/2010-12-01 INFO : root : copying botocore/data/elasticbeanstalk/2010-12-01/service-2.json -> build/lib/botocore/data/elasticbeanstalk/2010-12-01 INFO : root : copying botocore/data/elasticbeanstalk/2010-12-01/waiters-2.json -> build/lib/botocore/data/elasticbeanstalk/2010-12-01 INFO : root : creating build/lib/botocore/data/elastictranscoder INFO : root : creating build/lib/botocore/data/elastictranscoder/2012-09-25 INFO : root : copying botocore/data/elastictranscoder/2012-09-25/examples-1.json -> build/lib/botocore/data/elastictranscoder/2012-09-25 INFO : root : copying botocore/data/elastictranscoder/2012-09-25/paginators-1.json -> build/lib/botocore/data/elastictranscoder/2012-09-25 INFO : root : copying botocore/data/elastictranscoder/2012-09-25/service-2.json -> build/lib/botocore/data/elastictranscoder/2012-09-25 INFO : root : copying botocore/data/elastictranscoder/2012-09-25/waiters-2.json -> build/lib/botocore/data/elastictranscoder/2012-09-25 INFO : root : creating build/lib/botocore/data/elb INFO : root : creating build/lib/botocore/data/elb/2012-06-01 INFO : root : copying botocore/data/elb/2012-06-01/examples-1.json -> build/lib/botocore/data/elb/2012-06-01 INFO : root : copying botocore/data/elb/2012-06-01/paginators-1.json -> build/lib/botocore/data/elb/2012-06-01 INFO : root : copying botocore/data/elb/2012-06-01/service-2.json -> build/lib/botocore/data/elb/2012-06-01 INFO : root : copying botocore/data/elb/2012-06-01/waiters-2.json -> build/lib/botocore/data/elb/2012-06-01 INFO : root : creating build/lib/botocore/data/elbv2 INFO : root : creating build/lib/botocore/data/elbv2/2015-12-01 INFO : root : copying botocore/data/elbv2/2015-12-01/examples-1.json -> build/lib/botocore/data/elbv2/2015-12-01 INFO : root : copying botocore/data/elbv2/2015-12-01/paginators-1.json -> build/lib/botocore/data/elbv2/2015-12-01 INFO : root : copying botocore/data/elbv2/2015-12-01/service-2.json -> build/lib/botocore/data/elbv2/2015-12-01 INFO : root : copying botocore/data/elbv2/2015-12-01/waiters-2.json -> build/lib/botocore/data/elbv2/2015-12-01 INFO : root : creating build/lib/botocore/data/emr-containers INFO : root : creating build/lib/botocore/data/emr-containers/2020-10-01 INFO : root : copying botocore/data/emr-containers/2020-10-01/examples-1.json -> build/lib/botocore/data/emr-containers/2020-10-01 INFO : root : copying botocore/data/emr-containers/2020-10-01/paginators-1.json -> build/lib/botocore/data/emr-containers/2020-10-01 INFO : root : copying botocore/data/emr-containers/2020-10-01/service-2.json -> build/lib/botocore/data/emr-containers/2020-10-01 INFO : root : creating build/lib/botocore/data/emr-serverless INFO : root : creating build/lib/botocore/data/emr-serverless/2021-07-13 INFO : root : copying botocore/data/emr-serverless/2021-07-13/paginators-1.json -> build/lib/botocore/data/emr-serverless/2021-07-13 INFO : root : copying botocore/data/emr-serverless/2021-07-13/service-2.json -> build/lib/botocore/data/emr-serverless/2021-07-13 INFO : root : creating build/lib/botocore/data/emr INFO : root : creating build/lib/botocore/data/emr/2009-03-31 INFO : root : copying botocore/data/emr/2009-03-31/examples-1.json -> build/lib/botocore/data/emr/2009-03-31 INFO : root : copying botocore/data/emr/2009-03-31/paginators-1.json -> build/lib/botocore/data/emr/2009-03-31 INFO : root : copying botocore/data/emr/2009-03-31/service-2.json -> build/lib/botocore/data/emr/2009-03-31 INFO : root : copying botocore/data/emr/2009-03-31/waiters-2.json -> build/lib/botocore/data/emr/2009-03-31 INFO : root : creating build/lib/botocore/data/es INFO : root : creating build/lib/botocore/data/es/2015-01-01 INFO : root : copying botocore/data/es/2015-01-01/examples-1.json -> build/lib/botocore/data/es/2015-01-01 INFO : root : copying botocore/data/es/2015-01-01/paginators-1.json -> build/lib/botocore/data/es/2015-01-01 INFO : root : copying botocore/data/es/2015-01-01/service-2.json -> build/lib/botocore/data/es/2015-01-01 INFO : root : creating build/lib/botocore/data/events INFO : root : creating build/lib/botocore/data/events/2014-02-03 INFO : root : copying botocore/data/events/2014-02-03/service-2.json -> build/lib/botocore/data/events/2014-02-03 INFO : root : creating build/lib/botocore/data/events/2015-10-07 INFO : root : copying botocore/data/events/2015-10-07/examples-1.json -> build/lib/botocore/data/events/2015-10-07 INFO : root : copying botocore/data/events/2015-10-07/paginators-1.json -> build/lib/botocore/data/events/2015-10-07 INFO : root : copying botocore/data/events/2015-10-07/service-2.json -> build/lib/botocore/data/events/2015-10-07 INFO : root : creating build/lib/botocore/data/evidently INFO : root : creating build/lib/botocore/data/evidently/2021-02-01 INFO : root : copying botocore/data/evidently/2021-02-01/examples-1.json -> build/lib/botocore/data/evidently/2021-02-01 INFO : root : copying botocore/data/evidently/2021-02-01/paginators-1.json -> build/lib/botocore/data/evidently/2021-02-01 INFO : root : copying botocore/data/evidently/2021-02-01/service-2.json -> build/lib/botocore/data/evidently/2021-02-01 INFO : root : creating build/lib/botocore/data/finspace-data INFO : root : creating build/lib/botocore/data/finspace-data/2020-07-13 INFO : root : copying botocore/data/finspace-data/2020-07-13/examples-1.json -> build/lib/botocore/data/finspace-data/2020-07-13 INFO : root : copying botocore/data/finspace-data/2020-07-13/paginators-1.json -> build/lib/botocore/data/finspace-data/2020-07-13 INFO : root : copying botocore/data/finspace-data/2020-07-13/service-2.json -> build/lib/botocore/data/finspace-data/2020-07-13 INFO : root : creating build/lib/botocore/data/finspace INFO : root : creating build/lib/botocore/data/finspace/2021-03-12 INFO : root : copying botocore/data/finspace/2021-03-12/examples-1.json -> build/lib/botocore/data/finspace/2021-03-12 INFO : root : copying botocore/data/finspace/2021-03-12/paginators-1.json -> build/lib/botocore/data/finspace/2021-03-12 INFO : root : copying botocore/data/finspace/2021-03-12/service-2.json -> build/lib/botocore/data/finspace/2021-03-12 INFO : root : creating build/lib/botocore/data/firehose INFO : root : creating build/lib/botocore/data/firehose/2015-08-04 INFO : root : copying botocore/data/firehose/2015-08-04/examples-1.json -> build/lib/botocore/data/firehose/2015-08-04 INFO : root : copying botocore/data/firehose/2015-08-04/paginators-1.json -> build/lib/botocore/data/firehose/2015-08-04 INFO : root : copying botocore/data/firehose/2015-08-04/service-2.json -> build/lib/botocore/data/firehose/2015-08-04 INFO : root : creating build/lib/botocore/data/fis INFO : root : creating build/lib/botocore/data/fis/2020-12-01 INFO : root : copying botocore/data/fis/2020-12-01/examples-1.json -> build/lib/botocore/data/fis/2020-12-01 INFO : root : copying botocore/data/fis/2020-12-01/paginators-1.json -> build/lib/botocore/data/fis/2020-12-01 INFO : root : copying botocore/data/fis/2020-12-01/service-2.json -> build/lib/botocore/data/fis/2020-12-01 INFO : root : creating build/lib/botocore/data/fms INFO : root : creating build/lib/botocore/data/fms/2018-01-01 INFO : root : copying botocore/data/fms/2018-01-01/examples-1.json -> build/lib/botocore/data/fms/2018-01-01 INFO : root : copying botocore/data/fms/2018-01-01/paginators-1.json -> build/lib/botocore/data/fms/2018-01-01 INFO : root : copying botocore/data/fms/2018-01-01/service-2.json -> build/lib/botocore/data/fms/2018-01-01 INFO : root : creating build/lib/botocore/data/forecast INFO : root : creating build/lib/botocore/data/forecast/2018-06-26 INFO : root : copying botocore/data/forecast/2018-06-26/examples-1.json -> build/lib/botocore/data/forecast/2018-06-26 INFO : root : copying botocore/data/forecast/2018-06-26/paginators-1.json -> build/lib/botocore/data/forecast/2018-06-26 INFO : root : copying botocore/data/forecast/2018-06-26/service-2.json -> build/lib/botocore/data/forecast/2018-06-26 INFO : root : creating build/lib/botocore/data/forecastquery INFO : root : creating build/lib/botocore/data/forecastquery/2018-06-26 INFO : root : copying botocore/data/forecastquery/2018-06-26/examples-1.json -> build/lib/botocore/data/forecastquery/2018-06-26 INFO : root : copying botocore/data/forecastquery/2018-06-26/paginators-1.json -> build/lib/botocore/data/forecastquery/2018-06-26 INFO : root : copying botocore/data/forecastquery/2018-06-26/service-2.json -> build/lib/botocore/data/forecastquery/2018-06-26 INFO : root : creating build/lib/botocore/data/frauddetector INFO : root : creating build/lib/botocore/data/frauddetector/2019-11-15 INFO : root : copying botocore/data/frauddetector/2019-11-15/examples-1.json -> build/lib/botocore/data/frauddetector/2019-11-15 INFO : root : copying botocore/data/frauddetector/2019-11-15/paginators-1.json -> build/lib/botocore/data/frauddetector/2019-11-15 INFO : root : copying botocore/data/frauddetector/2019-11-15/service-2.json -> build/lib/botocore/data/frauddetector/2019-11-15 INFO : root : creating build/lib/botocore/data/fsx INFO : root : creating build/lib/botocore/data/fsx/2018-03-01 INFO : root : copying botocore/data/fsx/2018-03-01/examples-1.json -> build/lib/botocore/data/fsx/2018-03-01 INFO : root : copying botocore/data/fsx/2018-03-01/paginators-1.json -> build/lib/botocore/data/fsx/2018-03-01 INFO : root : copying botocore/data/fsx/2018-03-01/service-2.json -> build/lib/botocore/data/fsx/2018-03-01 INFO : root : creating build/lib/botocore/data/gamelift INFO : root : creating build/lib/botocore/data/gamelift/2015-10-01 INFO : root : copying botocore/data/gamelift/2015-10-01/examples-1.json -> build/lib/botocore/data/gamelift/2015-10-01 INFO : root : copying botocore/data/gamelift/2015-10-01/paginators-1.json -> build/lib/botocore/data/gamelift/2015-10-01 INFO : root : copying botocore/data/gamelift/2015-10-01/service-2.json -> build/lib/botocore/data/gamelift/2015-10-01 INFO : root : creating build/lib/botocore/data/gamesparks INFO : root : creating build/lib/botocore/data/gamesparks/2021-08-17 INFO : root : copying botocore/data/gamesparks/2021-08-17/examples-1.json -> build/lib/botocore/data/gamesparks/2021-08-17 INFO : root : copying botocore/data/gamesparks/2021-08-17/paginators-1.json -> build/lib/botocore/data/gamesparks/2021-08-17 INFO : root : copying botocore/data/gamesparks/2021-08-17/service-2.json -> build/lib/botocore/data/gamesparks/2021-08-17 INFO : root : creating build/lib/botocore/data/glacier INFO : root : creating build/lib/botocore/data/glacier/2012-06-01 INFO : root : copying botocore/data/glacier/2012-06-01/examples-1.json -> build/lib/botocore/data/glacier/2012-06-01 INFO : root : copying botocore/data/glacier/2012-06-01/paginators-1.json -> build/lib/botocore/data/glacier/2012-06-01 INFO : root : copying botocore/data/glacier/2012-06-01/service-2.json -> build/lib/botocore/data/glacier/2012-06-01 INFO : root : copying botocore/data/glacier/2012-06-01/waiters-2.json -> build/lib/botocore/data/glacier/2012-06-01 INFO : root : creating build/lib/botocore/data/globalaccelerator INFO : root : creating build/lib/botocore/data/globalaccelerator/2018-08-08 INFO : root : copying botocore/data/globalaccelerator/2018-08-08/examples-1.json -> build/lib/botocore/data/globalaccelerator/2018-08-08 INFO : root : copying botocore/data/globalaccelerator/2018-08-08/paginators-1.json -> build/lib/botocore/data/globalaccelerator/2018-08-08 INFO : root : copying botocore/data/globalaccelerator/2018-08-08/service-2.json -> build/lib/botocore/data/globalaccelerator/2018-08-08 INFO : root : creating build/lib/botocore/data/glue INFO : root : creating build/lib/botocore/data/glue/2017-03-31 INFO : root : copying botocore/data/glue/2017-03-31/examples-1.json -> build/lib/botocore/data/glue/2017-03-31 INFO : root : copying botocore/data/glue/2017-03-31/paginators-1.json -> build/lib/botocore/data/glue/2017-03-31 INFO : root : copying botocore/data/glue/2017-03-31/service-2.json -> build/lib/botocore/data/glue/2017-03-31 INFO : root : creating build/lib/botocore/data/grafana INFO : root : creating build/lib/botocore/data/grafana/2020-08-18 INFO : root : copying botocore/data/grafana/2020-08-18/examples-1.json -> build/lib/botocore/data/grafana/2020-08-18 INFO : root : copying botocore/data/grafana/2020-08-18/paginators-1.json -> build/lib/botocore/data/grafana/2020-08-18 INFO : root : copying botocore/data/grafana/2020-08-18/service-2.json -> build/lib/botocore/data/grafana/2020-08-18 INFO : root : creating build/lib/botocore/data/greengrass INFO : root : creating build/lib/botocore/data/greengrass/2017-06-07 INFO : root : copying botocore/data/greengrass/2017-06-07/paginators-1.json -> build/lib/botocore/data/greengrass/2017-06-07 INFO : root : copying botocore/data/greengrass/2017-06-07/service-2.json -> build/lib/botocore/data/greengrass/2017-06-07 INFO : root : creating build/lib/botocore/data/greengrassv2 INFO : root : creating build/lib/botocore/data/greengrassv2/2020-11-30 INFO : root : copying botocore/data/greengrassv2/2020-11-30/examples-1.json -> build/lib/botocore/data/greengrassv2/2020-11-30 INFO : root : copying botocore/data/greengrassv2/2020-11-30/paginators-1.json -> build/lib/botocore/data/greengrassv2/2020-11-30 INFO : root : copying botocore/data/greengrassv2/2020-11-30/service-2.json -> build/lib/botocore/data/greengrassv2/2020-11-30 INFO : root : creating build/lib/botocore/data/groundstation INFO : root : creating build/lib/botocore/data/groundstation/2019-05-23 INFO : root : copying botocore/data/groundstation/2019-05-23/examples-1.json -> build/lib/botocore/data/groundstation/2019-05-23 INFO : root : copying botocore/data/groundstation/2019-05-23/paginators-1.json -> build/lib/botocore/data/groundstation/2019-05-23 INFO : root : copying botocore/data/groundstation/2019-05-23/service-2.json -> build/lib/botocore/data/groundstation/2019-05-23 INFO : root : creating build/lib/botocore/data/guardduty INFO : root : creating build/lib/botocore/data/guardduty/2017-11-28 INFO : root : copying botocore/data/guardduty/2017-11-28/examples-1.json -> build/lib/botocore/data/guardduty/2017-11-28 INFO : root : copying botocore/data/guardduty/2017-11-28/paginators-1.json -> build/lib/botocore/data/guardduty/2017-11-28 INFO : root : copying botocore/data/guardduty/2017-11-28/service-2.json -> build/lib/botocore/data/guardduty/2017-11-28 INFO : root : creating build/lib/botocore/data/health INFO : root : creating build/lib/botocore/data/health/2016-08-04 INFO : root : copying botocore/data/health/2016-08-04/examples-1.json -> build/lib/botocore/data/health/2016-08-04 INFO : root : copying botocore/data/health/2016-08-04/paginators-1.json -> build/lib/botocore/data/health/2016-08-04 INFO : root : copying botocore/data/health/2016-08-04/service-2.json -> build/lib/botocore/data/health/2016-08-04 INFO : root : creating build/lib/botocore/data/healthlake INFO : root : creating build/lib/botocore/data/healthlake/2017-07-01 INFO : root : copying botocore/data/healthlake/2017-07-01/examples-1.json -> build/lib/botocore/data/healthlake/2017-07-01 INFO : root : copying botocore/data/healthlake/2017-07-01/paginators-1.json -> build/lib/botocore/data/healthlake/2017-07-01 INFO : root : copying botocore/data/healthlake/2017-07-01/service-2.json -> build/lib/botocore/data/healthlake/2017-07-01 INFO : root : creating build/lib/botocore/data/honeycode INFO : root : creating build/lib/botocore/data/honeycode/2020-03-01 INFO : root : copying botocore/data/honeycode/2020-03-01/examples-1.json -> build/lib/botocore/data/honeycode/2020-03-01 INFO : root : copying botocore/data/honeycode/2020-03-01/paginators-1.json -> build/lib/botocore/data/honeycode/2020-03-01 INFO : root : copying botocore/data/honeycode/2020-03-01/paginators-1.sdk-extras.json -> build/lib/botocore/data/honeycode/2020-03-01 INFO : root : copying botocore/data/honeycode/2020-03-01/service-2.json -> build/lib/botocore/data/honeycode/2020-03-01 INFO : root : creating build/lib/botocore/data/iam INFO : root : creating build/lib/botocore/data/iam/2010-05-08 INFO : root : copying botocore/data/iam/2010-05-08/examples-1.json -> build/lib/botocore/data/iam/2010-05-08 INFO : root : copying botocore/data/iam/2010-05-08/paginators-1.json -> build/lib/botocore/data/iam/2010-05-08 INFO : root : copying botocore/data/iam/2010-05-08/service-2.json -> build/lib/botocore/data/iam/2010-05-08 INFO : root : copying botocore/data/iam/2010-05-08/waiters-2.json -> build/lib/botocore/data/iam/2010-05-08 INFO : root : creating build/lib/botocore/data/identitystore INFO : root : creating build/lib/botocore/data/identitystore/2020-06-15 INFO : root : copying botocore/data/identitystore/2020-06-15/examples-1.json -> build/lib/botocore/data/identitystore/2020-06-15 INFO : root : copying botocore/data/identitystore/2020-06-15/paginators-1.json -> build/lib/botocore/data/identitystore/2020-06-15 INFO : root : copying botocore/data/identitystore/2020-06-15/service-2.json -> build/lib/botocore/data/identitystore/2020-06-15 INFO : root : creating build/lib/botocore/data/imagebuilder INFO : root : creating build/lib/botocore/data/imagebuilder/2019-12-02 INFO : root : copying botocore/data/imagebuilder/2019-12-02/examples-1.json -> build/lib/botocore/data/imagebuilder/2019-12-02 INFO : root : copying botocore/data/imagebuilder/2019-12-02/paginators-1.json -> build/lib/botocore/data/imagebuilder/2019-12-02 INFO : root : copying botocore/data/imagebuilder/2019-12-02/service-2.json -> build/lib/botocore/data/imagebuilder/2019-12-02 INFO : root : creating build/lib/botocore/data/importexport INFO : root : creating build/lib/botocore/data/importexport/2010-06-01 INFO : root : copying botocore/data/importexport/2010-06-01/paginators-1.json -> build/lib/botocore/data/importexport/2010-06-01 INFO : root : copying botocore/data/importexport/2010-06-01/service-2.json -> build/lib/botocore/data/importexport/2010-06-01 INFO : root : creating build/lib/botocore/data/inspector INFO : root : creating build/lib/botocore/data/inspector/2015-08-18 INFO : root : copying botocore/data/inspector/2015-08-18/service-2.json -> build/lib/botocore/data/inspector/2015-08-18 INFO : root : creating build/lib/botocore/data/inspector/2016-02-16 INFO : root : copying botocore/data/inspector/2016-02-16/examples-1.json -> build/lib/botocore/data/inspector/2016-02-16 INFO : root : copying botocore/data/inspector/2016-02-16/paginators-1.json -> build/lib/botocore/data/inspector/2016-02-16 INFO : root : copying botocore/data/inspector/2016-02-16/service-2.json -> build/lib/botocore/data/inspector/2016-02-16 INFO : root : creating build/lib/botocore/data/inspector2 INFO : root : creating build/lib/botocore/data/inspector2/2020-06-08 INFO : root : copying botocore/data/inspector2/2020-06-08/examples-1.json -> build/lib/botocore/data/inspector2/2020-06-08 INFO : root : copying botocore/data/inspector2/2020-06-08/paginators-1.json -> build/lib/botocore/data/inspector2/2020-06-08 INFO : root : copying botocore/data/inspector2/2020-06-08/paginators-1.sdk-extras.json -> build/lib/botocore/data/inspector2/2020-06-08 INFO : root : copying botocore/data/inspector2/2020-06-08/service-2.json -> build/lib/botocore/data/inspector2/2020-06-08 INFO : root : creating build/lib/botocore/data/iot-data INFO : root : creating build/lib/botocore/data/iot-data/2015-05-28 INFO : root : copying botocore/data/iot-data/2015-05-28/examples-1.json -> build/lib/botocore/data/iot-data/2015-05-28 INFO : root : copying botocore/data/iot-data/2015-05-28/paginators-1.json -> build/lib/botocore/data/iot-data/2015-05-28 INFO : root : copying botocore/data/iot-data/2015-05-28/service-2.json -> build/lib/botocore/data/iot-data/2015-05-28 INFO : root : creating build/lib/botocore/data/iot-jobs-data INFO : root : creating build/lib/botocore/data/iot-jobs-data/2017-09-29 INFO : root : copying botocore/data/iot-jobs-data/2017-09-29/examples-1.json -> build/lib/botocore/data/iot-jobs-data/2017-09-29 INFO : root : copying botocore/data/iot-jobs-data/2017-09-29/paginators-1.json -> build/lib/botocore/data/iot-jobs-data/2017-09-29 INFO : root : copying botocore/data/iot-jobs-data/2017-09-29/service-2.json -> build/lib/botocore/data/iot-jobs-data/2017-09-29 INFO : root : creating build/lib/botocore/data/iot INFO : root : creating build/lib/botocore/data/iot/2015-05-28 INFO : root : copying botocore/data/iot/2015-05-28/examples-1.json -> build/lib/botocore/data/iot/2015-05-28 INFO : root : copying botocore/data/iot/2015-05-28/paginators-1.json -> build/lib/botocore/data/iot/2015-05-28 INFO : root : copying botocore/data/iot/2015-05-28/service-2.json -> build/lib/botocore/data/iot/2015-05-28 INFO : root : creating build/lib/botocore/data/iot1click-devices INFO : root : creating build/lib/botocore/data/iot1click-devices/2018-05-14 INFO : root : copying botocore/data/iot1click-devices/2018-05-14/paginators-1.json -> build/lib/botocore/data/iot1click-devices/2018-05-14 INFO : root : copying botocore/data/iot1click-devices/2018-05-14/service-2.json -> build/lib/botocore/data/iot1click-devices/2018-05-14 INFO : root : creating build/lib/botocore/data/iot1click-projects INFO : root : creating build/lib/botocore/data/iot1click-projects/2018-05-14 INFO : root : copying botocore/data/iot1click-projects/2018-05-14/examples-1.json -> build/lib/botocore/data/iot1click-projects/2018-05-14 INFO : root : copying botocore/data/iot1click-projects/2018-05-14/paginators-1.json -> build/lib/botocore/data/iot1click-projects/2018-05-14 INFO : root : copying botocore/data/iot1click-projects/2018-05-14/service-2.json -> build/lib/botocore/data/iot1click-projects/2018-05-14 INFO : root : creating build/lib/botocore/data/iotanalytics INFO : root : creating build/lib/botocore/data/iotanalytics/2017-11-27 INFO : root : copying botocore/data/iotanalytics/2017-11-27/examples-1.json -> build/lib/botocore/data/iotanalytics/2017-11-27 INFO : root : copying botocore/data/iotanalytics/2017-11-27/paginators-1.json -> build/lib/botocore/data/iotanalytics/2017-11-27 INFO : root : copying botocore/data/iotanalytics/2017-11-27/service-2.json -> build/lib/botocore/data/iotanalytics/2017-11-27 INFO : root : creating build/lib/botocore/data/iotdeviceadvisor INFO : root : creating build/lib/botocore/data/iotdeviceadvisor/2020-09-18 INFO : root : copying botocore/data/iotdeviceadvisor/2020-09-18/examples-1.json -> build/lib/botocore/data/iotdeviceadvisor/2020-09-18 INFO : root : copying botocore/data/iotdeviceadvisor/2020-09-18/paginators-1.json -> build/lib/botocore/data/iotdeviceadvisor/2020-09-18 INFO : root : copying botocore/data/iotdeviceadvisor/2020-09-18/service-2.json -> build/lib/botocore/data/iotdeviceadvisor/2020-09-18 INFO : root : creating build/lib/botocore/data/iotevents-data INFO : root : creating build/lib/botocore/data/iotevents-data/2018-10-23 INFO : root : copying botocore/data/iotevents-data/2018-10-23/examples-1.json -> build/lib/botocore/data/iotevents-data/2018-10-23 INFO : root : copying botocore/data/iotevents-data/2018-10-23/paginators-1.json -> build/lib/botocore/data/iotevents-data/2018-10-23 INFO : root : copying botocore/data/iotevents-data/2018-10-23/service-2.json -> build/lib/botocore/data/iotevents-data/2018-10-23 INFO : root : creating build/lib/botocore/data/iotevents INFO : root : creating build/lib/botocore/data/iotevents/2018-07-27 INFO : root : copying botocore/data/iotevents/2018-07-27/examples-1.json -> build/lib/botocore/data/iotevents/2018-07-27 INFO : root : copying botocore/data/iotevents/2018-07-27/paginators-1.json -> build/lib/botocore/data/iotevents/2018-07-27 INFO : root : copying botocore/data/iotevents/2018-07-27/service-2.json -> build/lib/botocore/data/iotevents/2018-07-27 INFO : root : creating build/lib/botocore/data/iotfleethub INFO : root : creating build/lib/botocore/data/iotfleethub/2020-11-03 INFO : root : copying botocore/data/iotfleethub/2020-11-03/examples-1.json -> build/lib/botocore/data/iotfleethub/2020-11-03 INFO : root : copying botocore/data/iotfleethub/2020-11-03/paginators-1.json -> build/lib/botocore/data/iotfleethub/2020-11-03 INFO : root : copying botocore/data/iotfleethub/2020-11-03/service-2.json -> build/lib/botocore/data/iotfleethub/2020-11-03 INFO : root : creating build/lib/botocore/data/iotfleetwise INFO : root : creating build/lib/botocore/data/iotfleetwise/2021-06-17 INFO : root : copying botocore/data/iotfleetwise/2021-06-17/paginators-1.json -> build/lib/botocore/data/iotfleetwise/2021-06-17 INFO : root : copying botocore/data/iotfleetwise/2021-06-17/service-2.json -> build/lib/botocore/data/iotfleetwise/2021-06-17 INFO : root : copying botocore/data/iotfleetwise/2021-06-17/waiters-2.json -> build/lib/botocore/data/iotfleetwise/2021-06-17 INFO : root : creating build/lib/botocore/data/iotsecuretunneling INFO : root : creating build/lib/botocore/data/iotsecuretunneling/2018-10-05 INFO : root : copying botocore/data/iotsecuretunneling/2018-10-05/examples-1.json -> build/lib/botocore/data/iotsecuretunneling/2018-10-05 INFO : root : copying botocore/data/iotsecuretunneling/2018-10-05/paginators-1.json -> build/lib/botocore/data/iotsecuretunneling/2018-10-05 INFO : root : copying botocore/data/iotsecuretunneling/2018-10-05/service-2.json -> build/lib/botocore/data/iotsecuretunneling/2018-10-05 INFO : root : creating build/lib/botocore/data/iotsitewise INFO : root : creating build/lib/botocore/data/iotsitewise/2019-12-02 INFO : root : copying botocore/data/iotsitewise/2019-12-02/examples-1.json -> build/lib/botocore/data/iotsitewise/2019-12-02 INFO : root : copying botocore/data/iotsitewise/2019-12-02/paginators-1.json -> build/lib/botocore/data/iotsitewise/2019-12-02 INFO : root : copying botocore/data/iotsitewise/2019-12-02/service-2.json -> build/lib/botocore/data/iotsitewise/2019-12-02 INFO : root : copying botocore/data/iotsitewise/2019-12-02/waiters-2.json -> build/lib/botocore/data/iotsitewise/2019-12-02 INFO : root : creating build/lib/botocore/data/iotthingsgraph INFO : root : creating build/lib/botocore/data/iotthingsgraph/2018-09-06 INFO : root : copying botocore/data/iotthingsgraph/2018-09-06/examples-1.json -> build/lib/botocore/data/iotthingsgraph/2018-09-06 INFO : root : copying botocore/data/iotthingsgraph/2018-09-06/paginators-1.json -> build/lib/botocore/data/iotthingsgraph/2018-09-06 INFO : root : copying botocore/data/iotthingsgraph/2018-09-06/service-2.json -> build/lib/botocore/data/iotthingsgraph/2018-09-06 INFO : root : creating build/lib/botocore/data/iottwinmaker INFO : root : creating build/lib/botocore/data/iottwinmaker/2021-11-29 INFO : root : copying botocore/data/iottwinmaker/2021-11-29/examples-1.json -> build/lib/botocore/data/iottwinmaker/2021-11-29 INFO : root : copying botocore/data/iottwinmaker/2021-11-29/paginators-1.json -> build/lib/botocore/data/iottwinmaker/2021-11-29 INFO : root : copying botocore/data/iottwinmaker/2021-11-29/service-2.json -> build/lib/botocore/data/iottwinmaker/2021-11-29 INFO : root : copying botocore/data/iottwinmaker/2021-11-29/waiters-2.json -> build/lib/botocore/data/iottwinmaker/2021-11-29 INFO : root : creating build/lib/botocore/data/iotwireless INFO : root : creating build/lib/botocore/data/iotwireless/2020-11-22 INFO : root : copying botocore/data/iotwireless/2020-11-22/examples-1.json -> build/lib/botocore/data/iotwireless/2020-11-22 INFO : root : copying botocore/data/iotwireless/2020-11-22/paginators-1.json -> build/lib/botocore/data/iotwireless/2020-11-22 INFO : root : copying botocore/data/iotwireless/2020-11-22/service-2.json -> build/lib/botocore/data/iotwireless/2020-11-22 INFO : root : creating build/lib/botocore/data/ivs INFO : root : creating build/lib/botocore/data/ivs/2020-07-14 INFO : root : copying botocore/data/ivs/2020-07-14/examples-1.json -> build/lib/botocore/data/ivs/2020-07-14 INFO : root : copying botocore/data/ivs/2020-07-14/paginators-1.json -> build/lib/botocore/data/ivs/2020-07-14 INFO : root : copying botocore/data/ivs/2020-07-14/service-2.json -> build/lib/botocore/data/ivs/2020-07-14 INFO : root : creating build/lib/botocore/data/ivschat INFO : root : creating build/lib/botocore/data/ivschat/2020-07-14 INFO : root : copying botocore/data/ivschat/2020-07-14/examples-1.json -> build/lib/botocore/data/ivschat/2020-07-14 INFO : root : copying botocore/data/ivschat/2020-07-14/paginators-1.json -> build/lib/botocore/data/ivschat/2020-07-14 INFO : root : copying botocore/data/ivschat/2020-07-14/service-2.json -> build/lib/botocore/data/ivschat/2020-07-14 INFO : root : creating build/lib/botocore/data/kafka INFO : root : creating build/lib/botocore/data/kafka/2018-11-14 INFO : root : copying botocore/data/kafka/2018-11-14/paginators-1.json -> build/lib/botocore/data/kafka/2018-11-14 INFO : root : copying botocore/data/kafka/2018-11-14/service-2.json -> build/lib/botocore/data/kafka/2018-11-14 INFO : root : creating build/lib/botocore/data/kafkaconnect INFO : root : creating build/lib/botocore/data/kafkaconnect/2021-09-14 INFO : root : copying botocore/data/kafkaconnect/2021-09-14/examples-1.json -> build/lib/botocore/data/kafkaconnect/2021-09-14 INFO : root : copying botocore/data/kafkaconnect/2021-09-14/paginators-1.json -> build/lib/botocore/data/kafkaconnect/2021-09-14 INFO : root : copying botocore/data/kafkaconnect/2021-09-14/service-2.json -> build/lib/botocore/data/kafkaconnect/2021-09-14 INFO : root : creating build/lib/botocore/data/kendra INFO : root : creating build/lib/botocore/data/kendra/2019-02-03 INFO : root : copying botocore/data/kendra/2019-02-03/examples-1.json -> build/lib/botocore/data/kendra/2019-02-03 INFO : root : copying botocore/data/kendra/2019-02-03/paginators-1.json -> build/lib/botocore/data/kendra/2019-02-03 INFO : root : copying botocore/data/kendra/2019-02-03/service-2.json -> build/lib/botocore/data/kendra/2019-02-03 INFO : root : creating build/lib/botocore/data/keyspaces INFO : root : creating build/lib/botocore/data/keyspaces/2022-02-10 INFO : root : copying botocore/data/keyspaces/2022-02-10/examples-1.json -> build/lib/botocore/data/keyspaces/2022-02-10 INFO : root : copying botocore/data/keyspaces/2022-02-10/paginators-1.json -> build/lib/botocore/data/keyspaces/2022-02-10 INFO : root : copying botocore/data/keyspaces/2022-02-10/service-2.json -> build/lib/botocore/data/keyspaces/2022-02-10 INFO : root : copying botocore/data/keyspaces/2022-02-10/waiters-2.json -> build/lib/botocore/data/keyspaces/2022-02-10 INFO : root : creating build/lib/botocore/data/kinesis-video-archived-media INFO : root : creating build/lib/botocore/data/kinesis-video-archived-media/2017-09-30 INFO : root : copying botocore/data/kinesis-video-archived-media/2017-09-30/examples-1.json -> build/lib/botocore/data/kinesis-video-archived-media/2017-09-30 INFO : root : copying botocore/data/kinesis-video-archived-media/2017-09-30/paginators-1.json -> build/lib/botocore/data/kinesis-video-archived-media/2017-09-30 INFO : root : copying botocore/data/kinesis-video-archived-media/2017-09-30/service-2.json -> build/lib/botocore/data/kinesis-video-archived-media/2017-09-30 INFO : root : creating build/lib/botocore/data/kinesis-video-media INFO : root : creating build/lib/botocore/data/kinesis-video-media/2017-09-30 INFO : root : copying botocore/data/kinesis-video-media/2017-09-30/examples-1.json -> build/lib/botocore/data/kinesis-video-media/2017-09-30 INFO : root : copying botocore/data/kinesis-video-media/2017-09-30/paginators-1.json -> build/lib/botocore/data/kinesis-video-media/2017-09-30 INFO : root : copying botocore/data/kinesis-video-media/2017-09-30/service-2.json -> build/lib/botocore/data/kinesis-video-media/2017-09-30 INFO : root : creating build/lib/botocore/data/kinesis-video-signaling INFO : root : creating build/lib/botocore/data/kinesis-video-signaling/2019-12-04 INFO : root : copying botocore/data/kinesis-video-signaling/2019-12-04/examples-1.json -> build/lib/botocore/data/kinesis-video-signaling/2019-12-04 INFO : root : copying botocore/data/kinesis-video-signaling/2019-12-04/paginators-1.json -> build/lib/botocore/data/kinesis-video-signaling/2019-12-04 INFO : root : copying botocore/data/kinesis-video-signaling/2019-12-04/service-2.json -> build/lib/botocore/data/kinesis-video-signaling/2019-12-04 INFO : root : creating build/lib/botocore/data/kinesis INFO : root : creating build/lib/botocore/data/kinesis/2013-12-02 INFO : root : copying botocore/data/kinesis/2013-12-02/examples-1.json -> build/lib/botocore/data/kinesis/2013-12-02 INFO : root : copying botocore/data/kinesis/2013-12-02/paginators-1.json -> build/lib/botocore/data/kinesis/2013-12-02 INFO : root : copying botocore/data/kinesis/2013-12-02/service-2.json -> build/lib/botocore/data/kinesis/2013-12-02 INFO : root : copying botocore/data/kinesis/2013-12-02/waiters-2.json -> build/lib/botocore/data/kinesis/2013-12-02 INFO : root : creating build/lib/botocore/data/kinesisanalytics INFO : root : creating build/lib/botocore/data/kinesisanalytics/2015-08-14 INFO : root : copying botocore/data/kinesisanalytics/2015-08-14/examples-1.json -> build/lib/botocore/data/kinesisanalytics/2015-08-14 INFO : root : copying botocore/data/kinesisanalytics/2015-08-14/paginators-1.json -> build/lib/botocore/data/kinesisanalytics/2015-08-14 INFO : root : copying botocore/data/kinesisanalytics/2015-08-14/service-2.json -> build/lib/botocore/data/kinesisanalytics/2015-08-14 INFO : root : creating build/lib/botocore/data/kinesisanalyticsv2 INFO : root : creating build/lib/botocore/data/kinesisanalyticsv2/2018-05-23 INFO : root : copying botocore/data/kinesisanalyticsv2/2018-05-23/examples-1.json -> build/lib/botocore/data/kinesisanalyticsv2/2018-05-23 INFO : root : copying botocore/data/kinesisanalyticsv2/2018-05-23/paginators-1.json -> build/lib/botocore/data/kinesisanalyticsv2/2018-05-23 INFO : root : copying botocore/data/kinesisanalyticsv2/2018-05-23/service-2.json -> build/lib/botocore/data/kinesisanalyticsv2/2018-05-23 INFO : root : creating build/lib/botocore/data/kinesisvideo INFO : root : creating build/lib/botocore/data/kinesisvideo/2017-09-30 INFO : root : copying botocore/data/kinesisvideo/2017-09-30/examples-1.json -> build/lib/botocore/data/kinesisvideo/2017-09-30 INFO : root : copying botocore/data/kinesisvideo/2017-09-30/paginators-1.json -> build/lib/botocore/data/kinesisvideo/2017-09-30 INFO : root : copying botocore/data/kinesisvideo/2017-09-30/service-2.json -> build/lib/botocore/data/kinesisvideo/2017-09-30 INFO : root : creating build/lib/botocore/data/kms INFO : root : creating build/lib/botocore/data/kms/2014-11-01 INFO : root : copying botocore/data/kms/2014-11-01/examples-1.json -> build/lib/botocore/data/kms/2014-11-01 INFO : root : copying botocore/data/kms/2014-11-01/paginators-1.json -> build/lib/botocore/data/kms/2014-11-01 INFO : root : copying botocore/data/kms/2014-11-01/service-2.json -> build/lib/botocore/data/kms/2014-11-01 INFO : root : creating build/lib/botocore/data/lakeformation INFO : root : creating build/lib/botocore/data/lakeformation/2017-03-31 INFO : root : copying botocore/data/lakeformation/2017-03-31/examples-1.json -> build/lib/botocore/data/lakeformation/2017-03-31 INFO : root : copying botocore/data/lakeformation/2017-03-31/paginators-1.json -> build/lib/botocore/data/lakeformation/2017-03-31 INFO : root : copying botocore/data/lakeformation/2017-03-31/paginators-1.sdk-extras.json -> build/lib/botocore/data/lakeformation/2017-03-31 INFO : root : copying botocore/data/lakeformation/2017-03-31/service-2.json -> build/lib/botocore/data/lakeformation/2017-03-31 INFO : root : creating build/lib/botocore/data/lambda INFO : root : creating build/lib/botocore/data/lambda/2014-11-11 INFO : root : copying botocore/data/lambda/2014-11-11/service-2.json -> build/lib/botocore/data/lambda/2014-11-11 INFO : root : creating build/lib/botocore/data/lambda/2015-03-31 INFO : root : copying botocore/data/lambda/2015-03-31/examples-1.json -> build/lib/botocore/data/lambda/2015-03-31 INFO : root : copying botocore/data/lambda/2015-03-31/paginators-1.json -> build/lib/botocore/data/lambda/2015-03-31 INFO : root : copying botocore/data/lambda/2015-03-31/service-2.json -> build/lib/botocore/data/lambda/2015-03-31 INFO : root : copying botocore/data/lambda/2015-03-31/waiters-2.json -> build/lib/botocore/data/lambda/2015-03-31 INFO : root : creating build/lib/botocore/data/lex-models INFO : root : creating build/lib/botocore/data/lex-models/2017-04-19 INFO : root : copying botocore/data/lex-models/2017-04-19/examples-1.json -> build/lib/botocore/data/lex-models/2017-04-19 INFO : root : copying botocore/data/lex-models/2017-04-19/paginators-1.json -> build/lib/botocore/data/lex-models/2017-04-19 INFO : root : copying botocore/data/lex-models/2017-04-19/service-2.json -> build/lib/botocore/data/lex-models/2017-04-19 INFO : root : creating build/lib/botocore/data/lex-runtime INFO : root : creating build/lib/botocore/data/lex-runtime/2016-11-28 INFO : root : copying botocore/data/lex-runtime/2016-11-28/examples-1.json -> build/lib/botocore/data/lex-runtime/2016-11-28 INFO : root : copying botocore/data/lex-runtime/2016-11-28/paginators-1.json -> build/lib/botocore/data/lex-runtime/2016-11-28 INFO : root : copying botocore/data/lex-runtime/2016-11-28/service-2.json -> build/lib/botocore/data/lex-runtime/2016-11-28 INFO : root : creating build/lib/botocore/data/lexv2-models INFO : root : creating build/lib/botocore/data/lexv2-models/2020-08-07 INFO : root : copying botocore/data/lexv2-models/2020-08-07/examples-1.json -> build/lib/botocore/data/lexv2-models/2020-08-07 INFO : root : copying botocore/data/lexv2-models/2020-08-07/paginators-1.json -> build/lib/botocore/data/lexv2-models/2020-08-07 INFO : root : copying botocore/data/lexv2-models/2020-08-07/service-2.json -> build/lib/botocore/data/lexv2-models/2020-08-07 INFO : root : copying botocore/data/lexv2-models/2020-08-07/waiters-2.json -> build/lib/botocore/data/lexv2-models/2020-08-07 INFO : root : creating build/lib/botocore/data/lexv2-runtime INFO : root : creating build/lib/botocore/data/lexv2-runtime/2020-08-07 INFO : root : copying botocore/data/lexv2-runtime/2020-08-07/examples-1.json -> build/lib/botocore/data/lexv2-runtime/2020-08-07 INFO : root : copying botocore/data/lexv2-runtime/2020-08-07/paginators-1.json -> build/lib/botocore/data/lexv2-runtime/2020-08-07 INFO : root : copying botocore/data/lexv2-runtime/2020-08-07/service-2.json -> build/lib/botocore/data/lexv2-runtime/2020-08-07 INFO : root : creating build/lib/botocore/data/license-manager-user-subscriptions INFO : root : creating build/lib/botocore/data/license-manager-user-subscriptions/2018-05-10 INFO : root : copying botocore/data/license-manager-user-subscriptions/2018-05-10/paginators-1.json -> build/lib/botocore/data/license-manager-user-subscriptions/2018-05-10 INFO : root : copying botocore/data/license-manager-user-subscriptions/2018-05-10/service-2.json -> build/lib/botocore/data/license-manager-user-subscriptions/2018-05-10 INFO : root : creating build/lib/botocore/data/license-manager INFO : root : creating build/lib/botocore/data/license-manager/2018-08-01 INFO : root : copying botocore/data/license-manager/2018-08-01/examples-1.json -> build/lib/botocore/data/license-manager/2018-08-01 INFO : root : copying botocore/data/license-manager/2018-08-01/paginators-1.json -> build/lib/botocore/data/license-manager/2018-08-01 INFO : root : copying botocore/data/license-manager/2018-08-01/service-2.json -> build/lib/botocore/data/license-manager/2018-08-01 INFO : root : creating build/lib/botocore/data/lightsail INFO : root : creating build/lib/botocore/data/lightsail/2016-11-28 INFO : root : copying botocore/data/lightsail/2016-11-28/examples-1.json -> build/lib/botocore/data/lightsail/2016-11-28 INFO : root : copying botocore/data/lightsail/2016-11-28/paginators-1.json -> build/lib/botocore/data/lightsail/2016-11-28 INFO : root : copying botocore/data/lightsail/2016-11-28/service-2.json -> build/lib/botocore/data/lightsail/2016-11-28 INFO : root : creating build/lib/botocore/data/location INFO : root : creating build/lib/botocore/data/location/2020-11-19 INFO : root : copying botocore/data/location/2020-11-19/examples-1.json -> build/lib/botocore/data/location/2020-11-19 INFO : root : copying botocore/data/location/2020-11-19/paginators-1.json -> build/lib/botocore/data/location/2020-11-19 INFO : root : copying botocore/data/location/2020-11-19/service-2.json -> build/lib/botocore/data/location/2020-11-19 INFO : root : creating build/lib/botocore/data/logs INFO : root : creating build/lib/botocore/data/logs/2014-03-28 INFO : root : copying botocore/data/logs/2014-03-28/examples-1.json -> build/lib/botocore/data/logs/2014-03-28 INFO : root : copying botocore/data/logs/2014-03-28/paginators-1.json -> build/lib/botocore/data/logs/2014-03-28 INFO : root : copying botocore/data/logs/2014-03-28/service-2.json -> build/lib/botocore/data/logs/2014-03-28 INFO : root : creating build/lib/botocore/data/lookoutequipment INFO : root : creating build/lib/botocore/data/lookoutequipment/2020-12-15 INFO : root : copying botocore/data/lookoutequipment/2020-12-15/examples-1.json -> build/lib/botocore/data/lookoutequipment/2020-12-15 INFO : root : copying botocore/data/lookoutequipment/2020-12-15/paginators-1.json -> build/lib/botocore/data/lookoutequipment/2020-12-15 INFO : root : copying botocore/data/lookoutequipment/2020-12-15/service-2.json -> build/lib/botocore/data/lookoutequipment/2020-12-15 INFO : root : creating build/lib/botocore/data/lookoutmetrics INFO : root : creating build/lib/botocore/data/lookoutmetrics/2017-07-25 INFO : root : copying botocore/data/lookoutmetrics/2017-07-25/examples-1.json -> build/lib/botocore/data/lookoutmetrics/2017-07-25 INFO : root : copying botocore/data/lookoutmetrics/2017-07-25/paginators-1.json -> build/lib/botocore/data/lookoutmetrics/2017-07-25 INFO : root : copying botocore/data/lookoutmetrics/2017-07-25/service-2.json -> build/lib/botocore/data/lookoutmetrics/2017-07-25 INFO : root : creating build/lib/botocore/data/lookoutvision INFO : root : creating build/lib/botocore/data/lookoutvision/2020-11-20 INFO : root : copying botocore/data/lookoutvision/2020-11-20/examples-1.json -> build/lib/botocore/data/lookoutvision/2020-11-20 INFO : root : copying botocore/data/lookoutvision/2020-11-20/paginators-1.json -> build/lib/botocore/data/lookoutvision/2020-11-20 INFO : root : copying botocore/data/lookoutvision/2020-11-20/service-2.json -> build/lib/botocore/data/lookoutvision/2020-11-20 INFO : root : creating build/lib/botocore/data/m2 INFO : root : creating build/lib/botocore/data/m2/2021-04-28 INFO : root : copying botocore/data/m2/2021-04-28/paginators-1.json -> build/lib/botocore/data/m2/2021-04-28 INFO : root : copying botocore/data/m2/2021-04-28/service-2.json -> build/lib/botocore/data/m2/2021-04-28 INFO : root : creating build/lib/botocore/data/machinelearning INFO : root : creating build/lib/botocore/data/machinelearning/2014-12-12 INFO : root : copying botocore/data/machinelearning/2014-12-12/examples-1.json -> build/lib/botocore/data/machinelearning/2014-12-12 INFO : root : copying botocore/data/machinelearning/2014-12-12/paginators-1.json -> build/lib/botocore/data/machinelearning/2014-12-12 INFO : root : copying botocore/data/machinelearning/2014-12-12/service-2.json -> build/lib/botocore/data/machinelearning/2014-12-12 INFO : root : copying botocore/data/machinelearning/2014-12-12/waiters-2.json -> build/lib/botocore/data/machinelearning/2014-12-12 INFO : root : creating build/lib/botocore/data/macie INFO : root : creating build/lib/botocore/data/macie/2017-12-19 INFO : root : copying botocore/data/macie/2017-12-19/examples-1.json -> build/lib/botocore/data/macie/2017-12-19 INFO : root : copying botocore/data/macie/2017-12-19/paginators-1.json -> build/lib/botocore/data/macie/2017-12-19 INFO : root : copying botocore/data/macie/2017-12-19/service-2.json -> build/lib/botocore/data/macie/2017-12-19 INFO : root : creating build/lib/botocore/data/macie2 INFO : root : creating build/lib/botocore/data/macie2/2020-01-01 INFO : root : copying botocore/data/macie2/2020-01-01/paginators-1.json -> build/lib/botocore/data/macie2/2020-01-01 INFO : root : copying botocore/data/macie2/2020-01-01/service-2.json -> build/lib/botocore/data/macie2/2020-01-01 INFO : root : copying botocore/data/macie2/2020-01-01/waiters-2.json -> build/lib/botocore/data/macie2/2020-01-01 INFO : root : creating build/lib/botocore/data/managedblockchain INFO : root : creating build/lib/botocore/data/managedblockchain/2018-09-24 INFO : root : copying botocore/data/managedblockchain/2018-09-24/examples-1.json -> build/lib/botocore/data/managedblockchain/2018-09-24 INFO : root : copying botocore/data/managedblockchain/2018-09-24/paginators-1.json -> build/lib/botocore/data/managedblockchain/2018-09-24 INFO : root : copying botocore/data/managedblockchain/2018-09-24/service-2.json -> build/lib/botocore/data/managedblockchain/2018-09-24 INFO : root : creating build/lib/botocore/data/marketplace-catalog INFO : root : creating build/lib/botocore/data/marketplace-catalog/2018-09-17 INFO : root : copying botocore/data/marketplace-catalog/2018-09-17/examples-1.json -> build/lib/botocore/data/marketplace-catalog/2018-09-17 INFO : root : copying botocore/data/marketplace-catalog/2018-09-17/paginators-1.json -> build/lib/botocore/data/marketplace-catalog/2018-09-17 INFO : root : copying botocore/data/marketplace-catalog/2018-09-17/service-2.json -> build/lib/botocore/data/marketplace-catalog/2018-09-17 INFO : root : creating build/lib/botocore/data/marketplace-entitlement INFO : root : creating build/lib/botocore/data/marketplace-entitlement/2017-01-11 INFO : root : copying botocore/data/marketplace-entitlement/2017-01-11/examples-1.json -> build/lib/botocore/data/marketplace-entitlement/2017-01-11 INFO : root : copying botocore/data/marketplace-entitlement/2017-01-11/paginators-1.json -> build/lib/botocore/data/marketplace-entitlement/2017-01-11 INFO : root : copying botocore/data/marketplace-entitlement/2017-01-11/service-2.json -> build/lib/botocore/data/marketplace-entitlement/2017-01-11 INFO : root : creating build/lib/botocore/data/marketplacecommerceanalytics INFO : root : creating build/lib/botocore/data/marketplacecommerceanalytics/2015-07-01 INFO : root : copying botocore/data/marketplacecommerceanalytics/2015-07-01/examples-1.json -> build/lib/botocore/data/marketplacecommerceanalytics/2015-07-01 INFO : root : copying botocore/data/marketplacecommerceanalytics/2015-07-01/paginators-1.json -> build/lib/botocore/data/marketplacecommerceanalytics/2015-07-01 INFO : root : copying botocore/data/marketplacecommerceanalytics/2015-07-01/service-2.json -> build/lib/botocore/data/marketplacecommerceanalytics/2015-07-01 INFO : root : creating build/lib/botocore/data/mediaconnect INFO : root : creating build/lib/botocore/data/mediaconnect/2018-11-14 INFO : root : copying botocore/data/mediaconnect/2018-11-14/paginators-1.json -> build/lib/botocore/data/mediaconnect/2018-11-14 INFO : root : copying botocore/data/mediaconnect/2018-11-14/service-2.json -> build/lib/botocore/data/mediaconnect/2018-11-14 INFO : root : copying botocore/data/mediaconnect/2018-11-14/waiters-2.json -> build/lib/botocore/data/mediaconnect/2018-11-14 INFO : root : creating build/lib/botocore/data/mediaconvert INFO : root : creating build/lib/botocore/data/mediaconvert/2017-08-29 INFO : root : copying botocore/data/mediaconvert/2017-08-29/paginators-1.json -> build/lib/botocore/data/mediaconvert/2017-08-29 INFO : root : copying botocore/data/mediaconvert/2017-08-29/service-2.json -> build/lib/botocore/data/mediaconvert/2017-08-29 INFO : root : creating build/lib/botocore/data/medialive INFO : root : creating build/lib/botocore/data/medialive/2017-10-14 INFO : root : copying botocore/data/medialive/2017-10-14/paginators-1.json -> build/lib/botocore/data/medialive/2017-10-14 INFO : root : copying botocore/data/medialive/2017-10-14/service-2.json -> build/lib/botocore/data/medialive/2017-10-14 INFO : root : copying botocore/data/medialive/2017-10-14/waiters-2.json -> build/lib/botocore/data/medialive/2017-10-14 INFO : root : creating build/lib/botocore/data/mediapackage-vod INFO : root : creating build/lib/botocore/data/mediapackage-vod/2018-11-07 INFO : root : copying botocore/data/mediapackage-vod/2018-11-07/paginators-1.json -> build/lib/botocore/data/mediapackage-vod/2018-11-07 INFO : root : copying botocore/data/mediapackage-vod/2018-11-07/service-2.json -> build/lib/botocore/data/mediapackage-vod/2018-11-07 INFO : root : creating build/lib/botocore/data/mediapackage INFO : root : creating build/lib/botocore/data/mediapackage/2017-10-12 INFO : root : copying botocore/data/mediapackage/2017-10-12/paginators-1.json -> build/lib/botocore/data/mediapackage/2017-10-12 INFO : root : copying botocore/data/mediapackage/2017-10-12/service-2.json -> build/lib/botocore/data/mediapackage/2017-10-12 INFO : root : creating build/lib/botocore/data/mediastore-data INFO : root : creating build/lib/botocore/data/mediastore-data/2017-09-01 INFO : root : copying botocore/data/mediastore-data/2017-09-01/examples-1.json -> build/lib/botocore/data/mediastore-data/2017-09-01 INFO : root : copying botocore/data/mediastore-data/2017-09-01/paginators-1.json -> build/lib/botocore/data/mediastore-data/2017-09-01 INFO : root : copying botocore/data/mediastore-data/2017-09-01/service-2.json -> build/lib/botocore/data/mediastore-data/2017-09-01 INFO : root : creating build/lib/botocore/data/mediastore INFO : root : creating build/lib/botocore/data/mediastore/2017-09-01 INFO : root : copying botocore/data/mediastore/2017-09-01/examples-1.json -> build/lib/botocore/data/mediastore/2017-09-01 INFO : root : copying botocore/data/mediastore/2017-09-01/paginators-1.json -> build/lib/botocore/data/mediastore/2017-09-01 INFO : root : copying botocore/data/mediastore/2017-09-01/service-2.json -> build/lib/botocore/data/mediastore/2017-09-01 INFO : root : creating build/lib/botocore/data/mediatailor INFO : root : creating build/lib/botocore/data/mediatailor/2018-04-23 INFO : root : copying botocore/data/mediatailor/2018-04-23/paginators-1.json -> build/lib/botocore/data/mediatailor/2018-04-23 INFO : root : copying botocore/data/mediatailor/2018-04-23/service-2.json -> build/lib/botocore/data/mediatailor/2018-04-23 INFO : root : creating build/lib/botocore/data/memorydb INFO : root : creating build/lib/botocore/data/memorydb/2021-01-01 INFO : root : copying botocore/data/memorydb/2021-01-01/examples-1.json -> build/lib/botocore/data/memorydb/2021-01-01 INFO : root : copying botocore/data/memorydb/2021-01-01/paginators-1.json -> build/lib/botocore/data/memorydb/2021-01-01 INFO : root : copying botocore/data/memorydb/2021-01-01/service-2.json -> build/lib/botocore/data/memorydb/2021-01-01 INFO : root : creating build/lib/botocore/data/meteringmarketplace INFO : root : creating build/lib/botocore/data/meteringmarketplace/2016-01-14 INFO : root : copying botocore/data/meteringmarketplace/2016-01-14/examples-1.json -> build/lib/botocore/data/meteringmarketplace/2016-01-14 INFO : root : copying botocore/data/meteringmarketplace/2016-01-14/paginators-1.json -> build/lib/botocore/data/meteringmarketplace/2016-01-14 INFO : root : copying botocore/data/meteringmarketplace/2016-01-14/service-2.json -> build/lib/botocore/data/meteringmarketplace/2016-01-14 INFO : root : creating build/lib/botocore/data/mgh INFO : root : creating build/lib/botocore/data/mgh/2017-05-31 INFO : root : copying botocore/data/mgh/2017-05-31/examples-1.json -> build/lib/botocore/data/mgh/2017-05-31 INFO : root : copying botocore/data/mgh/2017-05-31/paginators-1.json -> build/lib/botocore/data/mgh/2017-05-31 INFO : root : copying botocore/data/mgh/2017-05-31/service-2.json -> build/lib/botocore/data/mgh/2017-05-31 INFO : root : creating build/lib/botocore/data/mgn INFO : root : creating build/lib/botocore/data/mgn/2020-02-26 INFO : root : copying botocore/data/mgn/2020-02-26/examples-1.json -> build/lib/botocore/data/mgn/2020-02-26 INFO : root : copying botocore/data/mgn/2020-02-26/paginators-1.json -> build/lib/botocore/data/mgn/2020-02-26 INFO : root : copying botocore/data/mgn/2020-02-26/service-2.json -> build/lib/botocore/data/mgn/2020-02-26 INFO : root : creating build/lib/botocore/data/migration-hub-refactor-spaces INFO : root : creating build/lib/botocore/data/migration-hub-refactor-spaces/2021-10-26 INFO : root : copying botocore/data/migration-hub-refactor-spaces/2021-10-26/examples-1.json -> build/lib/botocore/data/migration-hub-refactor-spaces/2021-10-26 INFO : root : copying botocore/data/migration-hub-refactor-spaces/2021-10-26/paginators-1.json -> build/lib/botocore/data/migration-hub-refactor-spaces/2021-10-26 INFO : root : copying botocore/data/migration-hub-refactor-spaces/2021-10-26/service-2.json -> build/lib/botocore/data/migration-hub-refactor-spaces/2021-10-26 INFO : root : creating build/lib/botocore/data/migrationhub-config INFO : root : creating build/lib/botocore/data/migrationhub-config/2019-06-30 INFO : root : copying botocore/data/migrationhub-config/2019-06-30/examples-1.json -> build/lib/botocore/data/migrationhub-config/2019-06-30 INFO : root : copying botocore/data/migrationhub-config/2019-06-30/paginators-1.json -> build/lib/botocore/data/migrationhub-config/2019-06-30 INFO : root : copying botocore/data/migrationhub-config/2019-06-30/service-2.json -> build/lib/botocore/data/migrationhub-config/2019-06-30 INFO : root : creating build/lib/botocore/data/migrationhuborchestrator INFO : root : creating build/lib/botocore/data/migrationhuborchestrator/2021-08-28 INFO : root : copying botocore/data/migrationhuborchestrator/2021-08-28/paginators-1.json -> build/lib/botocore/data/migrationhuborchestrator/2021-08-28 INFO : root : copying botocore/data/migrationhuborchestrator/2021-08-28/service-2.json -> build/lib/botocore/data/migrationhuborchestrator/2021-08-28 INFO : root : copying botocore/data/migrationhuborchestrator/2021-08-28/waiters-2.json -> build/lib/botocore/data/migrationhuborchestrator/2021-08-28 INFO : root : creating build/lib/botocore/data/migrationhubstrategy INFO : root : creating build/lib/botocore/data/migrationhubstrategy/2020-02-19 INFO : root : copying botocore/data/migrationhubstrategy/2020-02-19/examples-1.json -> build/lib/botocore/data/migrationhubstrategy/2020-02-19 INFO : root : copying botocore/data/migrationhubstrategy/2020-02-19/paginators-1.json -> build/lib/botocore/data/migrationhubstrategy/2020-02-19 INFO : root : copying botocore/data/migrationhubstrategy/2020-02-19/paginators-1.sdk-extras.json -> build/lib/botocore/data/migrationhubstrategy/2020-02-19 INFO : root : copying botocore/data/migrationhubstrategy/2020-02-19/service-2.json -> build/lib/botocore/data/migrationhubstrategy/2020-02-19 INFO : root : creating build/lib/botocore/data/mobile INFO : root : creating build/lib/botocore/data/mobile/2017-07-01 INFO : root : copying botocore/data/mobile/2017-07-01/examples-1.json -> build/lib/botocore/data/mobile/2017-07-01 INFO : root : copying botocore/data/mobile/2017-07-01/paginators-1.json -> build/lib/botocore/data/mobile/2017-07-01 INFO : root : copying botocore/data/mobile/2017-07-01/service-2.json -> build/lib/botocore/data/mobile/2017-07-01 INFO : root : creating build/lib/botocore/data/mq INFO : root : creating build/lib/botocore/data/mq/2017-11-27 INFO : root : copying botocore/data/mq/2017-11-27/paginators-1.json -> build/lib/botocore/data/mq/2017-11-27 INFO : root : copying botocore/data/mq/2017-11-27/service-2.json -> build/lib/botocore/data/mq/2017-11-27 INFO : root : creating build/lib/botocore/data/mturk INFO : root : creating build/lib/botocore/data/mturk/2017-01-17 INFO : root : copying botocore/data/mturk/2017-01-17/examples-1.json -> build/lib/botocore/data/mturk/2017-01-17 INFO : root : copying botocore/data/mturk/2017-01-17/paginators-1.json -> build/lib/botocore/data/mturk/2017-01-17 INFO : root : copying botocore/data/mturk/2017-01-17/service-2.json -> build/lib/botocore/data/mturk/2017-01-17 INFO : root : creating build/lib/botocore/data/mwaa INFO : root : creating build/lib/botocore/data/mwaa/2020-07-01 INFO : root : copying botocore/data/mwaa/2020-07-01/examples-1.json -> build/lib/botocore/data/mwaa/2020-07-01 INFO : root : copying botocore/data/mwaa/2020-07-01/paginators-1.json -> build/lib/botocore/data/mwaa/2020-07-01 INFO : root : copying botocore/data/mwaa/2020-07-01/service-2.json -> build/lib/botocore/data/mwaa/2020-07-01 INFO : root : creating build/lib/botocore/data/neptune INFO : root : creating build/lib/botocore/data/neptune/2014-10-31 INFO : root : copying botocore/data/neptune/2014-10-31/examples-1.json -> build/lib/botocore/data/neptune/2014-10-31 INFO : root : copying botocore/data/neptune/2014-10-31/paginators-1.json -> build/lib/botocore/data/neptune/2014-10-31 INFO : root : copying botocore/data/neptune/2014-10-31/service-2.json -> build/lib/botocore/data/neptune/2014-10-31 INFO : root : copying botocore/data/neptune/2014-10-31/service-2.sdk-extras.json -> build/lib/botocore/data/neptune/2014-10-31 INFO : root : copying botocore/data/neptune/2014-10-31/waiters-2.json -> build/lib/botocore/data/neptune/2014-10-31 INFO : root : creating build/lib/botocore/data/network-firewall INFO : root : creating build/lib/botocore/data/network-firewall/2020-11-12 INFO : root : copying botocore/data/network-firewall/2020-11-12/examples-1.json -> build/lib/botocore/data/network-firewall/2020-11-12 INFO : root : copying botocore/data/network-firewall/2020-11-12/paginators-1.json -> build/lib/botocore/data/network-firewall/2020-11-12 INFO : root : copying botocore/data/network-firewall/2020-11-12/service-2.json -> build/lib/botocore/data/network-firewall/2020-11-12 INFO : root : creating build/lib/botocore/data/networkmanager INFO : root : creating build/lib/botocore/data/networkmanager/2019-07-05 INFO : root : copying botocore/data/networkmanager/2019-07-05/examples-1.json -> build/lib/botocore/data/networkmanager/2019-07-05 INFO : root : copying botocore/data/networkmanager/2019-07-05/paginators-1.json -> build/lib/botocore/data/networkmanager/2019-07-05 INFO : root : copying botocore/data/networkmanager/2019-07-05/service-2.json -> build/lib/botocore/data/networkmanager/2019-07-05 INFO : root : creating build/lib/botocore/data/nimble INFO : root : creating build/lib/botocore/data/nimble/2020-08-01 INFO : root : copying botocore/data/nimble/2020-08-01/examples-1.json -> build/lib/botocore/data/nimble/2020-08-01 INFO : root : copying botocore/data/nimble/2020-08-01/paginators-1.json -> build/lib/botocore/data/nimble/2020-08-01 INFO : root : copying botocore/data/nimble/2020-08-01/service-2.json -> build/lib/botocore/data/nimble/2020-08-01 INFO : root : copying botocore/data/nimble/2020-08-01/waiters-2.json -> build/lib/botocore/data/nimble/2020-08-01 INFO : root : creating build/lib/botocore/data/opensearch INFO : root : creating build/lib/botocore/data/opensearch/2021-01-01 INFO : root : copying botocore/data/opensearch/2021-01-01/examples-1.json -> build/lib/botocore/data/opensearch/2021-01-01 INFO : root : copying botocore/data/opensearch/2021-01-01/paginators-1.json -> build/lib/botocore/data/opensearch/2021-01-01 INFO : root : copying botocore/data/opensearch/2021-01-01/service-2.json -> build/lib/botocore/data/opensearch/2021-01-01 INFO : root : creating build/lib/botocore/data/opsworks INFO : root : creating build/lib/botocore/data/opsworks/2013-02-18 INFO : root : copying botocore/data/opsworks/2013-02-18/examples-1.json -> build/lib/botocore/data/opsworks/2013-02-18 INFO : root : copying botocore/data/opsworks/2013-02-18/paginators-1.json -> build/lib/botocore/data/opsworks/2013-02-18 INFO : root : copying botocore/data/opsworks/2013-02-18/service-2.json -> build/lib/botocore/data/opsworks/2013-02-18 INFO : root : copying botocore/data/opsworks/2013-02-18/waiters-2.json -> build/lib/botocore/data/opsworks/2013-02-18 INFO : root : creating build/lib/botocore/data/opsworkscm INFO : root : creating build/lib/botocore/data/opsworkscm/2016-11-01 INFO : root : copying botocore/data/opsworkscm/2016-11-01/examples-1.json -> build/lib/botocore/data/opsworkscm/2016-11-01 INFO : root : copying botocore/data/opsworkscm/2016-11-01/paginators-1.json -> build/lib/botocore/data/opsworkscm/2016-11-01 INFO : root : copying botocore/data/opsworkscm/2016-11-01/service-2.json -> build/lib/botocore/data/opsworkscm/2016-11-01 INFO : root : copying botocore/data/opsworkscm/2016-11-01/waiters-2.json -> build/lib/botocore/data/opsworkscm/2016-11-01 INFO : root : creating build/lib/botocore/data/organizations INFO : root : creating build/lib/botocore/data/organizations/2016-11-28 INFO : root : copying botocore/data/organizations/2016-11-28/examples-1.json -> build/lib/botocore/data/organizations/2016-11-28 INFO : root : copying botocore/data/organizations/2016-11-28/paginators-1.json -> build/lib/botocore/data/organizations/2016-11-28 INFO : root : copying botocore/data/organizations/2016-11-28/service-2.json -> build/lib/botocore/data/organizations/2016-11-28 INFO : root : creating build/lib/botocore/data/outposts INFO : root : creating build/lib/botocore/data/outposts/2019-12-03 INFO : root : copying botocore/data/outposts/2019-12-03/examples-1.json -> build/lib/botocore/data/outposts/2019-12-03 INFO : root : copying botocore/data/outposts/2019-12-03/paginators-1.json -> build/lib/botocore/data/outposts/2019-12-03 INFO : root : copying botocore/data/outposts/2019-12-03/service-2.json -> build/lib/botocore/data/outposts/2019-12-03 INFO : root : creating build/lib/botocore/data/panorama INFO : root : creating build/lib/botocore/data/panorama/2019-07-24 INFO : root : copying botocore/data/panorama/2019-07-24/examples-1.json -> build/lib/botocore/data/panorama/2019-07-24 INFO : root : copying botocore/data/panorama/2019-07-24/paginators-1.json -> build/lib/botocore/data/panorama/2019-07-24 INFO : root : copying botocore/data/panorama/2019-07-24/service-2.json -> build/lib/botocore/data/panorama/2019-07-24 INFO : root : creating build/lib/botocore/data/personalize-events INFO : root : creating build/lib/botocore/data/personalize-events/2018-03-22 INFO : root : copying botocore/data/personalize-events/2018-03-22/examples-1.json -> build/lib/botocore/data/personalize-events/2018-03-22 INFO : root : copying botocore/data/personalize-events/2018-03-22/paginators-1.json -> build/lib/botocore/data/personalize-events/2018-03-22 INFO : root : copying botocore/data/personalize-events/2018-03-22/service-2.json -> build/lib/botocore/data/personalize-events/2018-03-22 INFO : root : creating build/lib/botocore/data/personalize-runtime INFO : root : creating build/lib/botocore/data/personalize-runtime/2018-05-22 INFO : root : copying botocore/data/personalize-runtime/2018-05-22/examples-1.json -> build/lib/botocore/data/personalize-runtime/2018-05-22 INFO : root : copying botocore/data/personalize-runtime/2018-05-22/paginators-1.json -> build/lib/botocore/data/personalize-runtime/2018-05-22 INFO : root : copying botocore/data/personalize-runtime/2018-05-22/service-2.json -> build/lib/botocore/data/personalize-runtime/2018-05-22 INFO : root : creating build/lib/botocore/data/personalize INFO : root : creating build/lib/botocore/data/personalize/2018-05-22 INFO : root : copying botocore/data/personalize/2018-05-22/examples-1.json -> build/lib/botocore/data/personalize/2018-05-22 INFO : root : copying botocore/data/personalize/2018-05-22/paginators-1.json -> build/lib/botocore/data/personalize/2018-05-22 INFO : root : copying botocore/data/personalize/2018-05-22/service-2.json -> build/lib/botocore/data/personalize/2018-05-22 INFO : root : creating build/lib/botocore/data/pi INFO : root : creating build/lib/botocore/data/pi/2018-02-27 INFO : root : copying botocore/data/pi/2018-02-27/examples-1.json -> build/lib/botocore/data/pi/2018-02-27 INFO : root : copying botocore/data/pi/2018-02-27/paginators-1.json -> build/lib/botocore/data/pi/2018-02-27 INFO : root : copying botocore/data/pi/2018-02-27/service-2.json -> build/lib/botocore/data/pi/2018-02-27 INFO : root : creating build/lib/botocore/data/pinpoint-email INFO : root : creating build/lib/botocore/data/pinpoint-email/2018-07-26 INFO : root : copying botocore/data/pinpoint-email/2018-07-26/examples-1.json -> build/lib/botocore/data/pinpoint-email/2018-07-26 INFO : root : copying botocore/data/pinpoint-email/2018-07-26/paginators-1.json -> build/lib/botocore/data/pinpoint-email/2018-07-26 INFO : root : copying botocore/data/pinpoint-email/2018-07-26/service-2.json -> build/lib/botocore/data/pinpoint-email/2018-07-26 INFO : root : creating build/lib/botocore/data/pinpoint-sms-voice-v2 INFO : root : creating build/lib/botocore/data/pinpoint-sms-voice-v2/2022-03-31 INFO : root : copying botocore/data/pinpoint-sms-voice-v2/2022-03-31/examples-1.json -> build/lib/botocore/data/pinpoint-sms-voice-v2/2022-03-31 INFO : root : copying botocore/data/pinpoint-sms-voice-v2/2022-03-31/paginators-1.json -> build/lib/botocore/data/pinpoint-sms-voice-v2/2022-03-31 INFO : root : 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 INFO : root : copying botocore/data/pinpoint-sms-voice-v2/2022-03-31/service-2.json -> build/lib/botocore/data/pinpoint-sms-voice-v2/2022-03-31 INFO : root : copying botocore/data/pinpoint-sms-voice-v2/2022-03-31/waiters-2.json -> build/lib/botocore/data/pinpoint-sms-voice-v2/2022-03-31 INFO : root : creating build/lib/botocore/data/pinpoint-sms-voice INFO : root : creating build/lib/botocore/data/pinpoint-sms-voice/2018-09-05 INFO : root : copying botocore/data/pinpoint-sms-voice/2018-09-05/service-2.json -> build/lib/botocore/data/pinpoint-sms-voice/2018-09-05 INFO : root : creating build/lib/botocore/data/pinpoint INFO : root : creating build/lib/botocore/data/pinpoint/2016-12-01 INFO : root : copying botocore/data/pinpoint/2016-12-01/examples-1.json -> build/lib/botocore/data/pinpoint/2016-12-01 INFO : root : copying botocore/data/pinpoint/2016-12-01/service-2.json -> build/lib/botocore/data/pinpoint/2016-12-01 INFO : root : creating build/lib/botocore/data/polly INFO : root : creating build/lib/botocore/data/polly/2016-06-10 INFO : root : copying botocore/data/polly/2016-06-10/examples-1.json -> build/lib/botocore/data/polly/2016-06-10 INFO : root : copying botocore/data/polly/2016-06-10/paginators-1.json -> build/lib/botocore/data/polly/2016-06-10 INFO : root : copying botocore/data/polly/2016-06-10/service-2.json -> build/lib/botocore/data/polly/2016-06-10 INFO : root : creating build/lib/botocore/data/pricing INFO : root : creating build/lib/botocore/data/pricing/2017-10-15 INFO : root : copying botocore/data/pricing/2017-10-15/examples-1.json -> build/lib/botocore/data/pricing/2017-10-15 INFO : root : copying botocore/data/pricing/2017-10-15/paginators-1.json -> build/lib/botocore/data/pricing/2017-10-15 INFO : root : copying botocore/data/pricing/2017-10-15/service-2.json -> build/lib/botocore/data/pricing/2017-10-15 INFO : root : creating build/lib/botocore/data/privatenetworks INFO : root : creating build/lib/botocore/data/privatenetworks/2021-12-03 INFO : root : copying botocore/data/privatenetworks/2021-12-03/paginators-1.json -> build/lib/botocore/data/privatenetworks/2021-12-03 INFO : root : copying botocore/data/privatenetworks/2021-12-03/service-2.json -> build/lib/botocore/data/privatenetworks/2021-12-03 INFO : root : creating build/lib/botocore/data/proton INFO : root : creating build/lib/botocore/data/proton/2020-07-20 INFO : root : copying botocore/data/proton/2020-07-20/examples-1.json -> build/lib/botocore/data/proton/2020-07-20 INFO : root : copying botocore/data/proton/2020-07-20/paginators-1.json -> build/lib/botocore/data/proton/2020-07-20 INFO : root : copying botocore/data/proton/2020-07-20/service-2.json -> build/lib/botocore/data/proton/2020-07-20 INFO : root : copying botocore/data/proton/2020-07-20/waiters-2.json -> build/lib/botocore/data/proton/2020-07-20 INFO : root : creating build/lib/botocore/data/qldb-session INFO : root : creating build/lib/botocore/data/qldb-session/2019-07-11 INFO : root : copying botocore/data/qldb-session/2019-07-11/examples-1.json -> build/lib/botocore/data/qldb-session/2019-07-11 INFO : root : copying botocore/data/qldb-session/2019-07-11/paginators-1.json -> build/lib/botocore/data/qldb-session/2019-07-11 INFO : root : copying botocore/data/qldb-session/2019-07-11/service-2.json -> build/lib/botocore/data/qldb-session/2019-07-11 INFO : root : creating build/lib/botocore/data/qldb INFO : root : creating build/lib/botocore/data/qldb/2019-01-02 INFO : root : copying botocore/data/qldb/2019-01-02/examples-1.json -> build/lib/botocore/data/qldb/2019-01-02 INFO : root : copying botocore/data/qldb/2019-01-02/paginators-1.json -> build/lib/botocore/data/qldb/2019-01-02 INFO : root : copying botocore/data/qldb/2019-01-02/service-2.json -> build/lib/botocore/data/qldb/2019-01-02 INFO : root : creating build/lib/botocore/data/quicksight INFO : root : creating build/lib/botocore/data/quicksight/2018-04-01 INFO : root : copying botocore/data/quicksight/2018-04-01/examples-1.json -> build/lib/botocore/data/quicksight/2018-04-01 INFO : root : copying botocore/data/quicksight/2018-04-01/paginators-1.json -> build/lib/botocore/data/quicksight/2018-04-01 INFO : root : copying botocore/data/quicksight/2018-04-01/paginators-1.sdk-extras.json -> build/lib/botocore/data/quicksight/2018-04-01 INFO : root : copying botocore/data/quicksight/2018-04-01/service-2.json -> build/lib/botocore/data/quicksight/2018-04-01 INFO : root : creating build/lib/botocore/data/ram INFO : root : creating build/lib/botocore/data/ram/2018-01-04 INFO : root : copying botocore/data/ram/2018-01-04/examples-1.json -> build/lib/botocore/data/ram/2018-01-04 INFO : root : copying botocore/data/ram/2018-01-04/paginators-1.json -> build/lib/botocore/data/ram/2018-01-04 INFO : root : copying botocore/data/ram/2018-01-04/service-2.json -> build/lib/botocore/data/ram/2018-01-04 INFO : root : creating build/lib/botocore/data/rbin INFO : root : creating build/lib/botocore/data/rbin/2021-06-15 INFO : root : copying botocore/data/rbin/2021-06-15/examples-1.json -> build/lib/botocore/data/rbin/2021-06-15 INFO : root : copying botocore/data/rbin/2021-06-15/paginators-1.json -> build/lib/botocore/data/rbin/2021-06-15 INFO : root : copying botocore/data/rbin/2021-06-15/service-2.json -> build/lib/botocore/data/rbin/2021-06-15 INFO : root : creating build/lib/botocore/data/rds-data INFO : root : creating build/lib/botocore/data/rds-data/2018-08-01 INFO : root : copying botocore/data/rds-data/2018-08-01/examples-1.json -> build/lib/botocore/data/rds-data/2018-08-01 INFO : root : copying botocore/data/rds-data/2018-08-01/paginators-1.json -> build/lib/botocore/data/rds-data/2018-08-01 INFO : root : copying botocore/data/rds-data/2018-08-01/service-2.json -> build/lib/botocore/data/rds-data/2018-08-01 INFO : root : creating build/lib/botocore/data/rds INFO : root : creating build/lib/botocore/data/rds/2014-09-01 INFO : root : copying botocore/data/rds/2014-09-01/paginators-1.json -> build/lib/botocore/data/rds/2014-09-01 INFO : root : copying botocore/data/rds/2014-09-01/service-2.json -> build/lib/botocore/data/rds/2014-09-01 INFO : root : copying botocore/data/rds/2014-09-01/waiters-2.json -> build/lib/botocore/data/rds/2014-09-01 INFO : root : creating build/lib/botocore/data/rds/2014-10-31 INFO : root : copying botocore/data/rds/2014-10-31/examples-1.json -> build/lib/botocore/data/rds/2014-10-31 INFO : root : copying botocore/data/rds/2014-10-31/paginators-1.json -> build/lib/botocore/data/rds/2014-10-31 INFO : root : copying botocore/data/rds/2014-10-31/service-2.json -> build/lib/botocore/data/rds/2014-10-31 INFO : root : copying botocore/data/rds/2014-10-31/service-2.sdk-extras.json -> build/lib/botocore/data/rds/2014-10-31 INFO : root : copying botocore/data/rds/2014-10-31/waiters-2.json -> build/lib/botocore/data/rds/2014-10-31 INFO : root : creating build/lib/botocore/data/redshift-data INFO : root : creating build/lib/botocore/data/redshift-data/2019-12-20 INFO : root : copying botocore/data/redshift-data/2019-12-20/examples-1.json -> build/lib/botocore/data/redshift-data/2019-12-20 INFO : root : copying botocore/data/redshift-data/2019-12-20/paginators-1.json -> build/lib/botocore/data/redshift-data/2019-12-20 INFO : root : copying botocore/data/redshift-data/2019-12-20/paginators-1.sdk-extras.json -> build/lib/botocore/data/redshift-data/2019-12-20 INFO : root : copying botocore/data/redshift-data/2019-12-20/service-2.json -> build/lib/botocore/data/redshift-data/2019-12-20 INFO : root : creating build/lib/botocore/data/redshift-serverless INFO : root : creating build/lib/botocore/data/redshift-serverless/2021-04-21 INFO : root : copying botocore/data/redshift-serverless/2021-04-21/paginators-1.json -> build/lib/botocore/data/redshift-serverless/2021-04-21 INFO : root : copying botocore/data/redshift-serverless/2021-04-21/service-2.json -> build/lib/botocore/data/redshift-serverless/2021-04-21 INFO : root : creating build/lib/botocore/data/redshift INFO : root : creating build/lib/botocore/data/redshift/2012-12-01 INFO : root : copying botocore/data/redshift/2012-12-01/examples-1.json -> build/lib/botocore/data/redshift/2012-12-01 INFO : root : copying botocore/data/redshift/2012-12-01/paginators-1.json -> build/lib/botocore/data/redshift/2012-12-01 INFO : root : copying botocore/data/redshift/2012-12-01/service-2.json -> build/lib/botocore/data/redshift/2012-12-01 INFO : root : copying botocore/data/redshift/2012-12-01/waiters-2.json -> build/lib/botocore/data/redshift/2012-12-01 INFO : root : creating build/lib/botocore/data/rekognition INFO : root : creating build/lib/botocore/data/rekognition/2016-06-27 INFO : root : copying botocore/data/rekognition/2016-06-27/examples-1.json -> build/lib/botocore/data/rekognition/2016-06-27 INFO : root : copying botocore/data/rekognition/2016-06-27/paginators-1.json -> build/lib/botocore/data/rekognition/2016-06-27 INFO : root : copying botocore/data/rekognition/2016-06-27/service-2.json -> build/lib/botocore/data/rekognition/2016-06-27 INFO : root : copying botocore/data/rekognition/2016-06-27/waiters-2.json -> build/lib/botocore/data/rekognition/2016-06-27 INFO : root : creating build/lib/botocore/data/resiliencehub INFO : root : creating build/lib/botocore/data/resiliencehub/2020-04-30 INFO : root : copying botocore/data/resiliencehub/2020-04-30/examples-1.json -> build/lib/botocore/data/resiliencehub/2020-04-30 INFO : root : copying botocore/data/resiliencehub/2020-04-30/paginators-1.json -> build/lib/botocore/data/resiliencehub/2020-04-30 INFO : root : copying botocore/data/resiliencehub/2020-04-30/service-2.json -> build/lib/botocore/data/resiliencehub/2020-04-30 INFO : root : creating build/lib/botocore/data/resource-groups INFO : root : creating build/lib/botocore/data/resource-groups/2017-11-27 INFO : root : copying botocore/data/resource-groups/2017-11-27/examples-1.json -> build/lib/botocore/data/resource-groups/2017-11-27 INFO : root : copying botocore/data/resource-groups/2017-11-27/paginators-1.json -> build/lib/botocore/data/resource-groups/2017-11-27 INFO : root : copying botocore/data/resource-groups/2017-11-27/service-2.json -> build/lib/botocore/data/resource-groups/2017-11-27 INFO : root : creating build/lib/botocore/data/resourcegroupstaggingapi INFO : root : creating build/lib/botocore/data/resourcegroupstaggingapi/2017-01-26 INFO : root : copying botocore/data/resourcegroupstaggingapi/2017-01-26/examples-1.json -> build/lib/botocore/data/resourcegroupstaggingapi/2017-01-26 INFO : root : copying botocore/data/resourcegroupstaggingapi/2017-01-26/paginators-1.json -> build/lib/botocore/data/resourcegroupstaggingapi/2017-01-26 INFO : root : copying botocore/data/resourcegroupstaggingapi/2017-01-26/service-2.json -> build/lib/botocore/data/resourcegroupstaggingapi/2017-01-26 INFO : root : creating build/lib/botocore/data/robomaker INFO : root : creating build/lib/botocore/data/robomaker/2018-06-29 INFO : root : copying botocore/data/robomaker/2018-06-29/examples-1.json -> build/lib/botocore/data/robomaker/2018-06-29 INFO : root : copying botocore/data/robomaker/2018-06-29/paginators-1.json -> build/lib/botocore/data/robomaker/2018-06-29 INFO : root : copying botocore/data/robomaker/2018-06-29/service-2.json -> build/lib/botocore/data/robomaker/2018-06-29 INFO : root : creating build/lib/botocore/data/rolesanywhere INFO : root : creating build/lib/botocore/data/rolesanywhere/2018-05-10 INFO : root : copying botocore/data/rolesanywhere/2018-05-10/paginators-1.json -> build/lib/botocore/data/rolesanywhere/2018-05-10 INFO : root : copying botocore/data/rolesanywhere/2018-05-10/service-2.json -> build/lib/botocore/data/rolesanywhere/2018-05-10 INFO : root : creating build/lib/botocore/data/route53-recovery-cluster INFO : root : creating build/lib/botocore/data/route53-recovery-cluster/2019-12-02 INFO : root : copying botocore/data/route53-recovery-cluster/2019-12-02/examples-1.json -> build/lib/botocore/data/route53-recovery-cluster/2019-12-02 INFO : root : copying botocore/data/route53-recovery-cluster/2019-12-02/paginators-1.json -> build/lib/botocore/data/route53-recovery-cluster/2019-12-02 INFO : root : copying botocore/data/route53-recovery-cluster/2019-12-02/service-2.json -> build/lib/botocore/data/route53-recovery-cluster/2019-12-02 INFO : root : creating build/lib/botocore/data/route53-recovery-control-config INFO : root : creating build/lib/botocore/data/route53-recovery-control-config/2020-11-02 INFO : root : copying botocore/data/route53-recovery-control-config/2020-11-02/paginators-1.json -> build/lib/botocore/data/route53-recovery-control-config/2020-11-02 INFO : root : copying botocore/data/route53-recovery-control-config/2020-11-02/service-2.json -> build/lib/botocore/data/route53-recovery-control-config/2020-11-02 INFO : root : copying botocore/data/route53-recovery-control-config/2020-11-02/waiters-2.json -> build/lib/botocore/data/route53-recovery-control-config/2020-11-02 INFO : root : creating build/lib/botocore/data/route53-recovery-readiness INFO : root : creating build/lib/botocore/data/route53-recovery-readiness/2019-12-02 INFO : root : copying botocore/data/route53-recovery-readiness/2019-12-02/paginators-1.json -> build/lib/botocore/data/route53-recovery-readiness/2019-12-02 INFO : root : copying botocore/data/route53-recovery-readiness/2019-12-02/service-2.json -> build/lib/botocore/data/route53-recovery-readiness/2019-12-02 INFO : root : creating build/lib/botocore/data/route53 INFO : root : creating build/lib/botocore/data/route53/2013-04-01 INFO : root : copying botocore/data/route53/2013-04-01/examples-1.json -> build/lib/botocore/data/route53/2013-04-01 INFO : root : copying botocore/data/route53/2013-04-01/paginators-1.json -> build/lib/botocore/data/route53/2013-04-01 INFO : root : copying botocore/data/route53/2013-04-01/service-2.json -> build/lib/botocore/data/route53/2013-04-01 INFO : root : copying botocore/data/route53/2013-04-01/waiters-2.json -> build/lib/botocore/data/route53/2013-04-01 INFO : root : creating build/lib/botocore/data/route53domains INFO : root : creating build/lib/botocore/data/route53domains/2014-05-15 INFO : root : copying botocore/data/route53domains/2014-05-15/examples-1.json -> build/lib/botocore/data/route53domains/2014-05-15 INFO : root : copying botocore/data/route53domains/2014-05-15/paginators-1.json -> build/lib/botocore/data/route53domains/2014-05-15 INFO : root : copying botocore/data/route53domains/2014-05-15/service-2.json -> build/lib/botocore/data/route53domains/2014-05-15 INFO : root : creating build/lib/botocore/data/route53resolver INFO : root : creating build/lib/botocore/data/route53resolver/2018-04-01 INFO : root : copying botocore/data/route53resolver/2018-04-01/examples-1.json -> build/lib/botocore/data/route53resolver/2018-04-01 INFO : root : copying botocore/data/route53resolver/2018-04-01/paginators-1.json -> build/lib/botocore/data/route53resolver/2018-04-01 INFO : root : copying botocore/data/route53resolver/2018-04-01/paginators-1.sdk-extras.json -> build/lib/botocore/data/route53resolver/2018-04-01 INFO : root : copying botocore/data/route53resolver/2018-04-01/service-2.json -> build/lib/botocore/data/route53resolver/2018-04-01 INFO : root : creating build/lib/botocore/data/rum INFO : root : creating build/lib/botocore/data/rum/2018-05-10 INFO : root : copying botocore/data/rum/2018-05-10/examples-1.json -> build/lib/botocore/data/rum/2018-05-10 INFO : root : copying botocore/data/rum/2018-05-10/paginators-1.json -> build/lib/botocore/data/rum/2018-05-10 INFO : root : copying botocore/data/rum/2018-05-10/service-2.json -> build/lib/botocore/data/rum/2018-05-10 INFO : root : creating build/lib/botocore/data/s3 INFO : root : creating build/lib/botocore/data/s3/2006-03-01 INFO : root : copying botocore/data/s3/2006-03-01/examples-1.json -> build/lib/botocore/data/s3/2006-03-01 INFO : root : copying botocore/data/s3/2006-03-01/paginators-1.json -> build/lib/botocore/data/s3/2006-03-01 INFO : root : copying botocore/data/s3/2006-03-01/service-2.json -> build/lib/botocore/data/s3/2006-03-01 INFO : root : copying botocore/data/s3/2006-03-01/waiters-2.json -> build/lib/botocore/data/s3/2006-03-01 INFO : root : creating build/lib/botocore/data/s3control INFO : root : creating build/lib/botocore/data/s3control/2018-08-20 INFO : root : copying botocore/data/s3control/2018-08-20/examples-1.json -> build/lib/botocore/data/s3control/2018-08-20 INFO : root : copying botocore/data/s3control/2018-08-20/paginators-1.json -> build/lib/botocore/data/s3control/2018-08-20 INFO : root : copying botocore/data/s3control/2018-08-20/service-2.json -> build/lib/botocore/data/s3control/2018-08-20 INFO : root : creating build/lib/botocore/data/s3outposts INFO : root : creating build/lib/botocore/data/s3outposts/2017-07-25 INFO : root : copying botocore/data/s3outposts/2017-07-25/examples-1.json -> build/lib/botocore/data/s3outposts/2017-07-25 INFO : root : copying botocore/data/s3outposts/2017-07-25/paginators-1.json -> build/lib/botocore/data/s3outposts/2017-07-25 INFO : root : copying botocore/data/s3outposts/2017-07-25/service-2.json -> build/lib/botocore/data/s3outposts/2017-07-25 INFO : root : creating build/lib/botocore/data/sagemaker-a2i-runtime INFO : root : creating build/lib/botocore/data/sagemaker-a2i-runtime/2019-11-07 INFO : root : copying botocore/data/sagemaker-a2i-runtime/2019-11-07/examples-1.json -> build/lib/botocore/data/sagemaker-a2i-runtime/2019-11-07 INFO : root : copying botocore/data/sagemaker-a2i-runtime/2019-11-07/paginators-1.json -> build/lib/botocore/data/sagemaker-a2i-runtime/2019-11-07 INFO : root : copying botocore/data/sagemaker-a2i-runtime/2019-11-07/service-2.json -> build/lib/botocore/data/sagemaker-a2i-runtime/2019-11-07 INFO : root : creating build/lib/botocore/data/sagemaker-edge INFO : root : creating build/lib/botocore/data/sagemaker-edge/2020-09-23 INFO : root : copying botocore/data/sagemaker-edge/2020-09-23/examples-1.json -> build/lib/botocore/data/sagemaker-edge/2020-09-23 INFO : root : copying botocore/data/sagemaker-edge/2020-09-23/paginators-1.json -> build/lib/botocore/data/sagemaker-edge/2020-09-23 INFO : root : copying botocore/data/sagemaker-edge/2020-09-23/service-2.json -> build/lib/botocore/data/sagemaker-edge/2020-09-23 INFO : root : creating build/lib/botocore/data/sagemaker-featurestore-runtime INFO : root : creating build/lib/botocore/data/sagemaker-featurestore-runtime/2020-07-01 INFO : root : copying botocore/data/sagemaker-featurestore-runtime/2020-07-01/examples-1.json -> build/lib/botocore/data/sagemaker-featurestore-runtime/2020-07-01 INFO : root : copying botocore/data/sagemaker-featurestore-runtime/2020-07-01/paginators-1.json -> build/lib/botocore/data/sagemaker-featurestore-runtime/2020-07-01 INFO : root : copying botocore/data/sagemaker-featurestore-runtime/2020-07-01/service-2.json -> build/lib/botocore/data/sagemaker-featurestore-runtime/2020-07-01 INFO : root : creating build/lib/botocore/data/sagemaker-runtime INFO : root : creating build/lib/botocore/data/sagemaker-runtime/2017-05-13 INFO : root : copying botocore/data/sagemaker-runtime/2017-05-13/examples-1.json -> build/lib/botocore/data/sagemaker-runtime/2017-05-13 INFO : root : copying botocore/data/sagemaker-runtime/2017-05-13/paginators-1.json -> build/lib/botocore/data/sagemaker-runtime/2017-05-13 INFO : root : copying botocore/data/sagemaker-runtime/2017-05-13/service-2.json -> build/lib/botocore/data/sagemaker-runtime/2017-05-13 INFO : root : creating build/lib/botocore/data/sagemaker INFO : root : creating build/lib/botocore/data/sagemaker/2017-07-24 INFO : root : copying botocore/data/sagemaker/2017-07-24/examples-1.json -> build/lib/botocore/data/sagemaker/2017-07-24 INFO : root : copying botocore/data/sagemaker/2017-07-24/paginators-1.json -> build/lib/botocore/data/sagemaker/2017-07-24 INFO : root : copying botocore/data/sagemaker/2017-07-24/service-2.json -> build/lib/botocore/data/sagemaker/2017-07-24 INFO : root : copying botocore/data/sagemaker/2017-07-24/waiters-2.json -> build/lib/botocore/data/sagemaker/2017-07-24 INFO : root : creating build/lib/botocore/data/savingsplans INFO : root : creating build/lib/botocore/data/savingsplans/2019-06-28 INFO : root : copying botocore/data/savingsplans/2019-06-28/examples-1.json -> build/lib/botocore/data/savingsplans/2019-06-28 INFO : root : copying botocore/data/savingsplans/2019-06-28/paginators-1.json -> build/lib/botocore/data/savingsplans/2019-06-28 INFO : root : copying botocore/data/savingsplans/2019-06-28/service-2.json -> build/lib/botocore/data/savingsplans/2019-06-28 INFO : root : creating build/lib/botocore/data/schemas INFO : root : creating build/lib/botocore/data/schemas/2019-12-02 INFO : root : copying botocore/data/schemas/2019-12-02/paginators-1.json -> build/lib/botocore/data/schemas/2019-12-02 INFO : root : copying botocore/data/schemas/2019-12-02/service-2.json -> build/lib/botocore/data/schemas/2019-12-02 INFO : root : copying botocore/data/schemas/2019-12-02/waiters-2.json -> build/lib/botocore/data/schemas/2019-12-02 INFO : root : creating build/lib/botocore/data/sdb INFO : root : creating build/lib/botocore/data/sdb/2009-04-15 INFO : root : copying botocore/data/sdb/2009-04-15/paginators-1.json -> build/lib/botocore/data/sdb/2009-04-15 INFO : root : copying botocore/data/sdb/2009-04-15/service-2.json -> build/lib/botocore/data/sdb/2009-04-15 INFO : root : creating build/lib/botocore/data/secretsmanager INFO : root : creating build/lib/botocore/data/secretsmanager/2017-10-17 INFO : root : copying botocore/data/secretsmanager/2017-10-17/examples-1.json -> build/lib/botocore/data/secretsmanager/2017-10-17 INFO : root : copying botocore/data/secretsmanager/2017-10-17/paginators-1.json -> build/lib/botocore/data/secretsmanager/2017-10-17 INFO : root : copying botocore/data/secretsmanager/2017-10-17/service-2.json -> build/lib/botocore/data/secretsmanager/2017-10-17 INFO : root : copying botocore/data/secretsmanager/2017-10-17/service-2.sdk-extras.json -> build/lib/botocore/data/secretsmanager/2017-10-17 INFO : root : creating build/lib/botocore/data/securityhub INFO : root : creating build/lib/botocore/data/securityhub/2018-10-26 INFO : root : copying botocore/data/securityhub/2018-10-26/examples-1.json -> build/lib/botocore/data/securityhub/2018-10-26 INFO : root : copying botocore/data/securityhub/2018-10-26/paginators-1.json -> build/lib/botocore/data/securityhub/2018-10-26 INFO : root : copying botocore/data/securityhub/2018-10-26/service-2.json -> build/lib/botocore/data/securityhub/2018-10-26 INFO : root : creating build/lib/botocore/data/serverlessrepo INFO : root : creating build/lib/botocore/data/serverlessrepo/2017-09-08 INFO : root : copying botocore/data/serverlessrepo/2017-09-08/paginators-1.json -> build/lib/botocore/data/serverlessrepo/2017-09-08 INFO : root : copying botocore/data/serverlessrepo/2017-09-08/service-2.json -> build/lib/botocore/data/serverlessrepo/2017-09-08 INFO : root : creating build/lib/botocore/data/service-quotas INFO : root : creating build/lib/botocore/data/service-quotas/2019-06-24 INFO : root : copying botocore/data/service-quotas/2019-06-24/examples-1.json -> build/lib/botocore/data/service-quotas/2019-06-24 INFO : root : copying botocore/data/service-quotas/2019-06-24/paginators-1.json -> build/lib/botocore/data/service-quotas/2019-06-24 INFO : root : copying botocore/data/service-quotas/2019-06-24/service-2.json -> build/lib/botocore/data/service-quotas/2019-06-24 INFO : root : creating build/lib/botocore/data/servicecatalog-appregistry INFO : root : creating build/lib/botocore/data/servicecatalog-appregistry/2020-06-24 INFO : root : copying botocore/data/servicecatalog-appregistry/2020-06-24/examples-1.json -> build/lib/botocore/data/servicecatalog-appregistry/2020-06-24 INFO : root : copying botocore/data/servicecatalog-appregistry/2020-06-24/paginators-1.json -> build/lib/botocore/data/servicecatalog-appregistry/2020-06-24 INFO : root : copying botocore/data/servicecatalog-appregistry/2020-06-24/service-2.json -> build/lib/botocore/data/servicecatalog-appregistry/2020-06-24 INFO : root : creating build/lib/botocore/data/servicecatalog INFO : root : creating build/lib/botocore/data/servicecatalog/2015-12-10 INFO : root : copying botocore/data/servicecatalog/2015-12-10/examples-1.json -> build/lib/botocore/data/servicecatalog/2015-12-10 INFO : root : copying botocore/data/servicecatalog/2015-12-10/paginators-1.json -> build/lib/botocore/data/servicecatalog/2015-12-10 INFO : root : copying botocore/data/servicecatalog/2015-12-10/service-2.json -> build/lib/botocore/data/servicecatalog/2015-12-10 INFO : root : creating build/lib/botocore/data/servicediscovery INFO : root : creating build/lib/botocore/data/servicediscovery/2017-03-14 INFO : root : copying botocore/data/servicediscovery/2017-03-14/examples-1.json -> build/lib/botocore/data/servicediscovery/2017-03-14 INFO : root : copying botocore/data/servicediscovery/2017-03-14/paginators-1.json -> build/lib/botocore/data/servicediscovery/2017-03-14 INFO : root : copying botocore/data/servicediscovery/2017-03-14/service-2.json -> build/lib/botocore/data/servicediscovery/2017-03-14 INFO : root : creating build/lib/botocore/data/ses INFO : root : creating build/lib/botocore/data/ses/2010-12-01 INFO : root : copying botocore/data/ses/2010-12-01/examples-1.json -> build/lib/botocore/data/ses/2010-12-01 INFO : root : copying botocore/data/ses/2010-12-01/paginators-1.json -> build/lib/botocore/data/ses/2010-12-01 INFO : root : copying botocore/data/ses/2010-12-01/service-2.json -> build/lib/botocore/data/ses/2010-12-01 INFO : root : copying botocore/data/ses/2010-12-01/waiters-2.json -> build/lib/botocore/data/ses/2010-12-01 INFO : root : creating build/lib/botocore/data/sesv2 INFO : root : creating build/lib/botocore/data/sesv2/2019-09-27 INFO : root : copying botocore/data/sesv2/2019-09-27/examples-1.json -> build/lib/botocore/data/sesv2/2019-09-27 INFO : root : copying botocore/data/sesv2/2019-09-27/paginators-1.json -> build/lib/botocore/data/sesv2/2019-09-27 INFO : root : copying botocore/data/sesv2/2019-09-27/service-2.json -> build/lib/botocore/data/sesv2/2019-09-27 INFO : root : creating build/lib/botocore/data/shield INFO : root : creating build/lib/botocore/data/shield/2016-06-02 INFO : root : copying botocore/data/shield/2016-06-02/examples-1.json -> build/lib/botocore/data/shield/2016-06-02 INFO : root : copying botocore/data/shield/2016-06-02/paginators-1.json -> build/lib/botocore/data/shield/2016-06-02 INFO : root : copying botocore/data/shield/2016-06-02/service-2.json -> build/lib/botocore/data/shield/2016-06-02 INFO : root : creating build/lib/botocore/data/signer INFO : root : creating build/lib/botocore/data/signer/2017-08-25 INFO : root : copying botocore/data/signer/2017-08-25/examples-1.json -> build/lib/botocore/data/signer/2017-08-25 INFO : root : copying botocore/data/signer/2017-08-25/paginators-1.json -> build/lib/botocore/data/signer/2017-08-25 INFO : root : copying botocore/data/signer/2017-08-25/service-2.json -> build/lib/botocore/data/signer/2017-08-25 INFO : root : copying botocore/data/signer/2017-08-25/waiters-2.json -> build/lib/botocore/data/signer/2017-08-25 INFO : root : creating build/lib/botocore/data/sms-voice INFO : root : creating build/lib/botocore/data/sms-voice/2018-09-05 INFO : root : copying botocore/data/sms-voice/2018-09-05/service-2.json -> build/lib/botocore/data/sms-voice/2018-09-05 INFO : root : creating build/lib/botocore/data/sms INFO : root : creating build/lib/botocore/data/sms/2016-10-24 INFO : root : copying botocore/data/sms/2016-10-24/examples-1.json -> build/lib/botocore/data/sms/2016-10-24 INFO : root : copying botocore/data/sms/2016-10-24/paginators-1.json -> build/lib/botocore/data/sms/2016-10-24 INFO : root : copying botocore/data/sms/2016-10-24/service-2.json -> build/lib/botocore/data/sms/2016-10-24 INFO : root : creating build/lib/botocore/data/snow-device-management INFO : root : creating build/lib/botocore/data/snow-device-management/2021-08-04 INFO : root : copying botocore/data/snow-device-management/2021-08-04/examples-1.json -> build/lib/botocore/data/snow-device-management/2021-08-04 INFO : root : copying botocore/data/snow-device-management/2021-08-04/paginators-1.json -> build/lib/botocore/data/snow-device-management/2021-08-04 INFO : root : copying botocore/data/snow-device-management/2021-08-04/service-2.json -> build/lib/botocore/data/snow-device-management/2021-08-04 INFO : root : creating build/lib/botocore/data/snowball INFO : root : creating build/lib/botocore/data/snowball/2016-06-30 INFO : root : copying botocore/data/snowball/2016-06-30/examples-1.json -> build/lib/botocore/data/snowball/2016-06-30 INFO : root : copying botocore/data/snowball/2016-06-30/paginators-1.json -> build/lib/botocore/data/snowball/2016-06-30 INFO : root : copying botocore/data/snowball/2016-06-30/service-2.json -> build/lib/botocore/data/snowball/2016-06-30 INFO : root : creating build/lib/botocore/data/sns INFO : root : creating build/lib/botocore/data/sns/2010-03-31 INFO : root : copying botocore/data/sns/2010-03-31/examples-1.json -> build/lib/botocore/data/sns/2010-03-31 INFO : root : copying botocore/data/sns/2010-03-31/paginators-1.json -> build/lib/botocore/data/sns/2010-03-31 INFO : root : copying botocore/data/sns/2010-03-31/service-2.json -> build/lib/botocore/data/sns/2010-03-31 INFO : root : creating build/lib/botocore/data/sqs INFO : root : creating build/lib/botocore/data/sqs/2012-11-05 INFO : root : copying botocore/data/sqs/2012-11-05/examples-1.json -> build/lib/botocore/data/sqs/2012-11-05 INFO : root : copying botocore/data/sqs/2012-11-05/paginators-1.json -> build/lib/botocore/data/sqs/2012-11-05 INFO : root : copying botocore/data/sqs/2012-11-05/service-2.json -> build/lib/botocore/data/sqs/2012-11-05 INFO : root : creating build/lib/botocore/data/ssm-contacts INFO : root : creating build/lib/botocore/data/ssm-contacts/2021-05-03 INFO : root : copying botocore/data/ssm-contacts/2021-05-03/examples-1.json -> build/lib/botocore/data/ssm-contacts/2021-05-03 INFO : root : copying botocore/data/ssm-contacts/2021-05-03/paginators-1.json -> build/lib/botocore/data/ssm-contacts/2021-05-03 INFO : root : copying botocore/data/ssm-contacts/2021-05-03/service-2.json -> build/lib/botocore/data/ssm-contacts/2021-05-03 INFO : root : creating build/lib/botocore/data/ssm-incidents INFO : root : creating build/lib/botocore/data/ssm-incidents/2018-05-10 INFO : root : copying botocore/data/ssm-incidents/2018-05-10/examples-1.json -> build/lib/botocore/data/ssm-incidents/2018-05-10 INFO : root : copying botocore/data/ssm-incidents/2018-05-10/paginators-1.json -> build/lib/botocore/data/ssm-incidents/2018-05-10 INFO : root : copying botocore/data/ssm-incidents/2018-05-10/service-2.json -> build/lib/botocore/data/ssm-incidents/2018-05-10 INFO : root : copying botocore/data/ssm-incidents/2018-05-10/waiters-2.json -> build/lib/botocore/data/ssm-incidents/2018-05-10 INFO : root : creating build/lib/botocore/data/ssm INFO : root : creating build/lib/botocore/data/ssm/2014-11-06 INFO : root : copying botocore/data/ssm/2014-11-06/examples-1.json -> build/lib/botocore/data/ssm/2014-11-06 INFO : root : copying botocore/data/ssm/2014-11-06/paginators-1.json -> build/lib/botocore/data/ssm/2014-11-06 INFO : root : copying botocore/data/ssm/2014-11-06/service-2.json -> build/lib/botocore/data/ssm/2014-11-06 INFO : root : copying botocore/data/ssm/2014-11-06/waiters-2.json -> build/lib/botocore/data/ssm/2014-11-06 INFO : root : creating build/lib/botocore/data/sso-admin INFO : root : creating build/lib/botocore/data/sso-admin/2020-07-20 INFO : root : copying botocore/data/sso-admin/2020-07-20/examples-1.json -> build/lib/botocore/data/sso-admin/2020-07-20 INFO : root : copying botocore/data/sso-admin/2020-07-20/paginators-1.json -> build/lib/botocore/data/sso-admin/2020-07-20 INFO : root : copying botocore/data/sso-admin/2020-07-20/service-2.json -> build/lib/botocore/data/sso-admin/2020-07-20 INFO : root : creating build/lib/botocore/data/sso-oidc INFO : root : creating build/lib/botocore/data/sso-oidc/2019-06-10 INFO : root : copying botocore/data/sso-oidc/2019-06-10/examples-1.json -> build/lib/botocore/data/sso-oidc/2019-06-10 INFO : root : copying botocore/data/sso-oidc/2019-06-10/paginators-1.json -> build/lib/botocore/data/sso-oidc/2019-06-10 INFO : root : copying botocore/data/sso-oidc/2019-06-10/service-2.json -> build/lib/botocore/data/sso-oidc/2019-06-10 INFO : root : creating build/lib/botocore/data/sso INFO : root : creating build/lib/botocore/data/sso/2019-06-10 INFO : root : copying botocore/data/sso/2019-06-10/examples-1.json -> build/lib/botocore/data/sso/2019-06-10 INFO : root : copying botocore/data/sso/2019-06-10/paginators-1.json -> build/lib/botocore/data/sso/2019-06-10 INFO : root : copying botocore/data/sso/2019-06-10/service-2.json -> build/lib/botocore/data/sso/2019-06-10 INFO : root : creating build/lib/botocore/data/stepfunctions INFO : root : creating build/lib/botocore/data/stepfunctions/2016-11-23 INFO : root : copying botocore/data/stepfunctions/2016-11-23/examples-1.json -> build/lib/botocore/data/stepfunctions/2016-11-23 INFO : root : copying botocore/data/stepfunctions/2016-11-23/paginators-1.json -> build/lib/botocore/data/stepfunctions/2016-11-23 INFO : root : copying botocore/data/stepfunctions/2016-11-23/service-2.json -> build/lib/botocore/data/stepfunctions/2016-11-23 INFO : root : creating build/lib/botocore/data/storagegateway INFO : root : creating build/lib/botocore/data/storagegateway/2013-06-30 INFO : root : copying botocore/data/storagegateway/2013-06-30/examples-1.json -> build/lib/botocore/data/storagegateway/2013-06-30 INFO : root : copying botocore/data/storagegateway/2013-06-30/paginators-1.json -> build/lib/botocore/data/storagegateway/2013-06-30 INFO : root : copying botocore/data/storagegateway/2013-06-30/service-2.json -> build/lib/botocore/data/storagegateway/2013-06-30 INFO : root : creating build/lib/botocore/data/sts INFO : root : creating build/lib/botocore/data/sts/2011-06-15 INFO : root : copying botocore/data/sts/2011-06-15/examples-1.json -> build/lib/botocore/data/sts/2011-06-15 INFO : root : copying botocore/data/sts/2011-06-15/paginators-1.json -> build/lib/botocore/data/sts/2011-06-15 INFO : root : copying botocore/data/sts/2011-06-15/service-2.json -> build/lib/botocore/data/sts/2011-06-15 INFO : root : creating build/lib/botocore/data/support-app INFO : root : creating build/lib/botocore/data/support-app/2021-08-20 INFO : root : copying botocore/data/support-app/2021-08-20/paginators-1.json -> build/lib/botocore/data/support-app/2021-08-20 INFO : root : copying botocore/data/support-app/2021-08-20/service-2.json -> build/lib/botocore/data/support-app/2021-08-20 INFO : root : creating build/lib/botocore/data/support INFO : root : creating build/lib/botocore/data/support/2013-04-15 INFO : root : copying botocore/data/support/2013-04-15/examples-1.json -> build/lib/botocore/data/support/2013-04-15 INFO : root : copying botocore/data/support/2013-04-15/paginators-1.json -> build/lib/botocore/data/support/2013-04-15 INFO : root : copying botocore/data/support/2013-04-15/service-2.json -> build/lib/botocore/data/support/2013-04-15 INFO : root : creating build/lib/botocore/data/swf INFO : root : creating build/lib/botocore/data/swf/2012-01-25 INFO : root : copying botocore/data/swf/2012-01-25/examples-1.json -> build/lib/botocore/data/swf/2012-01-25 INFO : root : copying botocore/data/swf/2012-01-25/paginators-1.json -> build/lib/botocore/data/swf/2012-01-25 INFO : root : copying botocore/data/swf/2012-01-25/service-2.json -> build/lib/botocore/data/swf/2012-01-25 INFO : root : creating build/lib/botocore/data/synthetics INFO : root : creating build/lib/botocore/data/synthetics/2017-10-11 INFO : root : copying botocore/data/synthetics/2017-10-11/examples-1.json -> build/lib/botocore/data/synthetics/2017-10-11 INFO : root : copying botocore/data/synthetics/2017-10-11/paginators-1.json -> build/lib/botocore/data/synthetics/2017-10-11 INFO : root : copying botocore/data/synthetics/2017-10-11/service-2.json -> build/lib/botocore/data/synthetics/2017-10-11 INFO : root : creating build/lib/botocore/data/textract INFO : root : creating build/lib/botocore/data/textract/2018-06-27 INFO : root : copying botocore/data/textract/2018-06-27/examples-1.json -> build/lib/botocore/data/textract/2018-06-27 INFO : root : copying botocore/data/textract/2018-06-27/paginators-1.json -> build/lib/botocore/data/textract/2018-06-27 INFO : root : copying botocore/data/textract/2018-06-27/service-2.json -> build/lib/botocore/data/textract/2018-06-27 INFO : root : creating build/lib/botocore/data/timestream-query INFO : root : creating build/lib/botocore/data/timestream-query/2018-11-01 INFO : root : copying botocore/data/timestream-query/2018-11-01/examples-1.json -> build/lib/botocore/data/timestream-query/2018-11-01 INFO : root : copying botocore/data/timestream-query/2018-11-01/paginators-1.json -> build/lib/botocore/data/timestream-query/2018-11-01 INFO : root : copying botocore/data/timestream-query/2018-11-01/service-2.json -> build/lib/botocore/data/timestream-query/2018-11-01 INFO : root : creating build/lib/botocore/data/timestream-write INFO : root : creating build/lib/botocore/data/timestream-write/2018-11-01 INFO : root : copying botocore/data/timestream-write/2018-11-01/examples-1.json -> build/lib/botocore/data/timestream-write/2018-11-01 INFO : root : copying botocore/data/timestream-write/2018-11-01/paginators-1.json -> build/lib/botocore/data/timestream-write/2018-11-01 INFO : root : copying botocore/data/timestream-write/2018-11-01/service-2.json -> build/lib/botocore/data/timestream-write/2018-11-01 INFO : root : creating build/lib/botocore/data/transcribe INFO : root : creating build/lib/botocore/data/transcribe/2017-10-26 INFO : root : copying botocore/data/transcribe/2017-10-26/examples-1.json -> build/lib/botocore/data/transcribe/2017-10-26 INFO : root : copying botocore/data/transcribe/2017-10-26/paginators-1.json -> build/lib/botocore/data/transcribe/2017-10-26 INFO : root : copying botocore/data/transcribe/2017-10-26/service-2.json -> build/lib/botocore/data/transcribe/2017-10-26 INFO : root : creating build/lib/botocore/data/transfer INFO : root : creating build/lib/botocore/data/transfer/2018-11-05 INFO : root : copying botocore/data/transfer/2018-11-05/examples-1.json -> build/lib/botocore/data/transfer/2018-11-05 INFO : root : copying botocore/data/transfer/2018-11-05/paginators-1.json -> build/lib/botocore/data/transfer/2018-11-05 INFO : root : copying botocore/data/transfer/2018-11-05/service-2.json -> build/lib/botocore/data/transfer/2018-11-05 INFO : root : copying botocore/data/transfer/2018-11-05/waiters-2.json -> build/lib/botocore/data/transfer/2018-11-05 INFO : root : creating build/lib/botocore/data/translate INFO : root : creating build/lib/botocore/data/translate/2017-07-01 INFO : root : copying botocore/data/translate/2017-07-01/examples-1.json -> build/lib/botocore/data/translate/2017-07-01 INFO : root : copying botocore/data/translate/2017-07-01/paginators-1.json -> build/lib/botocore/data/translate/2017-07-01 INFO : root : copying botocore/data/translate/2017-07-01/service-2.json -> build/lib/botocore/data/translate/2017-07-01 INFO : root : creating build/lib/botocore/data/voice-id INFO : root : creating build/lib/botocore/data/voice-id/2021-09-27 INFO : root : copying botocore/data/voice-id/2021-09-27/examples-1.json -> build/lib/botocore/data/voice-id/2021-09-27 INFO : root : copying botocore/data/voice-id/2021-09-27/paginators-1.json -> build/lib/botocore/data/voice-id/2021-09-27 INFO : root : copying botocore/data/voice-id/2021-09-27/service-2.json -> build/lib/botocore/data/voice-id/2021-09-27 INFO : root : creating build/lib/botocore/data/waf-regional INFO : root : creating build/lib/botocore/data/waf-regional/2016-11-28 INFO : root : copying botocore/data/waf-regional/2016-11-28/examples-1.json -> build/lib/botocore/data/waf-regional/2016-11-28 INFO : root : copying botocore/data/waf-regional/2016-11-28/paginators-1.json -> build/lib/botocore/data/waf-regional/2016-11-28 INFO : root : copying botocore/data/waf-regional/2016-11-28/service-2.json -> build/lib/botocore/data/waf-regional/2016-11-28 INFO : root : creating build/lib/botocore/data/waf INFO : root : creating build/lib/botocore/data/waf/2015-08-24 INFO : root : copying botocore/data/waf/2015-08-24/examples-1.json -> build/lib/botocore/data/waf/2015-08-24 INFO : root : copying botocore/data/waf/2015-08-24/paginators-1.json -> build/lib/botocore/data/waf/2015-08-24 INFO : root : copying botocore/data/waf/2015-08-24/service-2.json -> build/lib/botocore/data/waf/2015-08-24 INFO : root : creating build/lib/botocore/data/wafv2 INFO : root : creating build/lib/botocore/data/wafv2/2019-07-29 INFO : root : copying botocore/data/wafv2/2019-07-29/examples-1.json -> build/lib/botocore/data/wafv2/2019-07-29 INFO : root : copying botocore/data/wafv2/2019-07-29/paginators-1.json -> build/lib/botocore/data/wafv2/2019-07-29 INFO : root : copying botocore/data/wafv2/2019-07-29/service-2.json -> build/lib/botocore/data/wafv2/2019-07-29 INFO : root : creating build/lib/botocore/data/wellarchitected INFO : root : creating build/lib/botocore/data/wellarchitected/2020-03-31 INFO : root : copying botocore/data/wellarchitected/2020-03-31/examples-1.json -> build/lib/botocore/data/wellarchitected/2020-03-31 INFO : root : copying botocore/data/wellarchitected/2020-03-31/paginators-1.json -> build/lib/botocore/data/wellarchitected/2020-03-31 INFO : root : copying botocore/data/wellarchitected/2020-03-31/service-2.json -> build/lib/botocore/data/wellarchitected/2020-03-31 INFO : root : creating build/lib/botocore/data/wisdom INFO : root : creating build/lib/botocore/data/wisdom/2020-10-19 INFO : root : copying botocore/data/wisdom/2020-10-19/examples-1.json -> build/lib/botocore/data/wisdom/2020-10-19 INFO : root : copying botocore/data/wisdom/2020-10-19/paginators-1.json -> build/lib/botocore/data/wisdom/2020-10-19 INFO : root : copying botocore/data/wisdom/2020-10-19/service-2.json -> build/lib/botocore/data/wisdom/2020-10-19 INFO : root : creating build/lib/botocore/data/workdocs INFO : root : creating build/lib/botocore/data/workdocs/2016-05-01 INFO : root : copying botocore/data/workdocs/2016-05-01/examples-1.json -> build/lib/botocore/data/workdocs/2016-05-01 INFO : root : copying botocore/data/workdocs/2016-05-01/paginators-1.json -> build/lib/botocore/data/workdocs/2016-05-01 INFO : root : copying botocore/data/workdocs/2016-05-01/service-2.json -> build/lib/botocore/data/workdocs/2016-05-01 INFO : root : creating build/lib/botocore/data/worklink INFO : root : creating build/lib/botocore/data/worklink/2018-09-25 INFO : root : copying botocore/data/worklink/2018-09-25/examples-1.json -> build/lib/botocore/data/worklink/2018-09-25 INFO : root : copying botocore/data/worklink/2018-09-25/paginators-1.json -> build/lib/botocore/data/worklink/2018-09-25 INFO : root : copying botocore/data/worklink/2018-09-25/service-2.json -> build/lib/botocore/data/worklink/2018-09-25 INFO : root : creating build/lib/botocore/data/workmail INFO : root : creating build/lib/botocore/data/workmail/2017-10-01 INFO : root : copying botocore/data/workmail/2017-10-01/examples-1.json -> build/lib/botocore/data/workmail/2017-10-01 INFO : root : copying botocore/data/workmail/2017-10-01/paginators-1.json -> build/lib/botocore/data/workmail/2017-10-01 INFO : root : copying botocore/data/workmail/2017-10-01/service-2.json -> build/lib/botocore/data/workmail/2017-10-01 INFO : root : creating build/lib/botocore/data/workmailmessageflow INFO : root : creating build/lib/botocore/data/workmailmessageflow/2019-05-01 INFO : root : copying botocore/data/workmailmessageflow/2019-05-01/examples-1.json -> build/lib/botocore/data/workmailmessageflow/2019-05-01 INFO : root : copying botocore/data/workmailmessageflow/2019-05-01/paginators-1.json -> build/lib/botocore/data/workmailmessageflow/2019-05-01 INFO : root : copying botocore/data/workmailmessageflow/2019-05-01/service-2.json -> build/lib/botocore/data/workmailmessageflow/2019-05-01 INFO : root : creating build/lib/botocore/data/workspaces-web INFO : root : creating build/lib/botocore/data/workspaces-web/2020-07-08 INFO : root : copying botocore/data/workspaces-web/2020-07-08/examples-1.json -> build/lib/botocore/data/workspaces-web/2020-07-08 INFO : root : copying botocore/data/workspaces-web/2020-07-08/paginators-1.json -> build/lib/botocore/data/workspaces-web/2020-07-08 INFO : root : copying botocore/data/workspaces-web/2020-07-08/service-2.json -> build/lib/botocore/data/workspaces-web/2020-07-08 INFO : root : creating build/lib/botocore/data/workspaces INFO : root : creating build/lib/botocore/data/workspaces/2015-04-08 INFO : root : copying botocore/data/workspaces/2015-04-08/examples-1.json -> build/lib/botocore/data/workspaces/2015-04-08 INFO : root : copying botocore/data/workspaces/2015-04-08/paginators-1.json -> build/lib/botocore/data/workspaces/2015-04-08 INFO : root : copying botocore/data/workspaces/2015-04-08/service-2.json -> build/lib/botocore/data/workspaces/2015-04-08 INFO : root : creating build/lib/botocore/data/xray INFO : root : creating build/lib/botocore/data/xray/2016-04-12 INFO : root : copying botocore/data/xray/2016-04-12/examples-1.json -> build/lib/botocore/data/xray/2016-04-12 INFO : root : copying botocore/data/xray/2016-04-12/paginators-1.json -> build/lib/botocore/data/xray/2016-04-12 INFO : root : copying botocore/data/xray/2016-04-12/service-2.json -> build/lib/botocore/data/xray/2016-04-12 INFO : wheel : installing to build/bdist.linux-i686/wheel INFO : root : running install INFO : root : running install_lib INFO : root : creating build/bdist.linux-i686 INFO : root : creating build/bdist.linux-i686/wheel INFO : root : creating build/bdist.linux-i686/wheel/botocore INFO : root : creating build/bdist.linux-i686/wheel/botocore/data INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/xray INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/xray/2016-04-12 INFO : root : copying build/lib/botocore/data/xray/2016-04-12/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/xray/2016-04-12 INFO : root : copying build/lib/botocore/data/xray/2016-04-12/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/xray/2016-04-12 INFO : root : copying build/lib/botocore/data/xray/2016-04-12/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/xray/2016-04-12 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/workspaces INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/workspaces/2015-04-08 INFO : root : copying build/lib/botocore/data/workspaces/2015-04-08/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/workspaces/2015-04-08 INFO : root : copying build/lib/botocore/data/workspaces/2015-04-08/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/workspaces/2015-04-08 INFO : root : copying build/lib/botocore/data/workspaces/2015-04-08/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/workspaces/2015-04-08 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/workspaces-web INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/workspaces-web/2020-07-08 INFO : root : copying build/lib/botocore/data/workspaces-web/2020-07-08/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/workspaces-web/2020-07-08 INFO : root : copying build/lib/botocore/data/workspaces-web/2020-07-08/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/workspaces-web/2020-07-08 INFO : root : copying build/lib/botocore/data/workspaces-web/2020-07-08/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/workspaces-web/2020-07-08 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/workmailmessageflow INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/workmailmessageflow/2019-05-01 INFO : root : copying build/lib/botocore/data/workmailmessageflow/2019-05-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/workmailmessageflow/2019-05-01 INFO : root : copying build/lib/botocore/data/workmailmessageflow/2019-05-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/workmailmessageflow/2019-05-01 INFO : root : copying build/lib/botocore/data/workmailmessageflow/2019-05-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/workmailmessageflow/2019-05-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/workmail INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/workmail/2017-10-01 INFO : root : copying build/lib/botocore/data/workmail/2017-10-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/workmail/2017-10-01 INFO : root : copying build/lib/botocore/data/workmail/2017-10-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/workmail/2017-10-01 INFO : root : copying build/lib/botocore/data/workmail/2017-10-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/workmail/2017-10-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/worklink INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/worklink/2018-09-25 INFO : root : copying build/lib/botocore/data/worklink/2018-09-25/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/worklink/2018-09-25 INFO : root : copying build/lib/botocore/data/worklink/2018-09-25/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/worklink/2018-09-25 INFO : root : copying build/lib/botocore/data/worklink/2018-09-25/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/worklink/2018-09-25 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/workdocs INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/workdocs/2016-05-01 INFO : root : copying build/lib/botocore/data/workdocs/2016-05-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/workdocs/2016-05-01 INFO : root : copying build/lib/botocore/data/workdocs/2016-05-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/workdocs/2016-05-01 INFO : root : copying build/lib/botocore/data/workdocs/2016-05-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/workdocs/2016-05-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/wisdom INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/wisdom/2020-10-19 INFO : root : copying build/lib/botocore/data/wisdom/2020-10-19/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/wisdom/2020-10-19 INFO : root : copying build/lib/botocore/data/wisdom/2020-10-19/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/wisdom/2020-10-19 INFO : root : copying build/lib/botocore/data/wisdom/2020-10-19/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/wisdom/2020-10-19 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/wellarchitected INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/wellarchitected/2020-03-31 INFO : root : copying build/lib/botocore/data/wellarchitected/2020-03-31/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/wellarchitected/2020-03-31 INFO : root : copying build/lib/botocore/data/wellarchitected/2020-03-31/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/wellarchitected/2020-03-31 INFO : root : copying build/lib/botocore/data/wellarchitected/2020-03-31/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/wellarchitected/2020-03-31 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/wafv2 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/wafv2/2019-07-29 INFO : root : copying build/lib/botocore/data/wafv2/2019-07-29/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/wafv2/2019-07-29 INFO : root : copying build/lib/botocore/data/wafv2/2019-07-29/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/wafv2/2019-07-29 INFO : root : copying build/lib/botocore/data/wafv2/2019-07-29/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/wafv2/2019-07-29 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/waf INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/waf/2015-08-24 INFO : root : copying build/lib/botocore/data/waf/2015-08-24/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/waf/2015-08-24 INFO : root : copying build/lib/botocore/data/waf/2015-08-24/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/waf/2015-08-24 INFO : root : copying build/lib/botocore/data/waf/2015-08-24/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/waf/2015-08-24 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/waf-regional INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/waf-regional/2016-11-28 INFO : root : copying build/lib/botocore/data/waf-regional/2016-11-28/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/waf-regional/2016-11-28 INFO : root : copying build/lib/botocore/data/waf-regional/2016-11-28/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/waf-regional/2016-11-28 INFO : root : copying build/lib/botocore/data/waf-regional/2016-11-28/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/waf-regional/2016-11-28 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/voice-id INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/voice-id/2021-09-27 INFO : root : copying build/lib/botocore/data/voice-id/2021-09-27/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/voice-id/2021-09-27 INFO : root : copying build/lib/botocore/data/voice-id/2021-09-27/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/voice-id/2021-09-27 INFO : root : copying build/lib/botocore/data/voice-id/2021-09-27/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/voice-id/2021-09-27 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/translate INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/translate/2017-07-01 INFO : root : copying build/lib/botocore/data/translate/2017-07-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/translate/2017-07-01 INFO : root : copying build/lib/botocore/data/translate/2017-07-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/translate/2017-07-01 INFO : root : copying build/lib/botocore/data/translate/2017-07-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/translate/2017-07-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/transfer INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/transfer/2018-11-05 INFO : root : copying build/lib/botocore/data/transfer/2018-11-05/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/transfer/2018-11-05 INFO : root : copying build/lib/botocore/data/transfer/2018-11-05/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/transfer/2018-11-05 INFO : root : copying build/lib/botocore/data/transfer/2018-11-05/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/transfer/2018-11-05 INFO : root : copying build/lib/botocore/data/transfer/2018-11-05/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/transfer/2018-11-05 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/transcribe INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/transcribe/2017-10-26 INFO : root : copying build/lib/botocore/data/transcribe/2017-10-26/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/transcribe/2017-10-26 INFO : root : copying build/lib/botocore/data/transcribe/2017-10-26/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/transcribe/2017-10-26 INFO : root : copying build/lib/botocore/data/transcribe/2017-10-26/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/transcribe/2017-10-26 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/timestream-write INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/timestream-write/2018-11-01 INFO : root : copying build/lib/botocore/data/timestream-write/2018-11-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/timestream-write/2018-11-01 INFO : root : copying build/lib/botocore/data/timestream-write/2018-11-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/timestream-write/2018-11-01 INFO : root : copying build/lib/botocore/data/timestream-write/2018-11-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/timestream-write/2018-11-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/timestream-query INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/timestream-query/2018-11-01 INFO : root : copying build/lib/botocore/data/timestream-query/2018-11-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/timestream-query/2018-11-01 INFO : root : copying build/lib/botocore/data/timestream-query/2018-11-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/timestream-query/2018-11-01 INFO : root : copying build/lib/botocore/data/timestream-query/2018-11-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/timestream-query/2018-11-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/textract INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/textract/2018-06-27 INFO : root : copying build/lib/botocore/data/textract/2018-06-27/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/textract/2018-06-27 INFO : root : copying build/lib/botocore/data/textract/2018-06-27/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/textract/2018-06-27 INFO : root : copying build/lib/botocore/data/textract/2018-06-27/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/textract/2018-06-27 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/synthetics INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/synthetics/2017-10-11 INFO : root : copying build/lib/botocore/data/synthetics/2017-10-11/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/synthetics/2017-10-11 INFO : root : copying build/lib/botocore/data/synthetics/2017-10-11/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/synthetics/2017-10-11 INFO : root : copying build/lib/botocore/data/synthetics/2017-10-11/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/synthetics/2017-10-11 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/swf INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/swf/2012-01-25 INFO : root : copying build/lib/botocore/data/swf/2012-01-25/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/swf/2012-01-25 INFO : root : copying build/lib/botocore/data/swf/2012-01-25/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/swf/2012-01-25 INFO : root : copying build/lib/botocore/data/swf/2012-01-25/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/swf/2012-01-25 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/support INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/support/2013-04-15 INFO : root : copying build/lib/botocore/data/support/2013-04-15/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/support/2013-04-15 INFO : root : copying build/lib/botocore/data/support/2013-04-15/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/support/2013-04-15 INFO : root : copying build/lib/botocore/data/support/2013-04-15/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/support/2013-04-15 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/support-app INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/support-app/2021-08-20 INFO : root : copying build/lib/botocore/data/support-app/2021-08-20/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/support-app/2021-08-20 INFO : root : copying build/lib/botocore/data/support-app/2021-08-20/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/support-app/2021-08-20 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/sts INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/sts/2011-06-15 INFO : root : copying build/lib/botocore/data/sts/2011-06-15/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/sts/2011-06-15 INFO : root : copying build/lib/botocore/data/sts/2011-06-15/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/sts/2011-06-15 INFO : root : copying build/lib/botocore/data/sts/2011-06-15/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/sts/2011-06-15 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/storagegateway INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/storagegateway/2013-06-30 INFO : root : copying build/lib/botocore/data/storagegateway/2013-06-30/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/storagegateway/2013-06-30 INFO : root : copying build/lib/botocore/data/storagegateway/2013-06-30/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/storagegateway/2013-06-30 INFO : root : copying build/lib/botocore/data/storagegateway/2013-06-30/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/storagegateway/2013-06-30 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/stepfunctions INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/stepfunctions/2016-11-23 INFO : root : copying build/lib/botocore/data/stepfunctions/2016-11-23/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/stepfunctions/2016-11-23 INFO : root : copying build/lib/botocore/data/stepfunctions/2016-11-23/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/stepfunctions/2016-11-23 INFO : root : copying build/lib/botocore/data/stepfunctions/2016-11-23/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/stepfunctions/2016-11-23 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/sso INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/sso/2019-06-10 INFO : root : copying build/lib/botocore/data/sso/2019-06-10/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/sso/2019-06-10 INFO : root : copying build/lib/botocore/data/sso/2019-06-10/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/sso/2019-06-10 INFO : root : copying build/lib/botocore/data/sso/2019-06-10/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/sso/2019-06-10 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/sso-oidc INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/sso-oidc/2019-06-10 INFO : root : copying build/lib/botocore/data/sso-oidc/2019-06-10/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/sso-oidc/2019-06-10 INFO : root : copying build/lib/botocore/data/sso-oidc/2019-06-10/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/sso-oidc/2019-06-10 INFO : root : copying build/lib/botocore/data/sso-oidc/2019-06-10/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/sso-oidc/2019-06-10 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/sso-admin INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/sso-admin/2020-07-20 INFO : root : copying build/lib/botocore/data/sso-admin/2020-07-20/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/sso-admin/2020-07-20 INFO : root : copying build/lib/botocore/data/sso-admin/2020-07-20/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/sso-admin/2020-07-20 INFO : root : copying build/lib/botocore/data/sso-admin/2020-07-20/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/sso-admin/2020-07-20 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ssm INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ssm/2014-11-06 INFO : root : copying build/lib/botocore/data/ssm/2014-11-06/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/ssm/2014-11-06 INFO : root : copying build/lib/botocore/data/ssm/2014-11-06/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/ssm/2014-11-06 INFO : root : copying build/lib/botocore/data/ssm/2014-11-06/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/ssm/2014-11-06 INFO : root : copying build/lib/botocore/data/ssm/2014-11-06/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/ssm/2014-11-06 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ssm-incidents INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ssm-incidents/2018-05-10 INFO : root : copying build/lib/botocore/data/ssm-incidents/2018-05-10/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/ssm-incidents/2018-05-10 INFO : root : copying build/lib/botocore/data/ssm-incidents/2018-05-10/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/ssm-incidents/2018-05-10 INFO : root : copying build/lib/botocore/data/ssm-incidents/2018-05-10/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/ssm-incidents/2018-05-10 INFO : root : copying build/lib/botocore/data/ssm-incidents/2018-05-10/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/ssm-incidents/2018-05-10 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ssm-contacts INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ssm-contacts/2021-05-03 INFO : root : copying build/lib/botocore/data/ssm-contacts/2021-05-03/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/ssm-contacts/2021-05-03 INFO : root : copying build/lib/botocore/data/ssm-contacts/2021-05-03/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/ssm-contacts/2021-05-03 INFO : root : copying build/lib/botocore/data/ssm-contacts/2021-05-03/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/ssm-contacts/2021-05-03 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/sqs INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/sqs/2012-11-05 INFO : root : copying build/lib/botocore/data/sqs/2012-11-05/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/sqs/2012-11-05 INFO : root : copying build/lib/botocore/data/sqs/2012-11-05/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/sqs/2012-11-05 INFO : root : copying build/lib/botocore/data/sqs/2012-11-05/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/sqs/2012-11-05 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/sns INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/sns/2010-03-31 INFO : root : copying build/lib/botocore/data/sns/2010-03-31/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/sns/2010-03-31 INFO : root : copying build/lib/botocore/data/sns/2010-03-31/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/sns/2010-03-31 INFO : root : copying build/lib/botocore/data/sns/2010-03-31/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/sns/2010-03-31 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/snowball INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/snowball/2016-06-30 INFO : root : copying build/lib/botocore/data/snowball/2016-06-30/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/snowball/2016-06-30 INFO : root : copying build/lib/botocore/data/snowball/2016-06-30/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/snowball/2016-06-30 INFO : root : copying build/lib/botocore/data/snowball/2016-06-30/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/snowball/2016-06-30 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/snow-device-management INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/snow-device-management/2021-08-04 INFO : root : copying build/lib/botocore/data/snow-device-management/2021-08-04/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/snow-device-management/2021-08-04 INFO : root : copying build/lib/botocore/data/snow-device-management/2021-08-04/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/snow-device-management/2021-08-04 INFO : root : copying build/lib/botocore/data/snow-device-management/2021-08-04/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/snow-device-management/2021-08-04 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/sms INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/sms/2016-10-24 INFO : root : copying build/lib/botocore/data/sms/2016-10-24/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/sms/2016-10-24 INFO : root : copying build/lib/botocore/data/sms/2016-10-24/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/sms/2016-10-24 INFO : root : copying build/lib/botocore/data/sms/2016-10-24/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/sms/2016-10-24 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/sms-voice INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/sms-voice/2018-09-05 INFO : root : copying build/lib/botocore/data/sms-voice/2018-09-05/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/sms-voice/2018-09-05 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/signer INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/signer/2017-08-25 INFO : root : copying build/lib/botocore/data/signer/2017-08-25/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/signer/2017-08-25 INFO : root : copying build/lib/botocore/data/signer/2017-08-25/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/signer/2017-08-25 INFO : root : copying build/lib/botocore/data/signer/2017-08-25/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/signer/2017-08-25 INFO : root : copying build/lib/botocore/data/signer/2017-08-25/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/signer/2017-08-25 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/shield INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/shield/2016-06-02 INFO : root : copying build/lib/botocore/data/shield/2016-06-02/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/shield/2016-06-02 INFO : root : copying build/lib/botocore/data/shield/2016-06-02/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/shield/2016-06-02 INFO : root : copying build/lib/botocore/data/shield/2016-06-02/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/shield/2016-06-02 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/sesv2 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/sesv2/2019-09-27 INFO : root : copying build/lib/botocore/data/sesv2/2019-09-27/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/sesv2/2019-09-27 INFO : root : copying build/lib/botocore/data/sesv2/2019-09-27/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/sesv2/2019-09-27 INFO : root : copying build/lib/botocore/data/sesv2/2019-09-27/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/sesv2/2019-09-27 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ses INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ses/2010-12-01 INFO : root : copying build/lib/botocore/data/ses/2010-12-01/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/ses/2010-12-01 INFO : root : copying build/lib/botocore/data/ses/2010-12-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/ses/2010-12-01 INFO : root : copying build/lib/botocore/data/ses/2010-12-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/ses/2010-12-01 INFO : root : copying build/lib/botocore/data/ses/2010-12-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/ses/2010-12-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/servicediscovery INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/servicediscovery/2017-03-14 INFO : root : copying build/lib/botocore/data/servicediscovery/2017-03-14/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/servicediscovery/2017-03-14 INFO : root : copying build/lib/botocore/data/servicediscovery/2017-03-14/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/servicediscovery/2017-03-14 INFO : root : copying build/lib/botocore/data/servicediscovery/2017-03-14/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/servicediscovery/2017-03-14 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/servicecatalog INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/servicecatalog/2015-12-10 INFO : root : copying build/lib/botocore/data/servicecatalog/2015-12-10/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/servicecatalog/2015-12-10 INFO : root : copying build/lib/botocore/data/servicecatalog/2015-12-10/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/servicecatalog/2015-12-10 INFO : root : copying build/lib/botocore/data/servicecatalog/2015-12-10/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/servicecatalog/2015-12-10 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/servicecatalog-appregistry INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/servicecatalog-appregistry/2020-06-24 INFO : root : copying build/lib/botocore/data/servicecatalog-appregistry/2020-06-24/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/servicecatalog-appregistry/2020-06-24 INFO : root : copying build/lib/botocore/data/servicecatalog-appregistry/2020-06-24/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/servicecatalog-appregistry/2020-06-24 INFO : root : copying build/lib/botocore/data/servicecatalog-appregistry/2020-06-24/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/servicecatalog-appregistry/2020-06-24 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/service-quotas INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/service-quotas/2019-06-24 INFO : root : copying build/lib/botocore/data/service-quotas/2019-06-24/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/service-quotas/2019-06-24 INFO : root : copying build/lib/botocore/data/service-quotas/2019-06-24/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/service-quotas/2019-06-24 INFO : root : copying build/lib/botocore/data/service-quotas/2019-06-24/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/service-quotas/2019-06-24 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/serverlessrepo INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/serverlessrepo/2017-09-08 INFO : root : copying build/lib/botocore/data/serverlessrepo/2017-09-08/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/serverlessrepo/2017-09-08 INFO : root : copying build/lib/botocore/data/serverlessrepo/2017-09-08/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/serverlessrepo/2017-09-08 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/securityhub INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/securityhub/2018-10-26 INFO : root : copying build/lib/botocore/data/securityhub/2018-10-26/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/securityhub/2018-10-26 INFO : root : copying build/lib/botocore/data/securityhub/2018-10-26/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/securityhub/2018-10-26 INFO : root : copying build/lib/botocore/data/securityhub/2018-10-26/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/securityhub/2018-10-26 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/secretsmanager INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/secretsmanager/2017-10-17 INFO : root : copying build/lib/botocore/data/secretsmanager/2017-10-17/service-2.sdk-extras.json -> build/bdist.linux-i686/wheel/botocore/data/secretsmanager/2017-10-17 INFO : root : copying build/lib/botocore/data/secretsmanager/2017-10-17/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/secretsmanager/2017-10-17 INFO : root : copying build/lib/botocore/data/secretsmanager/2017-10-17/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/secretsmanager/2017-10-17 INFO : root : copying build/lib/botocore/data/secretsmanager/2017-10-17/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/secretsmanager/2017-10-17 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/sdb INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/sdb/2009-04-15 INFO : root : copying build/lib/botocore/data/sdb/2009-04-15/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/sdb/2009-04-15 INFO : root : copying build/lib/botocore/data/sdb/2009-04-15/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/sdb/2009-04-15 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/schemas INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/schemas/2019-12-02 INFO : root : copying build/lib/botocore/data/schemas/2019-12-02/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/schemas/2019-12-02 INFO : root : copying build/lib/botocore/data/schemas/2019-12-02/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/schemas/2019-12-02 INFO : root : copying build/lib/botocore/data/schemas/2019-12-02/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/schemas/2019-12-02 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/savingsplans INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/savingsplans/2019-06-28 INFO : root : copying build/lib/botocore/data/savingsplans/2019-06-28/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/savingsplans/2019-06-28 INFO : root : copying build/lib/botocore/data/savingsplans/2019-06-28/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/savingsplans/2019-06-28 INFO : root : copying build/lib/botocore/data/savingsplans/2019-06-28/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/savingsplans/2019-06-28 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/sagemaker INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/sagemaker/2017-07-24 INFO : root : copying build/lib/botocore/data/sagemaker/2017-07-24/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/sagemaker/2017-07-24 INFO : root : copying build/lib/botocore/data/sagemaker/2017-07-24/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/sagemaker/2017-07-24 INFO : root : copying build/lib/botocore/data/sagemaker/2017-07-24/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/sagemaker/2017-07-24 INFO : root : copying build/lib/botocore/data/sagemaker/2017-07-24/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/sagemaker/2017-07-24 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/sagemaker-runtime INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/sagemaker-runtime/2017-05-13 INFO : root : copying build/lib/botocore/data/sagemaker-runtime/2017-05-13/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/sagemaker-runtime/2017-05-13 INFO : root : copying build/lib/botocore/data/sagemaker-runtime/2017-05-13/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/sagemaker-runtime/2017-05-13 INFO : root : copying build/lib/botocore/data/sagemaker-runtime/2017-05-13/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/sagemaker-runtime/2017-05-13 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/sagemaker-featurestore-runtime INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/sagemaker-featurestore-runtime/2020-07-01 INFO : root : copying build/lib/botocore/data/sagemaker-featurestore-runtime/2020-07-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/sagemaker-featurestore-runtime/2020-07-01 INFO : root : copying build/lib/botocore/data/sagemaker-featurestore-runtime/2020-07-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/sagemaker-featurestore-runtime/2020-07-01 INFO : root : copying build/lib/botocore/data/sagemaker-featurestore-runtime/2020-07-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/sagemaker-featurestore-runtime/2020-07-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/sagemaker-edge INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/sagemaker-edge/2020-09-23 INFO : root : copying build/lib/botocore/data/sagemaker-edge/2020-09-23/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/sagemaker-edge/2020-09-23 INFO : root : copying build/lib/botocore/data/sagemaker-edge/2020-09-23/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/sagemaker-edge/2020-09-23 INFO : root : copying build/lib/botocore/data/sagemaker-edge/2020-09-23/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/sagemaker-edge/2020-09-23 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/sagemaker-a2i-runtime INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/sagemaker-a2i-runtime/2019-11-07 INFO : root : copying build/lib/botocore/data/sagemaker-a2i-runtime/2019-11-07/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/sagemaker-a2i-runtime/2019-11-07 INFO : root : copying build/lib/botocore/data/sagemaker-a2i-runtime/2019-11-07/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/sagemaker-a2i-runtime/2019-11-07 INFO : root : copying build/lib/botocore/data/sagemaker-a2i-runtime/2019-11-07/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/sagemaker-a2i-runtime/2019-11-07 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/s3outposts INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/s3outposts/2017-07-25 INFO : root : copying build/lib/botocore/data/s3outposts/2017-07-25/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/s3outposts/2017-07-25 INFO : root : copying build/lib/botocore/data/s3outposts/2017-07-25/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/s3outposts/2017-07-25 INFO : root : copying build/lib/botocore/data/s3outposts/2017-07-25/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/s3outposts/2017-07-25 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/s3control INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/s3control/2018-08-20 INFO : root : copying build/lib/botocore/data/s3control/2018-08-20/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/s3control/2018-08-20 INFO : root : copying build/lib/botocore/data/s3control/2018-08-20/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/s3control/2018-08-20 INFO : root : copying build/lib/botocore/data/s3control/2018-08-20/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/s3control/2018-08-20 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/s3 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/s3/2006-03-01 INFO : root : copying build/lib/botocore/data/s3/2006-03-01/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/s3/2006-03-01 INFO : root : copying build/lib/botocore/data/s3/2006-03-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/s3/2006-03-01 INFO : root : copying build/lib/botocore/data/s3/2006-03-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/s3/2006-03-01 INFO : root : copying build/lib/botocore/data/s3/2006-03-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/s3/2006-03-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/rum INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/rum/2018-05-10 INFO : root : copying build/lib/botocore/data/rum/2018-05-10/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/rum/2018-05-10 INFO : root : copying build/lib/botocore/data/rum/2018-05-10/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/rum/2018-05-10 INFO : root : copying build/lib/botocore/data/rum/2018-05-10/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/rum/2018-05-10 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/route53resolver INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/route53resolver/2018-04-01 INFO : root : copying build/lib/botocore/data/route53resolver/2018-04-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/route53resolver/2018-04-01 INFO : root : copying build/lib/botocore/data/route53resolver/2018-04-01/paginators-1.sdk-extras.json -> build/bdist.linux-i686/wheel/botocore/data/route53resolver/2018-04-01 INFO : root : copying build/lib/botocore/data/route53resolver/2018-04-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/route53resolver/2018-04-01 INFO : root : copying build/lib/botocore/data/route53resolver/2018-04-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/route53resolver/2018-04-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/route53domains INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/route53domains/2014-05-15 INFO : root : copying build/lib/botocore/data/route53domains/2014-05-15/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/route53domains/2014-05-15 INFO : root : copying build/lib/botocore/data/route53domains/2014-05-15/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/route53domains/2014-05-15 INFO : root : copying build/lib/botocore/data/route53domains/2014-05-15/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/route53domains/2014-05-15 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/route53 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/route53/2013-04-01 INFO : root : copying build/lib/botocore/data/route53/2013-04-01/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/route53/2013-04-01 INFO : root : copying build/lib/botocore/data/route53/2013-04-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/route53/2013-04-01 INFO : root : copying build/lib/botocore/data/route53/2013-04-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/route53/2013-04-01 INFO : root : copying build/lib/botocore/data/route53/2013-04-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/route53/2013-04-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/route53-recovery-readiness INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/route53-recovery-readiness/2019-12-02 INFO : root : copying build/lib/botocore/data/route53-recovery-readiness/2019-12-02/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/route53-recovery-readiness/2019-12-02 INFO : root : copying build/lib/botocore/data/route53-recovery-readiness/2019-12-02/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/route53-recovery-readiness/2019-12-02 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/route53-recovery-control-config INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/route53-recovery-control-config/2020-11-02 INFO : root : copying build/lib/botocore/data/route53-recovery-control-config/2020-11-02/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/route53-recovery-control-config/2020-11-02 INFO : root : copying build/lib/botocore/data/route53-recovery-control-config/2020-11-02/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/route53-recovery-control-config/2020-11-02 INFO : root : copying build/lib/botocore/data/route53-recovery-control-config/2020-11-02/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/route53-recovery-control-config/2020-11-02 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/route53-recovery-cluster INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/route53-recovery-cluster/2019-12-02 INFO : root : copying build/lib/botocore/data/route53-recovery-cluster/2019-12-02/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/route53-recovery-cluster/2019-12-02 INFO : root : copying build/lib/botocore/data/route53-recovery-cluster/2019-12-02/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/route53-recovery-cluster/2019-12-02 INFO : root : copying build/lib/botocore/data/route53-recovery-cluster/2019-12-02/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/route53-recovery-cluster/2019-12-02 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/rolesanywhere INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/rolesanywhere/2018-05-10 INFO : root : copying build/lib/botocore/data/rolesanywhere/2018-05-10/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/rolesanywhere/2018-05-10 INFO : root : copying build/lib/botocore/data/rolesanywhere/2018-05-10/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/rolesanywhere/2018-05-10 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/robomaker INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/robomaker/2018-06-29 INFO : root : copying build/lib/botocore/data/robomaker/2018-06-29/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/robomaker/2018-06-29 INFO : root : copying build/lib/botocore/data/robomaker/2018-06-29/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/robomaker/2018-06-29 INFO : root : copying build/lib/botocore/data/robomaker/2018-06-29/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/robomaker/2018-06-29 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/resourcegroupstaggingapi INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/resourcegroupstaggingapi/2017-01-26 INFO : root : copying build/lib/botocore/data/resourcegroupstaggingapi/2017-01-26/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/resourcegroupstaggingapi/2017-01-26 INFO : root : copying build/lib/botocore/data/resourcegroupstaggingapi/2017-01-26/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/resourcegroupstaggingapi/2017-01-26 INFO : root : copying build/lib/botocore/data/resourcegroupstaggingapi/2017-01-26/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/resourcegroupstaggingapi/2017-01-26 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/resource-groups INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/resource-groups/2017-11-27 INFO : root : copying build/lib/botocore/data/resource-groups/2017-11-27/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/resource-groups/2017-11-27 INFO : root : copying build/lib/botocore/data/resource-groups/2017-11-27/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/resource-groups/2017-11-27 INFO : root : copying build/lib/botocore/data/resource-groups/2017-11-27/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/resource-groups/2017-11-27 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/resiliencehub INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/resiliencehub/2020-04-30 INFO : root : copying build/lib/botocore/data/resiliencehub/2020-04-30/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/resiliencehub/2020-04-30 INFO : root : copying build/lib/botocore/data/resiliencehub/2020-04-30/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/resiliencehub/2020-04-30 INFO : root : copying build/lib/botocore/data/resiliencehub/2020-04-30/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/resiliencehub/2020-04-30 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/rekognition INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/rekognition/2016-06-27 INFO : root : copying build/lib/botocore/data/rekognition/2016-06-27/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/rekognition/2016-06-27 INFO : root : copying build/lib/botocore/data/rekognition/2016-06-27/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/rekognition/2016-06-27 INFO : root : copying build/lib/botocore/data/rekognition/2016-06-27/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/rekognition/2016-06-27 INFO : root : copying build/lib/botocore/data/rekognition/2016-06-27/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/rekognition/2016-06-27 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/redshift INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/redshift/2012-12-01 INFO : root : copying build/lib/botocore/data/redshift/2012-12-01/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/redshift/2012-12-01 INFO : root : copying build/lib/botocore/data/redshift/2012-12-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/redshift/2012-12-01 INFO : root : copying build/lib/botocore/data/redshift/2012-12-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/redshift/2012-12-01 INFO : root : copying build/lib/botocore/data/redshift/2012-12-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/redshift/2012-12-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/redshift-serverless INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/redshift-serverless/2021-04-21 INFO : root : copying build/lib/botocore/data/redshift-serverless/2021-04-21/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/redshift-serverless/2021-04-21 INFO : root : copying build/lib/botocore/data/redshift-serverless/2021-04-21/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/redshift-serverless/2021-04-21 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/redshift-data INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/redshift-data/2019-12-20 INFO : root : copying build/lib/botocore/data/redshift-data/2019-12-20/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/redshift-data/2019-12-20 INFO : root : copying build/lib/botocore/data/redshift-data/2019-12-20/paginators-1.sdk-extras.json -> build/bdist.linux-i686/wheel/botocore/data/redshift-data/2019-12-20 INFO : root : copying build/lib/botocore/data/redshift-data/2019-12-20/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/redshift-data/2019-12-20 INFO : root : copying build/lib/botocore/data/redshift-data/2019-12-20/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/redshift-data/2019-12-20 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/rds INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/rds/2014-10-31 INFO : root : copying build/lib/botocore/data/rds/2014-10-31/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/rds/2014-10-31 INFO : root : copying build/lib/botocore/data/rds/2014-10-31/service-2.sdk-extras.json -> build/bdist.linux-i686/wheel/botocore/data/rds/2014-10-31 INFO : root : copying build/lib/botocore/data/rds/2014-10-31/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/rds/2014-10-31 INFO : root : copying build/lib/botocore/data/rds/2014-10-31/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/rds/2014-10-31 INFO : root : copying build/lib/botocore/data/rds/2014-10-31/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/rds/2014-10-31 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/rds/2014-09-01 INFO : root : copying build/lib/botocore/data/rds/2014-09-01/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/rds/2014-09-01 INFO : root : copying build/lib/botocore/data/rds/2014-09-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/rds/2014-09-01 INFO : root : copying build/lib/botocore/data/rds/2014-09-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/rds/2014-09-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/rds-data INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/rds-data/2018-08-01 INFO : root : copying build/lib/botocore/data/rds-data/2018-08-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/rds-data/2018-08-01 INFO : root : copying build/lib/botocore/data/rds-data/2018-08-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/rds-data/2018-08-01 INFO : root : copying build/lib/botocore/data/rds-data/2018-08-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/rds-data/2018-08-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/rbin INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/rbin/2021-06-15 INFO : root : copying build/lib/botocore/data/rbin/2021-06-15/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/rbin/2021-06-15 INFO : root : copying build/lib/botocore/data/rbin/2021-06-15/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/rbin/2021-06-15 INFO : root : copying build/lib/botocore/data/rbin/2021-06-15/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/rbin/2021-06-15 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ram INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ram/2018-01-04 INFO : root : copying build/lib/botocore/data/ram/2018-01-04/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/ram/2018-01-04 INFO : root : copying build/lib/botocore/data/ram/2018-01-04/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/ram/2018-01-04 INFO : root : copying build/lib/botocore/data/ram/2018-01-04/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/ram/2018-01-04 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/quicksight INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/quicksight/2018-04-01 INFO : root : copying build/lib/botocore/data/quicksight/2018-04-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/quicksight/2018-04-01 INFO : root : copying build/lib/botocore/data/quicksight/2018-04-01/paginators-1.sdk-extras.json -> build/bdist.linux-i686/wheel/botocore/data/quicksight/2018-04-01 INFO : root : copying build/lib/botocore/data/quicksight/2018-04-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/quicksight/2018-04-01 INFO : root : copying build/lib/botocore/data/quicksight/2018-04-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/quicksight/2018-04-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/qldb INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/qldb/2019-01-02 INFO : root : copying build/lib/botocore/data/qldb/2019-01-02/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/qldb/2019-01-02 INFO : root : copying build/lib/botocore/data/qldb/2019-01-02/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/qldb/2019-01-02 INFO : root : copying build/lib/botocore/data/qldb/2019-01-02/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/qldb/2019-01-02 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/qldb-session INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/qldb-session/2019-07-11 INFO : root : copying build/lib/botocore/data/qldb-session/2019-07-11/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/qldb-session/2019-07-11 INFO : root : copying build/lib/botocore/data/qldb-session/2019-07-11/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/qldb-session/2019-07-11 INFO : root : copying build/lib/botocore/data/qldb-session/2019-07-11/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/qldb-session/2019-07-11 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/proton INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/proton/2020-07-20 INFO : root : copying build/lib/botocore/data/proton/2020-07-20/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/proton/2020-07-20 INFO : root : copying build/lib/botocore/data/proton/2020-07-20/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/proton/2020-07-20 INFO : root : copying build/lib/botocore/data/proton/2020-07-20/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/proton/2020-07-20 INFO : root : copying build/lib/botocore/data/proton/2020-07-20/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/proton/2020-07-20 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/privatenetworks INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/privatenetworks/2021-12-03 INFO : root : copying build/lib/botocore/data/privatenetworks/2021-12-03/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/privatenetworks/2021-12-03 INFO : root : copying build/lib/botocore/data/privatenetworks/2021-12-03/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/privatenetworks/2021-12-03 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/pricing INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/pricing/2017-10-15 INFO : root : copying build/lib/botocore/data/pricing/2017-10-15/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/pricing/2017-10-15 INFO : root : copying build/lib/botocore/data/pricing/2017-10-15/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/pricing/2017-10-15 INFO : root : copying build/lib/botocore/data/pricing/2017-10-15/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/pricing/2017-10-15 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/polly INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/polly/2016-06-10 INFO : root : copying build/lib/botocore/data/polly/2016-06-10/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/polly/2016-06-10 INFO : root : copying build/lib/botocore/data/polly/2016-06-10/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/polly/2016-06-10 INFO : root : copying build/lib/botocore/data/polly/2016-06-10/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/polly/2016-06-10 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/pinpoint INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/pinpoint/2016-12-01 INFO : root : copying build/lib/botocore/data/pinpoint/2016-12-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/pinpoint/2016-12-01 INFO : root : copying build/lib/botocore/data/pinpoint/2016-12-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/pinpoint/2016-12-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/pinpoint-sms-voice INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/pinpoint-sms-voice/2018-09-05 INFO : root : copying build/lib/botocore/data/pinpoint-sms-voice/2018-09-05/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/pinpoint-sms-voice/2018-09-05 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/pinpoint-sms-voice-v2 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/pinpoint-sms-voice-v2/2022-03-31 INFO : root : copying build/lib/botocore/data/pinpoint-sms-voice-v2/2022-03-31/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/pinpoint-sms-voice-v2/2022-03-31 INFO : root : copying build/lib/botocore/data/pinpoint-sms-voice-v2/2022-03-31/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/pinpoint-sms-voice-v2/2022-03-31 INFO : root : copying build/lib/botocore/data/pinpoint-sms-voice-v2/2022-03-31/paginators-1.sdk-extras.json -> build/bdist.linux-i686/wheel/botocore/data/pinpoint-sms-voice-v2/2022-03-31 INFO : root : copying build/lib/botocore/data/pinpoint-sms-voice-v2/2022-03-31/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/pinpoint-sms-voice-v2/2022-03-31 INFO : root : copying build/lib/botocore/data/pinpoint-sms-voice-v2/2022-03-31/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/pinpoint-sms-voice-v2/2022-03-31 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/pinpoint-email INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/pinpoint-email/2018-07-26 INFO : root : copying build/lib/botocore/data/pinpoint-email/2018-07-26/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/pinpoint-email/2018-07-26 INFO : root : copying build/lib/botocore/data/pinpoint-email/2018-07-26/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/pinpoint-email/2018-07-26 INFO : root : copying build/lib/botocore/data/pinpoint-email/2018-07-26/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/pinpoint-email/2018-07-26 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/pi INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/pi/2018-02-27 INFO : root : copying build/lib/botocore/data/pi/2018-02-27/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/pi/2018-02-27 INFO : root : copying build/lib/botocore/data/pi/2018-02-27/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/pi/2018-02-27 INFO : root : copying build/lib/botocore/data/pi/2018-02-27/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/pi/2018-02-27 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/personalize INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/personalize/2018-05-22 INFO : root : copying build/lib/botocore/data/personalize/2018-05-22/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/personalize/2018-05-22 INFO : root : copying build/lib/botocore/data/personalize/2018-05-22/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/personalize/2018-05-22 INFO : root : copying build/lib/botocore/data/personalize/2018-05-22/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/personalize/2018-05-22 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/personalize-runtime INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/personalize-runtime/2018-05-22 INFO : root : copying build/lib/botocore/data/personalize-runtime/2018-05-22/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/personalize-runtime/2018-05-22 INFO : root : copying build/lib/botocore/data/personalize-runtime/2018-05-22/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/personalize-runtime/2018-05-22 INFO : root : copying build/lib/botocore/data/personalize-runtime/2018-05-22/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/personalize-runtime/2018-05-22 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/personalize-events INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/personalize-events/2018-03-22 INFO : root : copying build/lib/botocore/data/personalize-events/2018-03-22/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/personalize-events/2018-03-22 INFO : root : copying build/lib/botocore/data/personalize-events/2018-03-22/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/personalize-events/2018-03-22 INFO : root : copying build/lib/botocore/data/personalize-events/2018-03-22/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/personalize-events/2018-03-22 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/panorama INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/panorama/2019-07-24 INFO : root : copying build/lib/botocore/data/panorama/2019-07-24/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/panorama/2019-07-24 INFO : root : copying build/lib/botocore/data/panorama/2019-07-24/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/panorama/2019-07-24 INFO : root : copying build/lib/botocore/data/panorama/2019-07-24/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/panorama/2019-07-24 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/outposts INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/outposts/2019-12-03 INFO : root : copying build/lib/botocore/data/outposts/2019-12-03/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/outposts/2019-12-03 INFO : root : copying build/lib/botocore/data/outposts/2019-12-03/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/outposts/2019-12-03 INFO : root : copying build/lib/botocore/data/outposts/2019-12-03/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/outposts/2019-12-03 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/organizations INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/organizations/2016-11-28 INFO : root : copying build/lib/botocore/data/organizations/2016-11-28/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/organizations/2016-11-28 INFO : root : copying build/lib/botocore/data/organizations/2016-11-28/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/organizations/2016-11-28 INFO : root : copying build/lib/botocore/data/organizations/2016-11-28/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/organizations/2016-11-28 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/opsworkscm INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/opsworkscm/2016-11-01 INFO : root : copying build/lib/botocore/data/opsworkscm/2016-11-01/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/opsworkscm/2016-11-01 INFO : root : copying build/lib/botocore/data/opsworkscm/2016-11-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/opsworkscm/2016-11-01 INFO : root : copying build/lib/botocore/data/opsworkscm/2016-11-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/opsworkscm/2016-11-01 INFO : root : copying build/lib/botocore/data/opsworkscm/2016-11-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/opsworkscm/2016-11-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/opsworks INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/opsworks/2013-02-18 INFO : root : copying build/lib/botocore/data/opsworks/2013-02-18/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/opsworks/2013-02-18 INFO : root : copying build/lib/botocore/data/opsworks/2013-02-18/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/opsworks/2013-02-18 INFO : root : copying build/lib/botocore/data/opsworks/2013-02-18/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/opsworks/2013-02-18 INFO : root : copying build/lib/botocore/data/opsworks/2013-02-18/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/opsworks/2013-02-18 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/opensearch INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/opensearch/2021-01-01 INFO : root : copying build/lib/botocore/data/opensearch/2021-01-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/opensearch/2021-01-01 INFO : root : copying build/lib/botocore/data/opensearch/2021-01-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/opensearch/2021-01-01 INFO : root : copying build/lib/botocore/data/opensearch/2021-01-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/opensearch/2021-01-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/nimble INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/nimble/2020-08-01 INFO : root : copying build/lib/botocore/data/nimble/2020-08-01/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/nimble/2020-08-01 INFO : root : copying build/lib/botocore/data/nimble/2020-08-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/nimble/2020-08-01 INFO : root : copying build/lib/botocore/data/nimble/2020-08-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/nimble/2020-08-01 INFO : root : copying build/lib/botocore/data/nimble/2020-08-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/nimble/2020-08-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/networkmanager INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/networkmanager/2019-07-05 INFO : root : copying build/lib/botocore/data/networkmanager/2019-07-05/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/networkmanager/2019-07-05 INFO : root : copying build/lib/botocore/data/networkmanager/2019-07-05/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/networkmanager/2019-07-05 INFO : root : copying build/lib/botocore/data/networkmanager/2019-07-05/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/networkmanager/2019-07-05 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/network-firewall INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/network-firewall/2020-11-12 INFO : root : copying build/lib/botocore/data/network-firewall/2020-11-12/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/network-firewall/2020-11-12 INFO : root : copying build/lib/botocore/data/network-firewall/2020-11-12/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/network-firewall/2020-11-12 INFO : root : copying build/lib/botocore/data/network-firewall/2020-11-12/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/network-firewall/2020-11-12 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/neptune INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/neptune/2014-10-31 INFO : root : copying build/lib/botocore/data/neptune/2014-10-31/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/neptune/2014-10-31 INFO : root : copying build/lib/botocore/data/neptune/2014-10-31/service-2.sdk-extras.json -> build/bdist.linux-i686/wheel/botocore/data/neptune/2014-10-31 INFO : root : copying build/lib/botocore/data/neptune/2014-10-31/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/neptune/2014-10-31 INFO : root : copying build/lib/botocore/data/neptune/2014-10-31/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/neptune/2014-10-31 INFO : root : copying build/lib/botocore/data/neptune/2014-10-31/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/neptune/2014-10-31 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/mwaa INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/mwaa/2020-07-01 INFO : root : copying build/lib/botocore/data/mwaa/2020-07-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/mwaa/2020-07-01 INFO : root : copying build/lib/botocore/data/mwaa/2020-07-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/mwaa/2020-07-01 INFO : root : copying build/lib/botocore/data/mwaa/2020-07-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/mwaa/2020-07-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/mturk INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/mturk/2017-01-17 INFO : root : copying build/lib/botocore/data/mturk/2017-01-17/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/mturk/2017-01-17 INFO : root : copying build/lib/botocore/data/mturk/2017-01-17/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/mturk/2017-01-17 INFO : root : copying build/lib/botocore/data/mturk/2017-01-17/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/mturk/2017-01-17 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/mq INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/mq/2017-11-27 INFO : root : copying build/lib/botocore/data/mq/2017-11-27/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/mq/2017-11-27 INFO : root : copying build/lib/botocore/data/mq/2017-11-27/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/mq/2017-11-27 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/mobile INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/mobile/2017-07-01 INFO : root : copying build/lib/botocore/data/mobile/2017-07-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/mobile/2017-07-01 INFO : root : copying build/lib/botocore/data/mobile/2017-07-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/mobile/2017-07-01 INFO : root : copying build/lib/botocore/data/mobile/2017-07-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/mobile/2017-07-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/migrationhubstrategy INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/migrationhubstrategy/2020-02-19 INFO : root : copying build/lib/botocore/data/migrationhubstrategy/2020-02-19/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/migrationhubstrategy/2020-02-19 INFO : root : copying build/lib/botocore/data/migrationhubstrategy/2020-02-19/paginators-1.sdk-extras.json -> build/bdist.linux-i686/wheel/botocore/data/migrationhubstrategy/2020-02-19 INFO : root : copying build/lib/botocore/data/migrationhubstrategy/2020-02-19/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/migrationhubstrategy/2020-02-19 INFO : root : copying build/lib/botocore/data/migrationhubstrategy/2020-02-19/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/migrationhubstrategy/2020-02-19 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/migrationhuborchestrator INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/migrationhuborchestrator/2021-08-28 INFO : root : copying build/lib/botocore/data/migrationhuborchestrator/2021-08-28/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/migrationhuborchestrator/2021-08-28 INFO : root : copying build/lib/botocore/data/migrationhuborchestrator/2021-08-28/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/migrationhuborchestrator/2021-08-28 INFO : root : copying build/lib/botocore/data/migrationhuborchestrator/2021-08-28/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/migrationhuborchestrator/2021-08-28 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/migrationhub-config INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/migrationhub-config/2019-06-30 INFO : root : copying build/lib/botocore/data/migrationhub-config/2019-06-30/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/migrationhub-config/2019-06-30 INFO : root : copying build/lib/botocore/data/migrationhub-config/2019-06-30/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/migrationhub-config/2019-06-30 INFO : root : copying build/lib/botocore/data/migrationhub-config/2019-06-30/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/migrationhub-config/2019-06-30 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/migration-hub-refactor-spaces INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/migration-hub-refactor-spaces/2021-10-26 INFO : root : copying build/lib/botocore/data/migration-hub-refactor-spaces/2021-10-26/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/migration-hub-refactor-spaces/2021-10-26 INFO : root : copying build/lib/botocore/data/migration-hub-refactor-spaces/2021-10-26/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/migration-hub-refactor-spaces/2021-10-26 INFO : root : copying build/lib/botocore/data/migration-hub-refactor-spaces/2021-10-26/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/migration-hub-refactor-spaces/2021-10-26 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/mgn INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/mgn/2020-02-26 INFO : root : copying build/lib/botocore/data/mgn/2020-02-26/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/mgn/2020-02-26 INFO : root : copying build/lib/botocore/data/mgn/2020-02-26/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/mgn/2020-02-26 INFO : root : copying build/lib/botocore/data/mgn/2020-02-26/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/mgn/2020-02-26 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/mgh INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/mgh/2017-05-31 INFO : root : copying build/lib/botocore/data/mgh/2017-05-31/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/mgh/2017-05-31 INFO : root : copying build/lib/botocore/data/mgh/2017-05-31/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/mgh/2017-05-31 INFO : root : copying build/lib/botocore/data/mgh/2017-05-31/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/mgh/2017-05-31 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/meteringmarketplace INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/meteringmarketplace/2016-01-14 INFO : root : copying build/lib/botocore/data/meteringmarketplace/2016-01-14/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/meteringmarketplace/2016-01-14 INFO : root : copying build/lib/botocore/data/meteringmarketplace/2016-01-14/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/meteringmarketplace/2016-01-14 INFO : root : copying build/lib/botocore/data/meteringmarketplace/2016-01-14/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/meteringmarketplace/2016-01-14 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/memorydb INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/memorydb/2021-01-01 INFO : root : copying build/lib/botocore/data/memorydb/2021-01-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/memorydb/2021-01-01 INFO : root : copying build/lib/botocore/data/memorydb/2021-01-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/memorydb/2021-01-01 INFO : root : copying build/lib/botocore/data/memorydb/2021-01-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/memorydb/2021-01-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/mediatailor INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/mediatailor/2018-04-23 INFO : root : copying build/lib/botocore/data/mediatailor/2018-04-23/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/mediatailor/2018-04-23 INFO : root : copying build/lib/botocore/data/mediatailor/2018-04-23/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/mediatailor/2018-04-23 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/mediastore INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/mediastore/2017-09-01 INFO : root : copying build/lib/botocore/data/mediastore/2017-09-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/mediastore/2017-09-01 INFO : root : copying build/lib/botocore/data/mediastore/2017-09-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/mediastore/2017-09-01 INFO : root : copying build/lib/botocore/data/mediastore/2017-09-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/mediastore/2017-09-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/mediastore-data INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/mediastore-data/2017-09-01 INFO : root : copying build/lib/botocore/data/mediastore-data/2017-09-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/mediastore-data/2017-09-01 INFO : root : copying build/lib/botocore/data/mediastore-data/2017-09-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/mediastore-data/2017-09-01 INFO : root : copying build/lib/botocore/data/mediastore-data/2017-09-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/mediastore-data/2017-09-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/mediapackage INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/mediapackage/2017-10-12 INFO : root : copying build/lib/botocore/data/mediapackage/2017-10-12/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/mediapackage/2017-10-12 INFO : root : copying build/lib/botocore/data/mediapackage/2017-10-12/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/mediapackage/2017-10-12 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/mediapackage-vod INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/mediapackage-vod/2018-11-07 INFO : root : copying build/lib/botocore/data/mediapackage-vod/2018-11-07/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/mediapackage-vod/2018-11-07 INFO : root : copying build/lib/botocore/data/mediapackage-vod/2018-11-07/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/mediapackage-vod/2018-11-07 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/medialive INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/medialive/2017-10-14 INFO : root : copying build/lib/botocore/data/medialive/2017-10-14/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/medialive/2017-10-14 INFO : root : copying build/lib/botocore/data/medialive/2017-10-14/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/medialive/2017-10-14 INFO : root : copying build/lib/botocore/data/medialive/2017-10-14/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/medialive/2017-10-14 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/mediaconvert INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/mediaconvert/2017-08-29 INFO : root : copying build/lib/botocore/data/mediaconvert/2017-08-29/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/mediaconvert/2017-08-29 INFO : root : copying build/lib/botocore/data/mediaconvert/2017-08-29/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/mediaconvert/2017-08-29 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/mediaconnect INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/mediaconnect/2018-11-14 INFO : root : copying build/lib/botocore/data/mediaconnect/2018-11-14/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/mediaconnect/2018-11-14 INFO : root : copying build/lib/botocore/data/mediaconnect/2018-11-14/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/mediaconnect/2018-11-14 INFO : root : copying build/lib/botocore/data/mediaconnect/2018-11-14/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/mediaconnect/2018-11-14 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/marketplacecommerceanalytics INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/marketplacecommerceanalytics/2015-07-01 INFO : root : copying build/lib/botocore/data/marketplacecommerceanalytics/2015-07-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/marketplacecommerceanalytics/2015-07-01 INFO : root : copying build/lib/botocore/data/marketplacecommerceanalytics/2015-07-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/marketplacecommerceanalytics/2015-07-01 INFO : root : copying build/lib/botocore/data/marketplacecommerceanalytics/2015-07-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/marketplacecommerceanalytics/2015-07-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/marketplace-entitlement INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/marketplace-entitlement/2017-01-11 INFO : root : copying build/lib/botocore/data/marketplace-entitlement/2017-01-11/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/marketplace-entitlement/2017-01-11 INFO : root : copying build/lib/botocore/data/marketplace-entitlement/2017-01-11/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/marketplace-entitlement/2017-01-11 INFO : root : copying build/lib/botocore/data/marketplace-entitlement/2017-01-11/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/marketplace-entitlement/2017-01-11 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/marketplace-catalog INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/marketplace-catalog/2018-09-17 INFO : root : copying build/lib/botocore/data/marketplace-catalog/2018-09-17/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/marketplace-catalog/2018-09-17 INFO : root : copying build/lib/botocore/data/marketplace-catalog/2018-09-17/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/marketplace-catalog/2018-09-17 INFO : root : copying build/lib/botocore/data/marketplace-catalog/2018-09-17/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/marketplace-catalog/2018-09-17 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/managedblockchain INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/managedblockchain/2018-09-24 INFO : root : copying build/lib/botocore/data/managedblockchain/2018-09-24/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/managedblockchain/2018-09-24 INFO : root : copying build/lib/botocore/data/managedblockchain/2018-09-24/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/managedblockchain/2018-09-24 INFO : root : copying build/lib/botocore/data/managedblockchain/2018-09-24/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/managedblockchain/2018-09-24 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/macie2 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/macie2/2020-01-01 INFO : root : copying build/lib/botocore/data/macie2/2020-01-01/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/macie2/2020-01-01 INFO : root : copying build/lib/botocore/data/macie2/2020-01-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/macie2/2020-01-01 INFO : root : copying build/lib/botocore/data/macie2/2020-01-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/macie2/2020-01-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/macie INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/macie/2017-12-19 INFO : root : copying build/lib/botocore/data/macie/2017-12-19/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/macie/2017-12-19 INFO : root : copying build/lib/botocore/data/macie/2017-12-19/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/macie/2017-12-19 INFO : root : copying build/lib/botocore/data/macie/2017-12-19/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/macie/2017-12-19 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/machinelearning INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/machinelearning/2014-12-12 INFO : root : copying build/lib/botocore/data/machinelearning/2014-12-12/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/machinelearning/2014-12-12 INFO : root : copying build/lib/botocore/data/machinelearning/2014-12-12/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/machinelearning/2014-12-12 INFO : root : copying build/lib/botocore/data/machinelearning/2014-12-12/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/machinelearning/2014-12-12 INFO : root : copying build/lib/botocore/data/machinelearning/2014-12-12/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/machinelearning/2014-12-12 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/m2 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/m2/2021-04-28 INFO : root : copying build/lib/botocore/data/m2/2021-04-28/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/m2/2021-04-28 INFO : root : copying build/lib/botocore/data/m2/2021-04-28/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/m2/2021-04-28 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/lookoutvision INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/lookoutvision/2020-11-20 INFO : root : copying build/lib/botocore/data/lookoutvision/2020-11-20/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/lookoutvision/2020-11-20 INFO : root : copying build/lib/botocore/data/lookoutvision/2020-11-20/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/lookoutvision/2020-11-20 INFO : root : copying build/lib/botocore/data/lookoutvision/2020-11-20/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/lookoutvision/2020-11-20 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/lookoutmetrics INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/lookoutmetrics/2017-07-25 INFO : root : copying build/lib/botocore/data/lookoutmetrics/2017-07-25/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/lookoutmetrics/2017-07-25 INFO : root : copying build/lib/botocore/data/lookoutmetrics/2017-07-25/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/lookoutmetrics/2017-07-25 INFO : root : copying build/lib/botocore/data/lookoutmetrics/2017-07-25/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/lookoutmetrics/2017-07-25 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/lookoutequipment INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/lookoutequipment/2020-12-15 INFO : root : copying build/lib/botocore/data/lookoutequipment/2020-12-15/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/lookoutequipment/2020-12-15 INFO : root : copying build/lib/botocore/data/lookoutequipment/2020-12-15/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/lookoutequipment/2020-12-15 INFO : root : copying build/lib/botocore/data/lookoutequipment/2020-12-15/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/lookoutequipment/2020-12-15 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/logs INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/logs/2014-03-28 INFO : root : copying build/lib/botocore/data/logs/2014-03-28/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/logs/2014-03-28 INFO : root : copying build/lib/botocore/data/logs/2014-03-28/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/logs/2014-03-28 INFO : root : copying build/lib/botocore/data/logs/2014-03-28/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/logs/2014-03-28 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/location INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/location/2020-11-19 INFO : root : copying build/lib/botocore/data/location/2020-11-19/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/location/2020-11-19 INFO : root : copying build/lib/botocore/data/location/2020-11-19/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/location/2020-11-19 INFO : root : copying build/lib/botocore/data/location/2020-11-19/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/location/2020-11-19 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/lightsail INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/lightsail/2016-11-28 INFO : root : copying build/lib/botocore/data/lightsail/2016-11-28/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/lightsail/2016-11-28 INFO : root : copying build/lib/botocore/data/lightsail/2016-11-28/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/lightsail/2016-11-28 INFO : root : copying build/lib/botocore/data/lightsail/2016-11-28/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/lightsail/2016-11-28 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/license-manager INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/license-manager/2018-08-01 INFO : root : copying build/lib/botocore/data/license-manager/2018-08-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/license-manager/2018-08-01 INFO : root : copying build/lib/botocore/data/license-manager/2018-08-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/license-manager/2018-08-01 INFO : root : copying build/lib/botocore/data/license-manager/2018-08-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/license-manager/2018-08-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/license-manager-user-subscriptions INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/license-manager-user-subscriptions/2018-05-10 INFO : root : copying build/lib/botocore/data/license-manager-user-subscriptions/2018-05-10/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/license-manager-user-subscriptions/2018-05-10 INFO : root : copying build/lib/botocore/data/license-manager-user-subscriptions/2018-05-10/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/license-manager-user-subscriptions/2018-05-10 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/lexv2-runtime INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/lexv2-runtime/2020-08-07 INFO : root : copying build/lib/botocore/data/lexv2-runtime/2020-08-07/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/lexv2-runtime/2020-08-07 INFO : root : copying build/lib/botocore/data/lexv2-runtime/2020-08-07/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/lexv2-runtime/2020-08-07 INFO : root : copying build/lib/botocore/data/lexv2-runtime/2020-08-07/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/lexv2-runtime/2020-08-07 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/lexv2-models INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/lexv2-models/2020-08-07 INFO : root : copying build/lib/botocore/data/lexv2-models/2020-08-07/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/lexv2-models/2020-08-07 INFO : root : copying build/lib/botocore/data/lexv2-models/2020-08-07/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/lexv2-models/2020-08-07 INFO : root : copying build/lib/botocore/data/lexv2-models/2020-08-07/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/lexv2-models/2020-08-07 INFO : root : copying build/lib/botocore/data/lexv2-models/2020-08-07/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/lexv2-models/2020-08-07 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/lex-runtime INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/lex-runtime/2016-11-28 INFO : root : copying build/lib/botocore/data/lex-runtime/2016-11-28/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/lex-runtime/2016-11-28 INFO : root : copying build/lib/botocore/data/lex-runtime/2016-11-28/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/lex-runtime/2016-11-28 INFO : root : copying build/lib/botocore/data/lex-runtime/2016-11-28/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/lex-runtime/2016-11-28 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/lex-models INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/lex-models/2017-04-19 INFO : root : copying build/lib/botocore/data/lex-models/2017-04-19/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/lex-models/2017-04-19 INFO : root : copying build/lib/botocore/data/lex-models/2017-04-19/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/lex-models/2017-04-19 INFO : root : copying build/lib/botocore/data/lex-models/2017-04-19/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/lex-models/2017-04-19 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/lambda INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/lambda/2015-03-31 INFO : root : copying build/lib/botocore/data/lambda/2015-03-31/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/lambda/2015-03-31 INFO : root : copying build/lib/botocore/data/lambda/2015-03-31/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/lambda/2015-03-31 INFO : root : copying build/lib/botocore/data/lambda/2015-03-31/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/lambda/2015-03-31 INFO : root : copying build/lib/botocore/data/lambda/2015-03-31/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/lambda/2015-03-31 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/lambda/2014-11-11 INFO : root : copying build/lib/botocore/data/lambda/2014-11-11/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/lambda/2014-11-11 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/lakeformation INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/lakeformation/2017-03-31 INFO : root : copying build/lib/botocore/data/lakeformation/2017-03-31/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/lakeformation/2017-03-31 INFO : root : copying build/lib/botocore/data/lakeformation/2017-03-31/paginators-1.sdk-extras.json -> build/bdist.linux-i686/wheel/botocore/data/lakeformation/2017-03-31 INFO : root : copying build/lib/botocore/data/lakeformation/2017-03-31/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/lakeformation/2017-03-31 INFO : root : copying build/lib/botocore/data/lakeformation/2017-03-31/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/lakeformation/2017-03-31 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/kms INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/kms/2014-11-01 INFO : root : copying build/lib/botocore/data/kms/2014-11-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/kms/2014-11-01 INFO : root : copying build/lib/botocore/data/kms/2014-11-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/kms/2014-11-01 INFO : root : copying build/lib/botocore/data/kms/2014-11-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/kms/2014-11-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/kinesisvideo INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/kinesisvideo/2017-09-30 INFO : root : copying build/lib/botocore/data/kinesisvideo/2017-09-30/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/kinesisvideo/2017-09-30 INFO : root : copying build/lib/botocore/data/kinesisvideo/2017-09-30/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/kinesisvideo/2017-09-30 INFO : root : copying build/lib/botocore/data/kinesisvideo/2017-09-30/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/kinesisvideo/2017-09-30 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/kinesisanalyticsv2 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/kinesisanalyticsv2/2018-05-23 INFO : root : copying build/lib/botocore/data/kinesisanalyticsv2/2018-05-23/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/kinesisanalyticsv2/2018-05-23 INFO : root : copying build/lib/botocore/data/kinesisanalyticsv2/2018-05-23/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/kinesisanalyticsv2/2018-05-23 INFO : root : copying build/lib/botocore/data/kinesisanalyticsv2/2018-05-23/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/kinesisanalyticsv2/2018-05-23 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/kinesisanalytics INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/kinesisanalytics/2015-08-14 INFO : root : copying build/lib/botocore/data/kinesisanalytics/2015-08-14/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/kinesisanalytics/2015-08-14 INFO : root : copying build/lib/botocore/data/kinesisanalytics/2015-08-14/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/kinesisanalytics/2015-08-14 INFO : root : copying build/lib/botocore/data/kinesisanalytics/2015-08-14/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/kinesisanalytics/2015-08-14 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/kinesis INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/kinesis/2013-12-02 INFO : root : copying build/lib/botocore/data/kinesis/2013-12-02/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/kinesis/2013-12-02 INFO : root : copying build/lib/botocore/data/kinesis/2013-12-02/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/kinesis/2013-12-02 INFO : root : copying build/lib/botocore/data/kinesis/2013-12-02/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/kinesis/2013-12-02 INFO : root : copying build/lib/botocore/data/kinesis/2013-12-02/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/kinesis/2013-12-02 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/kinesis-video-signaling INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/kinesis-video-signaling/2019-12-04 INFO : root : copying build/lib/botocore/data/kinesis-video-signaling/2019-12-04/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/kinesis-video-signaling/2019-12-04 INFO : root : copying build/lib/botocore/data/kinesis-video-signaling/2019-12-04/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/kinesis-video-signaling/2019-12-04 INFO : root : copying build/lib/botocore/data/kinesis-video-signaling/2019-12-04/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/kinesis-video-signaling/2019-12-04 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/kinesis-video-media INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/kinesis-video-media/2017-09-30 INFO : root : copying build/lib/botocore/data/kinesis-video-media/2017-09-30/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/kinesis-video-media/2017-09-30 INFO : root : copying build/lib/botocore/data/kinesis-video-media/2017-09-30/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/kinesis-video-media/2017-09-30 INFO : root : copying build/lib/botocore/data/kinesis-video-media/2017-09-30/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/kinesis-video-media/2017-09-30 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/kinesis-video-archived-media INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/kinesis-video-archived-media/2017-09-30 INFO : root : copying build/lib/botocore/data/kinesis-video-archived-media/2017-09-30/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/kinesis-video-archived-media/2017-09-30 INFO : root : copying build/lib/botocore/data/kinesis-video-archived-media/2017-09-30/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/kinesis-video-archived-media/2017-09-30 INFO : root : copying build/lib/botocore/data/kinesis-video-archived-media/2017-09-30/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/kinesis-video-archived-media/2017-09-30 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/keyspaces INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/keyspaces/2022-02-10 INFO : root : copying build/lib/botocore/data/keyspaces/2022-02-10/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/keyspaces/2022-02-10 INFO : root : copying build/lib/botocore/data/keyspaces/2022-02-10/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/keyspaces/2022-02-10 INFO : root : copying build/lib/botocore/data/keyspaces/2022-02-10/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/keyspaces/2022-02-10 INFO : root : copying build/lib/botocore/data/keyspaces/2022-02-10/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/keyspaces/2022-02-10 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/kendra INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/kendra/2019-02-03 INFO : root : copying build/lib/botocore/data/kendra/2019-02-03/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/kendra/2019-02-03 INFO : root : copying build/lib/botocore/data/kendra/2019-02-03/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/kendra/2019-02-03 INFO : root : copying build/lib/botocore/data/kendra/2019-02-03/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/kendra/2019-02-03 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/kafkaconnect INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/kafkaconnect/2021-09-14 INFO : root : copying build/lib/botocore/data/kafkaconnect/2021-09-14/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/kafkaconnect/2021-09-14 INFO : root : copying build/lib/botocore/data/kafkaconnect/2021-09-14/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/kafkaconnect/2021-09-14 INFO : root : copying build/lib/botocore/data/kafkaconnect/2021-09-14/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/kafkaconnect/2021-09-14 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/kafka INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/kafka/2018-11-14 INFO : root : copying build/lib/botocore/data/kafka/2018-11-14/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/kafka/2018-11-14 INFO : root : copying build/lib/botocore/data/kafka/2018-11-14/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/kafka/2018-11-14 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ivschat INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ivschat/2020-07-14 INFO : root : copying build/lib/botocore/data/ivschat/2020-07-14/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/ivschat/2020-07-14 INFO : root : copying build/lib/botocore/data/ivschat/2020-07-14/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/ivschat/2020-07-14 INFO : root : copying build/lib/botocore/data/ivschat/2020-07-14/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/ivschat/2020-07-14 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ivs INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ivs/2020-07-14 INFO : root : copying build/lib/botocore/data/ivs/2020-07-14/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/ivs/2020-07-14 INFO : root : copying build/lib/botocore/data/ivs/2020-07-14/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/ivs/2020-07-14 INFO : root : copying build/lib/botocore/data/ivs/2020-07-14/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/ivs/2020-07-14 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iotwireless INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iotwireless/2020-11-22 INFO : root : copying build/lib/botocore/data/iotwireless/2020-11-22/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/iotwireless/2020-11-22 INFO : root : copying build/lib/botocore/data/iotwireless/2020-11-22/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/iotwireless/2020-11-22 INFO : root : copying build/lib/botocore/data/iotwireless/2020-11-22/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/iotwireless/2020-11-22 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iottwinmaker INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iottwinmaker/2021-11-29 INFO : root : copying build/lib/botocore/data/iottwinmaker/2021-11-29/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/iottwinmaker/2021-11-29 INFO : root : copying build/lib/botocore/data/iottwinmaker/2021-11-29/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/iottwinmaker/2021-11-29 INFO : root : copying build/lib/botocore/data/iottwinmaker/2021-11-29/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/iottwinmaker/2021-11-29 INFO : root : copying build/lib/botocore/data/iottwinmaker/2021-11-29/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/iottwinmaker/2021-11-29 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iotthingsgraph INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iotthingsgraph/2018-09-06 INFO : root : copying build/lib/botocore/data/iotthingsgraph/2018-09-06/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/iotthingsgraph/2018-09-06 INFO : root : copying build/lib/botocore/data/iotthingsgraph/2018-09-06/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/iotthingsgraph/2018-09-06 INFO : root : copying build/lib/botocore/data/iotthingsgraph/2018-09-06/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/iotthingsgraph/2018-09-06 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iotsitewise INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iotsitewise/2019-12-02 INFO : root : copying build/lib/botocore/data/iotsitewise/2019-12-02/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/iotsitewise/2019-12-02 INFO : root : copying build/lib/botocore/data/iotsitewise/2019-12-02/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/iotsitewise/2019-12-02 INFO : root : copying build/lib/botocore/data/iotsitewise/2019-12-02/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/iotsitewise/2019-12-02 INFO : root : copying build/lib/botocore/data/iotsitewise/2019-12-02/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/iotsitewise/2019-12-02 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iotsecuretunneling INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iotsecuretunneling/2018-10-05 INFO : root : copying build/lib/botocore/data/iotsecuretunneling/2018-10-05/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/iotsecuretunneling/2018-10-05 INFO : root : copying build/lib/botocore/data/iotsecuretunneling/2018-10-05/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/iotsecuretunneling/2018-10-05 INFO : root : copying build/lib/botocore/data/iotsecuretunneling/2018-10-05/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/iotsecuretunneling/2018-10-05 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iotfleetwise INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iotfleetwise/2021-06-17 INFO : root : copying build/lib/botocore/data/iotfleetwise/2021-06-17/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/iotfleetwise/2021-06-17 INFO : root : copying build/lib/botocore/data/iotfleetwise/2021-06-17/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/iotfleetwise/2021-06-17 INFO : root : copying build/lib/botocore/data/iotfleetwise/2021-06-17/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/iotfleetwise/2021-06-17 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iotfleethub INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iotfleethub/2020-11-03 INFO : root : copying build/lib/botocore/data/iotfleethub/2020-11-03/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/iotfleethub/2020-11-03 INFO : root : copying build/lib/botocore/data/iotfleethub/2020-11-03/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/iotfleethub/2020-11-03 INFO : root : copying build/lib/botocore/data/iotfleethub/2020-11-03/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/iotfleethub/2020-11-03 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iotevents INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iotevents/2018-07-27 INFO : root : copying build/lib/botocore/data/iotevents/2018-07-27/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/iotevents/2018-07-27 INFO : root : copying build/lib/botocore/data/iotevents/2018-07-27/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/iotevents/2018-07-27 INFO : root : copying build/lib/botocore/data/iotevents/2018-07-27/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/iotevents/2018-07-27 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iotevents-data INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iotevents-data/2018-10-23 INFO : root : copying build/lib/botocore/data/iotevents-data/2018-10-23/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/iotevents-data/2018-10-23 INFO : root : copying build/lib/botocore/data/iotevents-data/2018-10-23/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/iotevents-data/2018-10-23 INFO : root : copying build/lib/botocore/data/iotevents-data/2018-10-23/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/iotevents-data/2018-10-23 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iotdeviceadvisor INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iotdeviceadvisor/2020-09-18 INFO : root : copying build/lib/botocore/data/iotdeviceadvisor/2020-09-18/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/iotdeviceadvisor/2020-09-18 INFO : root : copying build/lib/botocore/data/iotdeviceadvisor/2020-09-18/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/iotdeviceadvisor/2020-09-18 INFO : root : copying build/lib/botocore/data/iotdeviceadvisor/2020-09-18/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/iotdeviceadvisor/2020-09-18 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iotanalytics INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iotanalytics/2017-11-27 INFO : root : copying build/lib/botocore/data/iotanalytics/2017-11-27/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/iotanalytics/2017-11-27 INFO : root : copying build/lib/botocore/data/iotanalytics/2017-11-27/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/iotanalytics/2017-11-27 INFO : root : copying build/lib/botocore/data/iotanalytics/2017-11-27/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/iotanalytics/2017-11-27 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iot1click-projects INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iot1click-projects/2018-05-14 INFO : root : copying build/lib/botocore/data/iot1click-projects/2018-05-14/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/iot1click-projects/2018-05-14 INFO : root : copying build/lib/botocore/data/iot1click-projects/2018-05-14/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/iot1click-projects/2018-05-14 INFO : root : copying build/lib/botocore/data/iot1click-projects/2018-05-14/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/iot1click-projects/2018-05-14 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iot1click-devices INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iot1click-devices/2018-05-14 INFO : root : copying build/lib/botocore/data/iot1click-devices/2018-05-14/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/iot1click-devices/2018-05-14 INFO : root : copying build/lib/botocore/data/iot1click-devices/2018-05-14/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/iot1click-devices/2018-05-14 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iot INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iot/2015-05-28 INFO : root : copying build/lib/botocore/data/iot/2015-05-28/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/iot/2015-05-28 INFO : root : copying build/lib/botocore/data/iot/2015-05-28/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/iot/2015-05-28 INFO : root : copying build/lib/botocore/data/iot/2015-05-28/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/iot/2015-05-28 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iot-jobs-data INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iot-jobs-data/2017-09-29 INFO : root : copying build/lib/botocore/data/iot-jobs-data/2017-09-29/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/iot-jobs-data/2017-09-29 INFO : root : copying build/lib/botocore/data/iot-jobs-data/2017-09-29/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/iot-jobs-data/2017-09-29 INFO : root : copying build/lib/botocore/data/iot-jobs-data/2017-09-29/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/iot-jobs-data/2017-09-29 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iot-data INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iot-data/2015-05-28 INFO : root : copying build/lib/botocore/data/iot-data/2015-05-28/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/iot-data/2015-05-28 INFO : root : copying build/lib/botocore/data/iot-data/2015-05-28/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/iot-data/2015-05-28 INFO : root : copying build/lib/botocore/data/iot-data/2015-05-28/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/iot-data/2015-05-28 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/inspector2 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/inspector2/2020-06-08 INFO : root : copying build/lib/botocore/data/inspector2/2020-06-08/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/inspector2/2020-06-08 INFO : root : copying build/lib/botocore/data/inspector2/2020-06-08/paginators-1.sdk-extras.json -> build/bdist.linux-i686/wheel/botocore/data/inspector2/2020-06-08 INFO : root : copying build/lib/botocore/data/inspector2/2020-06-08/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/inspector2/2020-06-08 INFO : root : copying build/lib/botocore/data/inspector2/2020-06-08/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/inspector2/2020-06-08 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/inspector INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/inspector/2016-02-16 INFO : root : copying build/lib/botocore/data/inspector/2016-02-16/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/inspector/2016-02-16 INFO : root : copying build/lib/botocore/data/inspector/2016-02-16/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/inspector/2016-02-16 INFO : root : copying build/lib/botocore/data/inspector/2016-02-16/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/inspector/2016-02-16 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/inspector/2015-08-18 INFO : root : copying build/lib/botocore/data/inspector/2015-08-18/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/inspector/2015-08-18 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/importexport INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/importexport/2010-06-01 INFO : root : copying build/lib/botocore/data/importexport/2010-06-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/importexport/2010-06-01 INFO : root : copying build/lib/botocore/data/importexport/2010-06-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/importexport/2010-06-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/imagebuilder INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/imagebuilder/2019-12-02 INFO : root : copying build/lib/botocore/data/imagebuilder/2019-12-02/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/imagebuilder/2019-12-02 INFO : root : copying build/lib/botocore/data/imagebuilder/2019-12-02/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/imagebuilder/2019-12-02 INFO : root : copying build/lib/botocore/data/imagebuilder/2019-12-02/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/imagebuilder/2019-12-02 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/identitystore INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/identitystore/2020-06-15 INFO : root : copying build/lib/botocore/data/identitystore/2020-06-15/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/identitystore/2020-06-15 INFO : root : copying build/lib/botocore/data/identitystore/2020-06-15/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/identitystore/2020-06-15 INFO : root : copying build/lib/botocore/data/identitystore/2020-06-15/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/identitystore/2020-06-15 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iam INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/iam/2010-05-08 INFO : root : copying build/lib/botocore/data/iam/2010-05-08/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/iam/2010-05-08 INFO : root : copying build/lib/botocore/data/iam/2010-05-08/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/iam/2010-05-08 INFO : root : copying build/lib/botocore/data/iam/2010-05-08/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/iam/2010-05-08 INFO : root : copying build/lib/botocore/data/iam/2010-05-08/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/iam/2010-05-08 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/honeycode INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/honeycode/2020-03-01 INFO : root : copying build/lib/botocore/data/honeycode/2020-03-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/honeycode/2020-03-01 INFO : root : copying build/lib/botocore/data/honeycode/2020-03-01/paginators-1.sdk-extras.json -> build/bdist.linux-i686/wheel/botocore/data/honeycode/2020-03-01 INFO : root : copying build/lib/botocore/data/honeycode/2020-03-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/honeycode/2020-03-01 INFO : root : copying build/lib/botocore/data/honeycode/2020-03-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/honeycode/2020-03-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/healthlake INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/healthlake/2017-07-01 INFO : root : copying build/lib/botocore/data/healthlake/2017-07-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/healthlake/2017-07-01 INFO : root : copying build/lib/botocore/data/healthlake/2017-07-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/healthlake/2017-07-01 INFO : root : copying build/lib/botocore/data/healthlake/2017-07-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/healthlake/2017-07-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/health INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/health/2016-08-04 INFO : root : copying build/lib/botocore/data/health/2016-08-04/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/health/2016-08-04 INFO : root : copying build/lib/botocore/data/health/2016-08-04/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/health/2016-08-04 INFO : root : copying build/lib/botocore/data/health/2016-08-04/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/health/2016-08-04 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/guardduty INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/guardduty/2017-11-28 INFO : root : copying build/lib/botocore/data/guardduty/2017-11-28/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/guardduty/2017-11-28 INFO : root : copying build/lib/botocore/data/guardduty/2017-11-28/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/guardduty/2017-11-28 INFO : root : copying build/lib/botocore/data/guardduty/2017-11-28/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/guardduty/2017-11-28 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/groundstation INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/groundstation/2019-05-23 INFO : root : copying build/lib/botocore/data/groundstation/2019-05-23/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/groundstation/2019-05-23 INFO : root : copying build/lib/botocore/data/groundstation/2019-05-23/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/groundstation/2019-05-23 INFO : root : copying build/lib/botocore/data/groundstation/2019-05-23/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/groundstation/2019-05-23 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/greengrassv2 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/greengrassv2/2020-11-30 INFO : root : copying build/lib/botocore/data/greengrassv2/2020-11-30/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/greengrassv2/2020-11-30 INFO : root : copying build/lib/botocore/data/greengrassv2/2020-11-30/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/greengrassv2/2020-11-30 INFO : root : copying build/lib/botocore/data/greengrassv2/2020-11-30/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/greengrassv2/2020-11-30 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/greengrass INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/greengrass/2017-06-07 INFO : root : copying build/lib/botocore/data/greengrass/2017-06-07/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/greengrass/2017-06-07 INFO : root : copying build/lib/botocore/data/greengrass/2017-06-07/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/greengrass/2017-06-07 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/grafana INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/grafana/2020-08-18 INFO : root : copying build/lib/botocore/data/grafana/2020-08-18/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/grafana/2020-08-18 INFO : root : copying build/lib/botocore/data/grafana/2020-08-18/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/grafana/2020-08-18 INFO : root : copying build/lib/botocore/data/grafana/2020-08-18/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/grafana/2020-08-18 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/glue INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/glue/2017-03-31 INFO : root : copying build/lib/botocore/data/glue/2017-03-31/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/glue/2017-03-31 INFO : root : copying build/lib/botocore/data/glue/2017-03-31/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/glue/2017-03-31 INFO : root : copying build/lib/botocore/data/glue/2017-03-31/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/glue/2017-03-31 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/globalaccelerator INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/globalaccelerator/2018-08-08 INFO : root : copying build/lib/botocore/data/globalaccelerator/2018-08-08/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/globalaccelerator/2018-08-08 INFO : root : copying build/lib/botocore/data/globalaccelerator/2018-08-08/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/globalaccelerator/2018-08-08 INFO : root : copying build/lib/botocore/data/globalaccelerator/2018-08-08/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/globalaccelerator/2018-08-08 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/glacier INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/glacier/2012-06-01 INFO : root : copying build/lib/botocore/data/glacier/2012-06-01/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/glacier/2012-06-01 INFO : root : copying build/lib/botocore/data/glacier/2012-06-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/glacier/2012-06-01 INFO : root : copying build/lib/botocore/data/glacier/2012-06-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/glacier/2012-06-01 INFO : root : copying build/lib/botocore/data/glacier/2012-06-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/glacier/2012-06-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/gamesparks INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/gamesparks/2021-08-17 INFO : root : copying build/lib/botocore/data/gamesparks/2021-08-17/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/gamesparks/2021-08-17 INFO : root : copying build/lib/botocore/data/gamesparks/2021-08-17/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/gamesparks/2021-08-17 INFO : root : copying build/lib/botocore/data/gamesparks/2021-08-17/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/gamesparks/2021-08-17 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/gamelift INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/gamelift/2015-10-01 INFO : root : copying build/lib/botocore/data/gamelift/2015-10-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/gamelift/2015-10-01 INFO : root : copying build/lib/botocore/data/gamelift/2015-10-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/gamelift/2015-10-01 INFO : root : copying build/lib/botocore/data/gamelift/2015-10-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/gamelift/2015-10-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/fsx INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/fsx/2018-03-01 INFO : root : copying build/lib/botocore/data/fsx/2018-03-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/fsx/2018-03-01 INFO : root : copying build/lib/botocore/data/fsx/2018-03-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/fsx/2018-03-01 INFO : root : copying build/lib/botocore/data/fsx/2018-03-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/fsx/2018-03-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/frauddetector INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/frauddetector/2019-11-15 INFO : root : copying build/lib/botocore/data/frauddetector/2019-11-15/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/frauddetector/2019-11-15 INFO : root : copying build/lib/botocore/data/frauddetector/2019-11-15/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/frauddetector/2019-11-15 INFO : root : copying build/lib/botocore/data/frauddetector/2019-11-15/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/frauddetector/2019-11-15 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/forecastquery INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/forecastquery/2018-06-26 INFO : root : copying build/lib/botocore/data/forecastquery/2018-06-26/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/forecastquery/2018-06-26 INFO : root : copying build/lib/botocore/data/forecastquery/2018-06-26/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/forecastquery/2018-06-26 INFO : root : copying build/lib/botocore/data/forecastquery/2018-06-26/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/forecastquery/2018-06-26 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/forecast INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/forecast/2018-06-26 INFO : root : copying build/lib/botocore/data/forecast/2018-06-26/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/forecast/2018-06-26 INFO : root : copying build/lib/botocore/data/forecast/2018-06-26/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/forecast/2018-06-26 INFO : root : copying build/lib/botocore/data/forecast/2018-06-26/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/forecast/2018-06-26 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/fms INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/fms/2018-01-01 INFO : root : copying build/lib/botocore/data/fms/2018-01-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/fms/2018-01-01 INFO : root : copying build/lib/botocore/data/fms/2018-01-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/fms/2018-01-01 INFO : root : copying build/lib/botocore/data/fms/2018-01-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/fms/2018-01-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/fis INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/fis/2020-12-01 INFO : root : copying build/lib/botocore/data/fis/2020-12-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/fis/2020-12-01 INFO : root : copying build/lib/botocore/data/fis/2020-12-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/fis/2020-12-01 INFO : root : copying build/lib/botocore/data/fis/2020-12-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/fis/2020-12-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/firehose INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/firehose/2015-08-04 INFO : root : copying build/lib/botocore/data/firehose/2015-08-04/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/firehose/2015-08-04 INFO : root : copying build/lib/botocore/data/firehose/2015-08-04/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/firehose/2015-08-04 INFO : root : copying build/lib/botocore/data/firehose/2015-08-04/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/firehose/2015-08-04 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/finspace INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/finspace/2021-03-12 INFO : root : copying build/lib/botocore/data/finspace/2021-03-12/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/finspace/2021-03-12 INFO : root : copying build/lib/botocore/data/finspace/2021-03-12/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/finspace/2021-03-12 INFO : root : copying build/lib/botocore/data/finspace/2021-03-12/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/finspace/2021-03-12 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/finspace-data INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/finspace-data/2020-07-13 INFO : root : copying build/lib/botocore/data/finspace-data/2020-07-13/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/finspace-data/2020-07-13 INFO : root : copying build/lib/botocore/data/finspace-data/2020-07-13/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/finspace-data/2020-07-13 INFO : root : copying build/lib/botocore/data/finspace-data/2020-07-13/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/finspace-data/2020-07-13 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/evidently INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/evidently/2021-02-01 INFO : root : copying build/lib/botocore/data/evidently/2021-02-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/evidently/2021-02-01 INFO : root : copying build/lib/botocore/data/evidently/2021-02-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/evidently/2021-02-01 INFO : root : copying build/lib/botocore/data/evidently/2021-02-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/evidently/2021-02-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/events INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/events/2015-10-07 INFO : root : copying build/lib/botocore/data/events/2015-10-07/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/events/2015-10-07 INFO : root : copying build/lib/botocore/data/events/2015-10-07/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/events/2015-10-07 INFO : root : copying build/lib/botocore/data/events/2015-10-07/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/events/2015-10-07 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/events/2014-02-03 INFO : root : copying build/lib/botocore/data/events/2014-02-03/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/events/2014-02-03 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/es INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/es/2015-01-01 INFO : root : copying build/lib/botocore/data/es/2015-01-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/es/2015-01-01 INFO : root : copying build/lib/botocore/data/es/2015-01-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/es/2015-01-01 INFO : root : copying build/lib/botocore/data/es/2015-01-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/es/2015-01-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/emr INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/emr/2009-03-31 INFO : root : copying build/lib/botocore/data/emr/2009-03-31/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/emr/2009-03-31 INFO : root : copying build/lib/botocore/data/emr/2009-03-31/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/emr/2009-03-31 INFO : root : copying build/lib/botocore/data/emr/2009-03-31/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/emr/2009-03-31 INFO : root : copying build/lib/botocore/data/emr/2009-03-31/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/emr/2009-03-31 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/emr-serverless INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/emr-serverless/2021-07-13 INFO : root : copying build/lib/botocore/data/emr-serverless/2021-07-13/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/emr-serverless/2021-07-13 INFO : root : copying build/lib/botocore/data/emr-serverless/2021-07-13/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/emr-serverless/2021-07-13 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/emr-containers INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/emr-containers/2020-10-01 INFO : root : copying build/lib/botocore/data/emr-containers/2020-10-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/emr-containers/2020-10-01 INFO : root : copying build/lib/botocore/data/emr-containers/2020-10-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/emr-containers/2020-10-01 INFO : root : copying build/lib/botocore/data/emr-containers/2020-10-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/emr-containers/2020-10-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/elbv2 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/elbv2/2015-12-01 INFO : root : copying build/lib/botocore/data/elbv2/2015-12-01/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/elbv2/2015-12-01 INFO : root : copying build/lib/botocore/data/elbv2/2015-12-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/elbv2/2015-12-01 INFO : root : copying build/lib/botocore/data/elbv2/2015-12-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/elbv2/2015-12-01 INFO : root : copying build/lib/botocore/data/elbv2/2015-12-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/elbv2/2015-12-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/elb INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/elb/2012-06-01 INFO : root : copying build/lib/botocore/data/elb/2012-06-01/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/elb/2012-06-01 INFO : root : copying build/lib/botocore/data/elb/2012-06-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/elb/2012-06-01 INFO : root : copying build/lib/botocore/data/elb/2012-06-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/elb/2012-06-01 INFO : root : copying build/lib/botocore/data/elb/2012-06-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/elb/2012-06-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/elastictranscoder INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/elastictranscoder/2012-09-25 INFO : root : copying build/lib/botocore/data/elastictranscoder/2012-09-25/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/elastictranscoder/2012-09-25 INFO : root : copying build/lib/botocore/data/elastictranscoder/2012-09-25/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/elastictranscoder/2012-09-25 INFO : root : copying build/lib/botocore/data/elastictranscoder/2012-09-25/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/elastictranscoder/2012-09-25 INFO : root : copying build/lib/botocore/data/elastictranscoder/2012-09-25/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/elastictranscoder/2012-09-25 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/elasticbeanstalk INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/elasticbeanstalk/2010-12-01 INFO : root : copying build/lib/botocore/data/elasticbeanstalk/2010-12-01/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/elasticbeanstalk/2010-12-01 INFO : root : copying build/lib/botocore/data/elasticbeanstalk/2010-12-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/elasticbeanstalk/2010-12-01 INFO : root : copying build/lib/botocore/data/elasticbeanstalk/2010-12-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/elasticbeanstalk/2010-12-01 INFO : root : copying build/lib/botocore/data/elasticbeanstalk/2010-12-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/elasticbeanstalk/2010-12-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/elasticache INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/elasticache/2015-02-02 INFO : root : copying build/lib/botocore/data/elasticache/2015-02-02/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/elasticache/2015-02-02 INFO : root : copying build/lib/botocore/data/elasticache/2015-02-02/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/elasticache/2015-02-02 INFO : root : copying build/lib/botocore/data/elasticache/2015-02-02/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/elasticache/2015-02-02 INFO : root : copying build/lib/botocore/data/elasticache/2015-02-02/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/elasticache/2015-02-02 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/elasticache/2014-09-30 INFO : root : copying build/lib/botocore/data/elasticache/2014-09-30/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/elasticache/2014-09-30 INFO : root : copying build/lib/botocore/data/elasticache/2014-09-30/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/elasticache/2014-09-30 INFO : root : copying build/lib/botocore/data/elasticache/2014-09-30/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/elasticache/2014-09-30 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/elastic-inference INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/elastic-inference/2017-07-25 INFO : root : copying build/lib/botocore/data/elastic-inference/2017-07-25/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/elastic-inference/2017-07-25 INFO : root : copying build/lib/botocore/data/elastic-inference/2017-07-25/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/elastic-inference/2017-07-25 INFO : root : copying build/lib/botocore/data/elastic-inference/2017-07-25/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/elastic-inference/2017-07-25 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/eks INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/eks/2017-11-01 INFO : root : copying build/lib/botocore/data/eks/2017-11-01/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/eks/2017-11-01 INFO : root : copying build/lib/botocore/data/eks/2017-11-01/service-2.sdk-extras.json -> build/bdist.linux-i686/wheel/botocore/data/eks/2017-11-01 INFO : root : copying build/lib/botocore/data/eks/2017-11-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/eks/2017-11-01 INFO : root : copying build/lib/botocore/data/eks/2017-11-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/eks/2017-11-01 INFO : root : copying build/lib/botocore/data/eks/2017-11-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/eks/2017-11-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/efs INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/efs/2015-02-01 INFO : root : copying build/lib/botocore/data/efs/2015-02-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/efs/2015-02-01 INFO : root : copying build/lib/botocore/data/efs/2015-02-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/efs/2015-02-01 INFO : root : copying build/lib/botocore/data/efs/2015-02-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/efs/2015-02-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ecs INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ecs/2014-11-13 INFO : root : copying build/lib/botocore/data/ecs/2014-11-13/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/ecs/2014-11-13 INFO : root : copying build/lib/botocore/data/ecs/2014-11-13/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/ecs/2014-11-13 INFO : root : copying build/lib/botocore/data/ecs/2014-11-13/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/ecs/2014-11-13 INFO : root : copying build/lib/botocore/data/ecs/2014-11-13/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/ecs/2014-11-13 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ecr INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ecr/2015-09-21 INFO : root : copying build/lib/botocore/data/ecr/2015-09-21/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/ecr/2015-09-21 INFO : root : copying build/lib/botocore/data/ecr/2015-09-21/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/ecr/2015-09-21 INFO : root : copying build/lib/botocore/data/ecr/2015-09-21/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/ecr/2015-09-21 INFO : root : copying build/lib/botocore/data/ecr/2015-09-21/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/ecr/2015-09-21 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ecr-public INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ecr-public/2020-10-30 INFO : root : copying build/lib/botocore/data/ecr-public/2020-10-30/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/ecr-public/2020-10-30 INFO : root : copying build/lib/botocore/data/ecr-public/2020-10-30/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/ecr-public/2020-10-30 INFO : root : copying build/lib/botocore/data/ecr-public/2020-10-30/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/ecr-public/2020-10-30 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ec2 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ec2/2016-11-15 INFO : root : copying build/lib/botocore/data/ec2/2016-11-15/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/ec2/2016-11-15 INFO : root : copying build/lib/botocore/data/ec2/2016-11-15/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/ec2/2016-11-15 INFO : root : copying build/lib/botocore/data/ec2/2016-11-15/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/ec2/2016-11-15 INFO : root : copying build/lib/botocore/data/ec2/2016-11-15/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/ec2/2016-11-15 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ec2/2016-09-15 INFO : root : copying build/lib/botocore/data/ec2/2016-09-15/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/ec2/2016-09-15 INFO : root : copying build/lib/botocore/data/ec2/2016-09-15/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/ec2/2016-09-15 INFO : root : copying build/lib/botocore/data/ec2/2016-09-15/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/ec2/2016-09-15 INFO : root : copying build/lib/botocore/data/ec2/2016-09-15/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/ec2/2016-09-15 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ec2/2016-04-01 INFO : root : copying build/lib/botocore/data/ec2/2016-04-01/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/ec2/2016-04-01 INFO : root : copying build/lib/botocore/data/ec2/2016-04-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/ec2/2016-04-01 INFO : root : copying build/lib/botocore/data/ec2/2016-04-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/ec2/2016-04-01 INFO : root : copying build/lib/botocore/data/ec2/2016-04-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/ec2/2016-04-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ec2/2015-10-01 INFO : root : copying build/lib/botocore/data/ec2/2015-10-01/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/ec2/2015-10-01 INFO : root : copying build/lib/botocore/data/ec2/2015-10-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/ec2/2015-10-01 INFO : root : copying build/lib/botocore/data/ec2/2015-10-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/ec2/2015-10-01 INFO : root : copying build/lib/botocore/data/ec2/2015-10-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/ec2/2015-10-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ec2/2015-04-15 INFO : root : copying build/lib/botocore/data/ec2/2015-04-15/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/ec2/2015-04-15 INFO : root : copying build/lib/botocore/data/ec2/2015-04-15/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/ec2/2015-04-15 INFO : root : copying build/lib/botocore/data/ec2/2015-04-15/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/ec2/2015-04-15 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ec2/2015-03-01 INFO : root : copying build/lib/botocore/data/ec2/2015-03-01/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/ec2/2015-03-01 INFO : root : copying build/lib/botocore/data/ec2/2015-03-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/ec2/2015-03-01 INFO : root : copying build/lib/botocore/data/ec2/2015-03-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/ec2/2015-03-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ec2/2014-10-01 INFO : root : copying build/lib/botocore/data/ec2/2014-10-01/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/ec2/2014-10-01 INFO : root : copying build/lib/botocore/data/ec2/2014-10-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/ec2/2014-10-01 INFO : root : copying build/lib/botocore/data/ec2/2014-10-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/ec2/2014-10-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ec2/2014-09-01 INFO : root : copying build/lib/botocore/data/ec2/2014-09-01/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/ec2/2014-09-01 INFO : root : copying build/lib/botocore/data/ec2/2014-09-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/ec2/2014-09-01 INFO : root : copying build/lib/botocore/data/ec2/2014-09-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/ec2/2014-09-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ec2-instance-connect INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ec2-instance-connect/2018-04-02 INFO : root : copying build/lib/botocore/data/ec2-instance-connect/2018-04-02/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/ec2-instance-connect/2018-04-02 INFO : root : copying build/lib/botocore/data/ec2-instance-connect/2018-04-02/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/ec2-instance-connect/2018-04-02 INFO : root : copying build/lib/botocore/data/ec2-instance-connect/2018-04-02/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/ec2-instance-connect/2018-04-02 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ebs INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ebs/2019-11-02 INFO : root : copying build/lib/botocore/data/ebs/2019-11-02/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/ebs/2019-11-02 INFO : root : copying build/lib/botocore/data/ebs/2019-11-02/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/ebs/2019-11-02 INFO : root : copying build/lib/botocore/data/ebs/2019-11-02/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/ebs/2019-11-02 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/dynamodbstreams INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/dynamodbstreams/2012-08-10 INFO : root : copying build/lib/botocore/data/dynamodbstreams/2012-08-10/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/dynamodbstreams/2012-08-10 INFO : root : copying build/lib/botocore/data/dynamodbstreams/2012-08-10/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/dynamodbstreams/2012-08-10 INFO : root : copying build/lib/botocore/data/dynamodbstreams/2012-08-10/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/dynamodbstreams/2012-08-10 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/dynamodb INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/dynamodb/2012-08-10 INFO : root : copying build/lib/botocore/data/dynamodb/2012-08-10/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/dynamodb/2012-08-10 INFO : root : copying build/lib/botocore/data/dynamodb/2012-08-10/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/dynamodb/2012-08-10 INFO : root : copying build/lib/botocore/data/dynamodb/2012-08-10/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/dynamodb/2012-08-10 INFO : root : copying build/lib/botocore/data/dynamodb/2012-08-10/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/dynamodb/2012-08-10 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/dynamodb/2011-12-05 INFO : root : copying build/lib/botocore/data/dynamodb/2011-12-05/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/dynamodb/2011-12-05 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ds INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ds/2015-04-16 INFO : root : copying build/lib/botocore/data/ds/2015-04-16/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/ds/2015-04-16 INFO : root : copying build/lib/botocore/data/ds/2015-04-16/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/ds/2015-04-16 INFO : root : copying build/lib/botocore/data/ds/2015-04-16/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/ds/2015-04-16 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/drs INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/drs/2020-02-26 INFO : root : copying build/lib/botocore/data/drs/2020-02-26/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/drs/2020-02-26 INFO : root : copying build/lib/botocore/data/drs/2020-02-26/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/drs/2020-02-26 INFO : root : copying build/lib/botocore/data/drs/2020-02-26/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/drs/2020-02-26 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/docdb INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/docdb/2014-10-31 INFO : root : copying build/lib/botocore/data/docdb/2014-10-31/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/docdb/2014-10-31 INFO : root : copying build/lib/botocore/data/docdb/2014-10-31/service-2.sdk-extras.json -> build/bdist.linux-i686/wheel/botocore/data/docdb/2014-10-31 INFO : root : copying build/lib/botocore/data/docdb/2014-10-31/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/docdb/2014-10-31 INFO : root : copying build/lib/botocore/data/docdb/2014-10-31/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/docdb/2014-10-31 INFO : root : copying build/lib/botocore/data/docdb/2014-10-31/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/docdb/2014-10-31 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/dms INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/dms/2016-01-01 INFO : root : copying build/lib/botocore/data/dms/2016-01-01/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/dms/2016-01-01 INFO : root : copying build/lib/botocore/data/dms/2016-01-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/dms/2016-01-01 INFO : root : copying build/lib/botocore/data/dms/2016-01-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/dms/2016-01-01 INFO : root : copying build/lib/botocore/data/dms/2016-01-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/dms/2016-01-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/dlm INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/dlm/2018-01-12 INFO : root : copying build/lib/botocore/data/dlm/2018-01-12/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/dlm/2018-01-12 INFO : root : copying build/lib/botocore/data/dlm/2018-01-12/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/dlm/2018-01-12 INFO : root : copying build/lib/botocore/data/dlm/2018-01-12/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/dlm/2018-01-12 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/discovery INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/discovery/2015-11-01 INFO : root : copying build/lib/botocore/data/discovery/2015-11-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/discovery/2015-11-01 INFO : root : copying build/lib/botocore/data/discovery/2015-11-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/discovery/2015-11-01 INFO : root : copying build/lib/botocore/data/discovery/2015-11-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/discovery/2015-11-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/directconnect INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/directconnect/2012-10-25 INFO : root : copying build/lib/botocore/data/directconnect/2012-10-25/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/directconnect/2012-10-25 INFO : root : copying build/lib/botocore/data/directconnect/2012-10-25/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/directconnect/2012-10-25 INFO : root : copying build/lib/botocore/data/directconnect/2012-10-25/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/directconnect/2012-10-25 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/devops-guru INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/devops-guru/2020-12-01 INFO : root : copying build/lib/botocore/data/devops-guru/2020-12-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/devops-guru/2020-12-01 INFO : root : copying build/lib/botocore/data/devops-guru/2020-12-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/devops-guru/2020-12-01 INFO : root : copying build/lib/botocore/data/devops-guru/2020-12-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/devops-guru/2020-12-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/devicefarm INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/devicefarm/2015-06-23 INFO : root : copying build/lib/botocore/data/devicefarm/2015-06-23/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/devicefarm/2015-06-23 INFO : root : copying build/lib/botocore/data/devicefarm/2015-06-23/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/devicefarm/2015-06-23 INFO : root : copying build/lib/botocore/data/devicefarm/2015-06-23/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/devicefarm/2015-06-23 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/detective INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/detective/2018-10-26 INFO : root : copying build/lib/botocore/data/detective/2018-10-26/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/detective/2018-10-26 INFO : root : copying build/lib/botocore/data/detective/2018-10-26/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/detective/2018-10-26 INFO : root : copying build/lib/botocore/data/detective/2018-10-26/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/detective/2018-10-26 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/dax INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/dax/2017-04-19 INFO : root : copying build/lib/botocore/data/dax/2017-04-19/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/dax/2017-04-19 INFO : root : copying build/lib/botocore/data/dax/2017-04-19/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/dax/2017-04-19 INFO : root : copying build/lib/botocore/data/dax/2017-04-19/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/dax/2017-04-19 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/datasync INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/datasync/2018-11-09 INFO : root : copying build/lib/botocore/data/datasync/2018-11-09/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/datasync/2018-11-09 INFO : root : copying build/lib/botocore/data/datasync/2018-11-09/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/datasync/2018-11-09 INFO : root : copying build/lib/botocore/data/datasync/2018-11-09/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/datasync/2018-11-09 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/datapipeline INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/datapipeline/2012-10-29 INFO : root : copying build/lib/botocore/data/datapipeline/2012-10-29/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/datapipeline/2012-10-29 INFO : root : copying build/lib/botocore/data/datapipeline/2012-10-29/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/datapipeline/2012-10-29 INFO : root : copying build/lib/botocore/data/datapipeline/2012-10-29/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/datapipeline/2012-10-29 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/dataexchange INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/dataexchange/2017-07-25 INFO : root : copying build/lib/botocore/data/dataexchange/2017-07-25/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/dataexchange/2017-07-25 INFO : root : copying build/lib/botocore/data/dataexchange/2017-07-25/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/dataexchange/2017-07-25 INFO : root : copying build/lib/botocore/data/dataexchange/2017-07-25/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/dataexchange/2017-07-25 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/databrew INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/databrew/2017-07-25 INFO : root : copying build/lib/botocore/data/databrew/2017-07-25/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/databrew/2017-07-25 INFO : root : copying build/lib/botocore/data/databrew/2017-07-25/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/databrew/2017-07-25 INFO : root : copying build/lib/botocore/data/databrew/2017-07-25/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/databrew/2017-07-25 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/customer-profiles INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/customer-profiles/2020-08-15 INFO : root : copying build/lib/botocore/data/customer-profiles/2020-08-15/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/customer-profiles/2020-08-15 INFO : root : copying build/lib/botocore/data/customer-profiles/2020-08-15/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/customer-profiles/2020-08-15 INFO : root : copying build/lib/botocore/data/customer-profiles/2020-08-15/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/customer-profiles/2020-08-15 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cur INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cur/2017-01-06 INFO : root : copying build/lib/botocore/data/cur/2017-01-06/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cur/2017-01-06 INFO : root : copying build/lib/botocore/data/cur/2017-01-06/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/cur/2017-01-06 INFO : root : copying build/lib/botocore/data/cur/2017-01-06/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/cur/2017-01-06 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/controltower INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/controltower/2018-05-10 INFO : root : copying build/lib/botocore/data/controltower/2018-05-10/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/controltower/2018-05-10 INFO : root : copying build/lib/botocore/data/controltower/2018-05-10/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/controltower/2018-05-10 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/connectparticipant INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/connectparticipant/2018-09-07 INFO : root : copying build/lib/botocore/data/connectparticipant/2018-09-07/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/connectparticipant/2018-09-07 INFO : root : copying build/lib/botocore/data/connectparticipant/2018-09-07/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/connectparticipant/2018-09-07 INFO : root : copying build/lib/botocore/data/connectparticipant/2018-09-07/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/connectparticipant/2018-09-07 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/connectcases INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/connectcases/2022-10-03 INFO : root : copying build/lib/botocore/data/connectcases/2022-10-03/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/connectcases/2022-10-03 INFO : root : copying build/lib/botocore/data/connectcases/2022-10-03/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/connectcases/2022-10-03 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/connectcampaigns INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/connectcampaigns/2021-01-30 INFO : root : copying build/lib/botocore/data/connectcampaigns/2021-01-30/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/connectcampaigns/2021-01-30 INFO : root : copying build/lib/botocore/data/connectcampaigns/2021-01-30/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/connectcampaigns/2021-01-30 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/connect INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/connect/2017-08-08 INFO : root : copying build/lib/botocore/data/connect/2017-08-08/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/connect/2017-08-08 INFO : root : copying build/lib/botocore/data/connect/2017-08-08/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/connect/2017-08-08 INFO : root : copying build/lib/botocore/data/connect/2017-08-08/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/connect/2017-08-08 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/connect-contact-lens INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/connect-contact-lens/2020-08-21 INFO : root : copying build/lib/botocore/data/connect-contact-lens/2020-08-21/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/connect-contact-lens/2020-08-21 INFO : root : copying build/lib/botocore/data/connect-contact-lens/2020-08-21/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/connect-contact-lens/2020-08-21 INFO : root : copying build/lib/botocore/data/connect-contact-lens/2020-08-21/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/connect-contact-lens/2020-08-21 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/config INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/config/2014-11-12 INFO : root : copying build/lib/botocore/data/config/2014-11-12/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/config/2014-11-12 INFO : root : copying build/lib/botocore/data/config/2014-11-12/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/config/2014-11-12 INFO : root : copying build/lib/botocore/data/config/2014-11-12/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/config/2014-11-12 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/compute-optimizer INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/compute-optimizer/2019-11-01 INFO : root : copying build/lib/botocore/data/compute-optimizer/2019-11-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/compute-optimizer/2019-11-01 INFO : root : copying build/lib/botocore/data/compute-optimizer/2019-11-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/compute-optimizer/2019-11-01 INFO : root : copying build/lib/botocore/data/compute-optimizer/2019-11-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/compute-optimizer/2019-11-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/comprehendmedical INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/comprehendmedical/2018-10-30 INFO : root : copying build/lib/botocore/data/comprehendmedical/2018-10-30/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/comprehendmedical/2018-10-30 INFO : root : copying build/lib/botocore/data/comprehendmedical/2018-10-30/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/comprehendmedical/2018-10-30 INFO : root : copying build/lib/botocore/data/comprehendmedical/2018-10-30/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/comprehendmedical/2018-10-30 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/comprehend INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/comprehend/2017-11-27 INFO : root : copying build/lib/botocore/data/comprehend/2017-11-27/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/comprehend/2017-11-27 INFO : root : copying build/lib/botocore/data/comprehend/2017-11-27/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/comprehend/2017-11-27 INFO : root : copying build/lib/botocore/data/comprehend/2017-11-27/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/comprehend/2017-11-27 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cognito-sync INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cognito-sync/2014-06-30 INFO : root : copying build/lib/botocore/data/cognito-sync/2014-06-30/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cognito-sync/2014-06-30 INFO : root : copying build/lib/botocore/data/cognito-sync/2014-06-30/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/cognito-sync/2014-06-30 INFO : root : copying build/lib/botocore/data/cognito-sync/2014-06-30/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/cognito-sync/2014-06-30 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cognito-idp INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cognito-idp/2016-04-18 INFO : root : copying build/lib/botocore/data/cognito-idp/2016-04-18/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cognito-idp/2016-04-18 INFO : root : copying build/lib/botocore/data/cognito-idp/2016-04-18/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/cognito-idp/2016-04-18 INFO : root : copying build/lib/botocore/data/cognito-idp/2016-04-18/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/cognito-idp/2016-04-18 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cognito-identity INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cognito-identity/2014-06-30 INFO : root : copying build/lib/botocore/data/cognito-identity/2014-06-30/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cognito-identity/2014-06-30 INFO : root : copying build/lib/botocore/data/cognito-identity/2014-06-30/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/cognito-identity/2014-06-30 INFO : root : copying build/lib/botocore/data/cognito-identity/2014-06-30/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/cognito-identity/2014-06-30 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/codestar INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/codestar/2017-04-19 INFO : root : copying build/lib/botocore/data/codestar/2017-04-19/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/codestar/2017-04-19 INFO : root : copying build/lib/botocore/data/codestar/2017-04-19/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/codestar/2017-04-19 INFO : root : copying build/lib/botocore/data/codestar/2017-04-19/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/codestar/2017-04-19 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/codestar-notifications INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/codestar-notifications/2019-10-15 INFO : root : copying build/lib/botocore/data/codestar-notifications/2019-10-15/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/codestar-notifications/2019-10-15 INFO : root : copying build/lib/botocore/data/codestar-notifications/2019-10-15/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/codestar-notifications/2019-10-15 INFO : root : copying build/lib/botocore/data/codestar-notifications/2019-10-15/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/codestar-notifications/2019-10-15 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/codestar-connections INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/codestar-connections/2019-12-01 INFO : root : copying build/lib/botocore/data/codestar-connections/2019-12-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/codestar-connections/2019-12-01 INFO : root : copying build/lib/botocore/data/codestar-connections/2019-12-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/codestar-connections/2019-12-01 INFO : root : copying build/lib/botocore/data/codestar-connections/2019-12-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/codestar-connections/2019-12-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/codepipeline INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/codepipeline/2015-07-09 INFO : root : copying build/lib/botocore/data/codepipeline/2015-07-09/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/codepipeline/2015-07-09 INFO : root : copying build/lib/botocore/data/codepipeline/2015-07-09/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/codepipeline/2015-07-09 INFO : root : copying build/lib/botocore/data/codepipeline/2015-07-09/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/codepipeline/2015-07-09 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/codeguruprofiler INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/codeguruprofiler/2019-07-18 INFO : root : copying build/lib/botocore/data/codeguruprofiler/2019-07-18/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/codeguruprofiler/2019-07-18 INFO : root : copying build/lib/botocore/data/codeguruprofiler/2019-07-18/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/codeguruprofiler/2019-07-18 INFO : root : copying build/lib/botocore/data/codeguruprofiler/2019-07-18/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/codeguruprofiler/2019-07-18 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/codeguru-reviewer INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/codeguru-reviewer/2019-09-19 INFO : root : copying build/lib/botocore/data/codeguru-reviewer/2019-09-19/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/codeguru-reviewer/2019-09-19 INFO : root : copying build/lib/botocore/data/codeguru-reviewer/2019-09-19/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/codeguru-reviewer/2019-09-19 INFO : root : copying build/lib/botocore/data/codeguru-reviewer/2019-09-19/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/codeguru-reviewer/2019-09-19 INFO : root : copying build/lib/botocore/data/codeguru-reviewer/2019-09-19/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/codeguru-reviewer/2019-09-19 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/codedeploy INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/codedeploy/2014-10-06 INFO : root : copying build/lib/botocore/data/codedeploy/2014-10-06/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/codedeploy/2014-10-06 INFO : root : copying build/lib/botocore/data/codedeploy/2014-10-06/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/codedeploy/2014-10-06 INFO : root : copying build/lib/botocore/data/codedeploy/2014-10-06/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/codedeploy/2014-10-06 INFO : root : copying build/lib/botocore/data/codedeploy/2014-10-06/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/codedeploy/2014-10-06 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/codecommit INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/codecommit/2015-04-13 INFO : root : copying build/lib/botocore/data/codecommit/2015-04-13/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/codecommit/2015-04-13 INFO : root : copying build/lib/botocore/data/codecommit/2015-04-13/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/codecommit/2015-04-13 INFO : root : copying build/lib/botocore/data/codecommit/2015-04-13/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/codecommit/2015-04-13 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/codebuild INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/codebuild/2016-10-06 INFO : root : copying build/lib/botocore/data/codebuild/2016-10-06/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/codebuild/2016-10-06 INFO : root : copying build/lib/botocore/data/codebuild/2016-10-06/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/codebuild/2016-10-06 INFO : root : copying build/lib/botocore/data/codebuild/2016-10-06/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/codebuild/2016-10-06 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/codeartifact INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/codeartifact/2018-09-22 INFO : root : copying build/lib/botocore/data/codeartifact/2018-09-22/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/codeartifact/2018-09-22 INFO : root : copying build/lib/botocore/data/codeartifact/2018-09-22/paginators-1.sdk-extras.json -> build/bdist.linux-i686/wheel/botocore/data/codeartifact/2018-09-22 INFO : root : copying build/lib/botocore/data/codeartifact/2018-09-22/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/codeartifact/2018-09-22 INFO : root : copying build/lib/botocore/data/codeartifact/2018-09-22/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/codeartifact/2018-09-22 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudwatch INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudwatch/2010-08-01 INFO : root : copying build/lib/botocore/data/cloudwatch/2010-08-01/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudwatch/2010-08-01 INFO : root : copying build/lib/botocore/data/cloudwatch/2010-08-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudwatch/2010-08-01 INFO : root : copying build/lib/botocore/data/cloudwatch/2010-08-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudwatch/2010-08-01 INFO : root : copying build/lib/botocore/data/cloudwatch/2010-08-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudwatch/2010-08-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudtrail INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudtrail/2013-11-01 INFO : root : copying build/lib/botocore/data/cloudtrail/2013-11-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudtrail/2013-11-01 INFO : root : copying build/lib/botocore/data/cloudtrail/2013-11-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudtrail/2013-11-01 INFO : root : copying build/lib/botocore/data/cloudtrail/2013-11-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudtrail/2013-11-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudsearchdomain INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudsearchdomain/2013-01-01 INFO : root : copying build/lib/botocore/data/cloudsearchdomain/2013-01-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudsearchdomain/2013-01-01 INFO : root : copying build/lib/botocore/data/cloudsearchdomain/2013-01-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudsearchdomain/2013-01-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudsearch INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudsearch/2013-01-01 INFO : root : copying build/lib/botocore/data/cloudsearch/2013-01-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudsearch/2013-01-01 INFO : root : copying build/lib/botocore/data/cloudsearch/2013-01-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudsearch/2013-01-01 INFO : root : copying build/lib/botocore/data/cloudsearch/2013-01-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudsearch/2013-01-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudsearch/2011-02-01 INFO : root : copying build/lib/botocore/data/cloudsearch/2011-02-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudsearch/2011-02-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudhsmv2 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudhsmv2/2017-04-28 INFO : root : copying build/lib/botocore/data/cloudhsmv2/2017-04-28/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudhsmv2/2017-04-28 INFO : root : copying build/lib/botocore/data/cloudhsmv2/2017-04-28/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudhsmv2/2017-04-28 INFO : root : copying build/lib/botocore/data/cloudhsmv2/2017-04-28/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudhsmv2/2017-04-28 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudhsm INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudhsm/2014-05-30 INFO : root : copying build/lib/botocore/data/cloudhsm/2014-05-30/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudhsm/2014-05-30 INFO : root : copying build/lib/botocore/data/cloudhsm/2014-05-30/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudhsm/2014-05-30 INFO : root : copying build/lib/botocore/data/cloudhsm/2014-05-30/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudhsm/2014-05-30 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudfront INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudfront/2020-05-31 INFO : root : copying build/lib/botocore/data/cloudfront/2020-05-31/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2020-05-31 INFO : root : copying build/lib/botocore/data/cloudfront/2020-05-31/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2020-05-31 INFO : root : copying build/lib/botocore/data/cloudfront/2020-05-31/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2020-05-31 INFO : root : copying build/lib/botocore/data/cloudfront/2020-05-31/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2020-05-31 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudfront/2019-03-26 INFO : root : copying build/lib/botocore/data/cloudfront/2019-03-26/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2019-03-26 INFO : root : copying build/lib/botocore/data/cloudfront/2019-03-26/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2019-03-26 INFO : root : copying build/lib/botocore/data/cloudfront/2019-03-26/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2019-03-26 INFO : root : copying build/lib/botocore/data/cloudfront/2019-03-26/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2019-03-26 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudfront/2018-11-05 INFO : root : copying build/lib/botocore/data/cloudfront/2018-11-05/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2018-11-05 INFO : root : copying build/lib/botocore/data/cloudfront/2018-11-05/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2018-11-05 INFO : root : copying build/lib/botocore/data/cloudfront/2018-11-05/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2018-11-05 INFO : root : copying build/lib/botocore/data/cloudfront/2018-11-05/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2018-11-05 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudfront/2018-06-18 INFO : root : copying build/lib/botocore/data/cloudfront/2018-06-18/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2018-06-18 INFO : root : copying build/lib/botocore/data/cloudfront/2018-06-18/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2018-06-18 INFO : root : copying build/lib/botocore/data/cloudfront/2018-06-18/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2018-06-18 INFO : root : copying build/lib/botocore/data/cloudfront/2018-06-18/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2018-06-18 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudfront/2017-10-30 INFO : root : copying build/lib/botocore/data/cloudfront/2017-10-30/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2017-10-30 INFO : root : copying build/lib/botocore/data/cloudfront/2017-10-30/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2017-10-30 INFO : root : copying build/lib/botocore/data/cloudfront/2017-10-30/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2017-10-30 INFO : root : copying build/lib/botocore/data/cloudfront/2017-10-30/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2017-10-30 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudfront/2017-03-25 INFO : root : copying build/lib/botocore/data/cloudfront/2017-03-25/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2017-03-25 INFO : root : copying build/lib/botocore/data/cloudfront/2017-03-25/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2017-03-25 INFO : root : copying build/lib/botocore/data/cloudfront/2017-03-25/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2017-03-25 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-11-25 INFO : root : copying build/lib/botocore/data/cloudfront/2016-11-25/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-11-25 INFO : root : copying build/lib/botocore/data/cloudfront/2016-11-25/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-11-25 INFO : root : copying build/lib/botocore/data/cloudfront/2016-11-25/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-11-25 INFO : root : copying build/lib/botocore/data/cloudfront/2016-11-25/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-11-25 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-09-29 INFO : root : copying build/lib/botocore/data/cloudfront/2016-09-29/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-09-29 INFO : root : copying build/lib/botocore/data/cloudfront/2016-09-29/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-09-29 INFO : root : copying build/lib/botocore/data/cloudfront/2016-09-29/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-09-29 INFO : root : copying build/lib/botocore/data/cloudfront/2016-09-29/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-09-29 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-09-07 INFO : root : copying build/lib/botocore/data/cloudfront/2016-09-07/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-09-07 INFO : root : copying build/lib/botocore/data/cloudfront/2016-09-07/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-09-07 INFO : root : copying build/lib/botocore/data/cloudfront/2016-09-07/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-09-07 INFO : root : copying build/lib/botocore/data/cloudfront/2016-09-07/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-09-07 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-08-20 INFO : root : copying build/lib/botocore/data/cloudfront/2016-08-20/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-08-20 INFO : root : copying build/lib/botocore/data/cloudfront/2016-08-20/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-08-20 INFO : root : copying build/lib/botocore/data/cloudfront/2016-08-20/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-08-20 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-08-01 INFO : root : copying build/lib/botocore/data/cloudfront/2016-08-01/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-08-01 INFO : root : copying build/lib/botocore/data/cloudfront/2016-08-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-08-01 INFO : root : copying build/lib/botocore/data/cloudfront/2016-08-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-08-01 INFO : root : copying build/lib/botocore/data/cloudfront/2016-08-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-08-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-01-28 INFO : root : copying build/lib/botocore/data/cloudfront/2016-01-28/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-01-28 INFO : root : copying build/lib/botocore/data/cloudfront/2016-01-28/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-01-28 INFO : root : copying build/lib/botocore/data/cloudfront/2016-01-28/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-01-28 INFO : root : copying build/lib/botocore/data/cloudfront/2016-01-28/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-01-28 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-01-13 INFO : root : copying build/lib/botocore/data/cloudfront/2016-01-13/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-01-13 INFO : root : copying build/lib/botocore/data/cloudfront/2016-01-13/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-01-13 INFO : root : copying build/lib/botocore/data/cloudfront/2016-01-13/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2016-01-13 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudfront/2015-09-17 INFO : root : copying build/lib/botocore/data/cloudfront/2015-09-17/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2015-09-17 INFO : root : copying build/lib/botocore/data/cloudfront/2015-09-17/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2015-09-17 INFO : root : copying build/lib/botocore/data/cloudfront/2015-09-17/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2015-09-17 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudfront/2015-07-27 INFO : root : copying build/lib/botocore/data/cloudfront/2015-07-27/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2015-07-27 INFO : root : copying build/lib/botocore/data/cloudfront/2015-07-27/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2015-07-27 INFO : root : copying build/lib/botocore/data/cloudfront/2015-07-27/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2015-07-27 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudfront/2015-04-17 INFO : root : copying build/lib/botocore/data/cloudfront/2015-04-17/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2015-04-17 INFO : root : copying build/lib/botocore/data/cloudfront/2015-04-17/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2015-04-17 INFO : root : copying build/lib/botocore/data/cloudfront/2015-04-17/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2015-04-17 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudfront/2014-11-06 INFO : root : copying build/lib/botocore/data/cloudfront/2014-11-06/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2014-11-06 INFO : root : copying build/lib/botocore/data/cloudfront/2014-11-06/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2014-11-06 INFO : root : copying build/lib/botocore/data/cloudfront/2014-11-06/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2014-11-06 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudfront/2014-10-21 INFO : root : copying build/lib/botocore/data/cloudfront/2014-10-21/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2014-10-21 INFO : root : copying build/lib/botocore/data/cloudfront/2014-10-21/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2014-10-21 INFO : root : copying build/lib/botocore/data/cloudfront/2014-10-21/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2014-10-21 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudfront/2014-05-31 INFO : root : copying build/lib/botocore/data/cloudfront/2014-05-31/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2014-05-31 INFO : root : copying build/lib/botocore/data/cloudfront/2014-05-31/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2014-05-31 INFO : root : copying build/lib/botocore/data/cloudfront/2014-05-31/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudfront/2014-05-31 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudformation INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudformation/2010-05-15 INFO : root : copying build/lib/botocore/data/cloudformation/2010-05-15/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudformation/2010-05-15 INFO : root : copying build/lib/botocore/data/cloudformation/2010-05-15/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudformation/2010-05-15 INFO : root : copying build/lib/botocore/data/cloudformation/2010-05-15/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudformation/2010-05-15 INFO : root : copying build/lib/botocore/data/cloudformation/2010-05-15/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudformation/2010-05-15 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/clouddirectory INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/clouddirectory/2017-01-11 INFO : root : copying build/lib/botocore/data/clouddirectory/2017-01-11/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/clouddirectory/2017-01-11 INFO : root : copying build/lib/botocore/data/clouddirectory/2017-01-11/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/clouddirectory/2017-01-11 INFO : root : copying build/lib/botocore/data/clouddirectory/2017-01-11/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/clouddirectory/2017-01-11 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/clouddirectory/2016-05-10 INFO : root : copying build/lib/botocore/data/clouddirectory/2016-05-10/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/clouddirectory/2016-05-10 INFO : root : copying build/lib/botocore/data/clouddirectory/2016-05-10/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/clouddirectory/2016-05-10 INFO : root : copying build/lib/botocore/data/clouddirectory/2016-05-10/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/clouddirectory/2016-05-10 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudcontrol INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloudcontrol/2021-09-30 INFO : root : copying build/lib/botocore/data/cloudcontrol/2021-09-30/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudcontrol/2021-09-30 INFO : root : copying build/lib/botocore/data/cloudcontrol/2021-09-30/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloudcontrol/2021-09-30 INFO : root : copying build/lib/botocore/data/cloudcontrol/2021-09-30/paginators-1.sdk-extras.json -> build/bdist.linux-i686/wheel/botocore/data/cloudcontrol/2021-09-30 INFO : root : copying build/lib/botocore/data/cloudcontrol/2021-09-30/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudcontrol/2021-09-30 INFO : root : copying build/lib/botocore/data/cloudcontrol/2021-09-30/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloudcontrol/2021-09-30 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloud9 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/cloud9/2017-09-23 INFO : root : copying build/lib/botocore/data/cloud9/2017-09-23/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/cloud9/2017-09-23 INFO : root : copying build/lib/botocore/data/cloud9/2017-09-23/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloud9/2017-09-23 INFO : root : copying build/lib/botocore/data/cloud9/2017-09-23/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/cloud9/2017-09-23 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/chime INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/chime/2018-05-01 INFO : root : copying build/lib/botocore/data/chime/2018-05-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/chime/2018-05-01 INFO : root : copying build/lib/botocore/data/chime/2018-05-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/chime/2018-05-01 INFO : root : copying build/lib/botocore/data/chime/2018-05-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/chime/2018-05-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/chime-sdk-messaging INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/chime-sdk-messaging/2021-05-15 INFO : root : copying build/lib/botocore/data/chime-sdk-messaging/2021-05-15/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/chime-sdk-messaging/2021-05-15 INFO : root : copying build/lib/botocore/data/chime-sdk-messaging/2021-05-15/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/chime-sdk-messaging/2021-05-15 INFO : root : copying build/lib/botocore/data/chime-sdk-messaging/2021-05-15/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/chime-sdk-messaging/2021-05-15 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/chime-sdk-meetings INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/chime-sdk-meetings/2021-07-15 INFO : root : copying build/lib/botocore/data/chime-sdk-meetings/2021-07-15/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/chime-sdk-meetings/2021-07-15 INFO : root : copying build/lib/botocore/data/chime-sdk-meetings/2021-07-15/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/chime-sdk-meetings/2021-07-15 INFO : root : copying build/lib/botocore/data/chime-sdk-meetings/2021-07-15/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/chime-sdk-meetings/2021-07-15 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/chime-sdk-media-pipelines INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/chime-sdk-media-pipelines/2021-07-15 INFO : root : copying build/lib/botocore/data/chime-sdk-media-pipelines/2021-07-15/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/chime-sdk-media-pipelines/2021-07-15 INFO : root : copying build/lib/botocore/data/chime-sdk-media-pipelines/2021-07-15/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/chime-sdk-media-pipelines/2021-07-15 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/chime-sdk-identity INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/chime-sdk-identity/2021-04-20 INFO : root : copying build/lib/botocore/data/chime-sdk-identity/2021-04-20/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/chime-sdk-identity/2021-04-20 INFO : root : copying build/lib/botocore/data/chime-sdk-identity/2021-04-20/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/chime-sdk-identity/2021-04-20 INFO : root : copying build/lib/botocore/data/chime-sdk-identity/2021-04-20/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/chime-sdk-identity/2021-04-20 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ce INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/ce/2017-10-25 INFO : root : copying build/lib/botocore/data/ce/2017-10-25/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/ce/2017-10-25 INFO : root : copying build/lib/botocore/data/ce/2017-10-25/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/ce/2017-10-25 INFO : root : copying build/lib/botocore/data/ce/2017-10-25/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/ce/2017-10-25 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/budgets INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/budgets/2016-10-20 INFO : root : copying build/lib/botocore/data/budgets/2016-10-20/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/budgets/2016-10-20 INFO : root : copying build/lib/botocore/data/budgets/2016-10-20/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/budgets/2016-10-20 INFO : root : copying build/lib/botocore/data/budgets/2016-10-20/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/budgets/2016-10-20 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/braket INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/braket/2019-09-01 INFO : root : copying build/lib/botocore/data/braket/2019-09-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/braket/2019-09-01 INFO : root : copying build/lib/botocore/data/braket/2019-09-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/braket/2019-09-01 INFO : root : copying build/lib/botocore/data/braket/2019-09-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/braket/2019-09-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/billingconductor INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/billingconductor/2021-07-30 INFO : root : copying build/lib/botocore/data/billingconductor/2021-07-30/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/billingconductor/2021-07-30 INFO : root : copying build/lib/botocore/data/billingconductor/2021-07-30/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/billingconductor/2021-07-30 INFO : root : copying build/lib/botocore/data/billingconductor/2021-07-30/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/billingconductor/2021-07-30 INFO : root : copying build/lib/botocore/data/billingconductor/2021-07-30/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/billingconductor/2021-07-30 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/batch INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/batch/2016-08-10 INFO : root : copying build/lib/botocore/data/batch/2016-08-10/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/batch/2016-08-10 INFO : root : copying build/lib/botocore/data/batch/2016-08-10/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/batch/2016-08-10 INFO : root : copying build/lib/botocore/data/batch/2016-08-10/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/batch/2016-08-10 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/backupstorage INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/backupstorage/2018-04-10 INFO : root : copying build/lib/botocore/data/backupstorage/2018-04-10/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/backupstorage/2018-04-10 INFO : root : copying build/lib/botocore/data/backupstorage/2018-04-10/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/backupstorage/2018-04-10 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/backup INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/backup/2018-11-15 INFO : root : copying build/lib/botocore/data/backup/2018-11-15/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/backup/2018-11-15 INFO : root : copying build/lib/botocore/data/backup/2018-11-15/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/backup/2018-11-15 INFO : root : copying build/lib/botocore/data/backup/2018-11-15/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/backup/2018-11-15 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/backup-gateway INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/backup-gateway/2021-01-01 INFO : root : copying build/lib/botocore/data/backup-gateway/2021-01-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/backup-gateway/2021-01-01 INFO : root : copying build/lib/botocore/data/backup-gateway/2021-01-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/backup-gateway/2021-01-01 INFO : root : copying build/lib/botocore/data/backup-gateway/2021-01-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/backup-gateway/2021-01-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/autoscaling INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/autoscaling/2011-01-01 INFO : root : copying build/lib/botocore/data/autoscaling/2011-01-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/autoscaling/2011-01-01 INFO : root : copying build/lib/botocore/data/autoscaling/2011-01-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/autoscaling/2011-01-01 INFO : root : copying build/lib/botocore/data/autoscaling/2011-01-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/autoscaling/2011-01-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/autoscaling-plans INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/autoscaling-plans/2018-01-06 INFO : root : copying build/lib/botocore/data/autoscaling-plans/2018-01-06/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/autoscaling-plans/2018-01-06 INFO : root : copying build/lib/botocore/data/autoscaling-plans/2018-01-06/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/autoscaling-plans/2018-01-06 INFO : root : copying build/lib/botocore/data/autoscaling-plans/2018-01-06/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/autoscaling-plans/2018-01-06 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/auditmanager INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/auditmanager/2017-07-25 INFO : root : copying build/lib/botocore/data/auditmanager/2017-07-25/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/auditmanager/2017-07-25 INFO : root : copying build/lib/botocore/data/auditmanager/2017-07-25/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/auditmanager/2017-07-25 INFO : root : copying build/lib/botocore/data/auditmanager/2017-07-25/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/auditmanager/2017-07-25 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/athena INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/athena/2017-05-18 INFO : root : copying build/lib/botocore/data/athena/2017-05-18/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/athena/2017-05-18 INFO : root : copying build/lib/botocore/data/athena/2017-05-18/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/athena/2017-05-18 INFO : root : copying build/lib/botocore/data/athena/2017-05-18/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/athena/2017-05-18 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/appsync INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/appsync/2017-07-25 INFO : root : copying build/lib/botocore/data/appsync/2017-07-25/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/appsync/2017-07-25 INFO : root : copying build/lib/botocore/data/appsync/2017-07-25/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/appsync/2017-07-25 INFO : root : copying build/lib/botocore/data/appsync/2017-07-25/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/appsync/2017-07-25 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/appstream INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/appstream/2016-12-01 INFO : root : copying build/lib/botocore/data/appstream/2016-12-01/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/appstream/2016-12-01 INFO : root : copying build/lib/botocore/data/appstream/2016-12-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/appstream/2016-12-01 INFO : root : copying build/lib/botocore/data/appstream/2016-12-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/appstream/2016-12-01 INFO : root : copying build/lib/botocore/data/appstream/2016-12-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/appstream/2016-12-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/apprunner INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/apprunner/2020-05-15 INFO : root : copying build/lib/botocore/data/apprunner/2020-05-15/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/apprunner/2020-05-15 INFO : root : copying build/lib/botocore/data/apprunner/2020-05-15/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/apprunner/2020-05-15 INFO : root : copying build/lib/botocore/data/apprunner/2020-05-15/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/apprunner/2020-05-15 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/appmesh INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/appmesh/2019-01-25 INFO : root : copying build/lib/botocore/data/appmesh/2019-01-25/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/appmesh/2019-01-25 INFO : root : copying build/lib/botocore/data/appmesh/2019-01-25/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/appmesh/2019-01-25 INFO : root : copying build/lib/botocore/data/appmesh/2019-01-25/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/appmesh/2019-01-25 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/appmesh/2018-10-01 INFO : root : copying build/lib/botocore/data/appmesh/2018-10-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/appmesh/2018-10-01 INFO : root : copying build/lib/botocore/data/appmesh/2018-10-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/appmesh/2018-10-01 INFO : root : copying build/lib/botocore/data/appmesh/2018-10-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/appmesh/2018-10-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/applicationcostprofiler INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/applicationcostprofiler/2020-09-10 INFO : root : copying build/lib/botocore/data/applicationcostprofiler/2020-09-10/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/applicationcostprofiler/2020-09-10 INFO : root : copying build/lib/botocore/data/applicationcostprofiler/2020-09-10/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/applicationcostprofiler/2020-09-10 INFO : root : copying build/lib/botocore/data/applicationcostprofiler/2020-09-10/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/applicationcostprofiler/2020-09-10 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/application-insights INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/application-insights/2018-11-25 INFO : root : copying build/lib/botocore/data/application-insights/2018-11-25/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/application-insights/2018-11-25 INFO : root : copying build/lib/botocore/data/application-insights/2018-11-25/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/application-insights/2018-11-25 INFO : root : copying build/lib/botocore/data/application-insights/2018-11-25/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/application-insights/2018-11-25 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/application-autoscaling INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/application-autoscaling/2016-02-06 INFO : root : copying build/lib/botocore/data/application-autoscaling/2016-02-06/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/application-autoscaling/2016-02-06 INFO : root : copying build/lib/botocore/data/application-autoscaling/2016-02-06/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/application-autoscaling/2016-02-06 INFO : root : copying build/lib/botocore/data/application-autoscaling/2016-02-06/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/application-autoscaling/2016-02-06 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/appintegrations INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/appintegrations/2020-07-29 INFO : root : copying build/lib/botocore/data/appintegrations/2020-07-29/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/appintegrations/2020-07-29 INFO : root : copying build/lib/botocore/data/appintegrations/2020-07-29/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/appintegrations/2020-07-29 INFO : root : copying build/lib/botocore/data/appintegrations/2020-07-29/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/appintegrations/2020-07-29 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/appflow INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/appflow/2020-08-23 INFO : root : copying build/lib/botocore/data/appflow/2020-08-23/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/appflow/2020-08-23 INFO : root : copying build/lib/botocore/data/appflow/2020-08-23/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/appflow/2020-08-23 INFO : root : copying build/lib/botocore/data/appflow/2020-08-23/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/appflow/2020-08-23 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/appconfigdata INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/appconfigdata/2021-11-11 INFO : root : copying build/lib/botocore/data/appconfigdata/2021-11-11/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/appconfigdata/2021-11-11 INFO : root : copying build/lib/botocore/data/appconfigdata/2021-11-11/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/appconfigdata/2021-11-11 INFO : root : copying build/lib/botocore/data/appconfigdata/2021-11-11/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/appconfigdata/2021-11-11 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/appconfig INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/appconfig/2019-10-09 INFO : root : copying build/lib/botocore/data/appconfig/2019-10-09/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/appconfig/2019-10-09 INFO : root : copying build/lib/botocore/data/appconfig/2019-10-09/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/appconfig/2019-10-09 INFO : root : copying build/lib/botocore/data/appconfig/2019-10-09/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/appconfig/2019-10-09 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/apigatewayv2 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/apigatewayv2/2018-11-29 INFO : root : copying build/lib/botocore/data/apigatewayv2/2018-11-29/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/apigatewayv2/2018-11-29 INFO : root : copying build/lib/botocore/data/apigatewayv2/2018-11-29/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/apigatewayv2/2018-11-29 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/apigatewaymanagementapi INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/apigatewaymanagementapi/2018-11-29 INFO : root : copying build/lib/botocore/data/apigatewaymanagementapi/2018-11-29/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/apigatewaymanagementapi/2018-11-29 INFO : root : copying build/lib/botocore/data/apigatewaymanagementapi/2018-11-29/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/apigatewaymanagementapi/2018-11-29 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/apigateway INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/apigateway/2015-07-09 INFO : root : copying build/lib/botocore/data/apigateway/2015-07-09/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/apigateway/2015-07-09 INFO : root : copying build/lib/botocore/data/apigateway/2015-07-09/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/apigateway/2015-07-09 INFO : root : copying build/lib/botocore/data/apigateway/2015-07-09/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/apigateway/2015-07-09 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/amplifyuibuilder INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/amplifyuibuilder/2021-08-11 INFO : root : copying build/lib/botocore/data/amplifyuibuilder/2021-08-11/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/amplifyuibuilder/2021-08-11 INFO : root : copying build/lib/botocore/data/amplifyuibuilder/2021-08-11/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/amplifyuibuilder/2021-08-11 INFO : root : copying build/lib/botocore/data/amplifyuibuilder/2021-08-11/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/amplifyuibuilder/2021-08-11 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/amplifybackend INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/amplifybackend/2020-08-11 INFO : root : copying build/lib/botocore/data/amplifybackend/2020-08-11/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/amplifybackend/2020-08-11 INFO : root : copying build/lib/botocore/data/amplifybackend/2020-08-11/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/amplifybackend/2020-08-11 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/amplify INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/amplify/2017-07-25 INFO : root : copying build/lib/botocore/data/amplify/2017-07-25/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/amplify/2017-07-25 INFO : root : copying build/lib/botocore/data/amplify/2017-07-25/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/amplify/2017-07-25 INFO : root : copying build/lib/botocore/data/amplify/2017-07-25/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/amplify/2017-07-25 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/amp INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/amp/2020-08-01 INFO : root : copying build/lib/botocore/data/amp/2020-08-01/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/amp/2020-08-01 INFO : root : copying build/lib/botocore/data/amp/2020-08-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/amp/2020-08-01 INFO : root : copying build/lib/botocore/data/amp/2020-08-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/amp/2020-08-01 INFO : root : copying build/lib/botocore/data/amp/2020-08-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/amp/2020-08-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/alexaforbusiness INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/alexaforbusiness/2017-11-09 INFO : root : copying build/lib/botocore/data/alexaforbusiness/2017-11-09/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/alexaforbusiness/2017-11-09 INFO : root : copying build/lib/botocore/data/alexaforbusiness/2017-11-09/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/alexaforbusiness/2017-11-09 INFO : root : copying build/lib/botocore/data/alexaforbusiness/2017-11-09/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/alexaforbusiness/2017-11-09 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/acm INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/acm/2015-12-08 INFO : root : copying build/lib/botocore/data/acm/2015-12-08/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/acm/2015-12-08 INFO : root : copying build/lib/botocore/data/acm/2015-12-08/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/acm/2015-12-08 INFO : root : copying build/lib/botocore/data/acm/2015-12-08/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/acm/2015-12-08 INFO : root : copying build/lib/botocore/data/acm/2015-12-08/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/acm/2015-12-08 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/acm-pca INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/acm-pca/2017-08-22 INFO : root : copying build/lib/botocore/data/acm-pca/2017-08-22/waiters-2.json -> build/bdist.linux-i686/wheel/botocore/data/acm-pca/2017-08-22 INFO : root : copying build/lib/botocore/data/acm-pca/2017-08-22/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/acm-pca/2017-08-22 INFO : root : copying build/lib/botocore/data/acm-pca/2017-08-22/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/acm-pca/2017-08-22 INFO : root : copying build/lib/botocore/data/acm-pca/2017-08-22/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/acm-pca/2017-08-22 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/account INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/account/2021-02-01 INFO : root : copying build/lib/botocore/data/account/2021-02-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/account/2021-02-01 INFO : root : copying build/lib/botocore/data/account/2021-02-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/account/2021-02-01 INFO : root : copying build/lib/botocore/data/account/2021-02-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/account/2021-02-01 INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/accessanalyzer INFO : root : creating build/bdist.linux-i686/wheel/botocore/data/accessanalyzer/2019-11-01 INFO : root : copying build/lib/botocore/data/accessanalyzer/2019-11-01/service-2.json -> build/bdist.linux-i686/wheel/botocore/data/accessanalyzer/2019-11-01 INFO : root : copying build/lib/botocore/data/accessanalyzer/2019-11-01/paginators-1.json -> build/bdist.linux-i686/wheel/botocore/data/accessanalyzer/2019-11-01 INFO : root : copying build/lib/botocore/data/accessanalyzer/2019-11-01/examples-1.json -> build/bdist.linux-i686/wheel/botocore/data/accessanalyzer/2019-11-01 INFO : root : copying build/lib/botocore/data/sdk-default-configuration.json -> build/bdist.linux-i686/wheel/botocore/data INFO : root : copying build/lib/botocore/data/partitions.json -> build/bdist.linux-i686/wheel/botocore/data INFO : root : copying build/lib/botocore/data/endpoints.json -> build/bdist.linux-i686/wheel/botocore/data INFO : root : copying build/lib/botocore/data/_retry.json -> build/bdist.linux-i686/wheel/botocore/data INFO : root : creating build/bdist.linux-i686/wheel/botocore/crt INFO : root : copying build/lib/botocore/crt/__init__.py -> build/bdist.linux-i686/wheel/botocore/crt INFO : root : copying build/lib/botocore/crt/auth.py -> build/bdist.linux-i686/wheel/botocore/crt INFO : root : creating build/bdist.linux-i686/wheel/botocore/docs INFO : root : creating build/bdist.linux-i686/wheel/botocore/docs/bcdoc INFO : root : copying build/lib/botocore/docs/bcdoc/__init__.py -> build/bdist.linux-i686/wheel/botocore/docs/bcdoc INFO : root : copying build/lib/botocore/docs/bcdoc/docstringparser.py -> build/bdist.linux-i686/wheel/botocore/docs/bcdoc INFO : root : copying build/lib/botocore/docs/bcdoc/restdoc.py -> build/bdist.linux-i686/wheel/botocore/docs/bcdoc INFO : root : copying build/lib/botocore/docs/bcdoc/style.py -> build/bdist.linux-i686/wheel/botocore/docs/bcdoc INFO : root : copying build/lib/botocore/docs/__init__.py -> build/bdist.linux-i686/wheel/botocore/docs INFO : root : copying build/lib/botocore/docs/client.py -> build/bdist.linux-i686/wheel/botocore/docs INFO : root : copying build/lib/botocore/docs/docstring.py -> build/bdist.linux-i686/wheel/botocore/docs INFO : root : copying build/lib/botocore/docs/example.py -> build/bdist.linux-i686/wheel/botocore/docs INFO : root : copying build/lib/botocore/docs/method.py -> build/bdist.linux-i686/wheel/botocore/docs INFO : root : copying build/lib/botocore/docs/paginator.py -> build/bdist.linux-i686/wheel/botocore/docs INFO : root : copying build/lib/botocore/docs/params.py -> build/bdist.linux-i686/wheel/botocore/docs INFO : root : copying build/lib/botocore/docs/service.py -> build/bdist.linux-i686/wheel/botocore/docs INFO : root : copying build/lib/botocore/docs/shape.py -> build/bdist.linux-i686/wheel/botocore/docs INFO : root : copying build/lib/botocore/docs/sharedexample.py -> build/bdist.linux-i686/wheel/botocore/docs INFO : root : copying build/lib/botocore/docs/utils.py -> build/bdist.linux-i686/wheel/botocore/docs INFO : root : copying build/lib/botocore/docs/waiter.py -> build/bdist.linux-i686/wheel/botocore/docs INFO : root : creating build/bdist.linux-i686/wheel/botocore/retries INFO : root : copying build/lib/botocore/retries/__init__.py -> build/bdist.linux-i686/wheel/botocore/retries INFO : root : copying build/lib/botocore/retries/adaptive.py -> build/bdist.linux-i686/wheel/botocore/retries INFO : root : copying build/lib/botocore/retries/base.py -> build/bdist.linux-i686/wheel/botocore/retries INFO : root : copying build/lib/botocore/retries/bucket.py -> build/bdist.linux-i686/wheel/botocore/retries INFO : root : copying build/lib/botocore/retries/quota.py -> build/bdist.linux-i686/wheel/botocore/retries INFO : root : copying build/lib/botocore/retries/special.py -> build/bdist.linux-i686/wheel/botocore/retries INFO : root : copying build/lib/botocore/retries/standard.py -> build/bdist.linux-i686/wheel/botocore/retries INFO : root : copying build/lib/botocore/retries/throttling.py -> build/bdist.linux-i686/wheel/botocore/retries INFO : root : creating build/bdist.linux-i686/wheel/botocore/vendored INFO : root : copying build/lib/botocore/vendored/__init__.py -> build/bdist.linux-i686/wheel/botocore/vendored INFO : root : copying build/lib/botocore/__init__.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/args.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/auth.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/awsrequest.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/client.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/compat.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/config.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/configloader.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/configprovider.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/credentials.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/discovery.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/endpoint.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/endpoint_provider.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/errorfactory.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/eventstream.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/exceptions.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/handlers.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/history.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/hooks.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/httpchecksum.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/loaders.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/model.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/monitoring.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/paginate.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/parsers.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/regions.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/response.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/retryhandler.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/serialize.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/session.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/signers.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/stub.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/tokens.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/translate.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/utils.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/validate.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/waiter.py -> build/bdist.linux-i686/wheel/botocore INFO : root : copying build/lib/botocore/httpsession.py -> build/bdist.linux-i686/wheel/botocore INFO : root : running install_egg_info INFO : root : Copying botocore.egg-info to build/bdist.linux-i686/wheel/botocore-1.27.90-py3.10.egg-info INFO : root : running install_scripts INFO : wheel : creating build/bdist.linux-i686/wheel/botocore-1.27.90.dist-info/WHEEL INFO : wheel : creating '/usr/src/RPM/BUILD/python3-module-botocore-1.27.90/dist/.tmp-93_bjua5/botocore-1.27.90-py3-none-any.whl' and adding 'build/bdist.linux-i686/wheel' to it INFO : wheel : adding 'botocore/__init__.py' INFO : wheel : adding 'botocore/args.py' INFO : wheel : adding 'botocore/auth.py' INFO : wheel : adding 'botocore/awsrequest.py' INFO : wheel : adding 'botocore/client.py' INFO : wheel : adding 'botocore/compat.py' INFO : wheel : adding 'botocore/config.py' INFO : wheel : adding 'botocore/configloader.py' INFO : wheel : adding 'botocore/configprovider.py' INFO : wheel : adding 'botocore/credentials.py' INFO : wheel : adding 'botocore/discovery.py' INFO : wheel : adding 'botocore/endpoint.py' INFO : wheel : adding 'botocore/endpoint_provider.py' INFO : wheel : adding 'botocore/errorfactory.py' INFO : wheel : adding 'botocore/eventstream.py' INFO : wheel : adding 'botocore/exceptions.py' INFO : wheel : adding 'botocore/handlers.py' INFO : wheel : adding 'botocore/history.py' INFO : wheel : adding 'botocore/hooks.py' INFO : wheel : adding 'botocore/httpchecksum.py' INFO : wheel : adding 'botocore/httpsession.py' INFO : wheel : adding 'botocore/loaders.py' INFO : wheel : adding 'botocore/model.py' INFO : wheel : adding 'botocore/monitoring.py' INFO : wheel : adding 'botocore/paginate.py' INFO : wheel : adding 'botocore/parsers.py' INFO : wheel : adding 'botocore/regions.py' INFO : wheel : adding 'botocore/response.py' INFO : wheel : adding 'botocore/retryhandler.py' INFO : wheel : adding 'botocore/serialize.py' INFO : wheel : adding 'botocore/session.py' INFO : wheel : adding 'botocore/signers.py' INFO : wheel : adding 'botocore/stub.py' INFO : wheel : adding 'botocore/tokens.py' INFO : wheel : adding 'botocore/translate.py' INFO : wheel : adding 'botocore/utils.py' INFO : wheel : adding 'botocore/validate.py' INFO : wheel : adding 'botocore/waiter.py' INFO : wheel : adding 'botocore/crt/__init__.py' INFO : wheel : adding 'botocore/crt/auth.py' INFO : wheel : adding 'botocore/data/_retry.json' INFO : wheel : adding 'botocore/data/endpoints.json' INFO : wheel : adding 'botocore/data/partitions.json' INFO : wheel : adding 'botocore/data/sdk-default-configuration.json' INFO : wheel : adding 'botocore/data/accessanalyzer/2019-11-01/examples-1.json' INFO : wheel : adding 'botocore/data/accessanalyzer/2019-11-01/paginators-1.json' INFO : wheel : adding 'botocore/data/accessanalyzer/2019-11-01/service-2.json' INFO : wheel : adding 'botocore/data/account/2021-02-01/examples-1.json' INFO : wheel : adding 'botocore/data/account/2021-02-01/paginators-1.json' INFO : wheel : adding 'botocore/data/account/2021-02-01/service-2.json' INFO : wheel : adding 'botocore/data/acm/2015-12-08/examples-1.json' INFO : wheel : adding 'botocore/data/acm/2015-12-08/paginators-1.json' INFO : wheel : adding 'botocore/data/acm/2015-12-08/service-2.json' INFO : wheel : adding 'botocore/data/acm/2015-12-08/waiters-2.json' INFO : wheel : adding 'botocore/data/acm-pca/2017-08-22/examples-1.json' INFO : wheel : adding 'botocore/data/acm-pca/2017-08-22/paginators-1.json' INFO : wheel : adding 'botocore/data/acm-pca/2017-08-22/service-2.json' INFO : wheel : adding 'botocore/data/acm-pca/2017-08-22/waiters-2.json' INFO : wheel : adding 'botocore/data/alexaforbusiness/2017-11-09/examples-1.json' INFO : wheel : adding 'botocore/data/alexaforbusiness/2017-11-09/paginators-1.json' INFO : wheel : adding 'botocore/data/alexaforbusiness/2017-11-09/service-2.json' INFO : wheel : adding 'botocore/data/amp/2020-08-01/examples-1.json' INFO : wheel : adding 'botocore/data/amp/2020-08-01/paginators-1.json' INFO : wheel : adding 'botocore/data/amp/2020-08-01/service-2.json' INFO : wheel : adding 'botocore/data/amp/2020-08-01/waiters-2.json' INFO : wheel : adding 'botocore/data/amplify/2017-07-25/examples-1.json' INFO : wheel : adding 'botocore/data/amplify/2017-07-25/paginators-1.json' INFO : wheel : adding 'botocore/data/amplify/2017-07-25/service-2.json' INFO : wheel : adding 'botocore/data/amplifybackend/2020-08-11/paginators-1.json' INFO : wheel : adding 'botocore/data/amplifybackend/2020-08-11/service-2.json' INFO : wheel : adding 'botocore/data/amplifyuibuilder/2021-08-11/examples-1.json' INFO : wheel : adding 'botocore/data/amplifyuibuilder/2021-08-11/paginators-1.json' INFO : wheel : adding 'botocore/data/amplifyuibuilder/2021-08-11/service-2.json' INFO : wheel : adding 'botocore/data/apigateway/2015-07-09/examples-1.json' INFO : wheel : adding 'botocore/data/apigateway/2015-07-09/paginators-1.json' INFO : wheel : adding 'botocore/data/apigateway/2015-07-09/service-2.json' INFO : wheel : adding 'botocore/data/apigatewaymanagementapi/2018-11-29/paginators-1.json' INFO : wheel : adding 'botocore/data/apigatewaymanagementapi/2018-11-29/service-2.json' INFO : wheel : adding 'botocore/data/apigatewayv2/2018-11-29/paginators-1.json' INFO : wheel : adding 'botocore/data/apigatewayv2/2018-11-29/service-2.json' INFO : wheel : adding 'botocore/data/appconfig/2019-10-09/examples-1.json' INFO : wheel : adding 'botocore/data/appconfig/2019-10-09/paginators-1.json' INFO : wheel : adding 'botocore/data/appconfig/2019-10-09/service-2.json' INFO : wheel : adding 'botocore/data/appconfigdata/2021-11-11/examples-1.json' INFO : wheel : adding 'botocore/data/appconfigdata/2021-11-11/paginators-1.json' INFO : wheel : adding 'botocore/data/appconfigdata/2021-11-11/service-2.json' INFO : wheel : adding 'botocore/data/appflow/2020-08-23/examples-1.json' INFO : wheel : adding 'botocore/data/appflow/2020-08-23/paginators-1.json' INFO : wheel : adding 'botocore/data/appflow/2020-08-23/service-2.json' INFO : wheel : adding 'botocore/data/appintegrations/2020-07-29/examples-1.json' INFO : wheel : adding 'botocore/data/appintegrations/2020-07-29/paginators-1.json' INFO : wheel : adding 'botocore/data/appintegrations/2020-07-29/service-2.json' INFO : wheel : adding 'botocore/data/application-autoscaling/2016-02-06/examples-1.json' INFO : wheel : adding 'botocore/data/application-autoscaling/2016-02-06/paginators-1.json' INFO : wheel : adding 'botocore/data/application-autoscaling/2016-02-06/service-2.json' INFO : wheel : adding 'botocore/data/application-insights/2018-11-25/examples-1.json' INFO : wheel : adding 'botocore/data/application-insights/2018-11-25/paginators-1.json' INFO : wheel : adding 'botocore/data/application-insights/2018-11-25/service-2.json' INFO : wheel : adding 'botocore/data/applicationcostprofiler/2020-09-10/examples-1.json' INFO : wheel : adding 'botocore/data/applicationcostprofiler/2020-09-10/paginators-1.json' INFO : wheel : adding 'botocore/data/applicationcostprofiler/2020-09-10/service-2.json' INFO : wheel : adding 'botocore/data/appmesh/2018-10-01/examples-1.json' INFO : wheel : adding 'botocore/data/appmesh/2018-10-01/paginators-1.json' INFO : wheel : adding 'botocore/data/appmesh/2018-10-01/service-2.json' INFO : wheel : adding 'botocore/data/appmesh/2019-01-25/examples-1.json' INFO : wheel : adding 'botocore/data/appmesh/2019-01-25/paginators-1.json' INFO : wheel : adding 'botocore/data/appmesh/2019-01-25/service-2.json' INFO : wheel : adding 'botocore/data/apprunner/2020-05-15/examples-1.json' INFO : wheel : adding 'botocore/data/apprunner/2020-05-15/paginators-1.json' INFO : wheel : adding 'botocore/data/apprunner/2020-05-15/service-2.json' INFO : wheel : adding 'botocore/data/appstream/2016-12-01/examples-1.json' INFO : wheel : adding 'botocore/data/appstream/2016-12-01/paginators-1.json' INFO : wheel : adding 'botocore/data/appstream/2016-12-01/service-2.json' INFO : wheel : adding 'botocore/data/appstream/2016-12-01/waiters-2.json' INFO : wheel : adding 'botocore/data/appsync/2017-07-25/examples-1.json' INFO : wheel : adding 'botocore/data/appsync/2017-07-25/paginators-1.json' INFO : wheel : adding 'botocore/data/appsync/2017-07-25/service-2.json' INFO : wheel : adding 'botocore/data/athena/2017-05-18/examples-1.json' INFO : wheel : adding 'botocore/data/athena/2017-05-18/paginators-1.json' INFO : wheel : adding 'botocore/data/athena/2017-05-18/service-2.json' INFO : wheel : adding 'botocore/data/auditmanager/2017-07-25/examples-1.json' INFO : wheel : adding 'botocore/data/auditmanager/2017-07-25/paginators-1.json' INFO : wheel : adding 'botocore/data/auditmanager/2017-07-25/service-2.json' INFO : wheel : adding 'botocore/data/autoscaling/2011-01-01/examples-1.json' INFO : wheel : adding 'botocore/data/autoscaling/2011-01-01/paginators-1.json' INFO : wheel : adding 'botocore/data/autoscaling/2011-01-01/service-2.json' INFO : wheel : adding 'botocore/data/autoscaling-plans/2018-01-06/examples-1.json' INFO : wheel : adding 'botocore/data/autoscaling-plans/2018-01-06/paginators-1.json' INFO : wheel : adding 'botocore/data/autoscaling-plans/2018-01-06/service-2.json' INFO : wheel : adding 'botocore/data/backup/2018-11-15/examples-1.json' INFO : wheel : adding 'botocore/data/backup/2018-11-15/paginators-1.json' INFO : wheel : adding 'botocore/data/backup/2018-11-15/service-2.json' INFO : wheel : adding 'botocore/data/backup-gateway/2021-01-01/examples-1.json' INFO : wheel : adding 'botocore/data/backup-gateway/2021-01-01/paginators-1.json' INFO : wheel : adding 'botocore/data/backup-gateway/2021-01-01/service-2.json' INFO : wheel : adding 'botocore/data/backupstorage/2018-04-10/paginators-1.json' INFO : wheel : adding 'botocore/data/backupstorage/2018-04-10/service-2.json' INFO : wheel : adding 'botocore/data/batch/2016-08-10/examples-1.json' INFO : wheel : adding 'botocore/data/batch/2016-08-10/paginators-1.json' INFO : wheel : adding 'botocore/data/batch/2016-08-10/service-2.json' INFO : wheel : adding 'botocore/data/billingconductor/2021-07-30/examples-1.json' INFO : wheel : adding 'botocore/data/billingconductor/2021-07-30/paginators-1.json' INFO : wheel : adding 'botocore/data/billingconductor/2021-07-30/service-2.json' INFO : wheel : adding 'botocore/data/billingconductor/2021-07-30/waiters-2.json' INFO : wheel : adding 'botocore/data/braket/2019-09-01/examples-1.json' INFO : wheel : adding 'botocore/data/braket/2019-09-01/paginators-1.json' INFO : wheel : adding 'botocore/data/braket/2019-09-01/service-2.json' INFO : wheel : adding 'botocore/data/budgets/2016-10-20/examples-1.json' INFO : wheel : adding 'botocore/data/budgets/2016-10-20/paginators-1.json' INFO : wheel : adding 'botocore/data/budgets/2016-10-20/service-2.json' INFO : wheel : adding 'botocore/data/ce/2017-10-25/examples-1.json' INFO : wheel : adding 'botocore/data/ce/2017-10-25/paginators-1.json' INFO : wheel : adding 'botocore/data/ce/2017-10-25/service-2.json' INFO : wheel : adding 'botocore/data/chime/2018-05-01/examples-1.json' INFO : wheel : adding 'botocore/data/chime/2018-05-01/paginators-1.json' INFO : wheel : adding 'botocore/data/chime/2018-05-01/service-2.json' INFO : wheel : adding 'botocore/data/chime-sdk-identity/2021-04-20/examples-1.json' INFO : wheel : adding 'botocore/data/chime-sdk-identity/2021-04-20/paginators-1.json' INFO : wheel : adding 'botocore/data/chime-sdk-identity/2021-04-20/service-2.json' INFO : wheel : adding 'botocore/data/chime-sdk-media-pipelines/2021-07-15/paginators-1.json' INFO : wheel : adding 'botocore/data/chime-sdk-media-pipelines/2021-07-15/service-2.json' INFO : wheel : adding 'botocore/data/chime-sdk-meetings/2021-07-15/examples-1.json' INFO : wheel : adding 'botocore/data/chime-sdk-meetings/2021-07-15/paginators-1.json' INFO : wheel : adding 'botocore/data/chime-sdk-meetings/2021-07-15/service-2.json' INFO : wheel : adding 'botocore/data/chime-sdk-messaging/2021-05-15/examples-1.json' INFO : wheel : adding 'botocore/data/chime-sdk-messaging/2021-05-15/paginators-1.json' INFO : wheel : adding 'botocore/data/chime-sdk-messaging/2021-05-15/service-2.json' INFO : wheel : adding 'botocore/data/cloud9/2017-09-23/examples-1.json' INFO : wheel : adding 'botocore/data/cloud9/2017-09-23/paginators-1.json' INFO : wheel : adding 'botocore/data/cloud9/2017-09-23/service-2.json' INFO : wheel : adding 'botocore/data/cloudcontrol/2021-09-30/examples-1.json' INFO : wheel : adding 'botocore/data/cloudcontrol/2021-09-30/paginators-1.json' INFO : wheel : adding 'botocore/data/cloudcontrol/2021-09-30/paginators-1.sdk-extras.json' INFO : wheel : adding 'botocore/data/cloudcontrol/2021-09-30/service-2.json' INFO : wheel : adding 'botocore/data/cloudcontrol/2021-09-30/waiters-2.json' INFO : wheel : adding 'botocore/data/clouddirectory/2016-05-10/examples-1.json' INFO : wheel : adding 'botocore/data/clouddirectory/2016-05-10/paginators-1.json' INFO : wheel : adding 'botocore/data/clouddirectory/2016-05-10/service-2.json' INFO : wheel : adding 'botocore/data/clouddirectory/2017-01-11/examples-1.json' INFO : wheel : adding 'botocore/data/clouddirectory/2017-01-11/paginators-1.json' INFO : wheel : adding 'botocore/data/clouddirectory/2017-01-11/service-2.json' INFO : wheel : adding 'botocore/data/cloudformation/2010-05-15/examples-1.json' INFO : wheel : adding 'botocore/data/cloudformation/2010-05-15/paginators-1.json' INFO : wheel : adding 'botocore/data/cloudformation/2010-05-15/service-2.json' INFO : wheel : adding 'botocore/data/cloudformation/2010-05-15/waiters-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2014-05-31/paginators-1.json' INFO : wheel : adding 'botocore/data/cloudfront/2014-05-31/service-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2014-05-31/waiters-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2014-10-21/paginators-1.json' INFO : wheel : adding 'botocore/data/cloudfront/2014-10-21/service-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2014-10-21/waiters-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2014-11-06/paginators-1.json' INFO : wheel : adding 'botocore/data/cloudfront/2014-11-06/service-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2014-11-06/waiters-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2015-04-17/paginators-1.json' INFO : wheel : adding 'botocore/data/cloudfront/2015-04-17/service-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2015-04-17/waiters-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2015-07-27/paginators-1.json' INFO : wheel : adding 'botocore/data/cloudfront/2015-07-27/service-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2015-07-27/waiters-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2015-09-17/paginators-1.json' INFO : wheel : adding 'botocore/data/cloudfront/2015-09-17/service-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2015-09-17/waiters-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2016-01-13/paginators-1.json' INFO : wheel : adding 'botocore/data/cloudfront/2016-01-13/service-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2016-01-13/waiters-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2016-01-28/examples-1.json' INFO : wheel : adding 'botocore/data/cloudfront/2016-01-28/paginators-1.json' INFO : wheel : adding 'botocore/data/cloudfront/2016-01-28/service-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2016-01-28/waiters-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2016-08-01/examples-1.json' INFO : wheel : adding 'botocore/data/cloudfront/2016-08-01/paginators-1.json' INFO : wheel : adding 'botocore/data/cloudfront/2016-08-01/service-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2016-08-01/waiters-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2016-08-20/paginators-1.json' INFO : wheel : adding 'botocore/data/cloudfront/2016-08-20/service-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2016-08-20/waiters-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2016-09-07/examples-1.json' INFO : wheel : adding 'botocore/data/cloudfront/2016-09-07/paginators-1.json' INFO : wheel : adding 'botocore/data/cloudfront/2016-09-07/service-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2016-09-07/waiters-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2016-09-29/examples-1.json' INFO : wheel : adding 'botocore/data/cloudfront/2016-09-29/paginators-1.json' INFO : wheel : adding 'botocore/data/cloudfront/2016-09-29/service-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2016-09-29/waiters-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2016-11-25/examples-1.json' INFO : wheel : adding 'botocore/data/cloudfront/2016-11-25/paginators-1.json' INFO : wheel : adding 'botocore/data/cloudfront/2016-11-25/service-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2016-11-25/waiters-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2017-03-25/paginators-1.json' INFO : wheel : adding 'botocore/data/cloudfront/2017-03-25/service-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2017-03-25/waiters-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2017-10-30/examples-1.json' INFO : wheel : adding 'botocore/data/cloudfront/2017-10-30/paginators-1.json' INFO : wheel : adding 'botocore/data/cloudfront/2017-10-30/service-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2017-10-30/waiters-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2018-06-18/examples-1.json' INFO : wheel : adding 'botocore/data/cloudfront/2018-06-18/paginators-1.json' INFO : wheel : adding 'botocore/data/cloudfront/2018-06-18/service-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2018-06-18/waiters-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2018-11-05/examples-1.json' INFO : wheel : adding 'botocore/data/cloudfront/2018-11-05/paginators-1.json' INFO : wheel : adding 'botocore/data/cloudfront/2018-11-05/service-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2018-11-05/waiters-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2019-03-26/examples-1.json' INFO : wheel : adding 'botocore/data/cloudfront/2019-03-26/paginators-1.json' INFO : wheel : adding 'botocore/data/cloudfront/2019-03-26/service-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2019-03-26/waiters-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2020-05-31/examples-1.json' INFO : wheel : adding 'botocore/data/cloudfront/2020-05-31/paginators-1.json' INFO : wheel : adding 'botocore/data/cloudfront/2020-05-31/service-2.json' INFO : wheel : adding 'botocore/data/cloudfront/2020-05-31/waiters-2.json' INFO : wheel : adding 'botocore/data/cloudhsm/2014-05-30/examples-1.json' INFO : wheel : adding 'botocore/data/cloudhsm/2014-05-30/paginators-1.json' INFO : wheel : adding 'botocore/data/cloudhsm/2014-05-30/service-2.json' INFO : wheel : adding 'botocore/data/cloudhsmv2/2017-04-28/examples-1.json' INFO : wheel : adding 'botocore/data/cloudhsmv2/2017-04-28/paginators-1.json' INFO : wheel : adding 'botocore/data/cloudhsmv2/2017-04-28/service-2.json' INFO : wheel : adding 'botocore/data/cloudsearch/2011-02-01/service-2.json' INFO : wheel : adding 'botocore/data/cloudsearch/2013-01-01/examples-1.json' INFO : wheel : adding 'botocore/data/cloudsearch/2013-01-01/paginators-1.json' INFO : wheel : adding 'botocore/data/cloudsearch/2013-01-01/service-2.json' INFO : wheel : adding 'botocore/data/cloudsearchdomain/2013-01-01/examples-1.json' INFO : wheel : adding 'botocore/data/cloudsearchdomain/2013-01-01/service-2.json' INFO : wheel : adding 'botocore/data/cloudtrail/2013-11-01/examples-1.json' INFO : wheel : adding 'botocore/data/cloudtrail/2013-11-01/paginators-1.json' INFO : wheel : adding 'botocore/data/cloudtrail/2013-11-01/service-2.json' INFO : wheel : adding 'botocore/data/cloudwatch/2010-08-01/examples-1.json' INFO : wheel : adding 'botocore/data/cloudwatch/2010-08-01/paginators-1.json' INFO : wheel : adding 'botocore/data/cloudwatch/2010-08-01/service-2.json' INFO : wheel : adding 'botocore/data/cloudwatch/2010-08-01/waiters-2.json' INFO : wheel : adding 'botocore/data/codeartifact/2018-09-22/examples-1.json' INFO : wheel : adding 'botocore/data/codeartifact/2018-09-22/paginators-1.json' INFO : wheel : adding 'botocore/data/codeartifact/2018-09-22/paginators-1.sdk-extras.json' INFO : wheel : adding 'botocore/data/codeartifact/2018-09-22/service-2.json' INFO : wheel : adding 'botocore/data/codebuild/2016-10-06/examples-1.json' INFO : wheel : adding 'botocore/data/codebuild/2016-10-06/paginators-1.json' INFO : wheel : adding 'botocore/data/codebuild/2016-10-06/service-2.json' INFO : wheel : adding 'botocore/data/codecommit/2015-04-13/examples-1.json' INFO : wheel : adding 'botocore/data/codecommit/2015-04-13/paginators-1.json' INFO : wheel : adding 'botocore/data/codecommit/2015-04-13/service-2.json' INFO : wheel : adding 'botocore/data/codedeploy/2014-10-06/examples-1.json' INFO : wheel : adding 'botocore/data/codedeploy/2014-10-06/paginators-1.json' INFO : wheel : adding 'botocore/data/codedeploy/2014-10-06/service-2.json' INFO : wheel : adding 'botocore/data/codedeploy/2014-10-06/waiters-2.json' INFO : wheel : adding 'botocore/data/codeguru-reviewer/2019-09-19/examples-1.json' INFO : wheel : adding 'botocore/data/codeguru-reviewer/2019-09-19/paginators-1.json' INFO : wheel : adding 'botocore/data/codeguru-reviewer/2019-09-19/service-2.json' INFO : wheel : adding 'botocore/data/codeguru-reviewer/2019-09-19/waiters-2.json' INFO : wheel : adding 'botocore/data/codeguruprofiler/2019-07-18/examples-1.json' INFO : wheel : adding 'botocore/data/codeguruprofiler/2019-07-18/paginators-1.json' INFO : wheel : adding 'botocore/data/codeguruprofiler/2019-07-18/service-2.json' INFO : wheel : adding 'botocore/data/codepipeline/2015-07-09/examples-1.json' INFO : wheel : adding 'botocore/data/codepipeline/2015-07-09/paginators-1.json' INFO : wheel : adding 'botocore/data/codepipeline/2015-07-09/service-2.json' INFO : wheel : adding 'botocore/data/codestar/2017-04-19/examples-1.json' INFO : wheel : adding 'botocore/data/codestar/2017-04-19/paginators-1.json' INFO : wheel : adding 'botocore/data/codestar/2017-04-19/service-2.json' INFO : wheel : adding 'botocore/data/codestar-connections/2019-12-01/examples-1.json' INFO : wheel : adding 'botocore/data/codestar-connections/2019-12-01/paginators-1.json' INFO : wheel : adding 'botocore/data/codestar-connections/2019-12-01/service-2.json' INFO : wheel : adding 'botocore/data/codestar-notifications/2019-10-15/examples-1.json' INFO : wheel : adding 'botocore/data/codestar-notifications/2019-10-15/paginators-1.json' INFO : wheel : adding 'botocore/data/codestar-notifications/2019-10-15/service-2.json' INFO : wheel : adding 'botocore/data/cognito-identity/2014-06-30/examples-1.json' INFO : wheel : adding 'botocore/data/cognito-identity/2014-06-30/paginators-1.json' INFO : wheel : adding 'botocore/data/cognito-identity/2014-06-30/service-2.json' INFO : wheel : adding 'botocore/data/cognito-idp/2016-04-18/examples-1.json' INFO : wheel : adding 'botocore/data/cognito-idp/2016-04-18/paginators-1.json' INFO : wheel : adding 'botocore/data/cognito-idp/2016-04-18/service-2.json' INFO : wheel : adding 'botocore/data/cognito-sync/2014-06-30/examples-1.json' INFO : wheel : adding 'botocore/data/cognito-sync/2014-06-30/paginators-1.json' INFO : wheel : adding 'botocore/data/cognito-sync/2014-06-30/service-2.json' INFO : wheel : adding 'botocore/data/comprehend/2017-11-27/examples-1.json' INFO : wheel : adding 'botocore/data/comprehend/2017-11-27/paginators-1.json' INFO : wheel : adding 'botocore/data/comprehend/2017-11-27/service-2.json' INFO : wheel : adding 'botocore/data/comprehendmedical/2018-10-30/examples-1.json' INFO : wheel : adding 'botocore/data/comprehendmedical/2018-10-30/paginators-1.json' INFO : wheel : adding 'botocore/data/comprehendmedical/2018-10-30/service-2.json' INFO : wheel : adding 'botocore/data/compute-optimizer/2019-11-01/examples-1.json' INFO : wheel : adding 'botocore/data/compute-optimizer/2019-11-01/paginators-1.json' INFO : wheel : adding 'botocore/data/compute-optimizer/2019-11-01/service-2.json' INFO : wheel : adding 'botocore/data/config/2014-11-12/examples-1.json' INFO : wheel : adding 'botocore/data/config/2014-11-12/paginators-1.json' INFO : wheel : adding 'botocore/data/config/2014-11-12/service-2.json' INFO : wheel : adding 'botocore/data/connect/2017-08-08/examples-1.json' INFO : wheel : adding 'botocore/data/connect/2017-08-08/paginators-1.json' INFO : wheel : adding 'botocore/data/connect/2017-08-08/service-2.json' INFO : wheel : adding 'botocore/data/connect-contact-lens/2020-08-21/examples-1.json' INFO : wheel : adding 'botocore/data/connect-contact-lens/2020-08-21/paginators-1.json' INFO : wheel : adding 'botocore/data/connect-contact-lens/2020-08-21/service-2.json' INFO : wheel : adding 'botocore/data/connectcampaigns/2021-01-30/paginators-1.json' INFO : wheel : adding 'botocore/data/connectcampaigns/2021-01-30/service-2.json' INFO : wheel : adding 'botocore/data/connectcases/2022-10-03/paginators-1.json' INFO : wheel : adding 'botocore/data/connectcases/2022-10-03/service-2.json' INFO : wheel : adding 'botocore/data/connectparticipant/2018-09-07/examples-1.json' INFO : wheel : adding 'botocore/data/connectparticipant/2018-09-07/paginators-1.json' INFO : wheel : adding 'botocore/data/connectparticipant/2018-09-07/service-2.json' INFO : wheel : adding 'botocore/data/controltower/2018-05-10/paginators-1.json' INFO : wheel : adding 'botocore/data/controltower/2018-05-10/service-2.json' INFO : wheel : adding 'botocore/data/cur/2017-01-06/examples-1.json' INFO : wheel : adding 'botocore/data/cur/2017-01-06/paginators-1.json' INFO : wheel : adding 'botocore/data/cur/2017-01-06/service-2.json' INFO : wheel : adding 'botocore/data/customer-profiles/2020-08-15/examples-1.json' INFO : wheel : adding 'botocore/data/customer-profiles/2020-08-15/paginators-1.json' INFO : wheel : adding 'botocore/data/customer-profiles/2020-08-15/service-2.json' INFO : wheel : adding 'botocore/data/databrew/2017-07-25/examples-1.json' INFO : wheel : adding 'botocore/data/databrew/2017-07-25/paginators-1.json' INFO : wheel : adding 'botocore/data/databrew/2017-07-25/service-2.json' INFO : wheel : adding 'botocore/data/dataexchange/2017-07-25/paginators-1.json' INFO : wheel : adding 'botocore/data/dataexchange/2017-07-25/service-2.json' INFO : wheel : adding 'botocore/data/dataexchange/2017-07-25/waiters-2.json' INFO : wheel : adding 'botocore/data/datapipeline/2012-10-29/examples-1.json' INFO : wheel : adding 'botocore/data/datapipeline/2012-10-29/paginators-1.json' INFO : wheel : adding 'botocore/data/datapipeline/2012-10-29/service-2.json' INFO : wheel : adding 'botocore/data/datasync/2018-11-09/examples-1.json' INFO : wheel : adding 'botocore/data/datasync/2018-11-09/paginators-1.json' INFO : wheel : adding 'botocore/data/datasync/2018-11-09/service-2.json' INFO : wheel : adding 'botocore/data/dax/2017-04-19/examples-1.json' INFO : wheel : adding 'botocore/data/dax/2017-04-19/paginators-1.json' INFO : wheel : adding 'botocore/data/dax/2017-04-19/service-2.json' INFO : wheel : adding 'botocore/data/detective/2018-10-26/examples-1.json' INFO : wheel : adding 'botocore/data/detective/2018-10-26/paginators-1.json' INFO : wheel : adding 'botocore/data/detective/2018-10-26/service-2.json' INFO : wheel : adding 'botocore/data/devicefarm/2015-06-23/examples-1.json' INFO : wheel : adding 'botocore/data/devicefarm/2015-06-23/paginators-1.json' INFO : wheel : adding 'botocore/data/devicefarm/2015-06-23/service-2.json' INFO : wheel : adding 'botocore/data/devops-guru/2020-12-01/examples-1.json' INFO : wheel : adding 'botocore/data/devops-guru/2020-12-01/paginators-1.json' INFO : wheel : adding 'botocore/data/devops-guru/2020-12-01/service-2.json' INFO : wheel : adding 'botocore/data/directconnect/2012-10-25/examples-1.json' INFO : wheel : adding 'botocore/data/directconnect/2012-10-25/paginators-1.json' INFO : wheel : adding 'botocore/data/directconnect/2012-10-25/service-2.json' INFO : wheel : adding 'botocore/data/discovery/2015-11-01/examples-1.json' INFO : wheel : adding 'botocore/data/discovery/2015-11-01/paginators-1.json' INFO : wheel : adding 'botocore/data/discovery/2015-11-01/service-2.json' INFO : wheel : adding 'botocore/data/dlm/2018-01-12/examples-1.json' INFO : wheel : adding 'botocore/data/dlm/2018-01-12/paginators-1.json' INFO : wheel : adding 'botocore/data/dlm/2018-01-12/service-2.json' INFO : wheel : adding 'botocore/data/dms/2016-01-01/examples-1.json' INFO : wheel : adding 'botocore/data/dms/2016-01-01/paginators-1.json' INFO : wheel : adding 'botocore/data/dms/2016-01-01/service-2.json' INFO : wheel : adding 'botocore/data/dms/2016-01-01/waiters-2.json' INFO : wheel : adding 'botocore/data/docdb/2014-10-31/examples-1.json' INFO : wheel : adding 'botocore/data/docdb/2014-10-31/paginators-1.json' INFO : wheel : adding 'botocore/data/docdb/2014-10-31/service-2.json' INFO : wheel : adding 'botocore/data/docdb/2014-10-31/service-2.sdk-extras.json' INFO : wheel : adding 'botocore/data/docdb/2014-10-31/waiters-2.json' INFO : wheel : adding 'botocore/data/drs/2020-02-26/examples-1.json' INFO : wheel : adding 'botocore/data/drs/2020-02-26/paginators-1.json' INFO : wheel : adding 'botocore/data/drs/2020-02-26/service-2.json' INFO : wheel : adding 'botocore/data/ds/2015-04-16/examples-1.json' INFO : wheel : adding 'botocore/data/ds/2015-04-16/paginators-1.json' INFO : wheel : adding 'botocore/data/ds/2015-04-16/service-2.json' INFO : wheel : adding 'botocore/data/dynamodb/2011-12-05/examples-1.json' INFO : wheel : adding 'botocore/data/dynamodb/2012-08-10/examples-1.json' INFO : wheel : adding 'botocore/data/dynamodb/2012-08-10/paginators-1.json' INFO : wheel : adding 'botocore/data/dynamodb/2012-08-10/service-2.json' INFO : wheel : adding 'botocore/data/dynamodb/2012-08-10/waiters-2.json' INFO : wheel : adding 'botocore/data/dynamodbstreams/2012-08-10/examples-1.json' INFO : wheel : adding 'botocore/data/dynamodbstreams/2012-08-10/paginators-1.json' INFO : wheel : adding 'botocore/data/dynamodbstreams/2012-08-10/service-2.json' INFO : wheel : adding 'botocore/data/ebs/2019-11-02/examples-1.json' INFO : wheel : adding 'botocore/data/ebs/2019-11-02/paginators-1.json' INFO : wheel : adding 'botocore/data/ebs/2019-11-02/service-2.json' INFO : wheel : adding 'botocore/data/ec2/2014-09-01/paginators-1.json' INFO : wheel : adding 'botocore/data/ec2/2014-09-01/service-2.json' INFO : wheel : adding 'botocore/data/ec2/2014-09-01/waiters-2.json' INFO : wheel : adding 'botocore/data/ec2/2014-10-01/paginators-1.json' INFO : wheel : adding 'botocore/data/ec2/2014-10-01/service-2.json' INFO : wheel : adding 'botocore/data/ec2/2014-10-01/waiters-2.json' INFO : wheel : adding 'botocore/data/ec2/2015-03-01/paginators-1.json' INFO : wheel : adding 'botocore/data/ec2/2015-03-01/service-2.json' INFO : wheel : adding 'botocore/data/ec2/2015-03-01/waiters-2.json' INFO : wheel : adding 'botocore/data/ec2/2015-04-15/paginators-1.json' INFO : wheel : adding 'botocore/data/ec2/2015-04-15/service-2.json' INFO : wheel : adding 'botocore/data/ec2/2015-04-15/waiters-2.json' INFO : wheel : adding 'botocore/data/ec2/2015-10-01/examples-1.json' INFO : wheel : adding 'botocore/data/ec2/2015-10-01/paginators-1.json' INFO : wheel : adding 'botocore/data/ec2/2015-10-01/service-2.json' INFO : wheel : adding 'botocore/data/ec2/2015-10-01/waiters-2.json' INFO : wheel : adding 'botocore/data/ec2/2016-04-01/examples-1.json' INFO : wheel : adding 'botocore/data/ec2/2016-04-01/paginators-1.json' INFO : wheel : adding 'botocore/data/ec2/2016-04-01/service-2.json' INFO : wheel : adding 'botocore/data/ec2/2016-04-01/waiters-2.json' INFO : wheel : adding 'botocore/data/ec2/2016-09-15/examples-1.json' INFO : wheel : adding 'botocore/data/ec2/2016-09-15/paginators-1.json' INFO : wheel : adding 'botocore/data/ec2/2016-09-15/service-2.json' INFO : wheel : adding 'botocore/data/ec2/2016-09-15/waiters-2.json' INFO : wheel : adding 'botocore/data/ec2/2016-11-15/examples-1.json' INFO : wheel : adding 'botocore/data/ec2/2016-11-15/paginators-1.json' INFO : wheel : adding 'botocore/data/ec2/2016-11-15/service-2.json' INFO : wheel : adding 'botocore/data/ec2/2016-11-15/waiters-2.json' INFO : wheel : adding 'botocore/data/ec2-instance-connect/2018-04-02/examples-1.json' INFO : wheel : adding 'botocore/data/ec2-instance-connect/2018-04-02/paginators-1.json' INFO : wheel : adding 'botocore/data/ec2-instance-connect/2018-04-02/service-2.json' INFO : wheel : adding 'botocore/data/ecr/2015-09-21/examples-1.json' INFO : wheel : adding 'botocore/data/ecr/2015-09-21/paginators-1.json' INFO : wheel : adding 'botocore/data/ecr/2015-09-21/service-2.json' INFO : wheel : adding 'botocore/data/ecr/2015-09-21/waiters-2.json' INFO : wheel : adding 'botocore/data/ecr-public/2020-10-30/examples-1.json' INFO : wheel : adding 'botocore/data/ecr-public/2020-10-30/paginators-1.json' INFO : wheel : adding 'botocore/data/ecr-public/2020-10-30/service-2.json' INFO : wheel : adding 'botocore/data/ecs/2014-11-13/examples-1.json' INFO : wheel : adding 'botocore/data/ecs/2014-11-13/paginators-1.json' INFO : wheel : adding 'botocore/data/ecs/2014-11-13/service-2.json' INFO : wheel : adding 'botocore/data/ecs/2014-11-13/waiters-2.json' INFO : wheel : adding 'botocore/data/efs/2015-02-01/examples-1.json' INFO : wheel : adding 'botocore/data/efs/2015-02-01/paginators-1.json' INFO : wheel : adding 'botocore/data/efs/2015-02-01/service-2.json' INFO : wheel : adding 'botocore/data/eks/2017-11-01/examples-1.json' INFO : wheel : adding 'botocore/data/eks/2017-11-01/paginators-1.json' INFO : wheel : adding 'botocore/data/eks/2017-11-01/service-2.json' INFO : wheel : adding 'botocore/data/eks/2017-11-01/service-2.sdk-extras.json' INFO : wheel : adding 'botocore/data/eks/2017-11-01/waiters-2.json' INFO : wheel : adding 'botocore/data/elastic-inference/2017-07-25/examples-1.json' INFO : wheel : adding 'botocore/data/elastic-inference/2017-07-25/paginators-1.json' INFO : wheel : adding 'botocore/data/elastic-inference/2017-07-25/service-2.json' INFO : wheel : adding 'botocore/data/elasticache/2014-09-30/paginators-1.json' INFO : wheel : adding 'botocore/data/elasticache/2014-09-30/service-2.json' INFO : wheel : adding 'botocore/data/elasticache/2014-09-30/waiters-2.json' INFO : wheel : adding 'botocore/data/elasticache/2015-02-02/examples-1.json' INFO : wheel : adding 'botocore/data/elasticache/2015-02-02/paginators-1.json' INFO : wheel : adding 'botocore/data/elasticache/2015-02-02/service-2.json' INFO : wheel : adding 'botocore/data/elasticache/2015-02-02/waiters-2.json' INFO : wheel : adding 'botocore/data/elasticbeanstalk/2010-12-01/examples-1.json' INFO : wheel : adding 'botocore/data/elasticbeanstalk/2010-12-01/paginators-1.json' INFO : wheel : adding 'botocore/data/elasticbeanstalk/2010-12-01/service-2.json' INFO : wheel : adding 'botocore/data/elasticbeanstalk/2010-12-01/waiters-2.json' INFO : wheel : adding 'botocore/data/elastictranscoder/2012-09-25/examples-1.json' INFO : wheel : adding 'botocore/data/elastictranscoder/2012-09-25/paginators-1.json' INFO : wheel : adding 'botocore/data/elastictranscoder/2012-09-25/service-2.json' INFO : wheel : adding 'botocore/data/elastictranscoder/2012-09-25/waiters-2.json' INFO : wheel : adding 'botocore/data/elb/2012-06-01/examples-1.json' INFO : wheel : adding 'botocore/data/elb/2012-06-01/paginators-1.json' INFO : wheel : adding 'botocore/data/elb/2012-06-01/service-2.json' INFO : wheel : adding 'botocore/data/elb/2012-06-01/waiters-2.json' INFO : wheel : adding 'botocore/data/elbv2/2015-12-01/examples-1.json' INFO : wheel : adding 'botocore/data/elbv2/2015-12-01/paginators-1.json' INFO : wheel : adding 'botocore/data/elbv2/2015-12-01/service-2.json' INFO : wheel : adding 'botocore/data/elbv2/2015-12-01/waiters-2.json' INFO : wheel : adding 'botocore/data/emr/2009-03-31/examples-1.json' INFO : wheel : adding 'botocore/data/emr/2009-03-31/paginators-1.json' INFO : wheel : adding 'botocore/data/emr/2009-03-31/service-2.json' INFO : wheel : adding 'botocore/data/emr/2009-03-31/waiters-2.json' INFO : wheel : adding 'botocore/data/emr-containers/2020-10-01/examples-1.json' INFO : wheel : adding 'botocore/data/emr-containers/2020-10-01/paginators-1.json' INFO : wheel : adding 'botocore/data/emr-containers/2020-10-01/service-2.json' INFO : wheel : adding 'botocore/data/emr-serverless/2021-07-13/paginators-1.json' INFO : wheel : adding 'botocore/data/emr-serverless/2021-07-13/service-2.json' INFO : wheel : adding 'botocore/data/es/2015-01-01/examples-1.json' INFO : wheel : adding 'botocore/data/es/2015-01-01/paginators-1.json' INFO : wheel : adding 'botocore/data/es/2015-01-01/service-2.json' INFO : wheel : adding 'botocore/data/events/2014-02-03/service-2.json' INFO : wheel : adding 'botocore/data/events/2015-10-07/examples-1.json' INFO : wheel : adding 'botocore/data/events/2015-10-07/paginators-1.json' INFO : wheel : adding 'botocore/data/events/2015-10-07/service-2.json' INFO : wheel : adding 'botocore/data/evidently/2021-02-01/examples-1.json' INFO : wheel : adding 'botocore/data/evidently/2021-02-01/paginators-1.json' INFO : wheel : adding 'botocore/data/evidently/2021-02-01/service-2.json' INFO : wheel : adding 'botocore/data/finspace/2021-03-12/examples-1.json' INFO : wheel : adding 'botocore/data/finspace/2021-03-12/paginators-1.json' INFO : wheel : adding 'botocore/data/finspace/2021-03-12/service-2.json' INFO : wheel : adding 'botocore/data/finspace-data/2020-07-13/examples-1.json' INFO : wheel : adding 'botocore/data/finspace-data/2020-07-13/paginators-1.json' INFO : wheel : adding 'botocore/data/finspace-data/2020-07-13/service-2.json' INFO : wheel : adding 'botocore/data/firehose/2015-08-04/examples-1.json' INFO : wheel : adding 'botocore/data/firehose/2015-08-04/paginators-1.json' INFO : wheel : adding 'botocore/data/firehose/2015-08-04/service-2.json' INFO : wheel : adding 'botocore/data/fis/2020-12-01/examples-1.json' INFO : wheel : adding 'botocore/data/fis/2020-12-01/paginators-1.json' INFO : wheel : adding 'botocore/data/fis/2020-12-01/service-2.json' INFO : wheel : adding 'botocore/data/fms/2018-01-01/examples-1.json' INFO : wheel : adding 'botocore/data/fms/2018-01-01/paginators-1.json' INFO : wheel : adding 'botocore/data/fms/2018-01-01/service-2.json' INFO : wheel : adding 'botocore/data/forecast/2018-06-26/examples-1.json' INFO : wheel : adding 'botocore/data/forecast/2018-06-26/paginators-1.json' INFO : wheel : adding 'botocore/data/forecast/2018-06-26/service-2.json' INFO : wheel : adding 'botocore/data/forecastquery/2018-06-26/examples-1.json' INFO : wheel : adding 'botocore/data/forecastquery/2018-06-26/paginators-1.json' INFO : wheel : adding 'botocore/data/forecastquery/2018-06-26/service-2.json' INFO : wheel : adding 'botocore/data/frauddetector/2019-11-15/examples-1.json' INFO : wheel : adding 'botocore/data/frauddetector/2019-11-15/paginators-1.json' INFO : wheel : adding 'botocore/data/frauddetector/2019-11-15/service-2.json' INFO : wheel : adding 'botocore/data/fsx/2018-03-01/examples-1.json' INFO : wheel : adding 'botocore/data/fsx/2018-03-01/paginators-1.json' INFO : wheel : adding 'botocore/data/fsx/2018-03-01/service-2.json' INFO : wheel : adding 'botocore/data/gamelift/2015-10-01/examples-1.json' INFO : wheel : adding 'botocore/data/gamelift/2015-10-01/paginators-1.json' INFO : wheel : adding 'botocore/data/gamelift/2015-10-01/service-2.json' INFO : wheel : adding 'botocore/data/gamesparks/2021-08-17/examples-1.json' INFO : wheel : adding 'botocore/data/gamesparks/2021-08-17/paginators-1.json' INFO : wheel : adding 'botocore/data/gamesparks/2021-08-17/service-2.json' INFO : wheel : adding 'botocore/data/glacier/2012-06-01/examples-1.json' INFO : wheel : adding 'botocore/data/glacier/2012-06-01/paginators-1.json' INFO : wheel : adding 'botocore/data/glacier/2012-06-01/service-2.json' INFO : wheel : adding 'botocore/data/glacier/2012-06-01/waiters-2.json' INFO : wheel : adding 'botocore/data/globalaccelerator/2018-08-08/examples-1.json' INFO : wheel : adding 'botocore/data/globalaccelerator/2018-08-08/paginators-1.json' INFO : wheel : adding 'botocore/data/globalaccelerator/2018-08-08/service-2.json' INFO : wheel : adding 'botocore/data/glue/2017-03-31/examples-1.json' INFO : wheel : adding 'botocore/data/glue/2017-03-31/paginators-1.json' INFO : wheel : adding 'botocore/data/glue/2017-03-31/service-2.json' INFO : wheel : adding 'botocore/data/grafana/2020-08-18/examples-1.json' INFO : wheel : adding 'botocore/data/grafana/2020-08-18/paginators-1.json' INFO : wheel : adding 'botocore/data/grafana/2020-08-18/service-2.json' INFO : wheel : adding 'botocore/data/greengrass/2017-06-07/paginators-1.json' INFO : wheel : adding 'botocore/data/greengrass/2017-06-07/service-2.json' INFO : wheel : adding 'botocore/data/greengrassv2/2020-11-30/examples-1.json' INFO : wheel : adding 'botocore/data/greengrassv2/2020-11-30/paginators-1.json' INFO : wheel : adding 'botocore/data/greengrassv2/2020-11-30/service-2.json' INFO : wheel : adding 'botocore/data/groundstation/2019-05-23/examples-1.json' INFO : wheel : adding 'botocore/data/groundstation/2019-05-23/paginators-1.json' INFO : wheel : adding 'botocore/data/groundstation/2019-05-23/service-2.json' INFO : wheel : adding 'botocore/data/guardduty/2017-11-28/examples-1.json' INFO : wheel : adding 'botocore/data/guardduty/2017-11-28/paginators-1.json' INFO : wheel : adding 'botocore/data/guardduty/2017-11-28/service-2.json' INFO : wheel : adding 'botocore/data/health/2016-08-04/examples-1.json' INFO : wheel : adding 'botocore/data/health/2016-08-04/paginators-1.json' INFO : wheel : adding 'botocore/data/health/2016-08-04/service-2.json' INFO : wheel : adding 'botocore/data/healthlake/2017-07-01/examples-1.json' INFO : wheel : adding 'botocore/data/healthlake/2017-07-01/paginators-1.json' INFO : wheel : adding 'botocore/data/healthlake/2017-07-01/service-2.json' INFO : wheel : adding 'botocore/data/honeycode/2020-03-01/examples-1.json' INFO : wheel : adding 'botocore/data/honeycode/2020-03-01/paginators-1.json' INFO : wheel : adding 'botocore/data/honeycode/2020-03-01/paginators-1.sdk-extras.json' INFO : wheel : adding 'botocore/data/honeycode/2020-03-01/service-2.json' INFO : wheel : adding 'botocore/data/iam/2010-05-08/examples-1.json' INFO : wheel : adding 'botocore/data/iam/2010-05-08/paginators-1.json' INFO : wheel : adding 'botocore/data/iam/2010-05-08/service-2.json' INFO : wheel : adding 'botocore/data/iam/2010-05-08/waiters-2.json' INFO : wheel : adding 'botocore/data/identitystore/2020-06-15/examples-1.json' INFO : wheel : adding 'botocore/data/identitystore/2020-06-15/paginators-1.json' INFO : wheel : adding 'botocore/data/identitystore/2020-06-15/service-2.json' INFO : wheel : adding 'botocore/data/imagebuilder/2019-12-02/examples-1.json' INFO : wheel : adding 'botocore/data/imagebuilder/2019-12-02/paginators-1.json' INFO : wheel : adding 'botocore/data/imagebuilder/2019-12-02/service-2.json' INFO : wheel : adding 'botocore/data/importexport/2010-06-01/paginators-1.json' INFO : wheel : adding 'botocore/data/importexport/2010-06-01/service-2.json' INFO : wheel : adding 'botocore/data/inspector/2015-08-18/service-2.json' INFO : wheel : adding 'botocore/data/inspector/2016-02-16/examples-1.json' INFO : wheel : adding 'botocore/data/inspector/2016-02-16/paginators-1.json' INFO : wheel : adding 'botocore/data/inspector/2016-02-16/service-2.json' INFO : wheel : adding 'botocore/data/inspector2/2020-06-08/examples-1.json' INFO : wheel : adding 'botocore/data/inspector2/2020-06-08/paginators-1.json' INFO : wheel : adding 'botocore/data/inspector2/2020-06-08/paginators-1.sdk-extras.json' INFO : wheel : adding 'botocore/data/inspector2/2020-06-08/service-2.json' INFO : wheel : adding 'botocore/data/iot/2015-05-28/examples-1.json' INFO : wheel : adding 'botocore/data/iot/2015-05-28/paginators-1.json' INFO : wheel : adding 'botocore/data/iot/2015-05-28/service-2.json' INFO : wheel : adding 'botocore/data/iot-data/2015-05-28/examples-1.json' INFO : wheel : adding 'botocore/data/iot-data/2015-05-28/paginators-1.json' INFO : wheel : adding 'botocore/data/iot-data/2015-05-28/service-2.json' INFO : wheel : adding 'botocore/data/iot-jobs-data/2017-09-29/examples-1.json' INFO : wheel : adding 'botocore/data/iot-jobs-data/2017-09-29/paginators-1.json' INFO : wheel : adding 'botocore/data/iot-jobs-data/2017-09-29/service-2.json' INFO : wheel : adding 'botocore/data/iot1click-devices/2018-05-14/paginators-1.json' INFO : wheel : adding 'botocore/data/iot1click-devices/2018-05-14/service-2.json' INFO : wheel : adding 'botocore/data/iot1click-projects/2018-05-14/examples-1.json' INFO : wheel : adding 'botocore/data/iot1click-projects/2018-05-14/paginators-1.json' INFO : wheel : adding 'botocore/data/iot1click-projects/2018-05-14/service-2.json' INFO : wheel : adding 'botocore/data/iotanalytics/2017-11-27/examples-1.json' INFO : wheel : adding 'botocore/data/iotanalytics/2017-11-27/paginators-1.json' INFO : wheel : adding 'botocore/data/iotanalytics/2017-11-27/service-2.json' INFO : wheel : adding 'botocore/data/iotdeviceadvisor/2020-09-18/examples-1.json' INFO : wheel : adding 'botocore/data/iotdeviceadvisor/2020-09-18/paginators-1.json' INFO : wheel : adding 'botocore/data/iotdeviceadvisor/2020-09-18/service-2.json' INFO : wheel : adding 'botocore/data/iotevents/2018-07-27/examples-1.json' INFO : wheel : adding 'botocore/data/iotevents/2018-07-27/paginators-1.json' INFO : wheel : adding 'botocore/data/iotevents/2018-07-27/service-2.json' INFO : wheel : adding 'botocore/data/iotevents-data/2018-10-23/examples-1.json' INFO : wheel : adding 'botocore/data/iotevents-data/2018-10-23/paginators-1.json' INFO : wheel : adding 'botocore/data/iotevents-data/2018-10-23/service-2.json' INFO : wheel : adding 'botocore/data/iotfleethub/2020-11-03/examples-1.json' INFO : wheel : adding 'botocore/data/iotfleethub/2020-11-03/paginators-1.json' INFO : wheel : adding 'botocore/data/iotfleethub/2020-11-03/service-2.json' INFO : wheel : adding 'botocore/data/iotfleetwise/2021-06-17/paginators-1.json' INFO : wheel : adding 'botocore/data/iotfleetwise/2021-06-17/service-2.json' INFO : wheel : adding 'botocore/data/iotfleetwise/2021-06-17/waiters-2.json' INFO : wheel : adding 'botocore/data/iotsecuretunneling/2018-10-05/examples-1.json' INFO : wheel : adding 'botocore/data/iotsecuretunneling/2018-10-05/paginators-1.json' INFO : wheel : adding 'botocore/data/iotsecuretunneling/2018-10-05/service-2.json' INFO : wheel : adding 'botocore/data/iotsitewise/2019-12-02/examples-1.json' INFO : wheel : adding 'botocore/data/iotsitewise/2019-12-02/paginators-1.json' INFO : wheel : adding 'botocore/data/iotsitewise/2019-12-02/service-2.json' INFO : wheel : adding 'botocore/data/iotsitewise/2019-12-02/waiters-2.json' INFO : wheel : adding 'botocore/data/iotthingsgraph/2018-09-06/examples-1.json' INFO : wheel : adding 'botocore/data/iotthingsgraph/2018-09-06/paginators-1.json' INFO : wheel : adding 'botocore/data/iotthingsgraph/2018-09-06/service-2.json' INFO : wheel : adding 'botocore/data/iottwinmaker/2021-11-29/examples-1.json' INFO : wheel : adding 'botocore/data/iottwinmaker/2021-11-29/paginators-1.json' INFO : wheel : adding 'botocore/data/iottwinmaker/2021-11-29/service-2.json' INFO : wheel : adding 'botocore/data/iottwinmaker/2021-11-29/waiters-2.json' INFO : wheel : adding 'botocore/data/iotwireless/2020-11-22/examples-1.json' INFO : wheel : adding 'botocore/data/iotwireless/2020-11-22/paginators-1.json' INFO : wheel : adding 'botocore/data/iotwireless/2020-11-22/service-2.json' INFO : wheel : adding 'botocore/data/ivs/2020-07-14/examples-1.json' INFO : wheel : adding 'botocore/data/ivs/2020-07-14/paginators-1.json' INFO : wheel : adding 'botocore/data/ivs/2020-07-14/service-2.json' INFO : wheel : adding 'botocore/data/ivschat/2020-07-14/examples-1.json' INFO : wheel : adding 'botocore/data/ivschat/2020-07-14/paginators-1.json' INFO : wheel : adding 'botocore/data/ivschat/2020-07-14/service-2.json' INFO : wheel : adding 'botocore/data/kafka/2018-11-14/paginators-1.json' INFO : wheel : adding 'botocore/data/kafka/2018-11-14/service-2.json' INFO : wheel : adding 'botocore/data/kafkaconnect/2021-09-14/examples-1.json' INFO : wheel : adding 'botocore/data/kafkaconnect/2021-09-14/paginators-1.json' INFO : wheel : adding 'botocore/data/kafkaconnect/2021-09-14/service-2.json' INFO : wheel : adding 'botocore/data/kendra/2019-02-03/examples-1.json' INFO : wheel : adding 'botocore/data/kendra/2019-02-03/paginators-1.json' INFO : wheel : adding 'botocore/data/kendra/2019-02-03/service-2.json' INFO : wheel : adding 'botocore/data/keyspaces/2022-02-10/examples-1.json' INFO : wheel : adding 'botocore/data/keyspaces/2022-02-10/paginators-1.json' INFO : wheel : adding 'botocore/data/keyspaces/2022-02-10/service-2.json' INFO : wheel : adding 'botocore/data/keyspaces/2022-02-10/waiters-2.json' INFO : wheel : adding 'botocore/data/kinesis/2013-12-02/examples-1.json' INFO : wheel : adding 'botocore/data/kinesis/2013-12-02/paginators-1.json' INFO : wheel : adding 'botocore/data/kinesis/2013-12-02/service-2.json' INFO : wheel : adding 'botocore/data/kinesis/2013-12-02/waiters-2.json' INFO : wheel : adding 'botocore/data/kinesis-video-archived-media/2017-09-30/examples-1.json' INFO : wheel : adding 'botocore/data/kinesis-video-archived-media/2017-09-30/paginators-1.json' INFO : wheel : adding 'botocore/data/kinesis-video-archived-media/2017-09-30/service-2.json' INFO : wheel : adding 'botocore/data/kinesis-video-media/2017-09-30/examples-1.json' INFO : wheel : adding 'botocore/data/kinesis-video-media/2017-09-30/paginators-1.json' INFO : wheel : adding 'botocore/data/kinesis-video-media/2017-09-30/service-2.json' INFO : wheel : adding 'botocore/data/kinesis-video-signaling/2019-12-04/examples-1.json' INFO : wheel : adding 'botocore/data/kinesis-video-signaling/2019-12-04/paginators-1.json' INFO : wheel : adding 'botocore/data/kinesis-video-signaling/2019-12-04/service-2.json' INFO : wheel : adding 'botocore/data/kinesisanalytics/2015-08-14/examples-1.json' INFO : wheel : adding 'botocore/data/kinesisanalytics/2015-08-14/paginators-1.json' INFO : wheel : adding 'botocore/data/kinesisanalytics/2015-08-14/service-2.json' INFO : wheel : adding 'botocore/data/kinesisanalyticsv2/2018-05-23/examples-1.json' INFO : wheel : adding 'botocore/data/kinesisanalyticsv2/2018-05-23/paginators-1.json' INFO : wheel : adding 'botocore/data/kinesisanalyticsv2/2018-05-23/service-2.json' INFO : wheel : adding 'botocore/data/kinesisvideo/2017-09-30/examples-1.json' INFO : wheel : adding 'botocore/data/kinesisvideo/2017-09-30/paginators-1.json' INFO : wheel : adding 'botocore/data/kinesisvideo/2017-09-30/service-2.json' INFO : wheel : adding 'botocore/data/kms/2014-11-01/examples-1.json' INFO : wheel : adding 'botocore/data/kms/2014-11-01/paginators-1.json' INFO : wheel : adding 'botocore/data/kms/2014-11-01/service-2.json' INFO : wheel : adding 'botocore/data/lakeformation/2017-03-31/examples-1.json' INFO : wheel : adding 'botocore/data/lakeformation/2017-03-31/paginators-1.json' INFO : wheel : adding 'botocore/data/lakeformation/2017-03-31/paginators-1.sdk-extras.json' INFO : wheel : adding 'botocore/data/lakeformation/2017-03-31/service-2.json' INFO : wheel : adding 'botocore/data/lambda/2014-11-11/service-2.json' INFO : wheel : adding 'botocore/data/lambda/2015-03-31/examples-1.json' INFO : wheel : adding 'botocore/data/lambda/2015-03-31/paginators-1.json' INFO : wheel : adding 'botocore/data/lambda/2015-03-31/service-2.json' INFO : wheel : adding 'botocore/data/lambda/2015-03-31/waiters-2.json' INFO : wheel : adding 'botocore/data/lex-models/2017-04-19/examples-1.json' INFO : wheel : adding 'botocore/data/lex-models/2017-04-19/paginators-1.json' INFO : wheel : adding 'botocore/data/lex-models/2017-04-19/service-2.json' INFO : wheel : adding 'botocore/data/lex-runtime/2016-11-28/examples-1.json' INFO : wheel : adding 'botocore/data/lex-runtime/2016-11-28/paginators-1.json' INFO : wheel : adding 'botocore/data/lex-runtime/2016-11-28/service-2.json' INFO : wheel : adding 'botocore/data/lexv2-models/2020-08-07/examples-1.json' INFO : wheel : adding 'botocore/data/lexv2-models/2020-08-07/paginators-1.json' INFO : wheel : adding 'botocore/data/lexv2-models/2020-08-07/service-2.json' INFO : wheel : adding 'botocore/data/lexv2-models/2020-08-07/waiters-2.json' INFO : wheel : adding 'botocore/data/lexv2-runtime/2020-08-07/examples-1.json' INFO : wheel : adding 'botocore/data/lexv2-runtime/2020-08-07/paginators-1.json' INFO : wheel : adding 'botocore/data/lexv2-runtime/2020-08-07/service-2.json' INFO : wheel : adding 'botocore/data/license-manager/2018-08-01/examples-1.json' INFO : wheel : adding 'botocore/data/license-manager/2018-08-01/paginators-1.json' INFO : wheel : adding 'botocore/data/license-manager/2018-08-01/service-2.json' INFO : wheel : adding 'botocore/data/license-manager-user-subscriptions/2018-05-10/paginators-1.json' INFO : wheel : adding 'botocore/data/license-manager-user-subscriptions/2018-05-10/service-2.json' INFO : wheel : adding 'botocore/data/lightsail/2016-11-28/examples-1.json' INFO : wheel : adding 'botocore/data/lightsail/2016-11-28/paginators-1.json' INFO : wheel : adding 'botocore/data/lightsail/2016-11-28/service-2.json' INFO : wheel : adding 'botocore/data/location/2020-11-19/examples-1.json' INFO : wheel : adding 'botocore/data/location/2020-11-19/paginators-1.json' INFO : wheel : adding 'botocore/data/location/2020-11-19/service-2.json' INFO : wheel : adding 'botocore/data/logs/2014-03-28/examples-1.json' INFO : wheel : adding 'botocore/data/logs/2014-03-28/paginators-1.json' INFO : wheel : adding 'botocore/data/logs/2014-03-28/service-2.json' INFO : wheel : adding 'botocore/data/lookoutequipment/2020-12-15/examples-1.json' INFO : wheel : adding 'botocore/data/lookoutequipment/2020-12-15/paginators-1.json' INFO : wheel : adding 'botocore/data/lookoutequipment/2020-12-15/service-2.json' INFO : wheel : adding 'botocore/data/lookoutmetrics/2017-07-25/examples-1.json' INFO : wheel : adding 'botocore/data/lookoutmetrics/2017-07-25/paginators-1.json' INFO : wheel : adding 'botocore/data/lookoutmetrics/2017-07-25/service-2.json' INFO : wheel : adding 'botocore/data/lookoutvision/2020-11-20/examples-1.json' INFO : wheel : adding 'botocore/data/lookoutvision/2020-11-20/paginators-1.json' INFO : wheel : adding 'botocore/data/lookoutvision/2020-11-20/service-2.json' INFO : wheel : adding 'botocore/data/m2/2021-04-28/paginators-1.json' INFO : wheel : adding 'botocore/data/m2/2021-04-28/service-2.json' INFO : wheel : adding 'botocore/data/machinelearning/2014-12-12/examples-1.json' INFO : wheel : adding 'botocore/data/machinelearning/2014-12-12/paginators-1.json' INFO : wheel : adding 'botocore/data/machinelearning/2014-12-12/service-2.json' INFO : wheel : adding 'botocore/data/machinelearning/2014-12-12/waiters-2.json' INFO : wheel : adding 'botocore/data/macie/2017-12-19/examples-1.json' INFO : wheel : adding 'botocore/data/macie/2017-12-19/paginators-1.json' INFO : wheel : adding 'botocore/data/macie/2017-12-19/service-2.json' INFO : wheel : adding 'botocore/data/macie2/2020-01-01/paginators-1.json' INFO : wheel : adding 'botocore/data/macie2/2020-01-01/service-2.json' INFO : wheel : adding 'botocore/data/macie2/2020-01-01/waiters-2.json' INFO : wheel : adding 'botocore/data/managedblockchain/2018-09-24/examples-1.json' INFO : wheel : adding 'botocore/data/managedblockchain/2018-09-24/paginators-1.json' INFO : wheel : adding 'botocore/data/managedblockchain/2018-09-24/service-2.json' INFO : wheel : adding 'botocore/data/marketplace-catalog/2018-09-17/examples-1.json' INFO : wheel : adding 'botocore/data/marketplace-catalog/2018-09-17/paginators-1.json' INFO : wheel : adding 'botocore/data/marketplace-catalog/2018-09-17/service-2.json' INFO : wheel : adding 'botocore/data/marketplace-entitlement/2017-01-11/examples-1.json' INFO : wheel : adding 'botocore/data/marketplace-entitlement/2017-01-11/paginators-1.json' INFO : wheel : adding 'botocore/data/marketplace-entitlement/2017-01-11/service-2.json' INFO : wheel : adding 'botocore/data/marketplacecommerceanalytics/2015-07-01/examples-1.json' INFO : wheel : adding 'botocore/data/marketplacecommerceanalytics/2015-07-01/paginators-1.json' INFO : wheel : adding 'botocore/data/marketplacecommerceanalytics/2015-07-01/service-2.json' INFO : wheel : adding 'botocore/data/mediaconnect/2018-11-14/paginators-1.json' INFO : wheel : adding 'botocore/data/mediaconnect/2018-11-14/service-2.json' INFO : wheel : adding 'botocore/data/mediaconnect/2018-11-14/waiters-2.json' INFO : wheel : adding 'botocore/data/mediaconvert/2017-08-29/paginators-1.json' INFO : wheel : adding 'botocore/data/mediaconvert/2017-08-29/service-2.json' INFO : wheel : adding 'botocore/data/medialive/2017-10-14/paginators-1.json' INFO : wheel : adding 'botocore/data/medialive/2017-10-14/service-2.json' INFO : wheel : adding 'botocore/data/medialive/2017-10-14/waiters-2.json' INFO : wheel : adding 'botocore/data/mediapackage/2017-10-12/paginators-1.json' INFO : wheel : adding 'botocore/data/mediapackage/2017-10-12/service-2.json' INFO : wheel : adding 'botocore/data/mediapackage-vod/2018-11-07/paginators-1.json' INFO : wheel : adding 'botocore/data/mediapackage-vod/2018-11-07/service-2.json' INFO : wheel : adding 'botocore/data/mediastore/2017-09-01/examples-1.json' INFO : wheel : adding 'botocore/data/mediastore/2017-09-01/paginators-1.json' INFO : wheel : adding 'botocore/data/mediastore/2017-09-01/service-2.json' INFO : wheel : adding 'botocore/data/mediastore-data/2017-09-01/examples-1.json' INFO : wheel : adding 'botocore/data/mediastore-data/2017-09-01/paginators-1.json' INFO : wheel : adding 'botocore/data/mediastore-data/2017-09-01/service-2.json' INFO : wheel : adding 'botocore/data/mediatailor/2018-04-23/paginators-1.json' INFO : wheel : adding 'botocore/data/mediatailor/2018-04-23/service-2.json' INFO : wheel : adding 'botocore/data/memorydb/2021-01-01/examples-1.json' INFO : wheel : adding 'botocore/data/memorydb/2021-01-01/paginators-1.json' INFO : wheel : adding 'botocore/data/memorydb/2021-01-01/service-2.json' INFO : wheel : adding 'botocore/data/meteringmarketplace/2016-01-14/examples-1.json' INFO : wheel : adding 'botocore/data/meteringmarketplace/2016-01-14/paginators-1.json' INFO : wheel : adding 'botocore/data/meteringmarketplace/2016-01-14/service-2.json' INFO : wheel : adding 'botocore/data/mgh/2017-05-31/examples-1.json' INFO : wheel : adding 'botocore/data/mgh/2017-05-31/paginators-1.json' INFO : wheel : adding 'botocore/data/mgh/2017-05-31/service-2.json' INFO : wheel : adding 'botocore/data/mgn/2020-02-26/examples-1.json' INFO : wheel : adding 'botocore/data/mgn/2020-02-26/paginators-1.json' INFO : wheel : adding 'botocore/data/mgn/2020-02-26/service-2.json' INFO : wheel : adding 'botocore/data/migration-hub-refactor-spaces/2021-10-26/examples-1.json' INFO : wheel : adding 'botocore/data/migration-hub-refactor-spaces/2021-10-26/paginators-1.json' INFO : wheel : adding 'botocore/data/migration-hub-refactor-spaces/2021-10-26/service-2.json' INFO : wheel : adding 'botocore/data/migrationhub-config/2019-06-30/examples-1.json' INFO : wheel : adding 'botocore/data/migrationhub-config/2019-06-30/paginators-1.json' INFO : wheel : adding 'botocore/data/migrationhub-config/2019-06-30/service-2.json' INFO : wheel : adding 'botocore/data/migrationhuborchestrator/2021-08-28/paginators-1.json' INFO : wheel : adding 'botocore/data/migrationhuborchestrator/2021-08-28/service-2.json' INFO : wheel : adding 'botocore/data/migrationhuborchestrator/2021-08-28/waiters-2.json' INFO : wheel : adding 'botocore/data/migrationhubstrategy/2020-02-19/examples-1.json' INFO : wheel : adding 'botocore/data/migrationhubstrategy/2020-02-19/paginators-1.json' INFO : wheel : adding 'botocore/data/migrationhubstrategy/2020-02-19/paginators-1.sdk-extras.json' INFO : wheel : adding 'botocore/data/migrationhubstrategy/2020-02-19/service-2.json' INFO : wheel : adding 'botocore/data/mobile/2017-07-01/examples-1.json' INFO : wheel : adding 'botocore/data/mobile/2017-07-01/paginators-1.json' INFO : wheel : adding 'botocore/data/mobile/2017-07-01/service-2.json' INFO : wheel : adding 'botocore/data/mq/2017-11-27/paginators-1.json' INFO : wheel : adding 'botocore/data/mq/2017-11-27/service-2.json' INFO : wheel : adding 'botocore/data/mturk/2017-01-17/examples-1.json' INFO : wheel : adding 'botocore/data/mturk/2017-01-17/paginators-1.json' INFO : wheel : adding 'botocore/data/mturk/2017-01-17/service-2.json' INFO : wheel : adding 'botocore/data/mwaa/2020-07-01/examples-1.json' INFO : wheel : adding 'botocore/data/mwaa/2020-07-01/paginators-1.json' INFO : wheel : adding 'botocore/data/mwaa/2020-07-01/service-2.json' INFO : wheel : adding 'botocore/data/neptune/2014-10-31/examples-1.json' INFO : wheel : adding 'botocore/data/neptune/2014-10-31/paginators-1.json' INFO : wheel : adding 'botocore/data/neptune/2014-10-31/service-2.json' INFO : wheel : adding 'botocore/data/neptune/2014-10-31/service-2.sdk-extras.json' INFO : wheel : adding 'botocore/data/neptune/2014-10-31/waiters-2.json' INFO : wheel : adding 'botocore/data/network-firewall/2020-11-12/examples-1.json' INFO : wheel : adding 'botocore/data/network-firewall/2020-11-12/paginators-1.json' INFO : wheel : adding 'botocore/data/network-firewall/2020-11-12/service-2.json' INFO : wheel : adding 'botocore/data/networkmanager/2019-07-05/examples-1.json' INFO : wheel : adding 'botocore/data/networkmanager/2019-07-05/paginators-1.json' INFO : wheel : adding 'botocore/data/networkmanager/2019-07-05/service-2.json' INFO : wheel : adding 'botocore/data/nimble/2020-08-01/examples-1.json' INFO : wheel : adding 'botocore/data/nimble/2020-08-01/paginators-1.json' INFO : wheel : adding 'botocore/data/nimble/2020-08-01/service-2.json' INFO : wheel : adding 'botocore/data/nimble/2020-08-01/waiters-2.json' INFO : wheel : adding 'botocore/data/opensearch/2021-01-01/examples-1.json' INFO : wheel : adding 'botocore/data/opensearch/2021-01-01/paginators-1.json' INFO : wheel : adding 'botocore/data/opensearch/2021-01-01/service-2.json' INFO : wheel : adding 'botocore/data/opsworks/2013-02-18/examples-1.json' INFO : wheel : adding 'botocore/data/opsworks/2013-02-18/paginators-1.json' INFO : wheel : adding 'botocore/data/opsworks/2013-02-18/service-2.json' INFO : wheel : adding 'botocore/data/opsworks/2013-02-18/waiters-2.json' INFO : wheel : adding 'botocore/data/opsworkscm/2016-11-01/examples-1.json' INFO : wheel : adding 'botocore/data/opsworkscm/2016-11-01/paginators-1.json' INFO : wheel : adding 'botocore/data/opsworkscm/2016-11-01/service-2.json' INFO : wheel : adding 'botocore/data/opsworkscm/2016-11-01/waiters-2.json' INFO : wheel : adding 'botocore/data/organizations/2016-11-28/examples-1.json' INFO : wheel : adding 'botocore/data/organizations/2016-11-28/paginators-1.json' INFO : wheel : adding 'botocore/data/organizations/2016-11-28/service-2.json' INFO : wheel : adding 'botocore/data/outposts/2019-12-03/examples-1.json' INFO : wheel : adding 'botocore/data/outposts/2019-12-03/paginators-1.json' INFO : wheel : adding 'botocore/data/outposts/2019-12-03/service-2.json' INFO : wheel : adding 'botocore/data/panorama/2019-07-24/examples-1.json' INFO : wheel : adding 'botocore/data/panorama/2019-07-24/paginators-1.json' INFO : wheel : adding 'botocore/data/panorama/2019-07-24/service-2.json' INFO : wheel : adding 'botocore/data/personalize/2018-05-22/examples-1.json' INFO : wheel : adding 'botocore/data/personalize/2018-05-22/paginators-1.json' INFO : wheel : adding 'botocore/data/personalize/2018-05-22/service-2.json' INFO : wheel : adding 'botocore/data/personalize-events/2018-03-22/examples-1.json' INFO : wheel : adding 'botocore/data/personalize-events/2018-03-22/paginators-1.json' INFO : wheel : adding 'botocore/data/personalize-events/2018-03-22/service-2.json' INFO : wheel : adding 'botocore/data/personalize-runtime/2018-05-22/examples-1.json' INFO : wheel : adding 'botocore/data/personalize-runtime/2018-05-22/paginators-1.json' INFO : wheel : adding 'botocore/data/personalize-runtime/2018-05-22/service-2.json' INFO : wheel : adding 'botocore/data/pi/2018-02-27/examples-1.json' INFO : wheel : adding 'botocore/data/pi/2018-02-27/paginators-1.json' INFO : wheel : adding 'botocore/data/pi/2018-02-27/service-2.json' INFO : wheel : adding 'botocore/data/pinpoint/2016-12-01/examples-1.json' INFO : wheel : adding 'botocore/data/pinpoint/2016-12-01/service-2.json' INFO : wheel : adding 'botocore/data/pinpoint-email/2018-07-26/examples-1.json' INFO : wheel : adding 'botocore/data/pinpoint-email/2018-07-26/paginators-1.json' INFO : wheel : adding 'botocore/data/pinpoint-email/2018-07-26/service-2.json' INFO : wheel : adding 'botocore/data/pinpoint-sms-voice/2018-09-05/service-2.json' INFO : wheel : adding 'botocore/data/pinpoint-sms-voice-v2/2022-03-31/examples-1.json' INFO : wheel : adding 'botocore/data/pinpoint-sms-voice-v2/2022-03-31/paginators-1.json' INFO : wheel : adding 'botocore/data/pinpoint-sms-voice-v2/2022-03-31/paginators-1.sdk-extras.json' INFO : wheel : adding 'botocore/data/pinpoint-sms-voice-v2/2022-03-31/service-2.json' INFO : wheel : adding 'botocore/data/pinpoint-sms-voice-v2/2022-03-31/waiters-2.json' INFO : wheel : adding 'botocore/data/polly/2016-06-10/examples-1.json' INFO : wheel : adding 'botocore/data/polly/2016-06-10/paginators-1.json' INFO : wheel : adding 'botocore/data/polly/2016-06-10/service-2.json' INFO : wheel : adding 'botocore/data/pricing/2017-10-15/examples-1.json' INFO : wheel : adding 'botocore/data/pricing/2017-10-15/paginators-1.json' INFO : wheel : adding 'botocore/data/pricing/2017-10-15/service-2.json' INFO : wheel : adding 'botocore/data/privatenetworks/2021-12-03/paginators-1.json' INFO : wheel : adding 'botocore/data/privatenetworks/2021-12-03/service-2.json' INFO : wheel : adding 'botocore/data/proton/2020-07-20/examples-1.json' INFO : wheel : adding 'botocore/data/proton/2020-07-20/paginators-1.json' INFO : wheel : adding 'botocore/data/proton/2020-07-20/service-2.json' INFO : wheel : adding 'botocore/data/proton/2020-07-20/waiters-2.json' INFO : wheel : adding 'botocore/data/qldb/2019-01-02/examples-1.json' INFO : wheel : adding 'botocore/data/qldb/2019-01-02/paginators-1.json' INFO : wheel : adding 'botocore/data/qldb/2019-01-02/service-2.json' INFO : wheel : adding 'botocore/data/qldb-session/2019-07-11/examples-1.json' INFO : wheel : adding 'botocore/data/qldb-session/2019-07-11/paginators-1.json' INFO : wheel : adding 'botocore/data/qldb-session/2019-07-11/service-2.json' INFO : wheel : adding 'botocore/data/quicksight/2018-04-01/examples-1.json' INFO : wheel : adding 'botocore/data/quicksight/2018-04-01/paginators-1.json' INFO : wheel : adding 'botocore/data/quicksight/2018-04-01/paginators-1.sdk-extras.json' INFO : wheel : adding 'botocore/data/quicksight/2018-04-01/service-2.json' INFO : wheel : adding 'botocore/data/ram/2018-01-04/examples-1.json' INFO : wheel : adding 'botocore/data/ram/2018-01-04/paginators-1.json' INFO : wheel : adding 'botocore/data/ram/2018-01-04/service-2.json' INFO : wheel : adding 'botocore/data/rbin/2021-06-15/examples-1.json' INFO : wheel : adding 'botocore/data/rbin/2021-06-15/paginators-1.json' INFO : wheel : adding 'botocore/data/rbin/2021-06-15/service-2.json' INFO : wheel : adding 'botocore/data/rds/2014-09-01/paginators-1.json' INFO : wheel : adding 'botocore/data/rds/2014-09-01/service-2.json' INFO : wheel : adding 'botocore/data/rds/2014-09-01/waiters-2.json' INFO : wheel : adding 'botocore/data/rds/2014-10-31/examples-1.json' INFO : wheel : adding 'botocore/data/rds/2014-10-31/paginators-1.json' INFO : wheel : adding 'botocore/data/rds/2014-10-31/service-2.json' INFO : wheel : adding 'botocore/data/rds/2014-10-31/service-2.sdk-extras.json' INFO : wheel : adding 'botocore/data/rds/2014-10-31/waiters-2.json' INFO : wheel : adding 'botocore/data/rds-data/2018-08-01/examples-1.json' INFO : wheel : adding 'botocore/data/rds-data/2018-08-01/paginators-1.json' INFO : wheel : adding 'botocore/data/rds-data/2018-08-01/service-2.json' INFO : wheel : adding 'botocore/data/redshift/2012-12-01/examples-1.json' INFO : wheel : adding 'botocore/data/redshift/2012-12-01/paginators-1.json' INFO : wheel : adding 'botocore/data/redshift/2012-12-01/service-2.json' INFO : wheel : adding 'botocore/data/redshift/2012-12-01/waiters-2.json' INFO : wheel : adding 'botocore/data/redshift-data/2019-12-20/examples-1.json' INFO : wheel : adding 'botocore/data/redshift-data/2019-12-20/paginators-1.json' INFO : wheel : adding 'botocore/data/redshift-data/2019-12-20/paginators-1.sdk-extras.json' INFO : wheel : adding 'botocore/data/redshift-data/2019-12-20/service-2.json' INFO : wheel : adding 'botocore/data/redshift-serverless/2021-04-21/paginators-1.json' INFO : wheel : adding 'botocore/data/redshift-serverless/2021-04-21/service-2.json' INFO : wheel : adding 'botocore/data/rekognition/2016-06-27/examples-1.json' INFO : wheel : adding 'botocore/data/rekognition/2016-06-27/paginators-1.json' INFO : wheel : adding 'botocore/data/rekognition/2016-06-27/service-2.json' INFO : wheel : adding 'botocore/data/rekognition/2016-06-27/waiters-2.json' INFO : wheel : adding 'botocore/data/resiliencehub/2020-04-30/examples-1.json' INFO : wheel : adding 'botocore/data/resiliencehub/2020-04-30/paginators-1.json' INFO : wheel : adding 'botocore/data/resiliencehub/2020-04-30/service-2.json' INFO : wheel : adding 'botocore/data/resource-groups/2017-11-27/examples-1.json' INFO : wheel : adding 'botocore/data/resource-groups/2017-11-27/paginators-1.json' INFO : wheel : adding 'botocore/data/resource-groups/2017-11-27/service-2.json' INFO : wheel : adding 'botocore/data/resourcegroupstaggingapi/2017-01-26/examples-1.json' INFO : wheel : adding 'botocore/data/resourcegroupstaggingapi/2017-01-26/paginators-1.json' INFO : wheel : adding 'botocore/data/resourcegroupstaggingapi/2017-01-26/service-2.json' INFO : wheel : adding 'botocore/data/robomaker/2018-06-29/examples-1.json' INFO : wheel : adding 'botocore/data/robomaker/2018-06-29/paginators-1.json' INFO : wheel : adding 'botocore/data/robomaker/2018-06-29/service-2.json' INFO : wheel : adding 'botocore/data/rolesanywhere/2018-05-10/paginators-1.json' INFO : wheel : adding 'botocore/data/rolesanywhere/2018-05-10/service-2.json' INFO : wheel : adding 'botocore/data/route53/2013-04-01/examples-1.json' INFO : wheel : adding 'botocore/data/route53/2013-04-01/paginators-1.json' INFO : wheel : adding 'botocore/data/route53/2013-04-01/service-2.json' INFO : wheel : adding 'botocore/data/route53/2013-04-01/waiters-2.json' INFO : wheel : adding 'botocore/data/route53-recovery-cluster/2019-12-02/examples-1.json' INFO : wheel : adding 'botocore/data/route53-recovery-cluster/2019-12-02/paginators-1.json' INFO : wheel : adding 'botocore/data/route53-recovery-cluster/2019-12-02/service-2.json' INFO : wheel : adding 'botocore/data/route53-recovery-control-config/2020-11-02/paginators-1.json' INFO : wheel : adding 'botocore/data/route53-recovery-control-config/2020-11-02/service-2.json' INFO : wheel : adding 'botocore/data/route53-recovery-control-config/2020-11-02/waiters-2.json' INFO : wheel : adding 'botocore/data/route53-recovery-readiness/2019-12-02/paginators-1.json' INFO : wheel : adding 'botocore/data/route53-recovery-readiness/2019-12-02/service-2.json' INFO : wheel : adding 'botocore/data/route53domains/2014-05-15/examples-1.json' INFO : wheel : adding 'botocore/data/route53domains/2014-05-15/paginators-1.json' INFO : wheel : adding 'botocore/data/route53domains/2014-05-15/service-2.json' INFO : wheel : adding 'botocore/data/route53resolver/2018-04-01/examples-1.json' INFO : wheel : adding 'botocore/data/route53resolver/2018-04-01/paginators-1.json' INFO : wheel : adding 'botocore/data/route53resolver/2018-04-01/paginators-1.sdk-extras.json' INFO : wheel : adding 'botocore/data/route53resolver/2018-04-01/service-2.json' INFO : wheel : adding 'botocore/data/rum/2018-05-10/examples-1.json' INFO : wheel : adding 'botocore/data/rum/2018-05-10/paginators-1.json' INFO : wheel : adding 'botocore/data/rum/2018-05-10/service-2.json' INFO : wheel : adding 'botocore/data/s3/2006-03-01/examples-1.json' INFO : wheel : adding 'botocore/data/s3/2006-03-01/paginators-1.json' INFO : wheel : adding 'botocore/data/s3/2006-03-01/service-2.json' INFO : wheel : adding 'botocore/data/s3/2006-03-01/waiters-2.json' INFO : wheel : adding 'botocore/data/s3control/2018-08-20/examples-1.json' INFO : wheel : adding 'botocore/data/s3control/2018-08-20/paginators-1.json' INFO : wheel : adding 'botocore/data/s3control/2018-08-20/service-2.json' INFO : wheel : adding 'botocore/data/s3outposts/2017-07-25/examples-1.json' INFO : wheel : adding 'botocore/data/s3outposts/2017-07-25/paginators-1.json' INFO : wheel : adding 'botocore/data/s3outposts/2017-07-25/service-2.json' INFO : wheel : adding 'botocore/data/sagemaker/2017-07-24/examples-1.json' INFO : wheel : adding 'botocore/data/sagemaker/2017-07-24/paginators-1.json' INFO : wheel : adding 'botocore/data/sagemaker/2017-07-24/service-2.json' INFO : wheel : adding 'botocore/data/sagemaker/2017-07-24/waiters-2.json' INFO : wheel : adding 'botocore/data/sagemaker-a2i-runtime/2019-11-07/examples-1.json' INFO : wheel : adding 'botocore/data/sagemaker-a2i-runtime/2019-11-07/paginators-1.json' INFO : wheel : adding 'botocore/data/sagemaker-a2i-runtime/2019-11-07/service-2.json' INFO : wheel : adding 'botocore/data/sagemaker-edge/2020-09-23/examples-1.json' INFO : wheel : adding 'botocore/data/sagemaker-edge/2020-09-23/paginators-1.json' INFO : wheel : adding 'botocore/data/sagemaker-edge/2020-09-23/service-2.json' INFO : wheel : adding 'botocore/data/sagemaker-featurestore-runtime/2020-07-01/examples-1.json' INFO : wheel : adding 'botocore/data/sagemaker-featurestore-runtime/2020-07-01/paginators-1.json' INFO : wheel : adding 'botocore/data/sagemaker-featurestore-runtime/2020-07-01/service-2.json' INFO : wheel : adding 'botocore/data/sagemaker-runtime/2017-05-13/examples-1.json' INFO : wheel : adding 'botocore/data/sagemaker-runtime/2017-05-13/paginators-1.json' INFO : wheel : adding 'botocore/data/sagemaker-runtime/2017-05-13/service-2.json' INFO : wheel : adding 'botocore/data/savingsplans/2019-06-28/examples-1.json' INFO : wheel : adding 'botocore/data/savingsplans/2019-06-28/paginators-1.json' INFO : wheel : adding 'botocore/data/savingsplans/2019-06-28/service-2.json' INFO : wheel : adding 'botocore/data/schemas/2019-12-02/paginators-1.json' INFO : wheel : adding 'botocore/data/schemas/2019-12-02/service-2.json' INFO : wheel : adding 'botocore/data/schemas/2019-12-02/waiters-2.json' INFO : wheel : adding 'botocore/data/sdb/2009-04-15/paginators-1.json' INFO : wheel : adding 'botocore/data/sdb/2009-04-15/service-2.json' INFO : wheel : adding 'botocore/data/secretsmanager/2017-10-17/examples-1.json' INFO : wheel : adding 'botocore/data/secretsmanager/2017-10-17/paginators-1.json' INFO : wheel : adding 'botocore/data/secretsmanager/2017-10-17/service-2.json' INFO : wheel : adding 'botocore/data/secretsmanager/2017-10-17/service-2.sdk-extras.json' INFO : wheel : adding 'botocore/data/securityhub/2018-10-26/examples-1.json' INFO : wheel : adding 'botocore/data/securityhub/2018-10-26/paginators-1.json' INFO : wheel : adding 'botocore/data/securityhub/2018-10-26/service-2.json' INFO : wheel : adding 'botocore/data/serverlessrepo/2017-09-08/paginators-1.json' INFO : wheel : adding 'botocore/data/serverlessrepo/2017-09-08/service-2.json' INFO : wheel : adding 'botocore/data/service-quotas/2019-06-24/examples-1.json' INFO : wheel : adding 'botocore/data/service-quotas/2019-06-24/paginators-1.json' INFO : wheel : adding 'botocore/data/service-quotas/2019-06-24/service-2.json' INFO : wheel : adding 'botocore/data/servicecatalog/2015-12-10/examples-1.json' INFO : wheel : adding 'botocore/data/servicecatalog/2015-12-10/paginators-1.json' INFO : wheel : adding 'botocore/data/servicecatalog/2015-12-10/service-2.json' INFO : wheel : adding 'botocore/data/servicecatalog-appregistry/2020-06-24/examples-1.json' INFO : wheel : adding 'botocore/data/servicecatalog-appregistry/2020-06-24/paginators-1.json' INFO : wheel : adding 'botocore/data/servicecatalog-appregistry/2020-06-24/service-2.json' INFO : wheel : adding 'botocore/data/servicediscovery/2017-03-14/examples-1.json' INFO : wheel : adding 'botocore/data/servicediscovery/2017-03-14/paginators-1.json' INFO : wheel : adding 'botocore/data/servicediscovery/2017-03-14/service-2.json' INFO : wheel : adding 'botocore/data/ses/2010-12-01/examples-1.json' INFO : wheel : adding 'botocore/data/ses/2010-12-01/paginators-1.json' INFO : wheel : adding 'botocore/data/ses/2010-12-01/service-2.json' INFO : wheel : adding 'botocore/data/ses/2010-12-01/waiters-2.json' INFO : wheel : adding 'botocore/data/sesv2/2019-09-27/examples-1.json' INFO : wheel : adding 'botocore/data/sesv2/2019-09-27/paginators-1.json' INFO : wheel : adding 'botocore/data/sesv2/2019-09-27/service-2.json' INFO : wheel : adding 'botocore/data/shield/2016-06-02/examples-1.json' INFO : wheel : adding 'botocore/data/shield/2016-06-02/paginators-1.json' INFO : wheel : adding 'botocore/data/shield/2016-06-02/service-2.json' INFO : wheel : adding 'botocore/data/signer/2017-08-25/examples-1.json' INFO : wheel : adding 'botocore/data/signer/2017-08-25/paginators-1.json' INFO : wheel : adding 'botocore/data/signer/2017-08-25/service-2.json' INFO : wheel : adding 'botocore/data/signer/2017-08-25/waiters-2.json' INFO : wheel : adding 'botocore/data/sms/2016-10-24/examples-1.json' INFO : wheel : adding 'botocore/data/sms/2016-10-24/paginators-1.json' INFO : wheel : adding 'botocore/data/sms/2016-10-24/service-2.json' INFO : wheel : adding 'botocore/data/sms-voice/2018-09-05/service-2.json' INFO : wheel : adding 'botocore/data/snow-device-management/2021-08-04/examples-1.json' INFO : wheel : adding 'botocore/data/snow-device-management/2021-08-04/paginators-1.json' INFO : wheel : adding 'botocore/data/snow-device-management/2021-08-04/service-2.json' INFO : wheel : adding 'botocore/data/snowball/2016-06-30/examples-1.json' INFO : wheel : adding 'botocore/data/snowball/2016-06-30/paginators-1.json' INFO : wheel : adding 'botocore/data/snowball/2016-06-30/service-2.json' INFO : wheel : adding 'botocore/data/sns/2010-03-31/examples-1.json' INFO : wheel : adding 'botocore/data/sns/2010-03-31/paginators-1.json' INFO : wheel : adding 'botocore/data/sns/2010-03-31/service-2.json' INFO : wheel : adding 'botocore/data/sqs/2012-11-05/examples-1.json' INFO : wheel : adding 'botocore/data/sqs/2012-11-05/paginators-1.json' INFO : wheel : adding 'botocore/data/sqs/2012-11-05/service-2.json' INFO : wheel : adding 'botocore/data/ssm/2014-11-06/examples-1.json' INFO : wheel : adding 'botocore/data/ssm/2014-11-06/paginators-1.json' INFO : wheel : adding 'botocore/data/ssm/2014-11-06/service-2.json' INFO : wheel : adding 'botocore/data/ssm/2014-11-06/waiters-2.json' INFO : wheel : adding 'botocore/data/ssm-contacts/2021-05-03/examples-1.json' INFO : wheel : adding 'botocore/data/ssm-contacts/2021-05-03/paginators-1.json' INFO : wheel : adding 'botocore/data/ssm-contacts/2021-05-03/service-2.json' INFO : wheel : adding 'botocore/data/ssm-incidents/2018-05-10/examples-1.json' INFO : wheel : adding 'botocore/data/ssm-incidents/2018-05-10/paginators-1.json' INFO : wheel : adding 'botocore/data/ssm-incidents/2018-05-10/service-2.json' INFO : wheel : adding 'botocore/data/ssm-incidents/2018-05-10/waiters-2.json' INFO : wheel : adding 'botocore/data/sso/2019-06-10/examples-1.json' INFO : wheel : adding 'botocore/data/sso/2019-06-10/paginators-1.json' INFO : wheel : adding 'botocore/data/sso/2019-06-10/service-2.json' INFO : wheel : adding 'botocore/data/sso-admin/2020-07-20/examples-1.json' INFO : wheel : adding 'botocore/data/sso-admin/2020-07-20/paginators-1.json' INFO : wheel : adding 'botocore/data/sso-admin/2020-07-20/service-2.json' INFO : wheel : adding 'botocore/data/sso-oidc/2019-06-10/examples-1.json' INFO : wheel : adding 'botocore/data/sso-oidc/2019-06-10/paginators-1.json' INFO : wheel : adding 'botocore/data/sso-oidc/2019-06-10/service-2.json' INFO : wheel : adding 'botocore/data/stepfunctions/2016-11-23/examples-1.json' INFO : wheel : adding 'botocore/data/stepfunctions/2016-11-23/paginators-1.json' INFO : wheel : adding 'botocore/data/stepfunctions/2016-11-23/service-2.json' INFO : wheel : adding 'botocore/data/storagegateway/2013-06-30/examples-1.json' INFO : wheel : adding 'botocore/data/storagegateway/2013-06-30/paginators-1.json' INFO : wheel : adding 'botocore/data/storagegateway/2013-06-30/service-2.json' INFO : wheel : adding 'botocore/data/sts/2011-06-15/examples-1.json' INFO : wheel : adding 'botocore/data/sts/2011-06-15/paginators-1.json' INFO : wheel : adding 'botocore/data/sts/2011-06-15/service-2.json' INFO : wheel : adding 'botocore/data/support/2013-04-15/examples-1.json' INFO : wheel : adding 'botocore/data/support/2013-04-15/paginators-1.json' INFO : wheel : adding 'botocore/data/support/2013-04-15/service-2.json' INFO : wheel : adding 'botocore/data/support-app/2021-08-20/paginators-1.json' INFO : wheel : adding 'botocore/data/support-app/2021-08-20/service-2.json' INFO : wheel : adding 'botocore/data/swf/2012-01-25/examples-1.json' INFO : wheel : adding 'botocore/data/swf/2012-01-25/paginators-1.json' INFO : wheel : adding 'botocore/data/swf/2012-01-25/service-2.json' INFO : wheel : adding 'botocore/data/synthetics/2017-10-11/examples-1.json' INFO : wheel : adding 'botocore/data/synthetics/2017-10-11/paginators-1.json' INFO : wheel : adding 'botocore/data/synthetics/2017-10-11/service-2.json' INFO : wheel : adding 'botocore/data/textract/2018-06-27/examples-1.json' INFO : wheel : adding 'botocore/data/textract/2018-06-27/paginators-1.json' INFO : wheel : adding 'botocore/data/textract/2018-06-27/service-2.json' INFO : wheel : adding 'botocore/data/timestream-query/2018-11-01/examples-1.json' INFO : wheel : adding 'botocore/data/timestream-query/2018-11-01/paginators-1.json' INFO : wheel : adding 'botocore/data/timestream-query/2018-11-01/service-2.json' INFO : wheel : adding 'botocore/data/timestream-write/2018-11-01/examples-1.json' INFO : wheel : adding 'botocore/data/timestream-write/2018-11-01/paginators-1.json' INFO : wheel : adding 'botocore/data/timestream-write/2018-11-01/service-2.json' INFO : wheel : adding 'botocore/data/transcribe/2017-10-26/examples-1.json' INFO : wheel : adding 'botocore/data/transcribe/2017-10-26/paginators-1.json' INFO : wheel : adding 'botocore/data/transcribe/2017-10-26/service-2.json' INFO : wheel : adding 'botocore/data/transfer/2018-11-05/examples-1.json' INFO : wheel : adding 'botocore/data/transfer/2018-11-05/paginators-1.json' INFO : wheel : adding 'botocore/data/transfer/2018-11-05/service-2.json' INFO : wheel : adding 'botocore/data/transfer/2018-11-05/waiters-2.json' INFO : wheel : adding 'botocore/data/translate/2017-07-01/examples-1.json' INFO : wheel : adding 'botocore/data/translate/2017-07-01/paginators-1.json' INFO : wheel : adding 'botocore/data/translate/2017-07-01/service-2.json' INFO : wheel : adding 'botocore/data/voice-id/2021-09-27/examples-1.json' INFO : wheel : adding 'botocore/data/voice-id/2021-09-27/paginators-1.json' INFO : wheel : adding 'botocore/data/voice-id/2021-09-27/service-2.json' INFO : wheel : adding 'botocore/data/waf/2015-08-24/examples-1.json' INFO : wheel : adding 'botocore/data/waf/2015-08-24/paginators-1.json' INFO : wheel : adding 'botocore/data/waf/2015-08-24/service-2.json' INFO : wheel : adding 'botocore/data/waf-regional/2016-11-28/examples-1.json' INFO : wheel : adding 'botocore/data/waf-regional/2016-11-28/paginators-1.json' INFO : wheel : adding 'botocore/data/waf-regional/2016-11-28/service-2.json' INFO : wheel : adding 'botocore/data/wafv2/2019-07-29/examples-1.json' INFO : wheel : adding 'botocore/data/wafv2/2019-07-29/paginators-1.json' INFO : wheel : adding 'botocore/data/wafv2/2019-07-29/service-2.json' INFO : wheel : adding 'botocore/data/wellarchitected/2020-03-31/examples-1.json' INFO : wheel : adding 'botocore/data/wellarchitected/2020-03-31/paginators-1.json' INFO : wheel : adding 'botocore/data/wellarchitected/2020-03-31/service-2.json' INFO : wheel : adding 'botocore/data/wisdom/2020-10-19/examples-1.json' INFO : wheel : adding 'botocore/data/wisdom/2020-10-19/paginators-1.json' INFO : wheel : adding 'botocore/data/wisdom/2020-10-19/service-2.json' INFO : wheel : adding 'botocore/data/workdocs/2016-05-01/examples-1.json' INFO : wheel : adding 'botocore/data/workdocs/2016-05-01/paginators-1.json' INFO : wheel : adding 'botocore/data/workdocs/2016-05-01/service-2.json' INFO : wheel : adding 'botocore/data/worklink/2018-09-25/examples-1.json' INFO : wheel : adding 'botocore/data/worklink/2018-09-25/paginators-1.json' INFO : wheel : adding 'botocore/data/worklink/2018-09-25/service-2.json' INFO : wheel : adding 'botocore/data/workmail/2017-10-01/examples-1.json' INFO : wheel : adding 'botocore/data/workmail/2017-10-01/paginators-1.json' INFO : wheel : adding 'botocore/data/workmail/2017-10-01/service-2.json' INFO : wheel : adding 'botocore/data/workmailmessageflow/2019-05-01/examples-1.json' INFO : wheel : adding 'botocore/data/workmailmessageflow/2019-05-01/paginators-1.json' INFO : wheel : adding 'botocore/data/workmailmessageflow/2019-05-01/service-2.json' INFO : wheel : adding 'botocore/data/workspaces/2015-04-08/examples-1.json' INFO : wheel : adding 'botocore/data/workspaces/2015-04-08/paginators-1.json' INFO : wheel : adding 'botocore/data/workspaces/2015-04-08/service-2.json' INFO : wheel : adding 'botocore/data/workspaces-web/2020-07-08/examples-1.json' INFO : wheel : adding 'botocore/data/workspaces-web/2020-07-08/paginators-1.json' INFO : wheel : adding 'botocore/data/workspaces-web/2020-07-08/service-2.json' INFO : wheel : adding 'botocore/data/xray/2016-04-12/examples-1.json' INFO : wheel : adding 'botocore/data/xray/2016-04-12/paginators-1.json' INFO : wheel : adding 'botocore/data/xray/2016-04-12/service-2.json' INFO : wheel : adding 'botocore/docs/__init__.py' INFO : wheel : adding 'botocore/docs/client.py' INFO : wheel : adding 'botocore/docs/docstring.py' INFO : wheel : adding 'botocore/docs/example.py' INFO : wheel : adding 'botocore/docs/method.py' INFO : wheel : adding 'botocore/docs/paginator.py' INFO : wheel : adding 'botocore/docs/params.py' INFO : wheel : adding 'botocore/docs/service.py' INFO : wheel : adding 'botocore/docs/shape.py' INFO : wheel : adding 'botocore/docs/sharedexample.py' INFO : wheel : adding 'botocore/docs/utils.py' INFO : wheel : adding 'botocore/docs/waiter.py' INFO : wheel : adding 'botocore/docs/bcdoc/__init__.py' INFO : wheel : adding 'botocore/docs/bcdoc/docstringparser.py' INFO : wheel : adding 'botocore/docs/bcdoc/restdoc.py' INFO : wheel : adding 'botocore/docs/bcdoc/style.py' INFO : wheel : adding 'botocore/retries/__init__.py' INFO : wheel : adding 'botocore/retries/adaptive.py' INFO : wheel : adding 'botocore/retries/base.py' INFO : wheel : adding 'botocore/retries/bucket.py' INFO : wheel : adding 'botocore/retries/quota.py' INFO : wheel : adding 'botocore/retries/special.py' INFO : wheel : adding 'botocore/retries/standard.py' INFO : wheel : adding 'botocore/retries/throttling.py' INFO : wheel : adding 'botocore/vendored/__init__.py' INFO : wheel : adding 'botocore-1.27.90.dist-info/LICENSE.txt' INFO : wheel : adding 'botocore-1.27.90.dist-info/METADATA' INFO : wheel : adding 'botocore-1.27.90.dist-info/NOTICE' INFO : wheel : adding 'botocore-1.27.90.dist-info/WHEEL' INFO : wheel : adding 'botocore-1.27.90.dist-info/top_level.txt' INFO : wheel : adding 'botocore-1.27.90.dist-info/RECORD' INFO : wheel : removing build/bdist.linux-i686/wheel INFO : pyproject_installer.build_cmd._build : Built wheel: botocore-1.27.90-py3-none-any.whl + exit 0 Executing(%install): /bin/sh -e /usr/src/tmp/rpm-tmp.2693 + umask 022 + /bin/mkdir -p /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + /bin/chmod -Rf u+rwX -- /usr/src/tmp/python3-module-botocore-buildroot + : + /bin/rm -rf -- /usr/src/tmp/python3-module-botocore-buildroot + PATH=/usr/libexec/rpm-build:/usr/src/bin:/bin:/usr/bin:/usr/X11R6/bin:/usr/games + cd python3-module-botocore-1.27.90 + /usr/bin/python3 -m pyproject_installer -v install --destdir=/usr/src/tmp/python3-module-botocore-buildroot INFO : pyproject_installer.install_cmd._install : Installing wheel INFO : pyproject_installer.install_cmd._install : Wheel directory: /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/dist INFO : pyproject_installer.install_cmd._install : Wheel filename: botocore-1.27.90-py3-none-any.whl INFO : pyproject_installer.install_cmd._install : Destination: /usr/src/tmp/python3-module-botocore-buildroot DEBUG : pyproject_installer.lib.wheel : Parsing wheel filename DEBUG : pyproject_installer.lib.wheel : Validating wheel file DEBUG : pyproject_installer.lib.wheel : Validating wheel spec version DEBUG : pyproject_installer.lib.wheel : Parsing wheel spec metadata DEBUG : pyproject_installer.lib.wheel : Validating RECORD INFO : pyproject_installer.install_cmd._install : Wheel installation root: /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages INFO : pyproject_installer.install_cmd._install : Extracting wheel DEBUG : pyproject_installer.install_cmd._install : Filtering out not allowed file: botocore-1.27.90.dist-info/LICENSE.txt DEBUG : pyproject_installer.install_cmd._install : Filtering out not allowed file: botocore-1.27.90.dist-info/NOTICE DEBUG : pyproject_installer.install_cmd._install : Filtering out not allowed file: botocore-1.27.90.dist-info/WHEEL DEBUG : pyproject_installer.install_cmd._install : Filtering out not allowed file: botocore-1.27.90.dist-info/top_level.txt DEBUG : pyproject_installer.install_cmd._install : Filtering out not allowed file: botocore-1.27.90.dist-info/RECORD INFO : pyproject_installer.install_cmd._install : Wheel was installed + /usr/lib/rpm/brp-alt Cleaning files in /usr/src/tmp/python3-module-botocore-buildroot (auto) Verifying and fixing files in /usr/src/tmp/python3-module-botocore-buildroot (binconfig,pkgconfig,libtool,desktop,gnuconfig) Checking contents of files in /usr/src/tmp/python3-module-botocore-buildroot/ (default) Compressing files in /usr/src/tmp/python3-module-botocore-buildroot (auto) Adjusting library links in /usr/src/tmp/python3-module-botocore-buildroot ./usr/lib: (from :0) Verifying ELF objects in /usr/src/tmp/python3-module-botocore-buildroot (arch=normal,fhs=normal,lfs=relaxed,lint=relaxed,rpath=normal,stack=normal,textrel=normal,unresolved=normal) Bytecompiling python3 modules in /usr/src/tmp/python3-module-botocore-buildroot using /usr/bin/python3 compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/crt/__init__.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/crt/auth.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/bcdoc/__init__.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/bcdoc/docstringparser.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/bcdoc/restdoc.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/bcdoc/style.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/__init__.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/client.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/docstring.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/example.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/method.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/paginator.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/params.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/service.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/shape.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/sharedexample.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/utils.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/waiter.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retries/__init__.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retries/adaptive.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retries/base.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retries/bucket.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retries/quota.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retries/special.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retries/standard.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retries/throttling.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/vendored/__init__.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/__init__.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/args.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/auth.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/awsrequest.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/client.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/compat.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/config.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/configloader.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/configprovider.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/credentials.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/discovery.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/endpoint.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/endpoint_provider.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/errorfactory.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/eventstream.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/exceptions.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/handlers.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/history.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/hooks.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/httpchecksum.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/httpsession.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/loaders.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/model.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/monitoring.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/paginate.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/parsers.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/regions.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/response.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retryhandler.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/serialize.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/session.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/signers.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/stub.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/tokens.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/translate.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/utils.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/validate.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/waiter.py Bytecompiling python3 modules with optimization in /usr/src/tmp/python3-module-botocore-buildroot using /usr/bin/python3 -O compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/crt/__init__.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/crt/auth.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/bcdoc/__init__.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/bcdoc/docstringparser.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/bcdoc/restdoc.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/bcdoc/style.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/__init__.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/client.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/docstring.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/example.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/method.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/paginator.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/params.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/service.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/shape.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/sharedexample.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/utils.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/waiter.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retries/__init__.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retries/adaptive.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retries/base.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retries/bucket.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retries/quota.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retries/special.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retries/standard.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retries/throttling.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/vendored/__init__.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/__init__.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/args.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/auth.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/awsrequest.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/client.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/compat.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/config.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/configloader.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/configprovider.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/credentials.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/discovery.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/endpoint.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/endpoint_provider.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/errorfactory.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/eventstream.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/exceptions.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/handlers.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/history.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/hooks.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/httpchecksum.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/httpsession.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/loaders.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/model.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/monitoring.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/paginate.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/parsers.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/regions.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/response.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retryhandler.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/serialize.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/session.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/signers.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/stub.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/tokens.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/translate.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/utils.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/validate.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/waiter.py Bytecompiling python3 modules with optimization-2 in /usr/src/tmp/python3-module-botocore-buildroot using /usr/bin/python3 -OO compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/crt/__init__.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/crt/auth.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/bcdoc/__init__.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/bcdoc/docstringparser.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/bcdoc/restdoc.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/bcdoc/style.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/__init__.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/client.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/docstring.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/example.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/method.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/paginator.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/params.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/service.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/shape.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/sharedexample.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/utils.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/waiter.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retries/__init__.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retries/adaptive.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retries/base.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retries/bucket.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retries/quota.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retries/special.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retries/standard.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retries/throttling.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/vendored/__init__.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/__init__.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/args.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/auth.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/awsrequest.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/client.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/compat.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/config.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/configloader.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/configprovider.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/credentials.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/discovery.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/endpoint.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/endpoint_provider.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/errorfactory.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/eventstream.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/exceptions.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/handlers.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/history.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/hooks.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/httpchecksum.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/httpsession.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/loaders.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/model.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/monitoring.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/paginate.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/parsers.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/regions.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/response.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retryhandler.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/serialize.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/session.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/signers.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/stub.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/tokens.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/translate.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/utils.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/validate.py compile /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/waiter.py Hardlinking identical .pyc and .opt-?.pyc files './usr/lib/python3/site-packages/botocore/__pycache__/__init__.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/__init__.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/args.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/args.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/auth.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/auth.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/awsrequest.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/awsrequest.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/client.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/client.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/compat.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/compat.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/config.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/config.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/configloader.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/configloader.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/configprovider.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/configprovider.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/credentials.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/credentials.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/discovery.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/discovery.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/endpoint.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/endpoint.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/endpoint_provider.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/endpoint_provider.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/errorfactory.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/errorfactory.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/eventstream.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/eventstream.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/exceptions.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/exceptions.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/handlers.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/handlers.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/history.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/history.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/history.cpython-310.opt-2.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/history.cpython-310.opt-1.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/hooks.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/hooks.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/httpchecksum.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/httpchecksum.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/httpsession.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/httpsession.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/loaders.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/loaders.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/model.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/model.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/monitoring.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/monitoring.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/paginate.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/paginate.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/parsers.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/parsers.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/regions.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/regions.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/response.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/response.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/retryhandler.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/retryhandler.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/serialize.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/serialize.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/session.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/session.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/signers.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/signers.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/stub.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/stub.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/tokens.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/tokens.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/tokens.cpython-310.opt-2.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/tokens.cpython-310.opt-1.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/translate.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/translate.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/validate.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/validate.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/__pycache__/waiter.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/__pycache__/waiter.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/crt/__pycache__/__init__.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/crt/__pycache__/__init__.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/crt/__pycache__/__init__.cpython-310.opt-2.pyc' => './usr/lib/python3/site-packages/botocore/crt/__pycache__/__init__.cpython-310.opt-1.pyc' './usr/lib/python3/site-packages/botocore/crt/__pycache__/auth.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/crt/__pycache__/auth.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/docs/__pycache__/__init__.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/docs/__pycache__/__init__.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/docs/__pycache__/client.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/docs/__pycache__/client.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/docs/__pycache__/docstring.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/docs/__pycache__/docstring.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/docs/__pycache__/example.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/docs/__pycache__/example.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/docs/__pycache__/paginator.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/docs/__pycache__/paginator.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/docs/__pycache__/params.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/docs/__pycache__/params.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/docs/__pycache__/service.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/docs/__pycache__/service.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/docs/__pycache__/shape.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/docs/__pycache__/shape.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/docs/__pycache__/sharedexample.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/docs/__pycache__/sharedexample.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/docs/__pycache__/utils.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/docs/__pycache__/utils.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/docs/__pycache__/waiter.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/docs/__pycache__/waiter.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/docs/bcdoc/__pycache__/__init__.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/docs/bcdoc/__pycache__/__init__.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/docs/bcdoc/__pycache__/__init__.cpython-310.opt-2.pyc' => './usr/lib/python3/site-packages/botocore/docs/bcdoc/__pycache__/__init__.cpython-310.opt-1.pyc' './usr/lib/python3/site-packages/botocore/docs/bcdoc/__pycache__/docstringparser.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/docs/bcdoc/__pycache__/docstringparser.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/docs/bcdoc/__pycache__/restdoc.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/docs/bcdoc/__pycache__/restdoc.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/docs/bcdoc/__pycache__/style.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/docs/bcdoc/__pycache__/style.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/retries/__pycache__/__init__.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/retries/__pycache__/__init__.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/retries/__pycache__/adaptive.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/retries/__pycache__/adaptive.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/retries/__pycache__/base.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/retries/__pycache__/base.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/retries/__pycache__/bucket.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/retries/__pycache__/bucket.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/retries/__pycache__/quota.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/retries/__pycache__/quota.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/retries/__pycache__/special.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/retries/__pycache__/special.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/retries/__pycache__/standard.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/retries/__pycache__/standard.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/retries/__pycache__/throttling.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/retries/__pycache__/throttling.cpython-310.pyc' './usr/lib/python3/site-packages/botocore/vendored/__pycache__/__init__.cpython-310.opt-1.pyc' => './usr/lib/python3/site-packages/botocore/vendored/__pycache__/__init__.cpython-310.pyc' Executing(%check): /bin/sh -e /usr/src/tmp/rpm-tmp.77994 + umask 022 + /bin/mkdir -p /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + cd python3-module-botocore-1.27.90 ++ cat ./dist/.wheeltracker + _tox_wheel=botocore-1.27.90-py3-none-any.whl + export NO_INTERNET=YES + NO_INTERNET=YES + export PIP_NO_BUILD_ISOLATION=NO + PIP_NO_BUILD_ISOLATION=NO + export PIP_NO_INDEX=YES + PIP_NO_INDEX=YES + export TOXENV=py3 + TOXENV=py3 + export TOX_TESTENV_PASSENV=NO_INTERNET + TOX_TESTENV_PASSENV=NO_INTERNET + /usr/bin/tox.py3 --sitepackages -vvr -s false --no-deps --console-scripts --installpkg=./dist/botocore-1.27.90-py3-none-any.whl using tox.ini: /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/tox.ini (pid 2571336) using tox-3.27.1 from /usr/lib/python3/site-packages/tox/__init__.py (pid 2571336) using package '/usr/src/RPM/BUILD/python3-module-botocore-1.27.90/dist/botocore-1.27.90-py3-none-any.whl', skipping 'sdist' activity package .tox/.tmp/package/1/botocore-1.27.90-py3-none-any.whl links to dist/botocore-1.27.90-py3-none-any.whl (/usr/src/RPM/BUILD/python3-module-botocore-1.27.90) py3 uses /usr/bin/python3 py3 start: getenv /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3 py3 cannot reuse: -r flag py3 create: /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3 setting PATH=/usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin:/usr/src/bin:/bin:/usr/bin:/usr/X11R6/bin:/usr/games [2571525] /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox$ /usr/bin/python3 -m virtualenv --system-site-packages --no-download --python /usr/bin/python3 py3 created virtual environment CPython3.10.8.final.0-32 in 315ms creator CPython3Posix(dest=/usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3, clear=False, no_vcs_ignore=False, global=True) seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/usr/src/.local/share/virtualenv) added seed packages: pip==23.1.1, setuptools==67.7.2, wheel==0.40.0 activators BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator setting PATH=/usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin:/usr/src/bin:/bin:/usr/bin:/usr/X11R6/bin:/usr/games [2572033] /usr/src/RPM/BUILD/python3-module-botocore-1.27.90$ /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin/python /usr/lib/python3/site-packages/tox_console_scripts/helper/console_scripts.py Generating script tox into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script tox-quickstart into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script virtualenv into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script wheel into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script jsonschema into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script hypothesis into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script fonttools into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script pyftmerge into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script pyftsubset into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script ttx into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script black into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script blackd into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script django-admin into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script gunicorn into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script pt2to3 into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script ptdump into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script ptrepack into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script pttree into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script f2py into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script f2py3 into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script f2py3.10 into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script paster into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script cftp into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script ckeygen into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script conch into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script mailmail into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script pyhtmlizer into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script tkconch into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script trial into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script twist into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script twistd into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script automat-visualize into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script py.test into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script pytest into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script cpuinfo into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script sqlformat into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script dmypy into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script mypy into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script mypyc into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script stubgen into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script stubtest into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script cygdb into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script cython into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script cythonize into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script coverage into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script coverage-3.10 into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script coverage3 into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script pyserial-miniterm into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script pyserial-ports into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin Generating script normalizer into /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin py3 finish: getenv /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3 after 0.75 seconds py3 start: installpkg /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/.tmp/package/1/botocore-1.27.90-py3-none-any.whl py3 inst: /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/.tmp/package/1/botocore-1.27.90-py3-none-any.whl write config to /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/.tox-config1 as 'ea3f56100ae72877c67380e62865ec3d2e6e874d044824cf71661fc5bbc139b1 /usr/bin/python3\n3.27.1 1 0 0' setting PATH=/usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin:/usr/src/bin:/bin:/usr/bin:/usr/X11R6/bin:/usr/games [2572131] /usr/src/RPM/BUILD/python3-module-botocore-1.27.90$ /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin/python -m pip install --exists-action w .tox/.tmp/package/1/botocore-1.27.90-py3-none-any.whl Processing ./.tox/.tmp/package/1/botocore-1.27.90-py3-none-any.whl Requirement already satisfied: jmespath<2.0.0,>=0.7.1 in /usr/lib/python3/site-packages (from botocore==1.27.90) (1.0.1) Requirement already satisfied: python-dateutil<3.0.0,>=2.1 in /usr/lib/python3/site-packages (from botocore==1.27.90) (2.8.2) Requirement already satisfied: urllib3<1.27,>=1.25.4 in /usr/lib/python3/site-packages (from botocore==1.27.90) (1.26.14) Requirement already satisfied: six>=1.5 in /usr/lib/python3/site-packages (from python-dateutil<3.0.0,>=2.1->botocore==1.27.90) (1.16.0) Installing collected packages: botocore Successfully installed botocore-1.27.90 py3 finish: installpkg /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/.tmp/package/1/botocore-1.27.90-py3-none-any.whl after 2.57 seconds py3 start: envreport setting PATH=/usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin:/usr/src/bin:/bin:/usr/bin:/usr/X11R6/bin:/usr/games [2573675] /usr/src/RPM/BUILD/python3-module-botocore-1.27.90$ /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin/python -m pip freeze >.tox/py3/log/py3-0.log py3 finish: envreport after 0.60 seconds py3 installed: aiohttp==3.8.3,aiosignal==1.3.1,apipkg==1.5,appdirs==1.4.4,asgiref==3.4.1,astor==0.8.1,async-generator==1.10,async-timeout==4.0.2,attrs==22.2.0,Automat==20.2.0,beautifulsoup4==4.11.2,black==23.3.0,botocore @ file:///usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/.tmp/package/1/botocore-1.27.90-py3-none-any.whl#sha256=d6fdefa432b2eac30d3e19fc0439aed422e5eca0b48d87ddcfa43d696d11ca62,certifi==2021.5.30,cffi==1.15.1,charset-normalizer==2.1.1,click==8.1.3,constantly==15.1.0,coverage==6.5.0,cryptography==40.0.2,CT3==3.3.1,cycler==0.11.0,Cython==0.29.34,distlib==0.3.6,Django==3.2.18,dnspython==2.2.0,et-xmlfile==1.1.0,eventlet==0.33.3,exceptiongroup==1.1.1,filelock==3.12.0,fonttools==4.39.3,freetype-py==2.1.0.post1,frozenlist==1.3.3,fs==2.4.16,Genshi==0.7.7,geoip2==4.6.0,gevent==22.10.1,greenlet==1.1.2,gunicorn==20.1.0,hidapi==0.13.1,html5lib==1.1,hyperlink==21.0.0,hypothesis==6.68.1,idna==3.4,idna-ssl==1.1.0,incremental==22.10.0,iniconfig==2.0.0,jdcal==1.4.1,Jinja2==3.1.2,jmespath==1.0.1,jsonschema==4.17.3,kiwisolver @ file:///usr/src/RPM/BUILD/kiwi-1.4.4/dist/kiwisolver-1.4.4-cp310-cp310-linux_i686.whl,lark-parser==0.11.3,libcst==0.4.7,lxml==4.9.2,MarkupSafe==2.1.2,matplotlib==3.7.0,maxminddb==2.1.0,mpmath==1.2.1,multidict==6.0.4,mypy==1.2.0,mypy-extensions==1.0.0,numexpr==2.8.3,numpy==1.22.1,olefile==0.46,openpyxl==3.0.10,outcome==1.2.0,packaging==23.0,pandas==1.3.1,Paste==3.5.0,PasteDeploy==3.0.1,PasteScript==2.0.2,pathspec==0.11.1,Pillow==9.4.0,platformdirs==3.2.0,pluggy==1.0.0,psycopg2==2.9.5,py==1.11.0,py-cpuinfo==8.0.0,pycairo==1.23.0,pycares==4.1.2,pycparser==2.21,PyGObject==3.44.1,pyOpenSSL==23.1.1,pyparsing==3.0.9,pyproject-installer==0.5.0,pyrsistent==0.19.3,pyserial==3.5,pytest==7.3.1,python-dateutil==2.8.2,python3-openid==3.2.0,pytz==2022.6,PyYAML==6.0,railroad-diagrams==1.1.1,redis==3.4.1,reportlab==3.6.12,requests==2.28.2,SciPy==1.10.1,six==1.16.0,sniffio==1.2.0,sortedcontainers==2.4.0,soupsieve==2.3.1,SQLAlchemy==2.0.4,sqlparse==0.4.4,tables==3.8.0,tomli==2.0.1,tornado==6.3.1,tox==3.27.1,tox-console-scripts==0.3.2,tox-no-deps==0.2.0,trio==0.22.0,Twisted==20.3.0,typing-inspect==0.8.0,typing_extensions==4.5.0,urllib3==1.26.14,virtualenv==20.20.0,webencodings==0.5.1,xlrd==2.0.1,XlsxWriter==3.1.0,xlwt==1.3.0,yarl==1.8.1,zope.event==4.4,zope.interface==5.4.0 py3 start: run-test-pre py3 run-test-pre: PYTHONHASHSEED='2122314687' py3 finish: run-test-pre after 0.00 seconds py3 start: run-test py3 run-test: commands[0] | /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/scripts/ci/run-tests setting PATH=/usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/py3/bin:/usr/src/bin:/bin:/usr/bin:/usr/X11R6/bin:/usr/games [2574254] /usr/src/RPM/BUILD/python3-module-botocore-1.27.90$ /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/scripts/ci/run-tests ============================= test session starts ============================== platform linux -- Python 3.10.8, pytest-7.3.1, pluggy-1.0.0 cachedir: .tox/py3/.pytest_cache rootdir: /usr/src/RPM/BUILD/python3-module-botocore-1.27.90 configfile: pyproject.toml plugins: hypothesis-6.68.1 collected 30168 items unit/test_args.py ...................................................... [ 0%] ....... [ 0%] unit/test_auth_bearer.py .... [ 0%] unit/test_auth_sigv4.py .... [ 0%] unit/test_awsrequest.py ................................................ [ 0%] .......... [ 0%] unit/test_client.py .................................................... [ 0%] ........................................................................ [ 0%] ........................................................................ [ 1%] ......................................................... [ 1%] unit/test_compat.py .................................................... [ 1%] .................. [ 1%] unit/test_config_provider.py ........................................... [ 1%] ........................ [ 1%] unit/test_configloader.py ................ [ 1%] unit/test_credentials.py ............................................... [ 1%] ........................................................................ [ 2%] ................................................. [ 2%] unit/test_discovery.py ................................. [ 2%] unit/test_endpoint.py ............................ [ 2%] unit/test_endpoint_provider.py ......................................... [ 2%] ................................................................. [ 2%] unit/test_errorfactory.py ......... [ 2%] unit/test_eventstream.py .................................... [ 3%] unit/test_exceptions.py ........... [ 3%] unit/test_handlers.py .................................................. [ 3%] ........................................................................ [ 3%] ....... [ 3%] unit/test_history.py ........ [ 3%] unit/test_hooks.py ........................................... [ 3%] unit/test_http_client_exception_mapping.py ..... [ 3%] unit/test_http_session.py .............................................. [ 3%] .... [ 3%] unit/test_httpchecksum.py ..............................ss..ss...... [ 3%] unit/test_idempotency.py .. [ 3%] unit/test_loaders.py ................................ [ 4%] unit/test_model.py ..................................................... [ 4%] ................................ [ 4%] unit/test_monitoring.py ................................................ [ 4%] . [ 4%] unit/test_paginate.py .................................................. [ 4%] ........................ [ 4%] unit/test_parsers.py ................................................... [ 4%] .......................... [ 5%] unit/test_protocols.py ................................................. [ 5%] ........................................................................ [ 5%] ........................................................................ [ 5%] .................................................................... [ 5%] unit/test_regions.py ................................................... [ 6%] .................................................... [ 6%] unit/test_response.py ........................... [ 6%] unit/test_retryhandler.py ........................ [ 6%] unit/test_s3_addressing.py ................ [ 6%] unit/test_serialize.py ........................ [ 6%] unit/test_session.py ...................................ss.............. [ 6%] ........................................ [ 6%] unit/test_session_legacy.py ............................................ [ 6%] ....................... [ 7%] unit/test_signers.py ................................................... [ 7%] .......... [ 7%] unit/test_stub.py ............... [ 7%] unit/test_tokens.py .............. [ 7%] unit/test_translate.py .... [ 7%] unit/test_utils.py ..................................................... [ 7%] ........................................................................ [ 7%] ........................................................................ [ 8%] ........................................................................ [ 8%] .......... [ 8%] unit/test_validate.py ................................ [ 8%] unit/test_waiters.py ........................................ [ 8%] unit/auth/test_signers.py .............................................. [ 8%] .................... [ 8%] unit/auth/test_sigv4.py .............................. [ 8%] unit/crt/auth/test_crt_signers.py ..............................ssssssss [ 8%] ssssssssssssssssssssss [ 9%] unit/crt/auth/test_crt_sigv4.py ssssssssssssssssssssssssssssss [ 9%] unit/docs/test_client.py ... [ 9%] unit/docs/test_docs.py . [ 9%] unit/docs/test_docstring.py ......... [ 9%] unit/docs/test_example.py ...................... [ 9%] unit/docs/test_method.py ................ [ 9%] unit/docs/test_paginator.py .. [ 9%] unit/docs/test_params.py .................. [ 9%] unit/docs/test_service.py ... [ 9%] unit/docs/test_sharedexample.py ........... [ 9%] unit/docs/test_utils.py .................................. [ 9%] unit/docs/test_waiter.py . [ 9%] unit/docs/bcdoc/test_docstringparser.py .................. [ 9%] unit/docs/bcdoc/test_document.py ................ [ 9%] unit/docs/bcdoc/test_style.py .......................................... [ 9%] . [ 9%] unit/response_parsing/test_response_parsing.py ......................... [ 9%] ........................................................................ [ 10%] ........................................................................ [ 10%] ...................................................................... [ 10%] unit/retries/test_adaptive.py ........... [ 10%] unit/retries/test_bucket.py ....... [ 10%] unit/retries/test_quota.py ..... [ 10%] unit/retries/test_special.py ....... [ 10%] unit/retries/test_standard.py .......................................... [ 10%] ............................................................. [ 11%] unit/retries/test_throttling.py .... [ 11%] functional/test_alias.py ...... [ 11%] functional/test_apigateway.py . [ 11%] functional/test_client.py .. [ 11%] functional/test_client_class_names.py .................................. [ 11%] .............. [ 11%] functional/test_client_metadata.py ...... [ 11%] functional/test_cloudformation.py . [ 11%] functional/test_cloudsearchdomain.py . [ 11%] functional/test_cognito_idp.py ............. [ 11%] functional/test_config_provider.py ...... [ 11%] functional/test_credentials.py .......................... [ 11%] functional/test_discovery.py ........................ [ 11%] functional/test_docdb.py .. [ 11%] functional/test_dynamodb.py ... [ 11%] functional/test_ec2.py ... [ 11%] functional/test_endpoints.py ........................................... [ 11%] ........................................................................ [ 11%] ........................................................................ [ 12%] ........................................................................ [ 12%] ........................................................................ [ 12%] ........................................................................ [ 12%] ........................................................................ [ 13%] ........................................................................ [ 13%] ........................................................................ [ 13%] ................... [ 13%] functional/test_event_alias.py ......................................... [ 13%] ........................................................................ [ 14%] ........................................................................ [ 14%] ........................................................................ [ 14%] ........................................................................ [ 14%] ........................................................................ [ 14%] ......................... [ 15%] functional/test_eventbridge.py ss...ssss....sssss [ 15%] functional/test_events.py .. [ 15%] functional/test_h2_required.py s.. [ 15%] functional/test_history.py .... [ 15%] functional/test_iot_data.py .. [ 15%] functional/test_kinesis.py ... [ 15%] functional/test_lex.py .. [ 15%] functional/test_loaders.py . [ 15%] functional/test_machinelearning.py . [ 15%] functional/test_model_backcompat.py . [ 15%] functional/test_model_completeness.py .................... [ 15%] functional/test_modeled_exceptions.py .... [ 15%] functional/test_mturk.py . [ 15%] functional/test_neptune.py .. [ 15%] functional/test_paginate.py ......... [ 15%] functional/test_paginator_config.py .................................... [ 15%] ........................................................................ [ 15%] ........................................................................ [ 15%] ........................................................................ [ 16%] ........................................................................ [ 16%] ........................................................................ [ 16%] ........................................................................ [ 16%] ........................................................................ [ 17%] ........................................................................ [ 17%] ........................................................................ [ 17%] ........................................................................ [ 17%] ........................................................................ [ 18%] ........................................................................ [ 18%] ........................................................................ [ 18%] ........................................................................ [ 18%] ........................................................................ [ 19%] ........................................................................ [ 19%] ........................................................................ [ 19%] ........................................................................ [ 19%] ........................................................................ [ 19%] ........................................................................ [ 20%] ........................................................................ [ 20%] ........................................................................ [ 20%] ........................................................................ [ 20%] ........................................................................ [ 21%] .................................................................... [ 21%] functional/test_public_apis.py ...... [ 21%] functional/test_rds.py .... [ 21%] functional/test_regions.py ............................................. [ 21%] ........................................................................ [ 21%] ........................................................................ [ 22%] ........................................................................ [ 22%] ........................................................................ [ 22%] ............................................... [ 22%] functional/test_response_shadowing.py .................................. [ 22%] ........................................................................ [ 23%] ........................................................................ [ 23%] ........................................................................ [ 23%] ........................................................................ [ 23%] ........................................................................ [ 23%] ........................................................................ [ 24%] ........................................................................ [ 24%] ........................................................................ [ 24%] ........................................................................ [ 24%] ........................................................................ [ 25%] ........................................................................ [ 25%] ........................................................................ [ 25%] ........................................................................ [ 25%] ........................................................................ [ 26%] ........................................................................ [ 26%] ........................................................................ [ 26%] ........................................................................ [ 26%] ........................................................................ [ 27%] ........................................................................ [ 27%] ........................................................................ [ 27%] ........................................................................ [ 27%] ........................................................................ [ 28%] ........................................................................ [ 28%] ........................................................................ [ 28%] ........................................................................ [ 28%] ........................................................................ [ 28%] ........................................................................ [ 29%] ........................................................................ [ 29%] ........................................................................ [ 29%] ........................................................................ [ 29%] ........................................................................ [ 30%] ........................................................................ [ 30%] ........................................................................ [ 30%] ........................................................................ [ 30%] ........................................................................ [ 31%] ........................................................................ [ 31%] ........................................................................ [ 31%] ........................................................................ [ 31%] ........................................................................ [ 32%] ........................................................................ [ 32%] ........................................................................ [ 32%] ........................................................................ [ 32%] ........................................................................ [ 33%] ........................................................................ [ 33%] ........................................................................ [ 33%] ........................................................................ [ 33%] ........................................................................ [ 33%] ........................................................................ [ 34%] ........................................................................ [ 34%] ........................................................................ [ 34%] ........................................................................ [ 34%] ........................................................................ [ 35%] ........................................................................ [ 35%] ........................................................................ [ 35%] ........................................................................ [ 35%] ........................................................................ [ 36%] ........................................................................ [ 36%] ........................................................................ [ 36%] ........................................................................ [ 36%] ........................................................................ [ 37%] ........................................................................ [ 37%] ........................................................................ [ 37%] ........................................................................ [ 37%] ........................................................................ [ 38%] ........................................................................ [ 38%] ........................................................................ [ 38%] ........................................................................ [ 38%] ........................................................................ [ 39%] ........................................................................ [ 39%] ........................................................................ [ 39%] ........................................................................ [ 39%] ........................................................................ [ 39%] ........................................................................ [ 40%] ........................................................................ [ 40%] ........................................................................ [ 40%] ........................................................................ [ 40%] ........................................................................ [ 41%] ........................................................................ [ 41%] ........................................................................ [ 41%] ........................................................................ [ 41%] ........................................................................ [ 42%] ........................................................................ [ 42%] ........................................................................ [ 42%] ........................................................................ [ 42%] ........................................................................ [ 43%] ........................................................................ [ 43%] ........................................................................ [ 43%] ........................................................................ [ 43%] ........................................................................ [ 44%] ........................................................................ [ 44%] ........................................................................ [ 44%] ........................................................................ [ 44%] ........................................................................ [ 44%] ........................................................................ [ 45%] ........................................................................ [ 45%] ........................................................................ [ 45%] ........................................................................ [ 45%] ........................................................................ [ 46%] ........................................................................ [ 46%] ........................................................................ [ 46%] ........................................................................ [ 46%] ........................................................................ [ 47%] ........................................................................ [ 47%] ........................................................................ [ 47%] ........................................................................ [ 47%] ........................................................................ [ 48%] ........................................................................ [ 48%] ........................................................................ [ 48%] ........................................................................ [ 48%] ........................................................................ [ 49%] ........................................................................ [ 49%] ........................................................................ [ 49%] ........................................................................ [ 49%] ........................................................................ [ 49%] ........................................................................ [ 50%] ........................................................................ [ 50%] ........................................................................ [ 50%] ........................................................................ [ 50%] ........................................................................ [ 51%] ........................................................................ [ 51%] ........................................................................ [ 51%] ........................................................................ [ 51%] ........................................................................ [ 52%] ........................................................................ [ 52%] ........................................................................ [ 52%] ........................................................................ [ 52%] ........................................................................ [ 53%] ........................................................................ [ 53%] ........................................................................ [ 53%] ........................................................................ [ 53%] ........................................................................ [ 54%] ........................................................................ [ 54%] ........................................................................ [ 54%] ........................................................................ [ 54%] ........................................................................ [ 54%] ........................................................................ [ 55%] ........................................................................ [ 55%] ........................................................................ [ 55%] ........................................................................ [ 55%] ........................................................................ [ 56%] ........................................................................ [ 56%] ........................................................................ [ 56%] ........................................................................ [ 56%] ........................................................................ [ 57%] ........................................................................ [ 57%] ........................................................................ [ 57%] ........................................................................ [ 57%] ........................................................................ [ 58%] ........................................................................ [ 58%] ........................................................................ [ 58%] ........................................................................ [ 58%] ........................................................................ [ 59%] ........................................................................ [ 59%] ........................................................................ [ 59%] ........................................................................ [ 59%] ........................................................................ [ 60%] ........................................................................ [ 60%] ........................................................................ [ 60%] ........................................................................ [ 60%] ........................................................................ [ 60%] ........................................................................ [ 61%] ........................................................................ [ 61%] ........................................................................ [ 61%] ........................................................................ [ 61%] ........................................................................ [ 62%] ........................................................................ [ 62%] ........................................................................ [ 62%] ........................................................................ [ 62%] ........................................................................ [ 63%] ........................................................................ [ 63%] ........................................................................ [ 63%] ........................................................................ [ 63%] ........................................................................ [ 64%] ........................................................................ [ 64%] ........................................................................ [ 64%] ........................................................................ [ 64%] ........................................................................ [ 65%] ........................................................................ [ 65%] ........................................................................ [ 65%] ........................................................................ [ 65%] ........................................................................ [ 65%] ........................................................................ [ 66%] ........................................................................ [ 66%] ........................................................................ [ 66%] ........................................................................ [ 66%] ........................................................................ [ 67%] ........................................................................ [ 67%] ........................................................................ [ 67%] ........................................................................ [ 67%] ........................................................................ [ 68%] ........................................................................ [ 68%] ........................................................................ [ 68%] ........................................................................ [ 68%] ........................................................................ [ 69%] ........................................................................ [ 69%] ........................................................................ [ 69%] ........................................................................ [ 69%] ........................................................................ [ 70%] ........................................................................ [ 70%] ........................................................................ [ 70%] ........................................................................ [ 70%] ........................................................................ [ 70%] ........................................................................ [ 71%] ........................................................................ [ 71%] ........................................................................ [ 71%] ........................................................................ [ 71%] ........................................................................ [ 72%] ........................................................................ [ 72%] ........................................................................ [ 72%] ........................................................................ [ 72%] ........................................................................ [ 73%] ........................................................................ [ 73%] ........................................................................ [ 73%] ........................................................................ [ 73%] ........................................................................ [ 74%] ........................................................................ [ 74%] ........................................................................ [ 74%] ........................................................................ [ 74%] ........................................................................ [ 75%] ........................................................................ [ 75%] ........................................................................ [ 75%] ........................................................................ [ 75%] ........................................................................ [ 76%] ........................................................................ [ 76%] ........................................................................ [ 76%] ........................................................................ [ 76%] ........................................................................ [ 76%] ........................................................................ [ 77%] ........................................................................ [ 77%] ........................................................................ [ 77%] ........................................................................ [ 77%] ........................................................................ [ 78%] ........................................................................ [ 78%] ........................................................................ [ 78%] ........................................................................ [ 78%] ........................................................................ [ 79%] ........................................................................ [ 79%] ........................................................................ [ 79%] ........................................................................ [ 79%] ........................................................................ [ 80%] ........................................................................ [ 80%] ........................................................................ [ 80%] ........................................................................ [ 80%] ........................................................................ [ 81%] ........................................................................ [ 81%] ........................................................................ [ 81%] ........................................................................ [ 81%] ........................................................................ [ 81%] ........................................................................ [ 82%] ........................................................................ [ 82%] ........................................................................ [ 82%] ........................................................................ [ 82%] ........................................................................ [ 83%] ........................................................................ [ 83%] ........................................................................ [ 83%] ........................................................................ [ 83%] ........................................................................ [ 84%] ........................................................................ [ 84%] ........................................................................ [ 84%] ........................................................................ [ 84%] ........................................................................ [ 85%] ........................................................................ [ 85%] ........................................................................ [ 85%] ........................................................................ [ 85%] ........................................................................ [ 86%] ........................................................................ [ 86%] ........................................................................ [ 86%] ........................................................................ [ 86%] ........................................................................ [ 86%] ........................................................................ [ 87%] ........................................................................ [ 87%] ........................................................................ [ 87%] ........................................................................ [ 87%] ........................................................................ [ 88%] ........................................................................ [ 88%] ........................................................................ [ 88%] ........................................................................ [ 88%] ........................................................................ [ 89%] ........................................................................ [ 89%] ........................................................................ [ 89%] ........................................................................ [ 89%] ........................................................................ [ 90%] ........................................................................ [ 90%] ........................................................................ [ 90%] ........................................................................ [ 90%] ........................................................................ [ 91%] ........................................................................ [ 91%] ...................................... [ 91%] functional/test_retry.py ................. [ 91%] functional/test_route53.py .... [ 91%] functional/test_s3.py .................................................s [ 91%] .......sssssssssss...................................................... [ 91%] ........................................................................ [ 92%] ........................................................................ [ 92%] ....... [ 92%] functional/test_s3_control.py ... [ 92%] functional/test_s3_control_redirects.py ................................ [ 92%] .... [ 92%] functional/test_sagemaker.py .. [ 92%] functional/test_service_alias.py . [ 92%] functional/test_service_names.py ....................................... [ 92%] ........................................................................ [ 92%] ........................................................................ [ 93%] ........................................................................ [ 93%] ........................................................................ [ 93%] ........................................................................ [ 93%] ........................................................................ [ 94%] ........................................................................ [ 94%] ........................................................................ [ 94%] ..................... [ 94%] functional/test_session.py ....... [ 94%] functional/test_six_imports.py ......................................... [ 94%] ....................... [ 94%] functional/test_six_threading.py . [ 94%] functional/test_sts.py ....................... [ 94%] functional/test_stub.py ......................... [ 95%] functional/test_tagged_unions_unknown.py . [ 95%] functional/test_utils.py ... [ 95%] functional/test_waiter_config.py ....................................... [ 95%] ................... [ 95%] functional/csm/test_monitoring.py ..................... [ 95%] functional/docs/test_alias.py . [ 95%] functional/docs/test_autoscaling.py . [ 95%] functional/docs/test_ec2.py .... [ 95%] functional/docs/test_glacier.py .. [ 95%] functional/docs/test_lex.py . [ 95%] functional/docs/test_s3.py ...... [ 95%] functional/docs/test_secretsmanager.py . [ 95%] functional/docs/test_shared_example_config.py .......................... [ 95%] ........................................................................ [ 95%] ........................................................................ [ 95%] ........................................................................ [ 96%] ........................................................................ [ 96%] ........................................................................ [ 96%] ........................................................................ [ 96%] ........................................................................ [ 97%] ........................................................................ [ 97%] ........................................................................ [ 97%] ........................................................................ [ 97%] ........................................................................ [ 98%] ........................................................................ [ 98%] ........................................................................ [ 98%] ........................................................................ [ 98%] ........................................................................ [ 99%] ........................................................................ [ 99%] ........................................................................ [ 99%] ........................................................................ [ 99%] ...................................................................... [ 99%] functional/docs/test_sms_voice.py . [ 99%] functional/docs/test_streaming_body.py . [ 99%] functional/leak/test_resource_leaks.py ...... [ 99%] functional/retries/test_bucket.py .. [ 99%] functional/retries/test_quota.py . [100%] =============================== warnings summary =============================== ../botocore/vendored/__init__.py:1 /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/botocore/vendored/__init__.py:1: DeprecationWarning: invalid escape sequence '\.' """ ../botocore/client.py:625 tests/unit/test_signers.py::TestGenerateDBAuthToken::test_custom_region tests/unit/test_signers.py::TestGenerateDBAuthToken::test_generate_db_auth_token tests/functional/test_client_class_names.py::test_client_has_correct_class_name[rds] tests/functional/test_regions.py::test_single_service_region_endpoint[rds-us-east-1-rds.amazonaws.com] tests/functional/docs/test_streaming_body.py::TestStreamingBodyDocumentation::test_all_streaming_body_are_properly_documented /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/botocore/client.py:625: FutureWarning: The rds client is currently using a deprecated endpoint: rds.amazonaws.com. In the next minor version this will be moved to rds.us-east-1.amazonaws.com. See https://github.com/boto/botocore/issues/2705 for more details. warnings.warn( ../botocore/client.py:625 tests/functional/test_event_alias.py::test_event_alias_by_endpoint_prefix[health-health] tests/functional/test_event_alias.py::test_event_alias_by_service_id[health-health] tests/functional/test_event_alias.py::test_event_alias_by_client_name[health-health] tests/functional/docs/test_streaming_body.py::TestStreamingBodyDocumentation::test_all_streaming_body_are_properly_documented /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/botocore/client.py:625: FutureWarning: The health client is currently using a deprecated endpoint: health.us-east-1.amazonaws.com. In the next minor version this will be moved to global.health.amazonaws.com. See https://github.com/boto/botocore/issues/2705 for more details. warnings.warn( ../botocore/client.py:625 tests/functional/test_client_class_names.py::test_client_has_correct_class_name[sqs] tests/functional/test_regions.py::test_single_service_region_endpoint[sqs-us-east-1-queue.amazonaws.com] tests/functional/docs/test_streaming_body.py::TestStreamingBodyDocumentation::test_all_streaming_body_are_properly_documented /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/botocore/client.py:625: FutureWarning: The sqs client is currently using a deprecated endpoint: queue.amazonaws.com. In the next minor version this will be moved to sqs.us-east-1.amazonaws.com. See https://github.com/boto/botocore/issues/2705 for more details. warnings.warn( tests/unit/test_client.py::TestClientEndpointBridge::test_uses_ssl_common_name_over_hostname_if_present /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/botocore/client.py:625: FutureWarning: The myservice client is currently using a deprecated endpoint: common-name.com. In the next minor version this will be moved to do-not-use-this. See https://github.com/boto/botocore/issues/2705 for more details. warnings.warn( tests/functional/test_event_alias.py::test_event_alias_by_endpoint_prefix[emr-elasticmapreduce] tests/functional/test_event_alias.py::test_event_alias_by_service_id[emr-emr] tests/functional/test_event_alias.py::test_event_alias_by_client_name[emr-emr] tests/functional/test_regions.py::test_single_service_region_endpoint[elasticmapreduce-us-west-2-us-west-2.elasticmapreduce.amazonaws.com] /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/botocore/client.py:625: FutureWarning: The elasticmapreduce client is currently using a deprecated endpoint: us-west-2.elasticmapreduce.amazonaws.com. In the next minor version this will be moved to elasticmapreduce.us-west-2.amazonaws.com. See https://github.com/boto/botocore/issues/2705 for more details. warnings.warn( tests/functional/test_event_alias.py::test_event_alias_by_endpoint_prefix[sqs-sqs] tests/functional/test_event_alias.py::test_event_alias_by_service_id[sqs-sqs] tests/functional/test_event_alias.py::test_event_alias_by_client_name[sqs-sqs] tests/functional/test_regions.py::test_single_service_region_endpoint[sqs-us-west-2-us-west-2.queue.amazonaws.com] /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/botocore/client.py:625: FutureWarning: The sqs client is currently using a deprecated endpoint: us-west-2.queue.amazonaws.com. In the next minor version this will be moved to sqs.us-west-2.amazonaws.com. See https://github.com/boto/botocore/issues/2705 for more details. warnings.warn( tests/functional/test_regions.py::test_single_service_region_endpoint[elasticmapreduce-ap-northeast-1-ap-northeast-1.elasticmapreduce.amazonaws.com] /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/botocore/client.py:625: FutureWarning: The elasticmapreduce client is currently using a deprecated endpoint: ap-northeast-1.elasticmapreduce.amazonaws.com. In the next minor version this will be moved to elasticmapreduce.ap-northeast-1.amazonaws.com. See https://github.com/boto/botocore/issues/2705 for more details. warnings.warn( tests/functional/test_regions.py::test_single_service_region_endpoint[sqs-ap-northeast-1-ap-northeast-1.queue.amazonaws.com] /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/botocore/client.py:625: FutureWarning: The sqs client is currently using a deprecated endpoint: ap-northeast-1.queue.amazonaws.com. In the next minor version this will be moved to sqs.ap-northeast-1.amazonaws.com. See https://github.com/boto/botocore/issues/2705 for more details. warnings.warn( tests/functional/test_regions.py::test_single_service_region_endpoint[elasticmapreduce-ap-southeast-1-ap-southeast-1.elasticmapreduce.amazonaws.com] /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/botocore/client.py:625: FutureWarning: The elasticmapreduce client is currently using a deprecated endpoint: ap-southeast-1.elasticmapreduce.amazonaws.com. In the next minor version this will be moved to elasticmapreduce.ap-southeast-1.amazonaws.com. See https://github.com/boto/botocore/issues/2705 for more details. warnings.warn( tests/functional/test_regions.py::test_single_service_region_endpoint[sqs-ap-southeast-1-ap-southeast-1.queue.amazonaws.com] /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/botocore/client.py:625: FutureWarning: The sqs client is currently using a deprecated endpoint: ap-southeast-1.queue.amazonaws.com. In the next minor version this will be moved to sqs.ap-southeast-1.amazonaws.com. See https://github.com/boto/botocore/issues/2705 for more details. warnings.warn( tests/functional/test_regions.py::test_single_service_region_endpoint[elasticmapreduce-ap-southeast-2-ap-southeast-2.elasticmapreduce.amazonaws.com] /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/botocore/client.py:625: FutureWarning: The elasticmapreduce client is currently using a deprecated endpoint: ap-southeast-2.elasticmapreduce.amazonaws.com. In the next minor version this will be moved to elasticmapreduce.ap-southeast-2.amazonaws.com. See https://github.com/boto/botocore/issues/2705 for more details. warnings.warn( tests/functional/test_regions.py::test_single_service_region_endpoint[sqs-ap-southeast-2-ap-southeast-2.queue.amazonaws.com] /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/botocore/client.py:625: FutureWarning: The sqs client is currently using a deprecated endpoint: ap-southeast-2.queue.amazonaws.com. In the next minor version this will be moved to sqs.ap-southeast-2.amazonaws.com. See https://github.com/boto/botocore/issues/2705 for more details. warnings.warn( tests/functional/test_regions.py::test_single_service_region_endpoint[sqs-cn-north-1-cn-north-1.queue.amazonaws.com.cn] /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/botocore/client.py:625: FutureWarning: The sqs client is currently using a deprecated endpoint: cn-north-1.queue.amazonaws.com.cn. In the next minor version this will be moved to sqs.cn-north-1.amazonaws.com.cn. See https://github.com/boto/botocore/issues/2705 for more details. warnings.warn( tests/functional/test_regions.py::test_single_service_region_endpoint[sqs-eu-central-1-eu-central-1.queue.amazonaws.com] /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/botocore/client.py:625: FutureWarning: The sqs client is currently using a deprecated endpoint: eu-central-1.queue.amazonaws.com. In the next minor version this will be moved to sqs.eu-central-1.amazonaws.com. See https://github.com/boto/botocore/issues/2705 for more details. warnings.warn( tests/functional/test_regions.py::test_single_service_region_endpoint[elasticmapreduce-eu-west-1-eu-west-1.elasticmapreduce.amazonaws.com] /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/botocore/client.py:625: FutureWarning: The elasticmapreduce client is currently using a deprecated endpoint: eu-west-1.elasticmapreduce.amazonaws.com. In the next minor version this will be moved to elasticmapreduce.eu-west-1.amazonaws.com. See https://github.com/boto/botocore/issues/2705 for more details. warnings.warn( tests/functional/test_regions.py::test_single_service_region_endpoint[sqs-eu-west-1-eu-west-1.queue.amazonaws.com] /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/botocore/client.py:625: FutureWarning: The sqs client is currently using a deprecated endpoint: eu-west-1.queue.amazonaws.com. In the next minor version this will be moved to sqs.eu-west-1.amazonaws.com. See https://github.com/boto/botocore/issues/2705 for more details. warnings.warn( tests/functional/test_regions.py::test_single_service_region_endpoint[elasticmapreduce-sa-east-1-sa-east-1.elasticmapreduce.amazonaws.com] /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/botocore/client.py:625: FutureWarning: The elasticmapreduce client is currently using a deprecated endpoint: sa-east-1.elasticmapreduce.amazonaws.com. In the next minor version this will be moved to elasticmapreduce.sa-east-1.amazonaws.com. See https://github.com/boto/botocore/issues/2705 for more details. warnings.warn( tests/functional/test_regions.py::test_single_service_region_endpoint[sqs-sa-east-1-sa-east-1.queue.amazonaws.com] /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/botocore/client.py:625: FutureWarning: The sqs client is currently using a deprecated endpoint: sa-east-1.queue.amazonaws.com. In the next minor version this will be moved to sqs.sa-east-1.amazonaws.com. See https://github.com/boto/botocore/issues/2705 for more details. warnings.warn( tests/functional/test_regions.py::test_single_service_region_endpoint[sqs-us-gov-west-1-us-gov-west-1.queue.amazonaws.com] /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/botocore/client.py:625: FutureWarning: The sqs client is currently using a deprecated endpoint: us-gov-west-1.queue.amazonaws.com. In the next minor version this will be moved to sqs.us-gov-west-1.amazonaws.com. See https://github.com/boto/botocore/issues/2705 for more details. warnings.warn( tests/functional/test_regions.py::test_single_service_region_endpoint[elasticmapreduce-us-west-1-us-west-1.elasticmapreduce.amazonaws.com] /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/botocore/client.py:625: FutureWarning: The elasticmapreduce client is currently using a deprecated endpoint: us-west-1.elasticmapreduce.amazonaws.com. In the next minor version this will be moved to elasticmapreduce.us-west-1.amazonaws.com. See https://github.com/boto/botocore/issues/2705 for more details. warnings.warn( tests/functional/test_regions.py::test_single_service_region_endpoint[sqs-us-west-1-us-west-1.queue.amazonaws.com] /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/botocore/client.py:625: FutureWarning: The sqs client is currently using a deprecated endpoint: us-west-1.queue.amazonaws.com. In the next minor version this will be moved to sqs.us-west-1.amazonaws.com. See https://github.com/boto/botocore/issues/2705 for more details. warnings.warn( tests/functional/docs/test_shared_example_config.py::test_lint_shared_example_configs[DescribeStream-example_config228-service_model228] /usr/lib/python3/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 ========== 30078 passed, 90 skipped, 41 warnings in 241.29s (0:04:01) ========== Running pytest unit/ functional/... py3 finish: run-test after 247.92 seconds py3 start: run-test-post py3 finish: run-test-post after 0.00 seconds ___________________________________ summary ____________________________________ py3: commands succeeded congratulations :) cleanup /usr/src/RPM/BUILD/python3-module-botocore-1.27.90/.tox/.tmp/package/1/botocore-1.27.90-py3-none-any.whl + exit 0 Processing files: python3-module-botocore-1.27.90-alt1 Executing(%doc): /bin/sh -e /usr/src/tmp/rpm-tmp.45459 + umask 022 + /bin/mkdir -p /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + cd python3-module-botocore-1.27.90 + DOCDIR=/usr/src/tmp/python3-module-botocore-buildroot/usr/share/doc/python3-module-botocore-1.27.90 + export DOCDIR + rm -rf /usr/src/tmp/python3-module-botocore-buildroot/usr/share/doc/python3-module-botocore-1.27.90 + /bin/mkdir -p /usr/src/tmp/python3-module-botocore-buildroot/usr/share/doc/python3-module-botocore-1.27.90 + cp -prL LICENSE.txt /usr/src/tmp/python3-module-botocore-buildroot/usr/share/doc/python3-module-botocore-1.27.90 + chmod -R go-w /usr/src/tmp/python3-module-botocore-buildroot/usr/share/doc/python3-module-botocore-1.27.90 + chmod -R a+rX /usr/src/tmp/python3-module-botocore-buildroot/usr/share/doc/python3-module-botocore-1.27.90 + cp -prL CHANGELOG.rst CONTRIBUTING.rst README.rst /usr/src/tmp/python3-module-botocore-buildroot/usr/share/doc/python3-module-botocore-1.27.90 + chmod -R go-w /usr/src/tmp/python3-module-botocore-buildroot/usr/share/doc/python3-module-botocore-1.27.90 + chmod -R a+rX /usr/src/tmp/python3-module-botocore-buildroot/usr/share/doc/python3-module-botocore-1.27.90 + exit 0 Finding Provides (using /usr/lib/rpm/find-provides) Executing: /bin/sh -e /usr/src/tmp/rpm-tmp.bU1MUf find-provides: running scripts (alternatives,debuginfo,lib,pam,perl,pkgconfig,python,python3,shell) Finding Requires (using /usr/lib/rpm/find-requires) Executing: /bin/sh -e /usr/src/tmp/rpm-tmp.FoPz8E find-requires: running scripts (cpp,debuginfo,files,lib,pam,perl,pkgconfig,pkgconfiglib,python,python3,rpmlib,shebang,shell,static,symlinks,systemd-services) /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/args.py: botocore.config is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/args.py: botocore.endpoint is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/args.py: botocore.exceptions is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/args.py: botocore.parsers is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/args.py: botocore.regions is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/args.py: botocore.serialize is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/args.py: botocore.signers is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/args.py: botocore.utils is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/auth.py: botocore.compat is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/auth.py: botocore.crt.auth is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/auth.py: botocore.exceptions is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/auth.py: botocore.utils is possibly a self-providing dependency, skip it python3.req: /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/auth.py: skipping time /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/awsrequest.py: botocore.compat is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/awsrequest.py: botocore.exceptions is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/awsrequest.py: botocore.utils is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/client.py: botocore is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/client.py: botocore.args is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/client.py: botocore.auth is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/client.py: botocore.awsrequest is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/client.py: botocore.config is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/client.py: botocore.discovery is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/client.py: botocore.docs.docstring is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/client.py: botocore.exceptions is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/client.py: botocore.history is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/client.py: botocore.hooks is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/client.py: botocore.httpchecksum is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/client.py: botocore.model is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/client.py: botocore.paginate is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/client.py: botocore.retries is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/client.py: botocore.utils is possibly a self-providing dependency, skip it /usr/lib/rpm/python3.req.py: /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/compat.py: Ignore for REQ=slight module=awscrt.auth /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/compat.py: botocore.exceptions is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/compat.py: botocore.vendored is possibly a self-providing dependency, skip it /usr/lib/rpm/python3.req.py: /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/compat.py: Ignore for REQ=slight module=gzip python3.req: /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/compat.py: skipping itertools python3.req: /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/compat.py: skipping sys /usr/lib/rpm/python3.req.py: /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/compat.py: Ignore for REQ=slight module=xml.etree.ElementTree /usr/lib/rpm/python3.req.py: /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/compat.py: Ignore for REQ=slight module=xml.etree.cElementTree /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/config.py: botocore.compat is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/config.py: botocore.endpoint is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/config.py: botocore.exceptions is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/configloader.py: botocore.compat is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/configloader.py: botocore.exceptions is possibly a self-providing dependency, skip it python3.req: /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/configloader.py: skipping sys /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/configprovider.py: botocore is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/credentials.py: botocore is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/credentials.py: botocore.compat is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/credentials.py: botocore.config is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/credentials.py: botocore.configloader is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/credentials.py: botocore.exceptions is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/credentials.py: botocore.utils is possibly a self-providing dependency, skip it python3.req: /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/credentials.py: skipping time /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/crt/auth.py: botocore.auth is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/crt/auth.py: botocore.compat is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/crt/auth.py: botocore.exceptions is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/crt/auth.py: botocore.utils is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/discovery.py: botocore is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/discovery.py: botocore.exceptions is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/discovery.py: botocore.model is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/discovery.py: botocore.utils is possibly a self-providing dependency, skip it python3.req: /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/discovery.py: skipping time /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/__init__.py: botocore.docs.service is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/bcdoc/docstringparser.py: botocore.compat is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/bcdoc/restdoc.py: botocore.compat is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/bcdoc/restdoc.py: botocore.docs.bcdoc.docstringparser is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/bcdoc/restdoc.py: botocore.docs.bcdoc.style is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/client.py: botocore.compat is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/client.py: botocore.docs.example is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/client.py: botocore.docs.method is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/client.py: botocore.docs.params is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/client.py: botocore.docs.sharedexample is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/client.py: botocore.docs.utils is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/docstring.py: botocore.docs.bcdoc.restdoc is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/docstring.py: botocore.docs.method is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/docstring.py: botocore.docs.paginator is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/docstring.py: botocore.docs.waiter is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/example.py: botocore.docs.shape is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/example.py: botocore.docs.utils is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/method.py: botocore.docs.example is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/method.py: botocore.docs.params is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/paginator.py: botocore is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/paginator.py: botocore.compat is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/paginator.py: botocore.docs.method is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/paginator.py: botocore.docs.utils is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/paginator.py: botocore.utils is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/params.py: botocore.docs.shape is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/params.py: botocore.docs.utils is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/service.py: botocore.docs.bcdoc.restdoc is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/service.py: botocore.docs.client is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/service.py: botocore.docs.paginator is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/service.py: botocore.docs.waiter is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/service.py: botocore.exceptions is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/shape.py: botocore.utils is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/sharedexample.py: botocore.docs.utils is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/sharedexample.py: botocore.utils is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/waiter.py: botocore is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/waiter.py: botocore.compat is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/waiter.py: botocore.docs.method is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/waiter.py: botocore.docs.utils is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/docs/waiter.py: botocore.utils is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/endpoint.py: botocore is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/endpoint.py: botocore.awsrequest is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/endpoint.py: botocore.exceptions is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/endpoint.py: botocore.history is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/endpoint.py: botocore.hooks is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/endpoint.py: botocore.httpchecksum is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/endpoint.py: botocore.httpsession is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/endpoint.py: botocore.response is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/endpoint.py: botocore.utils is possibly a self-providing dependency, skip it python3.req: /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/endpoint.py: skipping time /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/endpoint_provider.py: botocore is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/endpoint_provider.py: botocore.compat is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/endpoint_provider.py: botocore.exceptions is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/endpoint_provider.py: botocore.utils is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/errorfactory.py: botocore.exceptions is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/errorfactory.py: botocore.utils is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/eventstream.py: botocore.exceptions is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/exceptions.py: botocore.vendored is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/handlers.py: botocore is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/handlers.py: botocore.auth is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/handlers.py: botocore.compat is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/handlers.py: botocore.docs.utils is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/handlers.py: botocore.exceptions is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/handlers.py: botocore.signers is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/handlers.py: botocore.utils is possibly a self-providing dependency, skip it /usr/lib/rpm/python3.req.py: /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/handlers.py: Ignore for REQ=slight module=ssl /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/hooks.py: botocore.compat is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/hooks.py: botocore.utils is possibly a self-providing dependency, skip it /usr/lib/rpm/python3.req.py: /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/httpchecksum.py: Ignore for REQ=slight module=awscrt /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/httpchecksum.py: botocore.compat is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/httpchecksum.py: botocore.exceptions is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/httpchecksum.py: botocore.response is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/httpchecksum.py: botocore.utils is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/httpsession.py: botocore.awsrequest is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/httpsession.py: botocore.compat is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/httpsession.py: botocore.exceptions is possibly a self-providing dependency, skip it /usr/lib/rpm/python3.req.py: /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/httpsession.py: Ignore for REQ=slight module=ssl python3.req: /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/httpsession.py: skipping sys /usr/lib/rpm/python3.req.py: /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/httpsession.py: Ignore for REQ=slight module=urllib3.contrib.pyopenssl /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/loaders.py: botocore is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/loaders.py: botocore.compat is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/loaders.py: botocore.exceptions is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/loaders.py: botocore.utils is possibly a self-providing dependency, skip it /usr/lib/rpm/python3.req.py: /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/loaders.py: Ignore for REQ=slight module=gzip /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/model.py: botocore.compat is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/model.py: botocore.exceptions is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/model.py: botocore.utils is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/monitoring.py: botocore.compat is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/monitoring.py: botocore.retryhandler is possibly a self-providing dependency, skip it python3.req: /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/monitoring.py: skipping time /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/paginate.py: botocore.exceptions is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/paginate.py: botocore.utils is possibly a self-providing dependency, skip it python3.req: /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/paginate.py: skipping itertools /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/parsers.py: botocore.compat is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/parsers.py: botocore.eventstream is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/parsers.py: botocore.utils is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/regions.py: botocore.exceptions is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/response.py: botocore is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/response.py: botocore.compat is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/response.py: botocore.exceptions is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/response.py: botocore.hooks is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retries/adaptive.py: botocore.retries is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retries/bucket.py: botocore.exceptions is possibly a self-providing dependency, skip it python3.req: /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retries/bucket.py: skipping time /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retries/special.py: botocore.retries.base is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retries/standard.py: botocore.exceptions is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retries/standard.py: botocore.retries is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retries/standard.py: botocore.retries.base is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/retryhandler.py: botocore.exceptions is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/serialize.py: botocore is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/serialize.py: botocore.compat is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/serialize.py: botocore.utils is possibly a self-providing dependency, skip it /usr/lib/rpm/python3.req.py: /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/session.py: Ignore for REQ=slight module=awscrt /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/session.py: botocore is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/session.py: botocore.client is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/session.py: botocore.compat is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/session.py: botocore.configloader is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/session.py: botocore.configprovider is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/session.py: botocore.credentials is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/session.py: botocore.errorfactory is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/session.py: botocore.exceptions is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/session.py: botocore.hooks is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/session.py: botocore.loaders is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/session.py: botocore.model is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/session.py: botocore.parsers is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/session.py: botocore.regions is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/session.py: botocore.tokens is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/session.py: botocore.utils is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/signers.py: botocore is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/signers.py: botocore.auth is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/signers.py: botocore.awsrequest is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/signers.py: botocore.compat is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/signers.py: botocore.exceptions is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/signers.py: botocore.utils is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/stub.py: botocore.awsrequest is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/stub.py: botocore.exceptions is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/stub.py: botocore.validate is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/tokens.py: botocore is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/tokens.py: botocore.compat is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/tokens.py: botocore.config is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/tokens.py: botocore.credentials is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/tokens.py: botocore.exceptions is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/tokens.py: botocore.utils is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/translate.py: botocore.utils is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/utils.py: botocore is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/utils.py: botocore.awsrequest is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/utils.py: botocore.compat is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/utils.py: botocore.exceptions is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/utils.py: botocore.httpsession is possibly a self-providing dependency, skip it python3.req: /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/utils.py: skipping time /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/validate.py: botocore.exceptions is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/validate.py: botocore.utils is possibly a self-providing dependency, skip it python3.req: /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/vendored/__init__.py: skipping sys /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/waiter.py: botocore.docs.docstring is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/waiter.py: botocore.utils is possibly a self-providing dependency, skip it python3.req: /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/waiter.py: skipping time /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/waiter.py: botocore is possibly a self-providing dependency, skip it /usr/src/tmp/python3-module-botocore-buildroot/usr/lib/python3/site-packages/botocore/waiter.py: botocore.exceptions is possibly a self-providing dependency, skip it ++ /bin/sed -e '/python3(botocore\.vendored\..*)/d' --- find-requires-deps 2023-04-29 06:31:42.814916194 +0000 +++ filter-requires-deps 2023-04-29 06:31:42.815916199 +0000 @@ -3,6 +3,2 @@ python3(binascii) < 0 -python3(botocore.vendored.requests.packages) < 0 -python3(botocore.vendored.six.moves) < 0 -python3(botocore.vendored.six.moves.urllib.request) < 0 -python3(botocore.vendored.six.moves.urllib_parse) < 0 python3(calendar) < 0 Provides: python3(botocore), python3(botocore.args), python3(botocore.auth), python3(botocore.awsrequest), python3(botocore.client), python3(botocore.compat), python3(botocore.config), python3(botocore.configloader), python3(botocore.configprovider), python3(botocore.credentials), python3(botocore.crt), python3(botocore.crt.auth), python3(botocore.discovery), python3(botocore.docs), python3(botocore.docs.bcdoc), python3(botocore.docs.bcdoc.docstringparser), python3(botocore.docs.bcdoc.restdoc), python3(botocore.docs.bcdoc.style), python3(botocore.docs.client), python3(botocore.docs.docstring), python3(botocore.docs.example), python3(botocore.docs.method), python3(botocore.docs.paginator), python3(botocore.docs.params), python3(botocore.docs.service), python3(botocore.docs.shape), python3(botocore.docs.sharedexample), python3(botocore.docs.utils), python3(botocore.docs.waiter), python3(botocore.endpoint), python3(botocore.endpoint_provider), python3(botocore.errorfactory), python3(botocore.eventstream), python3(botocore.exceptions), python3(botocore.handlers), python3(botocore.history), python3(botocore.hooks), python3(botocore.httpchecksum), python3(botocore.httpsession), python3(botocore.loaders), python3(botocore.model), python3(botocore.monitoring), python3(botocore.paginate), python3(botocore.parsers), python3(botocore.regions), python3(botocore.response), python3(botocore.retries), python3(botocore.retries.adaptive), python3(botocore.retries.base), python3(botocore.retries.bucket), python3(botocore.retries.quota), python3(botocore.retries.special), python3(botocore.retries.standard), python3(botocore.retries.throttling), python3(botocore.retryhandler), python3(botocore.serialize), python3(botocore.session), python3(botocore.signers), python3(botocore.stub), python3(botocore.tokens), python3(botocore.translate), python3(botocore.utils), python3(botocore.validate), python3(botocore.vendored), python3(botocore.waiter) Requires: python3(six) < 0, python3(requests) < 0, /usr/lib/python3/site-packages, python3(base64) < 0, python3(binascii) < 0, python3(calendar) < 0, python3(cgi) < 0, python3(collections) < 0, python3(collections.abc) < 0, python3(copy) < 0, python3(datetime) < 0, python3(dateutil.parser) < 0, python3(dateutil.tz) < 0, python3(decimal) < 0, python3(email.utils) < 0, python3(enum) < 0, python3(functools) < 0, python3(getpass) < 0, python3(hashlib) < 0, python3(hmac) < 0, python3(http.client) < 0, python3(importlib) < 0, python3(importlib.util) < 0, python3(inspect) < 0, python3(io) < 0, python3(jmespath) < 0, python3(json) < 0, python3(logging) < 0, python3(math) < 0, python3(numbers) < 0, python3(operator) < 0, python3(os) < 0, python3(os.path) < 0, python3(pathlib) < 0, python3(platform) < 0, python3(pprint) < 0, python3(random) < 0, python3(re) < 0, python3(shlex) < 0, python3(socket) < 0, python3(string) < 0, python3(struct) < 0, python3(subprocess) < 0, python3(threading) < 0, python3(types) < 0, python3(typing) < 0, python3(urllib.parse) < 0, python3(urllib3) < 0, python3(urllib3.connection) < 0, python3(urllib3.connectionpool) < 0, python3(urllib3.exceptions) < 0, python3(urllib3.util) < 0, python3(urllib3.util.retry) < 0, python3(urllib3.util.ssl_) < 0, python3(urllib3.util.url) < 0, python3(uuid) < 0, python3(warnings) < 0, python3(weakref) < 0, python3(xml.etree) < 0 Wrote: /usr/src/RPM/RPMS/noarch/python3-module-botocore-1.27.90-alt1.noarch.rpm (w2T8.xzdio) 257.20user 14.64system 4:38.26elapsed 97%CPU (0avgtext+0avgdata 1172528maxresident)k 0inputs+0outputs (0major+4884827minor)pagefaults 0swaps 7.46user 2.93system 5:10.14elapsed 3%CPU (0avgtext+0avgdata 109012maxresident)k 0inputs+0outputs (48908major+361604minor)pagefaults 0swaps --- python3-module-botocore-1.27.90-alt1.noarch.rpm.repo 2022-10-14 10:20:33.000000000 +0000 +++ python3-module-botocore-1.27.90-alt1.noarch.rpm.hasher 2023-04-29 06:31:46.635933146 +0000 @@ -2178,8 +2178,8 @@ File: /usr/lib/python3/site-packages/botocore/__pycache__/__init__.cpython-310.pyc 100644 root:root 622447b9c4241874829d5632854e2456 -File: /usr/lib/python3/site-packages/botocore/__pycache__/args.cpython-310.opt-1.pyc 100644 root:root c0648ded47b45cf35a7665eb4dee3169 -File: /usr/lib/python3/site-packages/botocore/__pycache__/args.cpython-310.opt-2.pyc 100644 root:root 4b17cf920c9cbc071955c92c74ec0cbe -File: /usr/lib/python3/site-packages/botocore/__pycache__/args.cpython-310.pyc 100644 root:root c0648ded47b45cf35a7665eb4dee3169 -File: /usr/lib/python3/site-packages/botocore/__pycache__/auth.cpython-310.opt-1.pyc 100644 root:root 366180c0b839fba5bc5223432f0a10dc -File: /usr/lib/python3/site-packages/botocore/__pycache__/auth.cpython-310.opt-2.pyc 100644 root:root 1a5ff3f0fa0459b3a028b1a2b9a4b584 -File: /usr/lib/python3/site-packages/botocore/__pycache__/auth.cpython-310.pyc 100644 root:root 366180c0b839fba5bc5223432f0a10dc +File: /usr/lib/python3/site-packages/botocore/__pycache__/args.cpython-310.opt-1.pyc 100644 root:root 93b5a0114266de4267ff7f9da677978a +File: /usr/lib/python3/site-packages/botocore/__pycache__/args.cpython-310.opt-2.pyc 100644 root:root f694ee6c3658baaac55a03b264a332da +File: /usr/lib/python3/site-packages/botocore/__pycache__/args.cpython-310.pyc 100644 root:root 93b5a0114266de4267ff7f9da677978a +File: /usr/lib/python3/site-packages/botocore/__pycache__/auth.cpython-310.opt-1.pyc 100644 root:root ed5e95e40d131ea06176a2b3424656f8 +File: /usr/lib/python3/site-packages/botocore/__pycache__/auth.cpython-310.opt-2.pyc 100644 root:root 50921e39a20622fde39bf3ea02a0fa2f +File: /usr/lib/python3/site-packages/botocore/__pycache__/auth.cpython-310.pyc 100644 root:root ed5e95e40d131ea06176a2b3424656f8 File: /usr/lib/python3/site-packages/botocore/__pycache__/awsrequest.cpython-310.opt-1.pyc 100644 root:root 75ebe96227936091eca5d0ba2233682b @@ -2187,5 +2187,5 @@ File: /usr/lib/python3/site-packages/botocore/__pycache__/awsrequest.cpython-310.pyc 100644 root:root 75ebe96227936091eca5d0ba2233682b -File: /usr/lib/python3/site-packages/botocore/__pycache__/client.cpython-310.opt-1.pyc 100644 root:root 5f099ca188749bf695b1ac400c272360 -File: /usr/lib/python3/site-packages/botocore/__pycache__/client.cpython-310.opt-2.pyc 100644 root:root f2d98ca711c63382060ac2f56b9ca2f3 -File: /usr/lib/python3/site-packages/botocore/__pycache__/client.cpython-310.pyc 100644 root:root 5f099ca188749bf695b1ac400c272360 +File: /usr/lib/python3/site-packages/botocore/__pycache__/client.cpython-310.opt-1.pyc 100644 root:root 67ef8f332ac6673589589471545e0833 +File: /usr/lib/python3/site-packages/botocore/__pycache__/client.cpython-310.opt-2.pyc 100644 root:root 041337789b2838d2de7d8bc58a3c7122 +File: /usr/lib/python3/site-packages/botocore/__pycache__/client.cpython-310.pyc 100644 root:root 67ef8f332ac6673589589471545e0833 File: /usr/lib/python3/site-packages/botocore/__pycache__/compat.cpython-310.opt-1.pyc 100644 root:root f6fabd4bbcb94c7f1d2ac973158748df @@ -2199,5 +2199,5 @@ File: /usr/lib/python3/site-packages/botocore/__pycache__/configloader.cpython-310.pyc 100644 root:root 957412ec27dae1f8b543f74c4c905e7b -File: /usr/lib/python3/site-packages/botocore/__pycache__/configprovider.cpython-310.opt-1.pyc 100644 root:root e71a024c54e69727f21b34772051e137 -File: /usr/lib/python3/site-packages/botocore/__pycache__/configprovider.cpython-310.opt-2.pyc 100644 root:root 437c2e483244e95b39d8c6699e3f9912 -File: /usr/lib/python3/site-packages/botocore/__pycache__/configprovider.cpython-310.pyc 100644 root:root e71a024c54e69727f21b34772051e137 +File: /usr/lib/python3/site-packages/botocore/__pycache__/configprovider.cpython-310.opt-1.pyc 100644 root:root 3534b58a0d8214d96d39aea2e95a0af2 +File: /usr/lib/python3/site-packages/botocore/__pycache__/configprovider.cpython-310.opt-2.pyc 100644 root:root 7793b0ad1a70baf0ad728a5b9ef71282 +File: /usr/lib/python3/site-packages/botocore/__pycache__/configprovider.cpython-310.pyc 100644 root:root 3534b58a0d8214d96d39aea2e95a0af2 File: /usr/lib/python3/site-packages/botocore/__pycache__/credentials.cpython-310.opt-1.pyc 100644 root:root 9ad959f69ae2be94e23c9cf96984b652 @@ -2205,11 +2205,11 @@ File: /usr/lib/python3/site-packages/botocore/__pycache__/credentials.cpython-310.pyc 100644 root:root 9ad959f69ae2be94e23c9cf96984b652 -File: /usr/lib/python3/site-packages/botocore/__pycache__/discovery.cpython-310.opt-1.pyc 100644 root:root 11e9c09df1b7641ca1f54977a62fadc7 -File: /usr/lib/python3/site-packages/botocore/__pycache__/discovery.cpython-310.opt-2.pyc 100644 root:root 2fef6aabc608ca7bfc26ed9374f362d9 -File: /usr/lib/python3/site-packages/botocore/__pycache__/discovery.cpython-310.pyc 100644 root:root 11e9c09df1b7641ca1f54977a62fadc7 -File: /usr/lib/python3/site-packages/botocore/__pycache__/endpoint.cpython-310.opt-1.pyc 100644 root:root 64d3f626722e4887e7e783739d1185b1 -File: /usr/lib/python3/site-packages/botocore/__pycache__/endpoint.cpython-310.opt-2.pyc 100644 root:root 87297bb88eebb1e183c0b684dfe08187 -File: /usr/lib/python3/site-packages/botocore/__pycache__/endpoint.cpython-310.pyc 100644 root:root 64d3f626722e4887e7e783739d1185b1 -File: /usr/lib/python3/site-packages/botocore/__pycache__/endpoint_provider.cpython-310.opt-1.pyc 100644 root:root 88428637f6a086a3abb81118704c56ae -File: /usr/lib/python3/site-packages/botocore/__pycache__/endpoint_provider.cpython-310.opt-2.pyc 100644 root:root 52971ff8d257dfd7029616f2ca4fd018 -File: /usr/lib/python3/site-packages/botocore/__pycache__/endpoint_provider.cpython-310.pyc 100644 root:root 88428637f6a086a3abb81118704c56ae +File: /usr/lib/python3/site-packages/botocore/__pycache__/discovery.cpython-310.opt-1.pyc 100644 root:root 7d56967d3b7ea08c9bdede1b54506e2a +File: /usr/lib/python3/site-packages/botocore/__pycache__/discovery.cpython-310.opt-2.pyc 100644 root:root 75fd950f829cc2e08d914e673211fb07 +File: /usr/lib/python3/site-packages/botocore/__pycache__/discovery.cpython-310.pyc 100644 root:root 7d56967d3b7ea08c9bdede1b54506e2a +File: /usr/lib/python3/site-packages/botocore/__pycache__/endpoint.cpython-310.opt-1.pyc 100644 root:root 89000d14214f001a691c5c095ce512af +File: /usr/lib/python3/site-packages/botocore/__pycache__/endpoint.cpython-310.opt-2.pyc 100644 root:root 00f8b8b86103d880dd807344fffa15a5 +File: /usr/lib/python3/site-packages/botocore/__pycache__/endpoint.cpython-310.pyc 100644 root:root 89000d14214f001a691c5c095ce512af +File: /usr/lib/python3/site-packages/botocore/__pycache__/endpoint_provider.cpython-310.opt-1.pyc 100644 root:root 66e116dbce39b94eb36e2fe9af4afdef +File: /usr/lib/python3/site-packages/botocore/__pycache__/endpoint_provider.cpython-310.opt-2.pyc 100644 root:root a0257c95693890d494e34f01269923b3 +File: /usr/lib/python3/site-packages/botocore/__pycache__/endpoint_provider.cpython-310.pyc 100644 root:root 66e116dbce39b94eb36e2fe9af4afdef File: /usr/lib/python3/site-packages/botocore/__pycache__/errorfactory.cpython-310.opt-1.pyc 100644 root:root 6e55a2b1988244da66d6db4f0ec3dcb7 @@ -2223,5 +2223,5 @@ File: /usr/lib/python3/site-packages/botocore/__pycache__/exceptions.cpython-310.pyc 100644 root:root 38525b74e8bea41488438c6f6fd41fb3 -File: /usr/lib/python3/site-packages/botocore/__pycache__/handlers.cpython-310.opt-1.pyc 100644 root:root ed48ddc9ceded1bf27485132113a7de9 -File: /usr/lib/python3/site-packages/botocore/__pycache__/handlers.cpython-310.opt-2.pyc 100644 root:root d600d05bac3c18e8a4af7015d6786ae0 -File: /usr/lib/python3/site-packages/botocore/__pycache__/handlers.cpython-310.pyc 100644 root:root ed48ddc9ceded1bf27485132113a7de9 +File: /usr/lib/python3/site-packages/botocore/__pycache__/handlers.cpython-310.opt-1.pyc 100644 root:root 0d1bf7771007abf7fcaec694ba2b2e8d +File: /usr/lib/python3/site-packages/botocore/__pycache__/handlers.cpython-310.opt-2.pyc 100644 root:root 1cc4b1a67bf4205ed512c00fa4bac6bb +File: /usr/lib/python3/site-packages/botocore/__pycache__/handlers.cpython-310.pyc 100644 root:root 0d1bf7771007abf7fcaec694ba2b2e8d File: /usr/lib/python3/site-packages/botocore/__pycache__/history.cpython-310.opt-1.pyc 100644 root:root 5a883eff19a4c4fd20d76c6888390282 @@ -2229,5 +2229,5 @@ File: /usr/lib/python3/site-packages/botocore/__pycache__/history.cpython-310.pyc 100644 root:root 5a883eff19a4c4fd20d76c6888390282 -File: /usr/lib/python3/site-packages/botocore/__pycache__/hooks.cpython-310.opt-1.pyc 100644 root:root 7569571b04e5cad6ae2ce292049a2750 -File: /usr/lib/python3/site-packages/botocore/__pycache__/hooks.cpython-310.opt-2.pyc 100644 root:root c6f1c8fe9daef123b5b5d3995ef35c69 -File: /usr/lib/python3/site-packages/botocore/__pycache__/hooks.cpython-310.pyc 100644 root:root 7569571b04e5cad6ae2ce292049a2750 +File: /usr/lib/python3/site-packages/botocore/__pycache__/hooks.cpython-310.opt-1.pyc 100644 root:root 14a3ad1a6fb4b7e41c115ffc475162aa +File: /usr/lib/python3/site-packages/botocore/__pycache__/hooks.cpython-310.opt-2.pyc 100644 root:root 56ce49cfac515dd364338e12e30cd104 +File: /usr/lib/python3/site-packages/botocore/__pycache__/hooks.cpython-310.pyc 100644 root:root 14a3ad1a6fb4b7e41c115ffc475162aa File: /usr/lib/python3/site-packages/botocore/__pycache__/httpchecksum.cpython-310.opt-1.pyc 100644 root:root 0dcd7d55ed56d9e6b26767ca3ca25e60 @@ -2235,5 +2235,5 @@ File: /usr/lib/python3/site-packages/botocore/__pycache__/httpchecksum.cpython-310.pyc 100644 root:root 0dcd7d55ed56d9e6b26767ca3ca25e60 -File: /usr/lib/python3/site-packages/botocore/__pycache__/httpsession.cpython-310.opt-1.pyc 100644 root:root 4ab908b6de8f29d74025c1dad5b9a31c -File: /usr/lib/python3/site-packages/botocore/__pycache__/httpsession.cpython-310.opt-2.pyc 100644 root:root 5a45b6c15c7b05b12530ddb0e8369e3c -File: /usr/lib/python3/site-packages/botocore/__pycache__/httpsession.cpython-310.pyc 100644 root:root 4ab908b6de8f29d74025c1dad5b9a31c +File: /usr/lib/python3/site-packages/botocore/__pycache__/httpsession.cpython-310.opt-1.pyc 100644 root:root eb46108f0406140e7a3c87777e5818ec +File: /usr/lib/python3/site-packages/botocore/__pycache__/httpsession.cpython-310.opt-2.pyc 100644 root:root 21f7b02d03b187fc92dc79084768e898 +File: /usr/lib/python3/site-packages/botocore/__pycache__/httpsession.cpython-310.pyc 100644 root:root eb46108f0406140e7a3c87777e5818ec File: /usr/lib/python3/site-packages/botocore/__pycache__/loaders.cpython-310.opt-1.pyc 100644 root:root 8c9a8097ec6a44606bb21334c295d971 @@ -2241,5 +2241,5 @@ File: /usr/lib/python3/site-packages/botocore/__pycache__/loaders.cpython-310.pyc 100644 root:root 8c9a8097ec6a44606bb21334c295d971 -File: /usr/lib/python3/site-packages/botocore/__pycache__/model.cpython-310.opt-1.pyc 100644 root:root 4f6377c21b691bb808306e4e0e73a39c -File: /usr/lib/python3/site-packages/botocore/__pycache__/model.cpython-310.opt-2.pyc 100644 root:root 2ff0ccbf028fb9dae615e57c0c540bf6 -File: /usr/lib/python3/site-packages/botocore/__pycache__/model.cpython-310.pyc 100644 root:root 4f6377c21b691bb808306e4e0e73a39c +File: /usr/lib/python3/site-packages/botocore/__pycache__/model.cpython-310.opt-1.pyc 100644 root:root 187faae2bacd2ef51e8003031b7e60b2 +File: /usr/lib/python3/site-packages/botocore/__pycache__/model.cpython-310.opt-2.pyc 100644 root:root 4e1f2ba354875c12e7a7f65bbc8203b5 +File: /usr/lib/python3/site-packages/botocore/__pycache__/model.cpython-310.pyc 100644 root:root 187faae2bacd2ef51e8003031b7e60b2 File: /usr/lib/python3/site-packages/botocore/__pycache__/monitoring.cpython-310.opt-1.pyc 100644 root:root e8a3e9c5aac54a2a06ca82b26274cc77 @@ -2247,11 +2247,11 @@ File: /usr/lib/python3/site-packages/botocore/__pycache__/monitoring.cpython-310.pyc 100644 root:root e8a3e9c5aac54a2a06ca82b26274cc77 -File: /usr/lib/python3/site-packages/botocore/__pycache__/paginate.cpython-310.opt-1.pyc 100644 root:root 181fa3633ca3716faa3ec76986df87b6 -File: /usr/lib/python3/site-packages/botocore/__pycache__/paginate.cpython-310.opt-2.pyc 100644 root:root 9d43a35e4e65d7b8677c83ca78f62b1a -File: /usr/lib/python3/site-packages/botocore/__pycache__/paginate.cpython-310.pyc 100644 root:root 181fa3633ca3716faa3ec76986df87b6 -File: /usr/lib/python3/site-packages/botocore/__pycache__/parsers.cpython-310.opt-1.pyc 100644 root:root 96256f1c975afe60b6cf1ac2f40d5c20 -File: /usr/lib/python3/site-packages/botocore/__pycache__/parsers.cpython-310.opt-2.pyc 100644 root:root fde79e122669114287cee5879de47724 -File: /usr/lib/python3/site-packages/botocore/__pycache__/parsers.cpython-310.pyc 100644 root:root 96256f1c975afe60b6cf1ac2f40d5c20 -File: /usr/lib/python3/site-packages/botocore/__pycache__/regions.cpython-310.opt-1.pyc 100644 root:root d64de743bb15c5238956bd8343bf3ddc -File: /usr/lib/python3/site-packages/botocore/__pycache__/regions.cpython-310.opt-2.pyc 100644 root:root ca06cfd43c41a1528c037cad3d9d5402 -File: /usr/lib/python3/site-packages/botocore/__pycache__/regions.cpython-310.pyc 100644 root:root d64de743bb15c5238956bd8343bf3ddc +File: /usr/lib/python3/site-packages/botocore/__pycache__/paginate.cpython-310.opt-1.pyc 100644 root:root 528bc780c6c16bd26061d1fb02e1ac16 +File: /usr/lib/python3/site-packages/botocore/__pycache__/paginate.cpython-310.opt-2.pyc 100644 root:root 4f12177c3aa3546e64d42e2975af9bf9 +File: /usr/lib/python3/site-packages/botocore/__pycache__/paginate.cpython-310.pyc 100644 root:root 528bc780c6c16bd26061d1fb02e1ac16 +File: /usr/lib/python3/site-packages/botocore/__pycache__/parsers.cpython-310.opt-1.pyc 100644 root:root 33725c4811f941c06fdea8806f0c5169 +File: /usr/lib/python3/site-packages/botocore/__pycache__/parsers.cpython-310.opt-2.pyc 100644 root:root a9e57f7aeabc226ac6096b52dd395245 +File: /usr/lib/python3/site-packages/botocore/__pycache__/parsers.cpython-310.pyc 100644 root:root 33725c4811f941c06fdea8806f0c5169 +File: /usr/lib/python3/site-packages/botocore/__pycache__/regions.cpython-310.opt-1.pyc 100644 root:root 076f8ba0267db39f3ec65803a8deed28 +File: /usr/lib/python3/site-packages/botocore/__pycache__/regions.cpython-310.opt-2.pyc 100644 root:root 73663d2ed07b8334d9f98a00abeb493a +File: /usr/lib/python3/site-packages/botocore/__pycache__/regions.cpython-310.pyc 100644 root:root 076f8ba0267db39f3ec65803a8deed28 File: /usr/lib/python3/site-packages/botocore/__pycache__/response.cpython-310.opt-1.pyc 100644 root:root 71951d0f332cc17387d1834a1dbb35b2 @@ -2262,11 +2262,11 @@ File: /usr/lib/python3/site-packages/botocore/__pycache__/retryhandler.cpython-310.pyc 100644 root:root b39df4dd06852fad6e6e6c965ec7bfc8 -File: /usr/lib/python3/site-packages/botocore/__pycache__/serialize.cpython-310.opt-1.pyc 100644 root:root f62c06ff0b3e8a4245fb0ac8a9269a2e -File: /usr/lib/python3/site-packages/botocore/__pycache__/serialize.cpython-310.opt-2.pyc 100644 root:root 66aa9267c76c7dee1ebbbb15150768b9 -File: /usr/lib/python3/site-packages/botocore/__pycache__/serialize.cpython-310.pyc 100644 root:root f62c06ff0b3e8a4245fb0ac8a9269a2e -File: /usr/lib/python3/site-packages/botocore/__pycache__/session.cpython-310.opt-1.pyc 100644 root:root f27d283a6d347a14c38941f94db424b6 -File: /usr/lib/python3/site-packages/botocore/__pycache__/session.cpython-310.opt-2.pyc 100644 root:root 0f2ecff4344dcdca10d9abb75f58c22c -File: /usr/lib/python3/site-packages/botocore/__pycache__/session.cpython-310.pyc 100644 root:root f27d283a6d347a14c38941f94db424b6 -File: /usr/lib/python3/site-packages/botocore/__pycache__/signers.cpython-310.opt-1.pyc 100644 root:root 1ae02dd392d320de37ac54352f3f0064 -File: /usr/lib/python3/site-packages/botocore/__pycache__/signers.cpython-310.opt-2.pyc 100644 root:root c9b3affd1d9f79586853191d6ec5261e -File: /usr/lib/python3/site-packages/botocore/__pycache__/signers.cpython-310.pyc 100644 root:root 1ae02dd392d320de37ac54352f3f0064 +File: /usr/lib/python3/site-packages/botocore/__pycache__/serialize.cpython-310.opt-1.pyc 100644 root:root 39c84e84e44dcf3f0a3cad3725abeff9 +File: /usr/lib/python3/site-packages/botocore/__pycache__/serialize.cpython-310.opt-2.pyc 100644 root:root 5f669756fc648cf9d2654ebe4d98b52a +File: /usr/lib/python3/site-packages/botocore/__pycache__/serialize.cpython-310.pyc 100644 root:root 39c84e84e44dcf3f0a3cad3725abeff9 +File: /usr/lib/python3/site-packages/botocore/__pycache__/session.cpython-310.opt-1.pyc 100644 root:root 35514885fd02a86beedead2f415dec8b +File: /usr/lib/python3/site-packages/botocore/__pycache__/session.cpython-310.opt-2.pyc 100644 root:root 96fae0f6ef965cb709080045f3c404ce +File: /usr/lib/python3/site-packages/botocore/__pycache__/session.cpython-310.pyc 100644 root:root 35514885fd02a86beedead2f415dec8b +File: /usr/lib/python3/site-packages/botocore/__pycache__/signers.cpython-310.opt-1.pyc 100644 root:root 929e508c0b3c14efd733bd38650154ca +File: /usr/lib/python3/site-packages/botocore/__pycache__/signers.cpython-310.opt-2.pyc 100644 root:root b516f0fbcf6767efd3e06bf7231b7e9b +File: /usr/lib/python3/site-packages/botocore/__pycache__/signers.cpython-310.pyc 100644 root:root 929e508c0b3c14efd733bd38650154ca File: /usr/lib/python3/site-packages/botocore/__pycache__/stub.cpython-310.opt-1.pyc 100644 root:root 67cdc8f84d89bd4c5d657b631b211055 @@ -2280,5 +2280,5 @@ File: /usr/lib/python3/site-packages/botocore/__pycache__/translate.cpython-310.pyc 100644 root:root a225b84de0d8c939b98536ba810bf334 -File: /usr/lib/python3/site-packages/botocore/__pycache__/utils.cpython-310.opt-1.pyc 100644 root:root 1d0c8bfc798f2b3b8210df7eba88d5e9 -File: /usr/lib/python3/site-packages/botocore/__pycache__/utils.cpython-310.opt-2.pyc 100644 root:root c2e4b70137535f87df84f5b1218a6b31 -File: /usr/lib/python3/site-packages/botocore/__pycache__/utils.cpython-310.pyc 100644 root:root 3249bd985e0f1d134d14bbf398036b26 +File: /usr/lib/python3/site-packages/botocore/__pycache__/utils.cpython-310.opt-1.pyc 100644 root:root 93ef7c3044db4227261cd9a536ec39ad +File: /usr/lib/python3/site-packages/botocore/__pycache__/utils.cpython-310.opt-2.pyc 100644 root:root 10f9d5631fbb288af8ea1290104dd5d4 +File: /usr/lib/python3/site-packages/botocore/__pycache__/utils.cpython-310.pyc 100644 root:root e50696afad750ec793dcc26fd2dc0bbd File: /usr/lib/python3/site-packages/botocore/__pycache__/validate.cpython-310.opt-1.pyc 100644 root:root 0c6f93535d55b287c6fd81b42be47181 @@ -2304,5 +2304,5 @@ File: /usr/lib/python3/site-packages/botocore/crt/__pycache__/__init__.cpython-310.pyc 100644 root:root 4f7fd7d54d718fb1ff02e393272e3841 -File: /usr/lib/python3/site-packages/botocore/crt/__pycache__/auth.cpython-310.opt-1.pyc 100644 root:root 415430dc43acfe4f360f4339b2dfb785 -File: /usr/lib/python3/site-packages/botocore/crt/__pycache__/auth.cpython-310.opt-2.pyc 100644 root:root a55d2cf20109988162ba768bd7054773 -File: /usr/lib/python3/site-packages/botocore/crt/__pycache__/auth.cpython-310.pyc 100644 root:root 415430dc43acfe4f360f4339b2dfb785 +File: /usr/lib/python3/site-packages/botocore/crt/__pycache__/auth.cpython-310.opt-1.pyc 100644 root:root 9ca618b0eec54a48b4a8438dac969296 +File: /usr/lib/python3/site-packages/botocore/crt/__pycache__/auth.cpython-310.opt-2.pyc 100644 root:root fed2a8427ebd312798c6059cc91ce49b +File: /usr/lib/python3/site-packages/botocore/crt/__pycache__/auth.cpython-310.pyc 100644 root:root 9ca618b0eec54a48b4a8438dac969296 File: /usr/lib/python3/site-packages/botocore/crt/auth.py 100644 root:root a79305fdd3f6c38b8af0a4f7f1aede39 @@ -4086,5 +4086,5 @@ File: /usr/lib/python3/site-packages/botocore/docs/__pycache__/docstring.cpython-310.pyc 100644 root:root a56e8d740467e8179c81211ca01eee14 -File: /usr/lib/python3/site-packages/botocore/docs/__pycache__/example.cpython-310.opt-1.pyc 100644 root:root 322d4188f6fd73f4214eaec65bfc85d9 -File: /usr/lib/python3/site-packages/botocore/docs/__pycache__/example.cpython-310.opt-2.pyc 100644 root:root 7b7b0c9ce3b76955c4bb832fa60cfa0f -File: /usr/lib/python3/site-packages/botocore/docs/__pycache__/example.cpython-310.pyc 100644 root:root 322d4188f6fd73f4214eaec65bfc85d9 +File: /usr/lib/python3/site-packages/botocore/docs/__pycache__/example.cpython-310.opt-1.pyc 100644 root:root 10d74b63cae42fb0fc76df619a7f645a +File: /usr/lib/python3/site-packages/botocore/docs/__pycache__/example.cpython-310.opt-2.pyc 100644 root:root 4450a2799b997ae716e188d0c56ab3f1 +File: /usr/lib/python3/site-packages/botocore/docs/__pycache__/example.cpython-310.pyc 100644 root:root 10d74b63cae42fb0fc76df619a7f645a File: /usr/lib/python3/site-packages/botocore/docs/__pycache__/method.cpython-310.opt-1.pyc 100644 root:root d24f5b837765cea5ea32d812d97442af @@ -4104,5 +4104,5 @@ File: /usr/lib/python3/site-packages/botocore/docs/__pycache__/shape.cpython-310.pyc 100644 root:root eac3677dbb0abeeb7238356ddd0a098f -File: /usr/lib/python3/site-packages/botocore/docs/__pycache__/sharedexample.cpython-310.opt-1.pyc 100644 root:root 631998adaa6a969bc65effa30bfa14ee -File: /usr/lib/python3/site-packages/botocore/docs/__pycache__/sharedexample.cpython-310.opt-2.pyc 100644 root:root d2886d65c4e15c70f5ffe4b9f157b5b7 -File: /usr/lib/python3/site-packages/botocore/docs/__pycache__/sharedexample.cpython-310.pyc 100644 root:root 631998adaa6a969bc65effa30bfa14ee +File: /usr/lib/python3/site-packages/botocore/docs/__pycache__/sharedexample.cpython-310.opt-1.pyc 100644 root:root 5ff27fe7033b4d1d35ee7b538396a163 +File: /usr/lib/python3/site-packages/botocore/docs/__pycache__/sharedexample.cpython-310.opt-2.pyc 100644 root:root 29913dcc0557234d580ac132a9803b0d +File: /usr/lib/python3/site-packages/botocore/docs/__pycache__/sharedexample.cpython-310.pyc 100644 root:root 5ff27fe7033b4d1d35ee7b538396a163 File: /usr/lib/python3/site-packages/botocore/docs/__pycache__/utils.cpython-310.opt-1.pyc 100644 root:root d3504587836793c8f8dad49bbbf8cc10 @@ -4180,5 +4180,5 @@ File: /usr/lib/python3/site-packages/botocore/retries/__pycache__/special.cpython-310.pyc 100644 root:root 159168713d29bf3075da248babd5597b -File: /usr/lib/python3/site-packages/botocore/retries/__pycache__/standard.cpython-310.opt-1.pyc 100644 root:root c5117e267d3bdc879093acaf505dcbb6 -File: /usr/lib/python3/site-packages/botocore/retries/__pycache__/standard.cpython-310.opt-2.pyc 100644 root:root 67a22e72778b17f36625debadff6be0b -File: /usr/lib/python3/site-packages/botocore/retries/__pycache__/standard.cpython-310.pyc 100644 root:root c5117e267d3bdc879093acaf505dcbb6 +File: /usr/lib/python3/site-packages/botocore/retries/__pycache__/standard.cpython-310.opt-1.pyc 100644 root:root f8db654f73bac66d681f58752cecbf5a +File: /usr/lib/python3/site-packages/botocore/retries/__pycache__/standard.cpython-310.opt-2.pyc 100644 root:root 98306bc192d6ed2b5e5c70cab231c578 +File: /usr/lib/python3/site-packages/botocore/retries/__pycache__/standard.cpython-310.pyc 100644 root:root f8db654f73bac66d681f58752cecbf5a File: /usr/lib/python3/site-packages/botocore/retries/__pycache__/throttling.cpython-310.opt-1.pyc 100644 root:root 275726bd996d2347d75e8fb0efbcecf5 @@ -4214,2 +4214,2 @@ File: /usr/share/doc/python3-module-botocore-1.27.90/README.rst 100644 root:root 19f0559f360ce61645714499b0871ef9 -RPMIdentity: 5bb28da1163d44e3f36e4a8fb3e148f608a114a33e047b35a9d993ed33986a1cde9b07616a356f708b64daf77c957bad245a431d0febba0944102a132da9039e +RPMIdentity: 15178acc95ce5270fd4b6f0c4cdfcc0bfd74fa8303fb907e56226114c813313735eef9a0c9baa637198ee7863ff85b5faffced7433577f9b1a6b1ebef833f070