The first commit is 724a279849a5cd09cdb5ef201fe6958a4c26fe73 but the issue
is reopened after some concerns about the possibility of masking imports
on Python 2.
--
Ticket URL: <https://code.djangoproject.com/ticket/26484>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* has_patch: 0 => 1
Comment:
I [https://github.com/django/django/pull/6438 implemented Shai's
suggestion] to catch the original exception, then try `import django` and
display the helpful message if that fails or reraise the original
exception if not.
--
Ticket URL: <https://code.djangoproject.com/ticket/26484#comment:1>
* stage: Unreviewed => Accepted
--
Ticket URL: <https://code.djangoproject.com/ticket/26484#comment:2>
Comment (by timgraham):
In 724a279849a5cd09cdb5ef201fe6958a4c26fe73:
Raised a more helpful ImportError message in manage.py template.
--
Ticket URL: <https://code.djangoproject.com/ticket/26484#comment:3>
Comment (by Tim Graham <timograham@…>):
In [changeset:"5c6d397956f405f5c3fee6dc42568386972b9fc2" 5c6d397]:
{{{
#!CommitTicketReference repository=""
revision="5c6d397956f405f5c3fee6dc42568386972b9fc2"
Refs #26484 -- Avoided masking useful exceptions in manage.py's
ImportError.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26484#comment:4>
* status: new => closed
* resolution: => fixed
--
Ticket URL: <https://code.djangoproject.com/ticket/26484#comment:5>