From 497930b7f69e2c298faa3f784c4523ea351e5e6f Mon Sep 17 00:00:00 2001 From: Baptiste Mispelon Date: Tue, 29 Oct 2013 21:53:51 +0100 Subject: [PATCH] Use `callable` instead of `six.callable`. The `callable` builtin was added back in python 3.2 which is the minimal python3 version supported by django at this point. --- django/db/migrations/operations/special.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/django/db/migrations/operations/special.py b/django/db/migrations/operations/special.py index 83cdea308e..ef3f7169a5 100644 --- a/django/db/migrations/operations/special.py +++ b/django/db/migrations/operations/special.py @@ -137,7 +137,7 @@ class RunPython(Operation): # object, representing the versioned models as an AppCache. # We could try to override the global cache, but then people will still # use direct imports, so we go with a documentation approach instead. - if six.callable(self.code): + if callable(self.code): self.code(models=from_state.render(), schema_editor=schema_editor) else: context = { @@ -149,7 +149,7 @@ class RunPython(Operation): def database_backwards(self, app_label, schema_editor, from_state, to_state): if self.reverse_code is None: raise NotImplementedError("You cannot reverse this operation") - elif six.callable(self.reverse_code): + elif callable(self.reverse_code): self.reverse_code(models=from_state.render(), schema_editor=schema_editor) else: context = {