* Use Python 3.11
* Run pyupgrade with Python 3.11+
* Update pyupgrade to latest version
* Update Celery and python-dateutil
Celery is not compatible with Python 3.11, leading to test failures. Need to update also python-dateutil to install the latest version.
* pytest.yield_fixture is a deprecated alias for pytest.fixture
* Update Django dev dependencies
* Update bleach
* Upgrade existing dependencies within the given constraints of the input files
* Fix jinja after update
* Update pip-tools
* Update django-* libraries
* Upgrade graphene-django
* Upgrade Django to 4.0
* Drop pytz
* ALLOWED_HOSTS must be a list
* Upgrade Django to 4.1
* Add workaround for the Raygun AttributeError
See:
https://github.com/MindscapeHQ/raygun4py/issues/108
* Avoid ValueError when instance doesn't have a primary key value but relationship is used.
See:
7ba6ebe914
* Upgrade Django to 4.2.11
* Drop pytz as a direct requirement
- Ignore resolver deprecation warning on make requirements
- Ignore egg fragment deprecation warning on make requirements
- Update test requirements (needed to update black)
- Update black (needed to install the regex package)
- Run make black
- Add regex package (needed to implement accesskey candidate generator)
* Update to compare-locales 9.0.1, fluent-syntax 0.19.0, pip-tools 6.13.0
The transitive dependency typing-extensions is also updated to 4.5.0
* ci: Use codecov action rather than the removed/deprecated pypi & npm packages
Using constraints has the benefit that updates to default.in only
show up in default.txt, and not in dev.txt. That should make reviews
easier. It still ensures there's only one version of each package
used across production, dev, and local testing.
* App configs are now automatically discovered, and most of our current app configs were redundant or had wrong names.
* The DEFAULT_AUTO_FIELD is needed to prevent unwanted migrations in the future, when the default value will change to BigAutoField.
* Make get_stats_sum return dict instead of AggregatedStats instance. Django 3.2 throws an error when instantiating an abstract model. Add tests for the relevant views that were previously not covered, marked with pytest.mark.no_cover.
Dj.debug brings some utils to help with development, but
we don't seem to be using it much, because it doesn't support Python 3
and we haven't noticed it so far.
All direct dependencies are now in requirements/*.in files, and the requirements/*.txt files are generated with pip-compile. We provide a script for that, since these files should always be updated all at once.
This commit:
* removes old migrations
* bumps up the dependencies that couldn't run on Django 2.2
* adds missing on_delete attributes
* removes all authenticated() calls and uses the property instead
* uses the Django's constraints mechanism and removes PartialIndex
* updates the config of django-notifications-hq
Fix all errors detected by flake8. `pytest` is able to run testsuites and report failing tests. Changes don't affect Pontoon on Python 2.
Included changes/bugfixes:
* bump up the version number of:
** Mercurial==5.0, it has experimental support for Python 3
** lxml==4.3.3
* add new dependencies:
** python3-openid - required by django-allauth
** defused-xml - required by python3-openid
* move sqlparse to `constraints.txt`, because it's a dependency of django-debug-toolbar
* nested() from contextlib is not available in Python 3
* update hashes of some dependencies for Python 3 (thanks to Hashin)
Newer versions of Pip (7.1+) allow to create a constraints file which keeps track of versions of all sub-dependencies.
* All requirements files are renamed and moved into a separate directory.
* All sub-dependencies are moved to a constraints file.
Francesco Lodolo
Matjaž Horvat
Eemeli Aro
Fabien LOISON
Axel Hecht
Philipp Fischbeck
Julen Ruiz Aizpuru
Jarek
Michael Kelly