Details
Description
Direct assignment to many-to-many relation is deprecated in Django 1.10.
This breaks one of the portals' fixtures. Because we are not planning to upgrade Django any time soon, this issue is meant to address this deprecation only in the following fixture: oioioi/portals/fixtures/test_portals.json
Docs: https://docs.djangoproject.com/en/2.1/releases/1.10/#direct-assignment-to-a-reverse-foreign-key-or-many-to-many-relation
This breaks one of the portals' fixtures. Because we are not planning to upgrade Django any time soon, this issue is meant to address this deprecation only in the following fixture: oioioi/portals/fixtures/test_portals.json
Docs: https://docs.djangoproject.com/en/2.1/releases/1.10/#direct-assignment-to-a-reverse-foreign-key-or-many-to-many-relation
https://gerrit.sio2project.mimuw.edu.pl/3211
(no-ticket) Fix pytest.ini so that it treats all deprecation warnings as errors
In the earlier similar commit class PendingDeprecationWarning was
not added to the list warning --> error (did not generated an error),
but it is now.
Additionally, new exceptions were added and appropriate
Jira issues were created:
SIO-2155Set the app_name attribute in urls modules strikes backSIO-2233Adapt old-style settings.MIDDLEWARE_CLASSES to the new versionSIO-2234Change use of User.is_authenticated() and User.is_anonymous() methodsSIO-2235Fix test_portals.json fixtureChange-Id: I5811b92c9294f2d87d61bc70d672dcaf4e5dacef