test_email is supposed to run, whether from the build directory or from an installation. It does both on Windows today, so yours must be a platform-specific bug. > -----Original Message----- > From: python-dev-admin@python.org [mailto:python-dev-admin@python.org]On > Behalf Of Brett Cannon > Sent: Sunday, January 19, 2003 6:57 PM > To: python-dev@python.org > Subject: [Python-Dev] test_email always supposed to be skipped? > > > I just updated my copy of CVS, compiled, and installed and once again the > test_email testing suite was skipped because regrtest.py couldn't find > email.test when running it from my newly installed copy. Since the > Makefile does not list email/test as a subdirectory to install I assume > it is not supposed to be installed and all of this is on purpose. So why > even have test_email.py installed if it is always going to fail? If the > only way to run it is to use the executable compiled in your CVS > directory I don't see the point of having ``make install`` copy > test_email over. > Would it be reasonable to add a note to test_email.py that email.test is > not installed and so it being skipped is expected outside of the CVS > directory? Or add some code that will just pass the test if email.test > can't be imported? Or at least have it raise TestSkipped on its own and > have it output that this is expected if you are not running from a > copy of CVS? > > -Brett > > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > http://mail.python.org/mailman/listinfo/python-dev
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4