-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Import fails with -Werror
python option
#2822
Comments
Hi @headtr1ck thanks for reaching out. This issue was previously reported here: #2744. You can refer to the discussion there for more context as well as the corresponding PR (#2763) for suppressing the warning. Please let us know if you had any follow up questions after reviewing the comments there. |
Thanks for pointing out that issue. Unfortunately in my case the solution of this PR does not work since no warning is issued when using So adding the DeprecationWarning to the expect block is the only thing that would help. |
Do you see that error on the latest version of boto3/botocore? |
Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one. |
Describe the bug
When importing
botocore.session
with the python option-Werror
the import fails.Expected Behavior
Import works
Current Behavior
The import raises:
Reproduction Steps
python -Werror -c "import botocore.session"
Possible Solution
In line:
botocore/botocore/httpsession.py
Line 35 in dfda41c
add
DeprecationWarning
to the excepted Errors.Additional Information/Context
See pydata/xarray#7322 which run into this problem.
SDK version used
1.27.59
Environment details (OS name and version, etc.)
Win10/linux
The text was updated successfully, but these errors were encountered: