#16342: Django unittests run against installed django by default (rather than
the
checkout)
--------------------------------------+-----------------------------------
Reporter: soren | Owner: nobody
Type: Bug | Status: new
Milestone: | Component: Testing framework
Version: 1.3 | Severity: Normal
Resolution: | Keywords:
Triage Stage: Unreviewed | Has patch: 1
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 1 | Easy pickings: 0
UI/UX: 0 |
--------------------------------------+-----------------------------------
Comment (by PaulM):
I agree that this turns off new developers, but it's an absolute non-issue
for the more experienced devs. To the best of my knowledge, everyone who
does much work on the codebase uses virtualenv to isolate their
environment. This means that there isn't a system install of Django at
all, and there's absolutely no chance that there is more than one valid
"django" to import.
We should really be teaching new users to use virtualenv at the end of the
tutorial. If we can't get it there, we should at least include it in the
documentation on writing tests or working on Django.
Mucking around with the path in the test suite is likely to be a
nonstarter. It's much better to let Python do the imports as expected, and
require users to modify the environment themselves where necessary.
--
Ticket URL: <https://code.djangoproject.com/ticket/16342#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
