Closed kivengh closed 9 months ago
This is a packaging bug. What should be occurring is that the awscli
package has its own embedded botocore as awscli.botocore
, and a separate package providing botocore
for use by other packages.
A fix for this is in the works. We don't have an ETA for it, but it'll be included in an upcoming AL2023 release.
Embedding python modules inside other packages is nearly always a very, very bad idea. Please update them together but segregate them entirely.
@nkadel awscli upstream has essentially re-absorbed what amounts to a fork of botocore. This was an intentional decision by the CLI developers. The packaging issue here is that the cli declares a Provides: python3-botocore
, which is wrong. The solution will be to provide both botocore and boto3 as standalone packages, and fix the awscli package to drop the Provides
. The work on this is mostly done and I expect that it'll be included in the next scheduled AL2023 release.
Done as of the AL2023.3 release just published.
Describe the bug Python3 botocore module provided by awscli cannot be imported as module in system Python3.9.
To Reproduce Steps to reproduce the behavior:
dnf install python3-botocore
python3
>>> import botocore
>>> import botocore Traceback (most recent call last): File "<stdin>", line 1, in <module> ModuleNotFoundError: No module named 'botocore'
Expected behavior Botocore should be available for Python interpreter, as it is provided as a system package.
Additional context The botocore module is not installed in "/usr/lib/python3.9/site-packages", but in "/usr/lib/python3.9/site-packages/awscli".
It will be great if you can provide a separate package for python-botocore or make botocore accessible to system python.