Fix deprecations: Round 1

[pradyunsg]

No description provided.

[pradyunsg]

369 warnings

sigh This is gonna take a while.

[palnabarun]

@pradyunsg I think it would be a better idea for new contributors to start fixing the deprecation warnings. Through that, they can get started on how junction is structured. Can you create an Umbrella issue with all the warnings?

[ananyo2012]

What are these warnings? And when are we able to see those ?

[pradyunsg]

They show up if you run the tests locally.

These were a little more involved. There are a few that are from our dependencies (which need to be upgraded) and a whole lot from needing to specify on_deleye behaviors.

I welcome someone to help with the second but, as well as to file an umbrella issue.

[sks444]

@ananyo2012 we can also run python -Wall manage.py runserver to see all the deprecated warnings. Removing these will help us in upgrading Django to 2/3.

@pradyunsg I can help out with the on_delete warnings.

[coveralls]

Coverage increased (+0.02%) to 67.163% when pulling 57558bf on pradyunsg:fix-deprecations-round-1 into 87c3172 on pythonindia:master.

[coveralls]

Coverage increased (+0.02%) to 67.163% when pulling 57558bf on pradyunsg:fix-deprecations-round-1 into 87c3172 on pythonindia:master.

[ananyo2012]

@pradyunsg Are these changes ready ?

[pradyunsg]

Yup!

[ananyo2012]

LGTM. Ship it !