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

Why was s3transfer==0.8.1 yanked? #298

Closed
martin-thoma opened this issue Dec 19, 2023 · 1 comment
Closed

Why was s3transfer==0.8.1 yanked? #298

martin-thoma opened this issue Dec 19, 2023 · 1 comment
Labels
closing-soon-if-no-response

Comments

@martin-thoma
Copy link

I've just noticed this: https://pypi.org/project/s3transfer/#history

image

Why was it yanked?
@nateprewitt
Copy link
Contributor

Hi @MT-Cash, we pulled 0.8.1 for boto/boto3#3951 which was resolved with #293 in 0.8.2. It will work on a properly configured installation but given the potential cases where users had older versions of the awscrt installed we decided to help avoid errors by yanking the problematic version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
closing-soon-if-no-response
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nateprewitt @martin-thoma