Flask-Reuploaded 0.3.2

Notes on this package

This is an independently maintained version of Flask-Uploads based on the 0.2.1 version of the original, but also including four years of unreleased changes - at least not released to PyPi.

Noteworthy is the fix for the Werkzeug API change.

Goals

• Flask-Reuploaded is a stable drop-in replacement for Flask-Uploads

• regain momentum for this widely used package

• provide working PyPi packages

Migration guide from Flask-Uploads

If you have used Flask-Uploads and want to migrate to Flask-Reuploaded, you only have to install Flask-Reuploaded instead of Flask-Uploads.

That’s all!

So, if you use pip to install your packages, instead of …

$ pip install Flask-Uploads # don’t do this! package is broken

… just do …

$ pip install Flask-Reuploaded

Flask-Reuploaded is a drop-in replacement.

This means you do not have to change a single line of code.

Installation

$ pip install Flask-Reuploaded

Documentation

The documentation can be found at…

https://flask-reuploaded.readthedocs.io/en/latest/

Contributing

Contributions are more than welcome. Please have a look at https://github.com/jugmac00/flask-reuploaded/issues

0.3.2

• documentation update (#5)

  • update docs/index.rst

  • use blue ReadTheDocs theme

  • update sphinx configuration

  • add documentation link to setup.py, so it shows on PyPi

  • add note about documentation in the README file

  • delete old theme files

• configure isort to force single line imports

0.3.1

• add badges to README (# 31)

• add migration guide from Flask-Uploads to Flask-Reuploaded (#11)

• add packaging guide (#28)

• update installation instruction in README

0.3

Besides including four years of unreleased changes from the original package, most notable the fix for the Werkzeug API change, the following changes happened since forking the original package.

• rename package from Flask-Uploads to Flask-Reuploaded (#10)

• update setup.py (#12)

• start using pre-commit.com (#4)

• update README (#14)

• setup CI (Travis) (#3)

• fix broken tests (#13)

• make use of pytest instead of the no longer maintained nose (#2)

• add a changelog and start tracking changes (#1)