3 ms·
Great news! Just for reference: The latest release for Django Rest Framework is not compatible with Django 4.0 yet. At least my first attempts failed due to a
by theomega 5y ago
Great news!
Just for reference: The latest release for Django Rest Framework is not compatible with Django 4.0 yet. At least my first attempts failed due to a missing `pytz` dependency. This is fixed in the `master` of DRF on Github. Installing `pytz` explicitly again to your project fixes DRF for now.
- mch82 5y agoThe transitional USE_DEPRECATED_PYTZ setting might help. Saw this in the extended release notes: https://docs.djangoproject.com/en/4.0/releases/4.0/#zoneinfo-default-timezone-implementation https://docs.djangoproject.com/en/4.0/releases/4.0/#zoneinfo... > The Python standard library’s zoneinfo is now the default timezone implementation in Django. > This is the next step in the migration from using pytz to using zoneinfo. Django 3.2 allowed the use of non-pytz time zones. Django 4.0 makes zoneinfo the default implementation. Support for pytz is now deprecated and will be removed in Django 5.0. > … > To give time for such an audit, the transitional USE_DEPRECATED_PYTZ setting allows continued use of pytz during the 4.x release cycle. This setting will be removed in Django 5.0.