Sourcing python-remove-tests-dir-hook Sourcing python-catch-conflicts-hook.sh Sourcing python-remove-bin-bytecode-hook.sh Sourcing pypa-build-hook Using pypaBuildPhase Sourcing python-runtime-deps-check-hook Using pythonRuntimeDepsCheckHook Sourcing pypa-install-hook Using pypaInstallPhase Sourcing python-imports-check-hook.sh Using pythonImportsCheckPhase Sourcing python-namespaces-hook Sourcing python-catch-conflicts-hook.sh Sourcing pytest-check-hook Using pytestCheckPhase Running phase: unpackPhase unpacking source archive /nix/store/kcy1qzpzbcmdiqpay5vhh23r5742yfks-source source root is source setting SOURCE_DATE_EPOCH to timestamp 315619200 of file "source/tox.ini" Running phase: patchPhase Running phase: updateAutotoolsGnuConfigScriptsPhase Running phase: configurePhase no configure script, doing nothing Running phase: buildPhase Executing pypaBuildPhase Creating a wheel... pypa build flags: --no-isolation --outdir dist/ --wheel * Getting build dependencies for wheel... /nix/store/5ipvqipbr52zh1mh0jq7agixgd4c4432-python3.13-setuptools-80.9.0/lib/python3.13/site-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: Apache Software License See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() running egg_info creating boto3.egg-info writing boto3.egg-info/PKG-INFO writing dependency_links to boto3.egg-info/dependency_links.txt writing requirements to boto3.egg-info/requires.txt writing top-level names to boto3.egg-info/top_level.txt writing manifest file 'boto3.egg-info/SOURCES.txt' reading manifest file 'boto3.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' adding license file 'NOTICE' writing manifest file 'boto3.egg-info/SOURCES.txt' * Building wheel... /nix/store/5ipvqipbr52zh1mh0jq7agixgd4c4432-python3.13-setuptools-80.9.0/lib/python3.13/site-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: Apache Software License See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() running bdist_wheel running build running build_py creating build/lib/boto3 copying boto3/session.py -> build/lib/boto3 copying boto3/__init__.py -> build/lib/boto3 copying boto3/compat.py -> build/lib/boto3 copying boto3/crt.py -> build/lib/boto3 copying boto3/exceptions.py -> build/lib/boto3 copying boto3/utils.py -> build/lib/boto3 creating build/lib/boto3/ec2 copying boto3/ec2/__init__.py -> build/lib/boto3/ec2 copying boto3/ec2/createtags.py -> build/lib/boto3/ec2 copying boto3/ec2/deletetags.py -> build/lib/boto3/ec2 creating build/lib/boto3/resources copying boto3/resources/base.py -> build/lib/boto3/resources copying boto3/resources/__init__.py -> build/lib/boto3/resources copying boto3/resources/model.py -> build/lib/boto3/resources copying boto3/resources/params.py -> build/lib/boto3/resources copying boto3/resources/response.py -> build/lib/boto3/resources copying boto3/resources/collection.py -> build/lib/boto3/resources copying boto3/resources/action.py -> build/lib/boto3/resources copying boto3/resources/factory.py -> build/lib/boto3/resources creating build/lib/boto3/s3 copying boto3/s3/__init__.py -> build/lib/boto3/s3 copying boto3/s3/inject.py -> build/lib/boto3/s3 copying boto3/s3/constants.py -> build/lib/boto3/s3 copying boto3/s3/transfer.py -> build/lib/boto3/s3 creating build/lib/boto3/dynamodb copying boto3/dynamodb/__init__.py -> build/lib/boto3/dynamodb copying boto3/dynamodb/types.py -> build/lib/boto3/dynamodb copying boto3/dynamodb/table.py -> build/lib/boto3/dynamodb copying boto3/dynamodb/conditions.py -> build/lib/boto3/dynamodb copying boto3/dynamodb/transform.py -> build/lib/boto3/dynamodb creating build/lib/boto3/docs copying boto3/docs/base.py -> build/lib/boto3/docs copying boto3/docs/__init__.py -> build/lib/boto3/docs copying boto3/docs/resource.py -> build/lib/boto3/docs copying boto3/docs/subresource.py -> build/lib/boto3/docs copying boto3/docs/client.py -> build/lib/boto3/docs copying boto3/docs/docstring.py -> build/lib/boto3/docs copying boto3/docs/method.py -> build/lib/boto3/docs copying boto3/docs/service.py -> build/lib/boto3/docs copying boto3/docs/collection.py -> build/lib/boto3/docs copying boto3/docs/attr.py -> build/lib/boto3/docs copying boto3/docs/waiter.py -> build/lib/boto3/docs copying boto3/docs/action.py -> build/lib/boto3/docs copying boto3/docs/utils.py -> build/lib/boto3/docs running egg_info writing boto3.egg-info/PKG-INFO writing dependency_links to boto3.egg-info/dependency_links.txt writing requirements to boto3.egg-info/requires.txt writing top-level names to boto3.egg-info/top_level.txt reading manifest file 'boto3.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' adding license file 'NOTICE' writing manifest file 'boto3.egg-info/SOURCES.txt' /nix/store/5ipvqipbr52zh1mh0jq7agixgd4c4432-python3.13-setuptools-80.9.0/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.data.cloudformation' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'boto3.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 'boto3.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 'boto3.data.cloudformation' to be distributed and are already explicitly excluding 'boto3.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) /nix/store/5ipvqipbr52zh1mh0jq7agixgd4c4432-python3.13-setuptools-80.9.0/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.data.cloudwatch' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'boto3.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 'boto3.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 'boto3.data.cloudwatch' to be distributed and are already explicitly excluding 'boto3.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) /nix/store/5ipvqipbr52zh1mh0jq7agixgd4c4432-python3.13-setuptools-80.9.0/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.data.dynamodb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'boto3.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 'boto3.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 'boto3.data.dynamodb' to be distributed and are already explicitly excluding 'boto3.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) /nix/store/5ipvqipbr52zh1mh0jq7agixgd4c4432-python3.13-setuptools-80.9.0/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.data.ec2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'boto3.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 'boto3.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 'boto3.data.ec2' to be distributed and are already explicitly excluding 'boto3.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) /nix/store/5ipvqipbr52zh1mh0jq7agixgd4c4432-python3.13-setuptools-80.9.0/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.data.glacier' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'boto3.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 'boto3.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 'boto3.data.glacier' to be distributed and are already explicitly excluding 'boto3.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) /nix/store/5ipvqipbr52zh1mh0jq7agixgd4c4432-python3.13-setuptools-80.9.0/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.data.iam' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'boto3.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 'boto3.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 'boto3.data.iam' to be distributed and are already explicitly excluding 'boto3.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) /nix/store/5ipvqipbr52zh1mh0jq7agixgd4c4432-python3.13-setuptools-80.9.0/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.data.opsworks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'boto3.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 'boto3.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 'boto3.data.opsworks' to be distributed and are already explicitly excluding 'boto3.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) /nix/store/5ipvqipbr52zh1mh0jq7agixgd4c4432-python3.13-setuptools-80.9.0/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.data.s3' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'boto3.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 'boto3.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 'boto3.data.s3' to be distributed and are already explicitly excluding 'boto3.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) /nix/store/5ipvqipbr52zh1mh0jq7agixgd4c4432-python3.13-setuptools-80.9.0/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.data.sns' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'boto3.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 'boto3.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 'boto3.data.sns' to be distributed and are already explicitly excluding 'boto3.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) /nix/store/5ipvqipbr52zh1mh0jq7agixgd4c4432-python3.13-setuptools-80.9.0/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.data.sqs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'boto3.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 'boto3.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 'boto3.data.sqs' to be distributed and are already explicitly excluding 'boto3.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) /nix/store/5ipvqipbr52zh1mh0jq7agixgd4c4432-python3.13-setuptools-80.9.0/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.examples' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'boto3.examples' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'boto3.examples' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'boto3.examples' to be distributed and are already explicitly excluding 'boto3.examples' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) creating build/lib/boto3/data/cloudformation/2010-05-15 copying boto3/data/cloudformation/2010-05-15/resources-1.json -> build/lib/boto3/data/cloudformation/2010-05-15 creating build/lib/boto3/data/cloudwatch/2010-08-01 copying boto3/data/cloudwatch/2010-08-01/resources-1.json -> build/lib/boto3/data/cloudwatch/2010-08-01 creating build/lib/boto3/data/dynamodb/2012-08-10 copying boto3/data/dynamodb/2012-08-10/resources-1.json -> build/lib/boto3/data/dynamodb/2012-08-10 creating build/lib/boto3/data/ec2/2014-10-01 copying boto3/data/ec2/2014-10-01/resources-1.json -> build/lib/boto3/data/ec2/2014-10-01 creating build/lib/boto3/data/ec2/2015-03-01 copying boto3/data/ec2/2015-03-01/resources-1.json -> build/lib/boto3/data/ec2/2015-03-01 creating build/lib/boto3/data/ec2/2015-04-15 copying boto3/data/ec2/2015-04-15/resources-1.json -> build/lib/boto3/data/ec2/2015-04-15 creating build/lib/boto3/data/ec2/2015-10-01 copying boto3/data/ec2/2015-10-01/resources-1.json -> build/lib/boto3/data/ec2/2015-10-01 creating build/lib/boto3/data/ec2/2016-04-01 copying boto3/data/ec2/2016-04-01/resources-1.json -> build/lib/boto3/data/ec2/2016-04-01 creating build/lib/boto3/data/ec2/2016-09-15 copying boto3/data/ec2/2016-09-15/resources-1.json -> build/lib/boto3/data/ec2/2016-09-15 creating build/lib/boto3/data/ec2/2016-11-15 copying boto3/data/ec2/2016-11-15/resources-1.json -> build/lib/boto3/data/ec2/2016-11-15 creating build/lib/boto3/data/glacier/2012-06-01 copying boto3/data/glacier/2012-06-01/resources-1.json -> build/lib/boto3/data/glacier/2012-06-01 creating build/lib/boto3/data/iam/2010-05-08 copying boto3/data/iam/2010-05-08/resources-1.json -> build/lib/boto3/data/iam/2010-05-08 creating build/lib/boto3/data/opsworks/2013-02-18 copying boto3/data/opsworks/2013-02-18/resources-1.json -> build/lib/boto3/data/opsworks/2013-02-18 creating build/lib/boto3/data/s3/2006-03-01 copying boto3/data/s3/2006-03-01/resources-1.json -> build/lib/boto3/data/s3/2006-03-01 creating build/lib/boto3/data/sns/2010-03-31 copying boto3/data/sns/2010-03-31/resources-1.json -> build/lib/boto3/data/sns/2010-03-31 creating build/lib/boto3/data/sqs/2012-11-05 copying boto3/data/sqs/2012-11-05/resources-1.json -> build/lib/boto3/data/sqs/2012-11-05 creating build/lib/boto3/examples copying boto3/examples/cloudfront.rst -> build/lib/boto3/examples copying boto3/examples/s3.rst -> build/lib/boto3/examples installing to build/bdist.linux-x86_64/wheel running install running install_lib creating build/bdist.linux-x86_64/wheel creating build/bdist.linux-x86_64/wheel/boto3 creating build/bdist.linux-x86_64/wheel/boto3/ec2 copying build/lib/boto3/ec2/__init__.py -> build/bdist.linux-x86_64/wheel/./boto3/ec2 copying build/lib/boto3/ec2/createtags.py -> build/bdist.linux-x86_64/wheel/./boto3/ec2 copying build/lib/boto3/ec2/deletetags.py -> build/bdist.linux-x86_64/wheel/./boto3/ec2 copying build/lib/boto3/session.py -> build/bdist.linux-x86_64/wheel/./boto3 copying build/lib/boto3/__init__.py -> build/bdist.linux-x86_64/wheel/./boto3 creating build/bdist.linux-x86_64/wheel/boto3/data creating build/bdist.linux-x86_64/wheel/boto3/data/cloudwatch creating build/bdist.linux-x86_64/wheel/boto3/data/cloudwatch/2010-08-01 copying build/lib/boto3/data/cloudwatch/2010-08-01/resources-1.json -> build/bdist.linux-x86_64/wheel/./boto3/data/cloudwatch/2010-08-01 creating build/bdist.linux-x86_64/wheel/boto3/data/ec2 creating build/bdist.linux-x86_64/wheel/boto3/data/ec2/2014-10-01 copying build/lib/boto3/data/ec2/2014-10-01/resources-1.json -> build/bdist.linux-x86_64/wheel/./boto3/data/ec2/2014-10-01 creating build/bdist.linux-x86_64/wheel/boto3/data/ec2/2015-04-15 copying build/lib/boto3/data/ec2/2015-04-15/resources-1.json -> build/bdist.linux-x86_64/wheel/./boto3/data/ec2/2015-04-15 creating build/bdist.linux-x86_64/wheel/boto3/data/ec2/2015-10-01 copying build/lib/boto3/data/ec2/2015-10-01/resources-1.json -> build/bdist.linux-x86_64/wheel/./boto3/data/ec2/2015-10-01 creating build/bdist.linux-x86_64/wheel/boto3/data/ec2/2016-09-15 copying build/lib/boto3/data/ec2/2016-09-15/resources-1.json -> build/bdist.linux-x86_64/wheel/./boto3/data/ec2/2016-09-15 creating build/bdist.linux-x86_64/wheel/boto3/data/ec2/2016-11-15 copying build/lib/boto3/data/ec2/2016-11-15/resources-1.json -> build/bdist.linux-x86_64/wheel/./boto3/data/ec2/2016-11-15 creating build/bdist.linux-x86_64/wheel/boto3/data/ec2/2015-03-01 copying build/lib/boto3/data/ec2/2015-03-01/resources-1.json -> build/bdist.linux-x86_64/wheel/./boto3/data/ec2/2015-03-01 creating build/bdist.linux-x86_64/wheel/boto3/data/ec2/2016-04-01 copying build/lib/boto3/data/ec2/2016-04-01/resources-1.json -> build/bdist.linux-x86_64/wheel/./boto3/data/ec2/2016-04-01 creating build/bdist.linux-x86_64/wheel/boto3/data/glacier creating build/bdist.linux-x86_64/wheel/boto3/data/glacier/2012-06-01 copying build/lib/boto3/data/glacier/2012-06-01/resources-1.json -> build/bdist.linux-x86_64/wheel/./boto3/data/glacier/2012-06-01 creating build/bdist.linux-x86_64/wheel/boto3/data/cloudformation creating build/bdist.linux-x86_64/wheel/boto3/data/cloudformation/2010-05-15 copying build/lib/boto3/data/cloudformation/2010-05-15/resources-1.json -> build/bdist.linux-x86_64/wheel/./boto3/data/cloudformation/2010-05-15 creating build/bdist.linux-x86_64/wheel/boto3/data/sqs creating build/bdist.linux-x86_64/wheel/boto3/data/sqs/2012-11-05 copying build/lib/boto3/data/sqs/2012-11-05/resources-1.json -> build/bdist.linux-x86_64/wheel/./boto3/data/sqs/2012-11-05 creating build/bdist.linux-x86_64/wheel/boto3/data/iam creating build/bdist.linux-x86_64/wheel/boto3/data/iam/2010-05-08 copying build/lib/boto3/data/iam/2010-05-08/resources-1.json -> build/bdist.linux-x86_64/wheel/./boto3/data/iam/2010-05-08 creating build/bdist.linux-x86_64/wheel/boto3/data/sns creating build/bdist.linux-x86_64/wheel/boto3/data/sns/2010-03-31 copying build/lib/boto3/data/sns/2010-03-31/resources-1.json -> build/bdist.linux-x86_64/wheel/./boto3/data/sns/2010-03-31 creating build/bdist.linux-x86_64/wheel/boto3/data/s3 creating build/bdist.linux-x86_64/wheel/boto3/data/s3/2006-03-01 copying build/lib/boto3/data/s3/2006-03-01/resources-1.json -> build/bdist.linux-x86_64/wheel/./boto3/data/s3/2006-03-01 creating build/bdist.linux-x86_64/wheel/boto3/data/opsworks creating build/bdist.linux-x86_64/wheel/boto3/data/opsworks/2013-02-18 copying build/lib/boto3/data/opsworks/2013-02-18/resources-1.json -> build/bdist.linux-x86_64/wheel/./boto3/data/opsworks/2013-02-18 creating build/bdist.linux-x86_64/wheel/boto3/data/dynamodb creating build/bdist.linux-x86_64/wheel/boto3/data/dynamodb/2012-08-10 copying build/lib/boto3/data/dynamodb/2012-08-10/resources-1.json -> build/bdist.linux-x86_64/wheel/./boto3/data/dynamodb/2012-08-10 copying build/lib/boto3/compat.py -> build/bdist.linux-x86_64/wheel/./boto3 creating build/bdist.linux-x86_64/wheel/boto3/examples copying build/lib/boto3/examples/s3.rst -> build/bdist.linux-x86_64/wheel/./boto3/examples copying build/lib/boto3/examples/cloudfront.rst -> build/bdist.linux-x86_64/wheel/./boto3/examples copying build/lib/boto3/crt.py -> build/bdist.linux-x86_64/wheel/./boto3 creating build/bdist.linux-x86_64/wheel/boto3/resources copying build/lib/boto3/resources/base.py -> build/bdist.linux-x86_64/wheel/./boto3/resources copying build/lib/boto3/resources/__init__.py -> build/bdist.linux-x86_64/wheel/./boto3/resources copying build/lib/boto3/resources/model.py -> build/bdist.linux-x86_64/wheel/./boto3/resources copying build/lib/boto3/resources/params.py -> build/bdist.linux-x86_64/wheel/./boto3/resources copying build/lib/boto3/resources/response.py -> build/bdist.linux-x86_64/wheel/./boto3/resources copying build/lib/boto3/resources/collection.py -> build/bdist.linux-x86_64/wheel/./boto3/resources copying build/lib/boto3/resources/action.py -> build/bdist.linux-x86_64/wheel/./boto3/resources copying build/lib/boto3/resources/factory.py -> build/bdist.linux-x86_64/wheel/./boto3/resources creating build/bdist.linux-x86_64/wheel/boto3/s3 copying build/lib/boto3/s3/__init__.py -> build/bdist.linux-x86_64/wheel/./boto3/s3 copying build/lib/boto3/s3/inject.py -> build/bdist.linux-x86_64/wheel/./boto3/s3 copying build/lib/boto3/s3/constants.py -> build/bdist.linux-x86_64/wheel/./boto3/s3 copying build/lib/boto3/s3/transfer.py -> build/bdist.linux-x86_64/wheel/./boto3/s3 copying build/lib/boto3/exceptions.py -> build/bdist.linux-x86_64/wheel/./boto3 creating build/bdist.linux-x86_64/wheel/boto3/dynamodb copying build/lib/boto3/dynamodb/__init__.py -> build/bdist.linux-x86_64/wheel/./boto3/dynamodb copying build/lib/boto3/dynamodb/types.py -> build/bdist.linux-x86_64/wheel/./boto3/dynamodb copying build/lib/boto3/dynamodb/table.py -> build/bdist.linux-x86_64/wheel/./boto3/dynamodb copying build/lib/boto3/dynamodb/conditions.py -> build/bdist.linux-x86_64/wheel/./boto3/dynamodb copying build/lib/boto3/dynamodb/transform.py -> build/bdist.linux-x86_64/wheel/./boto3/dynamodb copying build/lib/boto3/utils.py -> build/bdist.linux-x86_64/wheel/./boto3 creating build/bdist.linux-x86_64/wheel/boto3/docs copying build/lib/boto3/docs/base.py -> build/bdist.linux-x86_64/wheel/./boto3/docs copying build/lib/boto3/docs/__init__.py -> build/bdist.linux-x86_64/wheel/./boto3/docs copying build/lib/boto3/docs/resource.py -> build/bdist.linux-x86_64/wheel/./boto3/docs copying build/lib/boto3/docs/subresource.py -> build/bdist.linux-x86_64/wheel/./boto3/docs copying build/lib/boto3/docs/client.py -> build/bdist.linux-x86_64/wheel/./boto3/docs copying build/lib/boto3/docs/docstring.py -> build/bdist.linux-x86_64/wheel/./boto3/docs copying build/lib/boto3/docs/method.py -> build/bdist.linux-x86_64/wheel/./boto3/docs copying build/lib/boto3/docs/service.py -> build/bdist.linux-x86_64/wheel/./boto3/docs copying build/lib/boto3/docs/collection.py -> build/bdist.linux-x86_64/wheel/./boto3/docs copying build/lib/boto3/docs/attr.py -> build/bdist.linux-x86_64/wheel/./boto3/docs copying build/lib/boto3/docs/waiter.py -> build/bdist.linux-x86_64/wheel/./boto3/docs copying build/lib/boto3/docs/action.py -> build/bdist.linux-x86_64/wheel/./boto3/docs copying build/lib/boto3/docs/utils.py -> build/bdist.linux-x86_64/wheel/./boto3/docs running install_egg_info Copying boto3.egg-info to build/bdist.linux-x86_64/wheel/./boto3-1.40.18-py3.13.egg-info running install_scripts creating build/bdist.linux-x86_64/wheel/boto3-1.40.18.dist-info/WHEEL creating '/build/source/dist/.tmp-avepud_f/boto3-1.40.18-py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it adding 'boto3/__init__.py' adding 'boto3/compat.py' adding 'boto3/crt.py' adding 'boto3/exceptions.py' adding 'boto3/session.py' adding 'boto3/utils.py' adding 'boto3/data/cloudformation/2010-05-15/resources-1.json' adding 'boto3/data/cloudwatch/2010-08-01/resources-1.json' adding 'boto3/data/dynamodb/2012-08-10/resources-1.json' adding 'boto3/data/ec2/2014-10-01/resources-1.json' adding 'boto3/data/ec2/2015-03-01/resources-1.json' adding 'boto3/data/ec2/2015-04-15/resources-1.json' adding 'boto3/data/ec2/2015-10-01/resources-1.json' adding 'boto3/data/ec2/2016-04-01/resources-1.json' adding 'boto3/data/ec2/2016-09-15/resources-1.json' adding 'boto3/data/ec2/2016-11-15/resources-1.json' adding 'boto3/data/glacier/2012-06-01/resources-1.json' adding 'boto3/data/iam/2010-05-08/resources-1.json' adding 'boto3/data/opsworks/2013-02-18/resources-1.json' adding 'boto3/data/s3/2006-03-01/resources-1.json' adding 'boto3/data/sns/2010-03-31/resources-1.json' adding 'boto3/data/sqs/2012-11-05/resources-1.json' adding 'boto3/docs/__init__.py' adding 'boto3/docs/action.py' adding 'boto3/docs/attr.py' adding 'boto3/docs/base.py' adding 'boto3/docs/client.py' adding 'boto3/docs/collection.py' adding 'boto3/docs/docstring.py' adding 'boto3/docs/method.py' adding 'boto3/docs/resource.py' adding 'boto3/docs/service.py' adding 'boto3/docs/subresource.py' adding 'boto3/docs/utils.py' adding 'boto3/docs/waiter.py' adding 'boto3/dynamodb/__init__.py' adding 'boto3/dynamodb/conditions.py' adding 'boto3/dynamodb/table.py' adding 'boto3/dynamodb/transform.py' adding 'boto3/dynamodb/types.py' adding 'boto3/ec2/__init__.py' adding 'boto3/ec2/createtags.py' adding 'boto3/ec2/deletetags.py' adding 'boto3/examples/cloudfront.rst' adding 'boto3/examples/s3.rst' adding 'boto3/resources/__init__.py' adding 'boto3/resources/action.py' adding 'boto3/resources/base.py' adding 'boto3/resources/collection.py' adding 'boto3/resources/factory.py' adding 'boto3/resources/model.py' adding 'boto3/resources/params.py' adding 'boto3/resources/response.py' adding 'boto3/s3/__init__.py' adding 'boto3/s3/constants.py' adding 'boto3/s3/inject.py' adding 'boto3/s3/transfer.py' adding 'boto3-1.40.18.dist-info/licenses/LICENSE' adding 'boto3-1.40.18.dist-info/licenses/NOTICE' adding 'boto3-1.40.18.dist-info/METADATA' adding 'boto3-1.40.18.dist-info/WHEEL' adding 'boto3-1.40.18.dist-info/top_level.txt' adding 'boto3-1.40.18.dist-info/RECORD' removing build/bdist.linux-x86_64/wheel Successfully built boto3-1.40.18-py3-none-any.whl Finished creating a wheel... Finished executing pypaBuildPhase Running phase: pythonRuntimeDepsCheckHook Executing pythonRuntimeDepsCheck Checking runtime dependencies for boto3-1.40.18-py3-none-any.whl Finished executing pythonRuntimeDepsCheck Running phase: installPhase Executing pypaInstallPhase Successfully installed boto3-1.40.18-py3-none-any.whl Finished executing pypaInstallPhase Running phase: pythonOutputDistPhase Executing pythonOutputDistPhase Finished executing pythonOutputDistPhase Running phase: fixupPhase shrinking RPATHs of ELF executables and libraries in /nix/store/jbh077bh8lf8mb4450d3fy4wrb493sxq-python3.13-boto3-1.40.18 checking for references to /build/ in /nix/store/jbh077bh8lf8mb4450d3fy4wrb493sxq-python3.13-boto3-1.40.18... patching script interpreter paths in /nix/store/jbh077bh8lf8mb4450d3fy4wrb493sxq-python3.13-boto3-1.40.18 stripping (with command strip and flags -S -p) in /nix/store/jbh077bh8lf8mb4450d3fy4wrb493sxq-python3.13-boto3-1.40.18/lib shrinking RPATHs of ELF executables and libraries in /nix/store/ajsa56a5warybn4x3xj6qqdv372jsh6a-python3.13-boto3-1.40.18-dist checking for references to /build/ in /nix/store/ajsa56a5warybn4x3xj6qqdv372jsh6a-python3.13-boto3-1.40.18-dist... patching script interpreter paths in /nix/store/ajsa56a5warybn4x3xj6qqdv372jsh6a-python3.13-boto3-1.40.18-dist Executing pythonRemoveTestsDir Finished executing pythonRemoveTestsDir Running phase: installCheckPhase no Makefile or custom installCheckPhase, doing nothing Running phase: pythonCatchConflictsPhase Running phase: pythonRemoveBinBytecodePhase Running phase: pythonImportsCheckPhase Executing pythonImportsCheckPhase Check whether the following modules can be imported: boto3 Running phase: pytestCheckPhase Executing pytestCheckPhase pytest flags: -m pytest --ignore-glob=tests/integration --numprocesses=4 ============================= test session starts ============================== platform linux -- Python 3.13.11, pytest-8.4.2, pluggy-1.6.0 rootdir: /build/source configfile: pyproject.toml plugins: xdist-3.8.0 4 workers [1454 items] ........................................................................ [ 4%] ........................................................................ [ 9%] ........................................................................ [ 14%] ........................................................................ [ 19%] ........................................................................ [ 24%] ........................................................................ [ 29%] ........................................................................ [ 34%] ........................................................................ [ 39%] ........................................................................ [ 44%] ........................................................................ [ 49%] ........................................................................ [ 54%] ........................................................................ [ 59%] ........................................................................ [ 64%] ........................................................................ [ 69%] ........................................................................ [ 74%] ........................................................................ [ 79%] ........................................................................ [ 84%] ............................sssssssssss................................. [ 89%] ....................................................ssssss.............. [ 94%] ........................................................................ [ 99%] .............. [100%] =============================== warnings summary =============================== tests/functional/docs/test_smoke.py::test_documentation[dynamodbstreams] /nix/store/36lgv9rjxg0cid2372rzk49p19f3826g-python3.13-python-dateutil-2.9.0.post0/lib/python3.13/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 =========== 1437 passed, 17 skipped, 1 warning in 166.27s (0:02:46) ============ Finished executing pytestCheckPhase pytestCheckPhase completed in 2 minutes 47 seconds Running phase: pytestcachePhase Running phase: pytestRemoveBytecodePhase