Skip to content
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.

Sign up for GitHub

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

Jump to bottom

requirements: upgrade responses after opensearch-py supports urllib3>=2 #680

Closed
GraemeWatt opened this issue Jul 31, 2023 · 1 comment
Closed

requirements: upgrade responses after opensearch-py supports urllib3>=2 #680

GraemeWatt opened this issue Jul 31, 2023 · 1 comment
Assignees
@GraemeWatt
Labels
complexity: low priority: low type: bug Indicates an unexpected problem or unintended behaviour

Comments

@GraemeWatt
Copy link
Member

The latest responses v0.23.2 requires urllib3>=2.0.0,<3.0 but the latest opensearch-py v2.3.0 requires urllib3>=1.21.1,<2. For now, I've pinned responses==0.23.1, but responses should be upgraded after opensearch-py supports urllib3>=2.
@GraemeWatt GraemeWatt added type: bug Indicates an unexpected problem or unintended behaviour priority: low complexity: low labels Jul 31, 2023
@github-project-automation github-project-automation bot moved this to To do in @HEPData Jul 31, 2023
@GraemeWatt GraemeWatt moved this from To do to On Hold in @HEPData Jul 31, 2023
GraemeWatt added a commit that referenced this issue Jul 31, 2023
@GraemeWatt
requirements: pin responses==0.23.1 (see #680)
3dec4ec
@GraemeWatt
Copy link
Member Author

The pin urllib3<2 was removed in opensearch-py v2.4.0, so we can now upgrade responses to the latest v0.24.1.

@GraemeWatt GraemeWatt moved this from On Hold to In Progress in @HEPData Dec 14, 2023
@GraemeWatt GraemeWatt self-assigned this Dec 14, 2023
@github-project-automation github-project-automation bot moved this from In Progress to Done in @HEPData Dec 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@GraemeWatt GraemeWatt

Labels
complexity: low priority: low type: bug Indicates an unexpected problem or unintended behaviour
Projects
@HEPData
Status: Done
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GraemeWatt