Changes by Michael Foord mich...@voidspace.org.uk:
--
resolution: - accepted
stage: needs patch - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8547
Michael Foord mich...@voidspace.org.uk added the comment:
Committed revision 80932. Still needs documenting, so leaving open for the
moment.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8547
Benjamin Peterson benja...@python.org added the comment:
Reverted this in r80939. See
http://python.org/dev/buildbot/stable/builders/x86%20XP-4%20trunk/builds/3553/steps/test/logs/stdio
--
nosy: +benjamin.peterson
___
Python tracker
Michael Foord mich...@voidspace.org.uk added the comment:
Committed again revision 80946 after getting the tests to pass on Windows.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8547
___
holger krekel holger.kre...@gmail.com added the comment:
FWIW checking if an imported module really comes from a certain location and
erroring out is also how py.test does it.
--
nosy: +hpk
___
Python tracker rep...@bugs.python.org
Michael Foord mich...@voidspace.org.uk added the comment:
Sounds like the right approach then. :-)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8547
___
New submission from Michael Foord mich...@voidspace.org.uk:
When test discovery is invoked on a package on the filesystem which is also
installed in site-packages then importing the tests will look in the installed
version. This causes discovery to run the wrong tests or fail.
We can detect
