Introduced an AbstractBaseSession model and hooks providing the option
of overriding the model class used by the session store and the session
store class used by the model.
When using a TransactionTestCase with serialized_rollback=True,
after creating the database and running its migrations (along with
emitting the post_migrate signal), the contents of the database
are serialized to _test_serialized_contents.
After the first test case, _fixture_teardown() would flush the
tables but then the post_migrate signal would be emitted and new
rows (with new PKs) would be created in the django_content_type
table. Then in any subsequent test cases in a suite,
_fixture_setup() attempts to deserialize the content of
_test_serialized_contents, but these rows are identical to the
rows already in the database except for their PKs. This causes an
IntegrityError due to the unique constraint in the
django_content_type table.
This change made it so that in the above scenario the post_migrate
signal is not emitted after flushing the tables, since it will be
repopulated during fixture_setup().
The new attribute is checked when the `migrate --fake-initial` option
is used. initial will be set to True for all initial migrations (this
is particularly useful when initial migrations are split) as well as
for squashed migrations.
Added the mixins LoginRequiredMixin, PermissionRequiredMixin and
UserPassesTestMixin to contrib.auth as counterparts to the respective
view decorators.
The authentication mixins UserPassesTestMixin, LoginRequiredMixin and
PermissionRequiredMixin have been inspired by django-braces
<https://github.com/brack3t/django-braces/>
Thanks Raphael Michel for the initial patch, tests and docs on the PR
and Ana Balica, Kenneth Love, Marc Tamlyn, and Tim Graham for the
review.
The website only renders code blocks at 96 chars, and therefore
long code lines get wrapped. Manually breaking the lines prevents
the wrapping from occurring.
make_bytes() assumed that if the Content-Encoding header is set, then
everything had already been dealt with bytes-wise, but in a streaming
situation this was not necessarily the case.
make_bytes() is only called when necessary when working with a
StreamingHttpResponse iterable, but by that point the middleware has
added the Content-Encoding header and thus make_bytes() tried to call
bytes(value) (and dies). If it had been a normal HttpResponse,
make_bytes() would have been called when the content was set, well
before the middleware set the Content-Encoding header.
This commit removes the special casing when Content-Encoding is set,
allowing unicode strings to be encoded during the iteration before they
are e.g. gzipped. This behaviour was added a long time ago for #4969 and
it doesn't appear to be necessary any more, as everything is correctly
made into bytes at the appropriate places.
Two new tests, to show that supplying non-ASCII characters to a
StreamingHttpResponse works fine normally, and when passed through the
GZip middleware (the latter dies without the change to make_bytes()).
Removes the test with a nonsense Content-Encoding and Unicode input - if
this were to happen, it can still be encoded as bytes fine.
Chris Lamb
Sergey Fedoseev
Yusuke Miyazaki
Jonas Haag
Mariusz Felisiak
John Moses
ramez
sujayskumar
Tyson Clugg
Sergey Kolosov
sarthakmeh
Maxime Lorant
Tommy Beadle
Valentina Mukhamedzhanova
Brendan Hayward
Kenneth Love
Andrei Kulakov
Rigel Di Scala
Jan Pazdziora
William Schwartz
Francisco Albarran
Nick Pope
Markus Holtermann
JensDiemer
Sutrisno Efendi
girishkumarkh
Markus Amalthea Magnuson
Matthew Somerville
Adam Chainz
Riccardo Magliocchetti
Piotr Jakimiak
Nicolas Noé
Jon Dufresne
Jay Wineinger
Marten Kenbeek
Ryan Hall
Andriy Sokolovskiy
Moritz Sichert
Aymeric Augustin
Loek van Gent
ifedapo olarewaju
Aksel Ethem
Grzegorz Slusarek
Ian Lee
Justine Alexandra Roberts Tunney
Jakub Wilk
Michał Modzelewski
Oscar Ramirez
Andriy Sokolovskiy