In accordance with our security release policy, the Django team is issuing Django 3.2.4, Django 3.1.12, and Django 2.2.24. These release addresses the security issue detailed below. We encourage all users of Django to upgrade as soon as possible.
Today we've issued 3.2.3, 3.1.11, and 2.2.23 bugfix releases. The release package and checksums are available from our downloads page, as well as from the Python Package Index. The PGP key ID used for this release is Mariusz Felisiak: 2EF56372BA48CD1B.
In this article, we'll look at how to use Django REST Framework (DRF) serializers more efficiently and effectively by example. Along the way, we'll dive into some advanced concepts like using the source keyword, passing context, validating data, and much more.
In accordance with our security release policy, the Django team is issuing Django 3.2.2, Django 3.1.10, and Django 2.2.22. These releases address the security issue with severity "moderate" detailed below. We encourage all users of Django to upgrade as soon as possible.
In accordance with our security release policy, the Django team is issuing Django 3.2.1, Django 3.1.9, and Django 2.2.21. These release addresses the security issue detailed below. We encourage all users of Django to upgrade as soon as possible.
As you build and scale a Django app you'll inevitably need to run certain tasks periodically and automatically in the background.
In accordance with the security release policies that Django and Jazzband are following, the Jazzband project team for the Django Debug Toolbar project is issuing Django Debug Toolbar 3.2.1, Django Debug Toolbar 2.2.1 and Django Debug Toolbar 1.11.1. These releases address the security issue with severity "high" detailed below. We encourage all users of Django Debug Toolbar to upgrade as soon as possible.
The Django team is happy to announce the release of Django 3.2. This version has been designated as a long-term support (LTS) release, which means that security and data loss fixes will be applied for at least the next three years. It will also receive fixes for crashing bugs, major functionality bugs in newly-introduced features, and regressions from older versions of Django for the next eight months until December 2021.
In accordance with our security release policy, the Django team is issuing Django 3.1.8, Django 3.0.14 and Django 2.2.20. These releases address the security issue with severity "low" detailed below. We encourage all users of Django to upgrade as soon as possible.
It is important to understand the difference between AbstractUser and AbstractBaseUser in Django, this will help you make the right decision on which one to use when you are starting a Django project.
Django 3.2 release candidate 1 is the final opportunity for you to try out the mezcla of new features before Django 3.2 is released.
In this article, we'll look at how to prevent a Celery task dependent on a Django database transaction from executing before the database commits the transaction. This is a fairly common issue.
For more than a decade after Django was first released in 2005, pages were mostly static, AJAX was used only in limited use cases, and things were relatively uncomplicated. Over the past five years, real-time web applications have evolved, trending toward more client-server and peer-to-peer interaction. This type of communication is achievable with WebSockets, a new protocol that provides full-duplex communication and maintains a persistent, open connection between client and server.
Building a REST API in Django is so super easy. In this tutorial, we’ll walk through the steps to get your first API up and running.
Django 3.2 beta 1 is now available. It represents the second stage in the 3.2 release cycle and is an opportunity for you to try out the changes coming in Django 3.2.
In accordance with our security release policy, the Django team is issuing Django 3.1.7, Django 3.0.13, and Django 2.2.19. These release addresses the security issue detailed below. We encourage all users of Django to upgrade as soon as possible.
How do I fully replace the username field with an email field for Django authentication? This post explains step-by-step how to create a custom User model in Django so that an email address can be used as the primary user identifier instead of a username for authentication.
In accordance with our security release policy, the Django team is issuing Django 3.1.6, Django 3.0.12 and Django 2.2.18. These releases address the security issue with severity "low" detailed below. We encourage all users of Django to upgrade as soon as possible.
Django 3.2 alpha 1 is now available. It represents the first stage in the 3.2 release cycle and is an opportunity for you to try out the changes coming in Django 3.2.
Today we've issued the 3.1.5 bugfix release. The release package and checksums are available from our downloads page, as well as from the Py