#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: 0 | Easy pickings: 0
UI/UX: 0 |
--------------------------------------+-----------------------------------
Comment (by soren):
I was just told about ticket #9947, which refers to the same issue.
I'd like to attack this problem somehow. I'm not familiar with the bug
management rules here. If it's more appropriate to reopen the old one and
ditch this one, that's fine. Feel free to close this.
I can vaguely relate to the desire to run new tests against old code.
For those of you who actually make use of this, am I correct to assume
that this is less common than running new tests against new code? I mean,
it seems more natural to me that development of both "real" code and tests
happens in the code checkout, but I've been surprised before :)
Would everyone's needs be met if the default was to prepend the toplevel
dir to sys.path, but there was a simple way to disable this behaviour
(like setting an environment variable or something)?
--
Ticket URL: <https://code.djangoproject.com/ticket/16342#comment:3>
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.
