Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Fixed broken links + spell check in 1.5 release notes.

  • Loading branch information...
commit 48be78cf088e6fca87d1e4da7c527e17305f9fe2 1 parent 1d6b7f3
@timgraham timgraham authored
Showing with 14 additions and 14 deletions.
  1. +14 −14 docs/releases/1.5.txt
View
28 docs/releases/1.5.txt
@@ -26,7 +26,7 @@ yourself. This could be a simple extension to the existing ``User`` model -- for
example, you could add a Twitter or Facebook ID field -- or you could completely
replace the ``User`` with one totally customized for your site.
-Django 1.5 is also the first release with `Python 3 support`_! We're labling
+Django 1.5 is also the first release with `Python 3 support`_! We're labeling
this support "experimental" because we don't yet consider it production-ready,
but everything's in place for you to start porting your apps to Python 3.
Our next release, Django 1.6, will support Python 3 without reservations.
@@ -36,8 +36,8 @@ Other notable new features in Django 1.5 include:
* `Support for saving a subset of model's fields`_ -
:meth:`Model.save() <django.db.models.Model.save()>` now accepts an
``update_fields`` argument, letting you specify which fields are
- written back to the databse when you call ``save()``. This can help
- in high-concurrancy operations, and can improve performance.
+ written back to the database when you call ``save()``. This can help
+ in high-concurrency operations, and can improve performance.
* Better `support for streaming responses <#explicit-streaming-responses>`_ via
the new :class:`~django.http.StreamingHttpResponse` response class.
@@ -92,17 +92,17 @@ you can write application targeted for just Python 2, just Python 3, or single
applications that support both platforms.
However, we're labeling this support "experimental" for now: although it's
-receved extensive testing via our automated test suite, it's recieved very
+received extensive testing via our automated test suite, it's received very
little real-world testing. We've done our best to eliminate bugs, but we can't
be sure we covered all possible uses of Django. Further, Django's more than a
web framework; it's an ecosystem of pluggable components. At this point, very
-few third-party applications have been ported to Python 3, so it's unliukely
-that a real-world application will have all its dependecies satisfied under
+few third-party applications have been ported to Python 3, so it's unlikely
+that a real-world application will have all its dependencies satisfied under
Python 3.
Thus, we're recommending that Django 1.5 not be used in production under Python
-3. Instead, use this oportunity to begin :doc:`porting applications to Python 3
-<topics/python>`. If you're an author of a pluggable component, we encourage you
+3. Instead, use this opportunity to begin :doc:`porting applications to Python 3
+</topics/python3>`. If you're an author of a pluggable component, we encourage you
to start porting now.
We plan to offer first-class, production-ready support for Python 3 in our next
@@ -194,7 +194,7 @@ Retrieval of ``ContentType`` instances associated with proxy models
The methods :meth:`ContentTypeManager.get_for_model() <django.contrib.contenttypes.models.ContentTypeManager.get_for_model()>`
and :meth:`ContentTypeManager.get_for_models() <django.contrib.contenttypes.models.ContentTypeManager.get_for_models()>`
have a new keyword argument – respectively ``for_concrete_model`` and ``for_concrete_models``.
-By passing ``False`` using this argument it is now possible to retreive the
+By passing ``False`` using this argument it is now possible to retrieve the
:class:`ContentType <django.contrib.contenttypes.models.ContentType>`
associated with proxy models.
@@ -484,8 +484,8 @@ In order to be able to run unit tests in any order and to make sure they are
always isolated from each other, :class:`~django.test.TransactionTestCase` will
now reset the database *after* each test run instead.
-No more implict DB sequences reset
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+No more implicit DB sequences reset
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
:class:`~django.test.TransactionTestCase` tests used to reset primary key
sequences automatically together with the database flushing actions described
@@ -543,7 +543,7 @@ Miscellaneous
available at :func:`django.utils.html.remove_tags`.
* Uploaded files are no longer created as executable by default. If you need
- them to be executeable change :setting:`FILE_UPLOAD_PERMISSIONS` to your
+ them to be executable change :setting:`FILE_UPLOAD_PERMISSIONS` to your
needs. The new default value is `0666` (octal) and the current umask value
is first masked out.
@@ -580,8 +580,8 @@ Streaming behavior of :class:`HttpResponse`
Django 1.5 deprecates the ability to stream a response by passing an iterator
to :class:`~django.http.HttpResponse`. If you rely on this behavior, switch to
-:class:`~django.http.StreamingHttpResponse`. See :ref:`explicit-streaming-
-responses` above.
+:class:`~django.http.StreamingHttpResponse`. See
+:ref:`explicit-streaming-responses` above.
In Django 1.7 and above, the iterator will be consumed immediately by
:class:`~django.http.HttpResponse`.
Please sign in to comment.
Something went wrong with that request. Please try again.