1.28.0: `build` warnings
Author: kloczekCreated Jul 7, 2023Updated Aug 22, 2026
Labelsbugp2
Describe the bug
On use pep517 based build procedure are printed some warnings
Expected Behavior
It should be no warnings.
Current Behavior
Here is build output:
+ /usr/bin/python3 -sBm build -w --no-isolation
* Getting build dependencies for wheel...
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...
running bdist_wheel
running build
running build_py
creating build
creating build/lib
creating build/lib/boto3
copying boto3/__init__.py -> build/lib/boto3
copying boto3/compat.py -> build/lib/boto3
copying boto3/exceptions.py -> build/lib/boto3
copying boto3/session.py -> build/lib/boto3
copying boto3/utils.py -> build/lib/boto3
creating build/lib/boto3/docs
copying boto3/docs/__init__.py -> build/lib/boto3/docs
copying boto3/docs/action.py -> build/lib/boto3/docs
copying boto3/docs/attr.py -> build/lib/boto3/docs
copying boto3/docs/base.py -> build/lib/boto3/docs
copying boto3/docs/client.py -> build/lib/boto3/docs
copying boto3/docs/collection.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/resource.py -> build/lib/boto3/docs
copying boto3/docs/service.py -> build/lib/boto3/docs
copying boto3/docs/subresource.py -> build/lib/boto3/docs
copying boto3/docs/utils.py -> build/lib/boto3/docs
copying boto3/docs/waiter.py -> build/lib/boto3/docs
creating build/lib/boto3/dynamodb
copying boto3/dynamodb/__init__.py -> build/lib/boto3/dynamodb
copying boto3/dynamodb/conditions.py -> build/lib/boto3/dynamodb
copying boto3/dynamodb/table.py -> build/lib/boto3/dynamodb
copying boto3/dynamodb/transform.py -> build/lib/boto3/dynamodb
copying boto3/dynamodb/types.py -> build/lib/boto3/dynamodb
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/__init__.py -> build/lib/boto3/resources
copying boto3/resources/action.py -> build/lib/boto3/resources
copying boto3/resources/base.py -> build/lib/boto3/resources
copying boto3/resources/collection.py -> build/lib/boto3/resources
copying boto3/resources/factory.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
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/transfer.py -> build/lib/boto3/s3
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'
/usr/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _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)
/usr/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _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)
/usr/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _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)
/usr/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _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)
/usr/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _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)
/usr/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _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)
/usr/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _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)
/usr/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _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.Source: boto/boto3