-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
boto3-1.26.102 introduces import issue #3648
Comments
This is not closed, we merged a PR pinning our version to the old patch version. |
Hi @lmynsberge thanks for reaching out. Can you check which botocore version you're using? If you have botocore version 1.29.102 installed then you shouldn't get that error. The error message was recently added here to prevent deprecated service names from showing in the docs. |
With botocore 1.29.102 I am experiencing the same issue. |
@georgemansoor I'm not able to reproduce the issue. Can you confirm the botocore version imported in your script by adding: import botocore
print(botocore.__version__) If you're still seeing the issue can you share your debug logs by adding |
I'm having a similar issue. I think it stems from conflicts between boto3 and s3fs. If i install boto3 and s3fs serially with pip I get the same import error:
But if I install them simultaneously it works:
|
I took a look at s3fs, it relies on Until |
Yes, it works. |
Thanks for all the analysis and support y'all. I'm guessing I'm also hitting some sort of dependency combination issue. We're using a fresh install through a CircleCI Job. I can't reproduce locally at all. I don't see a dependency on s3fs or aiobotocore, so I'm not sure why. I leveraged Can anyone think of anything else that might be contributing to it?
|
@lmynsberge it looks like you are using |
I had similar import issue with latest version. It works . thanks! |
I am seeing this issue with |
@ksco92 are you also using a third-party software like s3fs? Are you using a Lambda layer and can you confirm that printing your botocore version as suggested here shows a version that is compatible with your version of boto3? |
any idea how can we fix this for python version 3.7 ? I tried all the above solutions but none worked for me |
how did you fix the issue ? |
…aneously Signed-off-by: Cuong Nguyen <can@anyscale.com>
- updated serverless, serverless-wsgi and serverless-python-requirements - move to python3.10 - pin boto3 and botcore to workaround boto/boto3#3648
@Bhawika16 Happened to me today with python3.7, fixed with |
This seems to work for me. Thanks! I was using botocore 1.29.103 before giving the same error. However downgrading botocore version to 1.29.102 seems to fix this issue. |
I hit this with a odd stack of dependencies:
I didn't dig into the exact versions but I did find that these 3 factors, in this order, triggered this issue. Installing So anyway heads up that package order may be a factor when installing from multiple sources, not just the packages themselves. |
It's completely nuts this isn't fixed yet. AWS isn't cheap! You guys can't get an engineer to fix a version conflict? This is how you lose a market. Just sharing my pinned versions in case it helps anyone.
|
Does anyone have a working combination of versions where botocore is more recent, like >=1.31.4? We need pyyaml 6.0.1, which requires awscli >= 1.29.4, which requires newer versions of botocore. Right now I have boto3 == 1.28.4 and botocore == 1.31.4, which look like they ought to be compatible according to their setup.py, but I'm getting the error described in this issue. Very annoying! |
Working config using Python 3.7 s3fs==2023.1.0 |
I just got this error using the version from the default runtime. Adding my own version of boto3 (1.28.64) to the package solved the problem. |
I had the same issue, but in my case was for a completely different reason.
Hope someone find this useful. |
This issue is now closed. Comments on closed issues are hard for our team to see. |
LAMBDA_WARNING: Unhandled exception. The most likely cause is an issue in the function code. However, in rare cases, a Lambda runtime update can cause unexpected function behavior. For functions using managed runtimes, runtime updates can be triggered by a function change, or can be applied automatically. To determine if the runtime has been updated, check the runtime version in the INIT_START log entry. If this error correlates with a change in the runtime version, you may be able to mitigate this error by temporarily rolling back to the previous runtime version. For more information, see https://docs.aws.amazon.com/lambda/latest/dg/runtimes-update.html boto3==1.19.9, botocore==1.22.9 facing same issue with python 3.8 |
solved by changing python version to |
Add boto3 as an explicit dependency and upgrade boto3 and botocore to avoid this issue: boto/boto3#3648.
Describe the bug
We are trying to run a tool using boto3 that stopped working with the most recent patch version (1.26.101 worked fine). Here is the stack trace:
It looks like this import was added in the patch version
Expected Behavior
No error to be thrown when importing the module.
Current Behavior
An error is thrown when importing the module
Reproduction Steps
Install the most recent patch version and reference boto3-1.26.102 on python 3.9
Possible Solution
No response
Additional Information/Context
For now we work around by pinning our boto3 version to 1.26.101
SDK version used
1.26.102
Environment details (OS name and version, etc.)
Kernel Version: 5.15.0-1030-aws Operating System: Ubuntu 20.04.5 LTS OSType: linux Architecture: x86_64
The text was updated successfully, but these errors were encountered: