Rebase with master 1.6.5+ #1
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Enable Python 3.5 builds on Travis * Fix Python 3.5 test failure from unittest.mock api change
Add documentation for AWS_QUERYSTRING_AUTH and AWS_QUERYSTRING_EXPIRE. See https://bitbucket.org/david/django-storages/issues/51/please-improve-s3-storage-documentation and jschneier#139.
This was needed when the name was django-storages-redux now is not the case.
* Added parameters to SFTP __init__ and fix File.close() * Added tests for SFTP * Moved SFTP documentation from comments to docs
* Improved DropBox storage * Adeded DropBox doc
* Added FTP readlines and fix storage init argument * Added FTP storage tests * Update doc
* New S3 Boto3 backend. * Based on existing s3boto module * Replace Boto2 headers settings with parameters * Does not support proxies, alternate host/port * S3Boto3 Updates from feedback and catching up to s3boto commits * Update s3boto3.py Non-existent file raises IOError in _open for backwards compatibility with s3boto Don't let the ClientError bubble up
Django expects a naive datetime from modified_time()[1]. Django 1.10 adds get_modified_time()[2], which respects USE_TZ. This commit fixes modified_time(), adds get_modified_time(), and adds relevant tests. [1]: https://docs.djangoproject.com/en/1.10/ref/files/storage/#django.core.files.storage.Storage.modified_time [2]: https://docs.djangoproject.com/en/1.10/ref/files/storage/#django.core.files.storage.Storage.get_modified_time
* Drop Django 1.7 support and add Django 1.10 Remove unnecessary compatability wrappers. * Tell Travis to use the correct envs * Update CHANGELOG * Fix OverwriteStorage typo
Looks like boto3 changed some keyword arguments and this prefix forgot to be captalised Signed-off-by: Leon Smith <[email protected]>
Alphabetized entries.
* Add support for files > 5 gb with S3BotoStorage Fixes jschneier#194 * Fix tests
to allow detection of changes in gzipped files by MD5 SUM in the same way as for non gzipped files
Fall under the general umbrella of linting the project. Run all linting tools as one stage of testing.
The client module was removed from the library.
Avoids unnecessary API requests to fetch and create the bucket when simply checking if a key exists. https://boto3.readthedocs.io/en/latest/reference/services/s3.html#S3.Client.head_object
The indirection was necessary for the older s3boto backend as it shared code with the (now deprecated) GS backend. The s3boto3 does not share code in this way. When the s3boto3 was developed, the indirection was carried over, but it is no longer necessary. To simplify the code, remove it. Other backends do not encode this style of indirection.
[gcloud] Add support for MIME type
Documentation for boto3 recommends a session per thread - https://boto3.readthedocs.io/en/latest/guide/resources.html#multithreading-multiprocessing As the storage class is (usually) only instantiated once per process, we need to set a thread local for each thread/connection used. Fixes jschneier#268
* Fix .save method of the Dropbox backend (jschneier#378) * Dropbox large file support (jschneier#301) * Make linter happy
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.