This will ultimately be used by the marketing site to retrieve program data without having to store a separate reference (e.g. UUID).

LEARNER-2053

EDUCATOR-882

Populate course run effort values from Drupal API

ECOM-5776

ECOM-5776

Django Compressor is still used by Publisher, so these settings are still needed.

ECOM-5776

The metadata refresh command should log the short code of the partner for which an access token is being retrieved instead of always logging the value of the partner_code argument.

ECOM-5776

LEARNER-1119

LEARNER-1887

This reverts commit bcbd1d4f.

LEARNER-1119

This reverts commit cda1efbe.

This reverts commit a90370b4.

Merge branches 'master' and 'vkaracic/LEARNER-1119' of https://github.com/edx/course-discovery into vkaracic/LEARNER-1119

LEARNER-1119

3.6.3 is tested against Django 1.11 and includes built-in, interactive API documentation. Sadly, the built-in documentation struggles with the URL patterns in this project and is only able to construct top-level entries (i.e., api, extensions, publisher). All the endpoints that should be underneath those are missing. This issue is documented in https://github.com/encode/django-rest-framework/issues/4984. Until it's resolved, we'll continue using django-rest-swagger.

The 3.6 release announcement is at http://www.django-rest-framework.org/topics/3.6-announcement. Extended release notes are at http://www.django-rest-framework.org/topics/release-notes/#36x-series.

LEARNER-1590

EDUCATOR-828

The query that fetches available courses performs a join across the
course table, the course_runs table, and the seats table and returns
a separate copy of the same course for each available run/seat
combination by default.

We have to use distinct() to make sure only a single copy of each
available course is returned.

3.5.4 features improved schema generation, including the ability to exclude views from generated schemas. 3.5.4 deprecates DjangoFilterBackend in favor of the implementation provided by the django-filter package.

LEARNER-1590

EDUCATOR-894

The API docs were broken by the Django 1.11 upgrade. This change includes an upgrade to the most recent version of django-rest-swagger that supports DRF 3.4. Newer versions of django-rest-swagger require DRF 3.5.

This change is complicated by a decision made by the maintainers of the django-filter package to avoid subclassing DRF's DjangoFilterBackend. For more on that decision, see https://github.com/carltongibson/django-filter/pull/576. The SchemaGenerator from DRF 3.4.7 expects instances of DjangoFilterBackend to have a get_fields() method. The DjangoFilterBackend from django-filter 1.0.4 doesn't have this method, instead replacing it with the get_schema_fields() used by the SchemaGenerator in DRF 3.5. To work around this, I've replaced our one use django-filter's DjangoFilterBackend with DRF's DjangoFilterBackend. Note that DRF 3.5 removes its implementation of DjangoFilterBackend in favor of django-filter's, so we will have to change how we import DjangoFilterBackend when we upgrade to 3.5.

LEARNER-1590

DRF 3.4.7 is the same version run by edx/credentials. Release notes are at http://www.django-rest-framework.org/topics/release-notes/#34x-series. Highlights include:

1. [Support for Django 1.10](https://github.com/encode/django-rest-framework/pull/4158) - sigh
2. [Support for schema generation](https://github.com/encode/django-rest-framework/pull/4179) - required for newer versions of django-rest-swagger
3. A change that [prevents paginated views from re-running queries](https://github.com/encode/django-rest-framework/issues/4201) when count queries return 0 - this explains the expected query count changes made in tests

LEARNER-1590