From d7b9aaa366dd54ecc3142c588162e3adc7c2f7ac Mon Sep 17 00:00:00 2001 From: Claude Paroz Date: Sat, 19 Nov 2016 18:19:41 +0100 Subject: Refs #23919 -- Removed encoding preambles and future imports --- docs/ref/files/file.txt | 1 - docs/ref/migration-operations.txt | 3 --- 2 files changed, 4 deletions(-) (limited to 'docs/ref') diff --git a/docs/ref/files/file.txt b/docs/ref/files/file.txt index 6c218e38b3..4169b74b88 100644 --- a/docs/ref/files/file.txt +++ b/docs/ref/files/file.txt @@ -111,7 +111,6 @@ The ``ContentFile`` class but unlike :class:`~django.core.files.File` it operates on string content (bytes also supported), rather than an actual file. For example:: - from __future__ import unicode_literals from django.core.files.base import ContentFile f1 = ContentFile("esta sentencia está en español") diff --git a/docs/ref/migration-operations.txt b/docs/ref/migration-operations.txt index 7e5f4d4784..e6e6f73a99 100644 --- a/docs/ref/migration-operations.txt +++ b/docs/ref/migration-operations.txt @@ -310,9 +310,6 @@ class in the migration file, and just pass it to ``RunPython``. Here's an example of using ``RunPython`` to create some initial objects on a ``Country`` model:: - # -*- coding: utf-8 -*- - from __future__ import unicode_literals - from django.db import migrations, models def forwards_func(apps, schema_editor): -- cgit v1.3