Get rid of PgModel, replacing it with simple signals
authorMagnus Hagander <magnus@hagander.net>
Mon, 7 Mar 2016 20:41:45 +0000 (21:41 +0100)
committerMagnus Hagander <magnus@hagander.net>
Mon, 7 Mar 2016 20:41:45 +0000 (21:41 +0100)
commit8058accee036bd353128a5ae0b89c8ea2da641f9
tree81fa8280e8fe7e5f9525853a95f0f4155c0e64ac
parentd15fc715afc4dbc15712a12eb7af5321f72425d6
Get rid of PgModel, replacing it with simple signals

We were already using signals for everything except delete, and even
in our old version of django the delete signal exists (it didn't exist
when this code was first written).

Django doesn't really like models to be OOP like this, so keeping PgModel
would cause issues with upcoming changes in django 1.8. Using simple functions
is easier, and the actual functionality is replicated straight off.
19 files changed:
docs/django.rst
docs/frontend.rst
pgweb/contributors/models.py
pgweb/core/models.py
pgweb/docs/models.py
pgweb/downloads/models.py
pgweb/events/models.py
pgweb/featurematrix/models.py
pgweb/lists/models.py
pgweb/news/models.py
pgweb/profserv/models.py
pgweb/pugs/models.py
pgweb/pwn/models.py
pgweb/quotes/models.py
pgweb/sponsors/models.py
pgweb/survey/models.py
pgweb/urls.py
pgweb/util/bases.py [deleted file]
pgweb/util/signals.py [new file with mode: 0644]