From b038abe1fe0c5abc2f503eb8e464087349766c1c Mon Sep 17 00:00:00 2001 From: Russell Keith-Magee Date: Fri, 11 Jul 2008 15:08:09 +0000 Subject: [PATCH] Fixed #7421 -- Corrected the condition used during syncdb to establish that a management module is or isn't available. This is to satisfy non-CPython implementations which can use different error messages. Thanks to Maciej Fijalkowski (fijal) for his help confirming the problem. git-svn-id: http://code.djangoproject.com/svn/django/trunk@7891 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- django/core/management/commands/syncdb.py | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/django/core/management/commands/syncdb.py b/django/core/management/commands/syncdb.py index 8e83ef61ebc..3792a312d75 100644 --- a/django/core/management/commands/syncdb.py +++ b/django/core/management/commands/syncdb.py @@ -41,10 +41,11 @@ class Command(NoArgsCommand): # but raises an ImportError for some reason. The only way we # can do this is to check the text of the exception. Note that # we're a bit broad in how we check the text, because different - # Python implementations may not use the same text. CPython - # uses the text "No module named management". + # Python implementations may not use the same text. + # CPython uses the text "No module named management" + # PyPy uses "No module named myproject.myapp.management" msg = exc.args[0] - if not msg.startswith('No module named management') or 'management' not in msg: + if not msg.startswith('No module named') or 'management' not in msg: raise cursor = connection.cursor()