Opened 11 years ago

Closed 10 years ago

#9947 closed (wontfix)

Add the current django folder to sys.path when you run tests with

Reported by: David Larlet Owned by: David Larlet
Component: Uncategorized Version: 1.0
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


Just because I felt very stupid when I report that tests are broken on #django-dev a few months (years?) ago: they were run against another installation of Django.

I don't know if it's worth the case but the fix is an oneliner.

Attachments (1)

patch_django_9947.20090102.diff (329 bytes) - added by David Larlet 11 years ago.
Patch against r9692

Download all attachments as: .zip

Change History (3)

Changed 11 years ago by David Larlet

Patch against r9692

comment:1 Changed 11 years ago by Karen Tracey

Hmm, I actually make use of the fact that things work as they do now. Download and apply a patch with tests and verify that the new tests fail as expected when run against old code in a different tree. Not that I haven't been bit by having my pythonpath set incorrectly at times...I'm just not sure I'd like it to always automatically use the code in the same tree as the tests.

comment:2 Changed 10 years ago by Jacob

Resolution: wontfix
Status: newclosed

Like Karen I take advantage of this to run new tests against old code. I think in this rare case the needs of us few maintainers has to override the needs of the many users.

Note: See TracTickets for help on using tickets.
Back to Top