diff options
| author | Tim Graham <timograham@gmail.com> | 2017-01-18 11:51:29 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-01-18 11:51:29 -0500 |
| commit | f6acd1d271122d66de8061e75ae26137ddf02658 (patch) | |
| tree | 26392839b0cf03b48696240d7ce6d835ec1011dc /docs/faq | |
| parent | c716fe87821df00f9f03ecc761c914d1682591a2 (diff) | |
Refs #23919 -- Removed Python 2 notes in docs.
Diffstat (limited to 'docs/faq')
| -rw-r--r-- | docs/faq/install.txt | 13 | ||||
| -rw-r--r-- | docs/faq/troubleshooting.txt | 9 |
2 files changed, 3 insertions, 19 deletions
diff --git a/docs/faq/install.txt b/docs/faq/install.txt index ea27b11db8..622334348e 100644 --- a/docs/faq/install.txt +++ b/docs/faq/install.txt @@ -65,18 +65,11 @@ is the last version to support Python 3.3. What Python version should I use with Django? ============================================= -As of Django 1.6, Python 3 support is considered stable and you can safely use -it in production. See also :doc:`/topics/python3`. However, the community is -still in the process of migrating third-party packages and applications to -Python 3. - -If you're starting a new project, and the dependencies you plan to use work on -Python 3, you should use Python 3. If they don't, consider contributing to the -porting efforts, or stick to Python 2. +Python 3 is recommended. Django 1.11 is the last version to support Python 2.7. +Support for Python 2.7 and Django 1.11 ends in 2020. Since newer versions of Python are often faster, have more features, and are -better supported, all else being equal, we recommend that you use the latest -2.x.y or 3.x.y release. +better supported, the latest version of Python 3 is recommended. You don't lose anything in Django by using an older release, but you don't take advantage of the improvements and optimizations in newer Python releases. diff --git a/docs/faq/troubleshooting.txt b/docs/faq/troubleshooting.txt index 1b2efd552f..5a56c6daa3 100644 --- a/docs/faq/troubleshooting.txt +++ b/docs/faq/troubleshooting.txt @@ -55,15 +55,6 @@ pitfalls producing this error: case, please refer to your system documentation to learn how you can change this to a UTF-8 locale. -* You created raw bytestrings, which is easy to do on Python 2:: - - my_string = 'café' - - Either use the ``u''`` prefix or even better, add the - ``from __future__ import unicode_literals`` line at the top of your file - so that your code will be compatible with Python 3.2 which doesn't support - the ``u''`` prefix. - Related resources: * :doc:`Unicode in Django </ref/unicode>` |