From 4ef9618e12510a84a4d21440b1e18ab704ee6d73 Mon Sep 17 00:00:00 2001 From: Collin Anderson Date: Thu, 9 Oct 2014 12:38:23 -0400 Subject: [PATCH] Avoided requiring sqlparse for a test. Refs #23426. Thanks Markus Holtermann for the suggestion. --- tests/migrations/test_operations.py | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/tests/migrations/test_operations.py b/tests/migrations/test_operations.py index 8fb708dc3d7..ad93513cc7f 100644 --- a/tests/migrations/test_operations.py +++ b/tests/migrations/test_operations.py @@ -1195,7 +1195,6 @@ class OperationTests(OperationTestBase): operation.database_backwards("test_runsql", editor, new_state, project_state) self.assertTableNotExists("i_love_ponies") - @unittest.skipIf(sqlparse is None and connection.features.requires_sqlparse_for_splitting, "Missing sqlparse") def test_run_sql_params(self): """ #23426 - RunSQL should accept parameters. @@ -1203,8 +1202,8 @@ class OperationTests(OperationTestBase): project_state = self.set_up_test_model("test_runsql") # Create the operation operation = migrations.RunSQL( - "CREATE TABLE i_love_ponies (id int, special_thing varchar(15));", - "DROP TABLE i_love_ponies", + ["CREATE TABLE i_love_ponies (id int, special_thing varchar(15));"], + ["DROP TABLE i_love_ponies"], ) param_operation = migrations.RunSQL( # forwards