Something broke related to XBlocks,
and it is no longer working.
TNL-6533

use PyPI version of edx-sga and move to base.txt

ECOM-7098

Utilize scrapy parse

specify custom callback and add port

Getting rid of scrapy parse. A modified crawl will work

remove log

Remove unnecessary input options

Remove extra empty line

version bump v1.5.9

Reduce duplicate code

add in port and simplify further

clean command further

add port to basic command

Bump Pa11yversion to the newest version

TNL-6294

* Use external celery_utils in edx-platform (TNL-6454)
* Remove old openedx.core celery_utils implementation.

TNL-6440, TNL-6439

Add consent check to course access prerequisites; add utility functions to provide interface to course-specific consent in Enterprise app

We're seeing an error in sending to the collector, there are also
a number of changes.
https://docs.newrelic.com/docs/release-notes/agent-release-notes/python-release-notes

[pa11ycrawler] enable load_courses from CLI

force pa11ycrawler to run

[pa11ycrawler] bump version to 1.5.5

move around some paver opts

crawl -> test

bump to v1.5.8

let's stick to crawl for now

Changing dash to underscore in skip-fetch

revert a couple of options

add back $RUN_PA11YCRAWLER check

https://github.com/edx/edx-rest-api-client/compare/1.6.0...1.7.1

ECOM-6634

and removes the -e from the install, as per the requirements rules.

With 2.0.1, and setuptools 34.0.2, errors happen like:

File "/edx/app/edxapp/venvs/edxapp-sandbox/local/lib/python2.7/site-packages/packaging/requirements.py", line 59, in <module>
    MARKER_EXPR = originalTextFor(MARKER_EXPR())("marker")
TypeError: __call__() takes exactly 2 arguments (1 given)

(cherry picked from commit 73519b35)

These are the only two egg names that are wrong in this file.  We have
to uninstall i18n-tools, because the distribution name changed.  The
lti-consumer XBlock hasn't changed named, we just had the wrong name in
the requirements file.

The new version includes a minor fix for the problem icon.

Waffle serves as a complement to config models. It's useful in feature rollout situations where you may not want to incur the overhead of creating and committing a migration (required for adding a field to a config model), and also handles gradual, percentage-based rollouts.

ECOM-4422