September 1, 2016
Django 1.10.1 fixes several bugs in 1.10.
SELECT @@SQL_AUTO_IS_NULL
doesn’t return a result (#%s26991).User.is_authenticated
and User.is_anonymous
properties to be
compared using ==
, !=
, and |
(#%s26988, #%s27154).BaseCommand.usage()
method which was for
optparse
support (#%s27000).Meta.default_permissions
(#%s26997).RadioSelect
with a
ModelChoiceField
form field (#%s27001).request.META['CONTENT_LENGTH']
is an empty string
(#%s27005).isnull
lookup on a ForeignKey
with its to_field
pointing to a CharField
or pointing to a CharField
defined with
primary_key=True
(#%s26983).migrate
command from raising
InconsistentMigrationHistory
in the presence of unapplied squashed
migrations (#%s27004).Client.force_login()
which required specifying a
backend
rather than automatically using the first one if multiple
backends are configured (#%s27027).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
(#%s27026).django.views.static.serve()
with show_indexes
enabled
(#%s26973).ClearableFileInput
to avoid the required
HTML attribute when
initial data exists (#%s27037).{% for %}
tag to unpack any iterable (#%s27058).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 (#%s27054, #%s27110, #%s27142).Model._meta.managers
(#%s27073).contrib.admindocs
crash when a view is in a class, such as some of
the admin views (#%s27018).field.many_to_many
back to
isinstance(field, models.ManyToManyField)
since it turned out the checks
weren’t suitable to be generalized like that (#%s26998).InconsistentMigrationHistory
message
raised by makemigrations
and migrate
(#%s27089).ContentType
and Permission
objects for models
of applications without migrations when calling the migrate
command with
no migrations to apply (#%s27044).Apps
instance
provided to the pre_migrate
signal receivers to allow ContentType
renaming to be performed on model rename (#%s27100).UserCreationForm
without USERNAME_FIELD
in
Meta.fields
(#%s27111).default
that
didn’t appear in POST data no longer used the default
(#%s27039).Sep 26, 2023