Upgrade to 1.0.0 caused issues which are described and being
investigated in https://github.com/django-ses/django-ses/issues/186.

Upgrade transifex-client version.

This is only made in order to run the tests with a transifex-client version compatible with python3.8

The actual problem that we have in edx-platform is that the last version of transifex-client has as constraint python-slugify<2.0.0 which is not compatible with the current requierements of edx-platform on the other hand, the current version used in edx-platform is not compatible with python3.8

sympy needs to be at a newer version for python3.

updated the constraints order

Remove pandas requirement.
Replace pandas functionality with itertools.group_by.

* Updating Python Requirements

* Pin django-pipeline and lxml

Co-authored-by: Jeremy Bowman <jbowman@edx.org>

Cleaned up a few more things about the testing configuration now that we've deployed Django 2.2 to production:

* Go back to a single version of django-oauth-toolkit, tox doesn't need to vary it anymore
* Go back to PyPI release of django-method-override
* Remove no longer needed dependency on python-oauth2 (we already removed the package it was used by)
* Update prepare_xdist_nodes.sh with new Django requirements file options

This reverts commit 27480a25.

* Updating Python Requirements

* Constrain django-cookies-samesite until dep bug fixed

* Fix PEP 8 problems revealed by pycodestyle upgrade

Co-authored-by: Tim McCormack <tmccormack@edx.org>
Co-authored-by: Jeremy Bowman <jbowman@edx.org>

Constrain ddt<1.4.0 until this issue is fixed:
- https://github.com/datadriventests/ddt/issues/83

These were pinned because they drop support for Django<2.2 (or were
planning on it, in the latter case.)

No related changes in computed requirements.

See ARCHBOM-1141 for details.  Effort required to upgrade pip.

ARCHBOM-1141:

This adds contraints to:
kiwisolver: next release only works with python>=3.6

The was run to upgrade:
django-splash
django-wiki
edx-search
The previous versions were constraining django below 2.0.

Co-authored-by: Robert Raposa <rraposa@edx.org>

We'll upgrade this again along with pytest once pytest-dev/pytest#6925 is resolved.

Also, it looks like a flaky error in test class DB setup outside a transaction was mucking things up for the rest of the test shard. I didn't try to fix the flakiness, but this should at least limit the blast radius to just that test class. We really need to start using setUpTestData() more consistently.

Also pinned httpretty < 1.0 because that upgrade broke many tests.

-Upgrade edx-drf-extensions
-settings-update

This partially reverts #23318.

The last time we tried this upgrade we encountered timeouts on the quality job, which it now appears were due to the worker running pylint common running out of memory and killing the Jenkins process. Switching to a different worker type with double the RAM (8 GB vs. 4 GB) seems to have fixed this; about 5.5 GB was used. Upstream is aware of the high memory usage on large projects, it's apparently due primarily to a cache of parsed modules: https://github.com/PyCQA/pylint/issues/1495 .

Even after disabling some of the new checks that have been added, the new version of pylint found about twice as much to complain about. Just bumping the threshold for now to unblock the Django upgrade, we can try automated utilities like pyupgrade to fix some of these later.

try to fix github

Remove duplicate constraints in requirements/constraints.txt uncovered by the recent change in pip-compile output format. I sorted the pinned dependencies by name to try and make it more obvious if this happens again. I also upgraded to pip-tools 4.5.1, which removes the line numbers from the enhanced pip-compile output added in 4.5.0, which should reduce future diff churn and merge conflicts but means that there's a large diff this one last time.

Also unpin edx-search again after the previous change to do that was apparently broken by a merge conflict.

- Reimplement `djcelery.common.respect_language` utility function so we
  can drop the dependency.
- Loosen `celery` pinning to a range, which brings in a fix for a
  possible crash bug

Also, pin `path` to 13.1.0 for now in order to continue supporting py35.

There is a planned edx-drf-extension update to 3.0.0 to remove the
toggle used for ENFORCE_JWT_SCOPES. Currently, edx-platform is dependent
on the this toggle. This constraint will keep other `make upgrade` PRs
working in the short window before the edx-paltform PR to remove the
same toggle can land.

BOM-1324

Upgrade django-toolbar.

https://openedx.atlassian.net/browse/BOM-1036