django-storages was (is) a project to provide a variety of storage backends in a single library. This is its maintained, Python 3 compatible fork. The reasons for the fork are given in the next section.

At the moment the only tested Python 3 compatible backend is the S3 Boto one but some of them should work without issue (hashpath, symlink, overwrite).

This library is compatible with Django >= 1.5.

The BitBucket repo of the original django-storages has seen no commit applied since March 2014 (it is currently December 2014) and no PyPi release since March 2013 despite a wealth of bugfixes that were applied in that year-long gap. There is plenty of community support for the django-storages project (especially the S3BotoStorage piece) and I have a personal need for a Python3 compatible version.

All of the Python3 compatible forks that currently exist (and there are a few) are lacking in some way. This can be anything from the fact that they don't release to PyPi, have no ongoing testing, didn't apply many important bugfixes that have occurred on the Bitbucket repo since forking or don't support older versions of Python and Django (vital to finding bugs and keeping a large community). For this fork I've done the small bit of work necessary to get a tox + travis ci matrix going for all of the supported Python + Django versions. In many cases the various forks are lacking in a few of the above ways.

I suspect that a few of the storage engines in backends/ have been unsupported for quite a long time. I personally only really need the S3Storage backend but welcome bug reports (and especially) patches and tests for some of the other backends.

Issues are tracked via GitHub issues at the project issue page.

The original documentation for django-storages is located at http://django-storages.readthedocs.org/. Stay tuned for forthcoming documentation updates.

1. Check for open issues at the project issue page or open a new issue to start a discussion about a feature or bug.
2. Fork the django-storages repository on GitHub to start making changes.
3. Add a test case to show that the bug is fixed or the feature is implemented correctly.
4. Bug me until I can merge your pull request. Also, don't forget to add yourself to AUTHORS.