-
-
Notifications
You must be signed in to change notification settings - Fork 867
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
Conversation
* 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
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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jschneier @mbarrien as far I know Django dropped Python 2.5 and 2.6. Probably this needs to be done...
Hello @jschneier Are you agree to remove it ? |
@ZuluPro On the very page you link, they link to Boto's documentation at http://boto.readthedocs.io/en/latest/ 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. |
No description provided.