Release v1.2.0

[mprahl]

• Upgrade Python packages in case the requirements have changed during package upgrades
• Split test dependencies since there is no need to install the test dependencies on a production system
• Upgrade dependencies
• Bump version to v1.2.0

[mprahl]

@thatarchguy I'll fix the tests tonight. I forgot to modify the travis file.

I was thinking that the test-requirements probably don't need to have versions pinned, so I could delete the test-requirements.txt file and rename test-requirements.in to test-requirements.txt.

What are your thoughts?

[thatarchguy]

I was thinking that the test-requirements probably don't need to have versions pinned, so I could delete the test-requirements.txt file and rename test-requirements.in to test-requirements.txt.

If we are splitting off the test requirements, then yeah pop it off unpinned to a .txt file for simplicity. I don't believe we should be compiling our test requirements separately.

Another pattern I've seen that I don't know if I'm fond of yet is

requirements/
    ./common.txt
    ./dev.txt

with ./dev containing -r common.txt so you don't need multiple pip install declarations.

[mprahl]

@thatarchguy I had to make some changes based on some breaking changes from passlib and a deprecation warning from flask-wtf, but it should be good to go now.

[thatarchguy]

pallets-eco/flask-wtf#250

[thatarchguy]

Good catch on the passlib and flask-wtf changes