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.

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

S3boto3 #179

merged 3 commits into from Aug 2, 2016


None yet
4 participants
Copy link

jschneier commented Aug 2, 2016

No description provided.

mbarrien added some commits Jul 2, 2015

New S3 Boto3 backend.
* Based on existing s3boto module
* Replace Boto2 headers settings with parameters
* Does not support proxies, alternate host/port
Non-existent file raises IOError in _open for backwards compatibility with s3boto

Don't let the ClientError bubble up

@jschneier jschneier merged commit 1fc2ef1 into master Aug 2, 2016

@jschneier jschneier deleted the s3boto3 branch Aug 2, 2016

This was referenced Aug 2, 2016

in your application.
# TODO: Read/Write (rw) mode may be a bit undefined at the moment. Needs testing.
# TODO: When Django drops support for Python 2.5, rewrite to use the

This comment has been minimized.

Copy link

galuszkak Aug 9, 2016

@jschneier @mbarrien as far I know Django dropped Python 2.5 and 2.6. Probably this needs to be done...


This comment has been minimized.

Copy link

ZuluPro commented Sep 1, 2016

Hello @jschneier
I'm looking to how to make boto & boto3 storage more DRY,
And in fact we don't need boto3:
boto supports Python3 !

Are you agree to remove it ?


This comment has been minimized.

Copy link

mbarrien commented Sep 1, 2016

@ZuluPro On the very page you link, they link to Boto's documentation at which says this multiple times on the page:

"Note Boto3, the next version of Boto, is now stable and recommended for general use. It can be used side-by-side with Boto in the same project, so it is easy to start using Boto3 in your existing projects as well as new projects. Going forward, API updates and all new feature work will be focused on Boto3."

Given that, I don't think dropping Boto 3 and just going with original Boto is a viable option in the long term, even with Python 3 support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.