---
title: "Informacje o wydaniu Django 1.10.1"
version: 5.1
locale: pl
source: https://docs.djangoproject.com/pl/5.1/releases/1.10.1/
canonical: https://djangodocs.dev/pl/5.1/releases/1.10.1/
---
# Informacje o wydaniu Django 1.10.1

*1 września 2016*

Django 1.10.1 zawiera poprawki błędów z wersji 1.10.

## Poprawki błędów

- Naprawiony crash w połączeniach MySQL, gdzie `SELECT @@SQL_AUTO_IS_NULL` nie zwraca wyniku ([#26991](https://code.djangoproject.com/ticket/26991)).
- Własności `User.is_authenticated` i `User.is_anonymous` mogą być porównywane przy użyciu `==`, `!=` i `|` ([#26988](https://code.djangoproject.com/ticket/26988), [#27154](https://code.djangoproject.com/ticket/27154)).
- Removed the broken `BaseCommand.usage()` method which was for
  `optparse` support ([#27000](https://code.djangoproject.com/ticket/27000)).
- Fixed a checks framework crash with an empty `Meta.default_permissions`
  ([#26997](https://code.djangoproject.com/ticket/26997)).
- Fixed a regression in the number of queries when using `RadioSelect` with a
  `ModelChoiceField` form field ([#27001](https://code.djangoproject.com/ticket/27001)).
- Fixed a crash if `request.META['CONTENT_LENGTH']` is an empty string
  ([#27005](https://code.djangoproject.com/ticket/27005)).
- Fixed the `isnull` lookup on a `ForeignKey` with its `to_field`
  pointing to a `CharField` or pointing to a `CharField` defined with
  `primary_key=True` ([#26983](https://code.djangoproject.com/ticket/26983)).
- Prevented the `migrate` command from raising
  `InconsistentMigrationHistory` in the presence of unapplied squashed
  migrations ([#27004](https://code.djangoproject.com/ticket/27004)).
- Fixed a regression in `Client.force_login()` which required specifying a
  `backend` rather than automatically using the first one if multiple
  backends are configured ([#27027](https://code.djangoproject.com/ticket/27027)).
- Made `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](https://code.djangoproject.com/ticket/27026)).
- Fixed crash of `django.views.static.serve()` with `show_indexes` enabled
  ([#26973](https://code.djangoproject.com/ticket/26973)).
- Fixed `ClearableFileInput` to avoid the `required` HTML attribute when
  initial data exists ([#27037](https://code.djangoproject.com/ticket/27037)).
- Fixed annotations with database functions when combined with lookups on
  PostGIS ([#27014](https://code.djangoproject.com/ticket/27014)).
- Reallowed the `{% for %}` tag to unpack any iterable ([#27058](https://code.djangoproject.com/ticket/27058)).
- Made `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](https://code.djangoproject.com/ticket/27054), [#27110](https://code.djangoproject.com/ticket/27110), [#27142](https://code.djangoproject.com/ticket/27142)).
- Removed duplicated managers in `Model._meta.managers` ([#27073](https://code.djangoproject.com/ticket/27073)).
- Fixed `contrib.admindocs` crash when a view is in a class, such as some of
  the admin views ([#27018](https://code.djangoproject.com/ticket/27018)).
- Reverted a few admin checks that checked `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](https://code.djangoproject.com/ticket/26998)).
- Added the database alias to the `InconsistentMigrationHistory` message
  raised by `makemigrations` and `migrate` ([#27089](https://code.djangoproject.com/ticket/27089)).
- Naprawiono tworzenie obiektów `ContentType` i ```Permission``dla modeli aplikacji bez migracji podczas wywołania komendy ``migrate``` bez migracji do zastosowania ([#27044](https://code.djangoproject.com/ticket/27044)).
- Dołączono już zastosowane zmiany stanu migracji w instancji `Apps` dostarczonej do odbiorników sygnału `pre_migrate`, aby umożliwić zmianę nazwy `ContentType` w czasie zmiany nazwy modelu ([#27100](https://code.djangoproject.com/ticket/27100)).
- Ponownie pozwolono na dziedziczenie `UserCreationForm` bez `USERNAME_FIELD` w `Meta.fields` ([#27111](https://code.djangoproject.com/ticket/27111)).
- Naprawiona regresja w model forms, gdzie pola modelu z `default`, które nie pojawiały się w danych POST, przestawały używać `default` ([#27039](https://code.djangoproject.com/ticket/27039)).