1 września 2016
Django 1.10.1 zawiera poprawki błędów z wersji 1.10.
SELECT @@SQL_AUTO_IS_NULL nie zwraca wyniku (#26991).User.is_authenticated i User.is_anonymous mogą być porównywane przy użyciu ==, != i | (#26988, #27154).BaseCommand.usage() method which was for
optparse support (#27000).Meta.default_permissions
(#26997).RadioSelect with a
ModelChoiceField form field (#27001).request.META['CONTENT_LENGTH'] is an empty string
(#27005).isnull lookup on a ForeignKey with its to_field
pointing to a CharField or pointing to a CharField defined with
primary_key=True (#26983).migrate command from raising
InconsistentMigrationHistory in the presence of unapplied squashed
migrations (#27004).Client.force_login() which required specifying a
backend rather than automatically using the first one if multiple
backends are configured (#27027).QuerySet.bulk_create() properly initialize model instances on
backends, such as PostgreSQL, that support returning the IDs of the created
records so that many-to-many relationships can be used on the new objects
(#27026).django.views.static.serve() with show_indexes enabled
(#26973).ClearableFileInput to avoid the required HTML attribute when
initial data exists (#27037).{% for %} tag to unpack any iterable (#27058).makemigrations skip inconsistent history checks on non-default
databases if database routers aren’t in use or if no apps can be migrated
to the database (#27054, #27110, #27142).Model._meta.managers (#27073).contrib.admindocs crash when a view is in a class, such as some of
the admin views (#27018).field.many_to_many back to
isinstance(field, models.ManyToManyField) since it turned out the checks
weren’t suitable to be generalized like that (#26998).InconsistentMigrationHistory message
raised by makemigrations and migrate (#27089).ContentType i Permission``dla modeli aplikacji bez migracji podczas wywołania komendy ``migrate bez migracji do zastosowania (#27044).Apps dostarczonej do odbiorników sygnału pre_migrate, aby umożliwić zmianę nazwy ContentType w czasie zmiany nazwy modelu (#27100).UserCreationForm bez USERNAME_FIELD w Meta.fields (#27111).default, które nie pojawiały się w danych POST, przestawały używać default (#27039).sie 03, 2022