-
Notifications
You must be signed in to change notification settings - Fork 395
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for loading tests from eggs #41
Comments
A workaround is to install a project using easy_install --always-unzip Or from source using python setup.py easy_install --always-unzip Google Code Info: |
See #150 for details on the current (broken) behavior with zipped eggs. nose fails to Google Code Info: |
This should be quite easy, in loadTestsFromNames you can use pkg_resources to return However, pkg_resources seems a bit braindead when getting the contents of packages Has anyone had any luck with discovering what is in the package from the In [96]: pkg_resources.resource_listdir('simplejson', 'tests') In [97]: pkg_resources.resource_listdir('simplejson', '') In [98]: pkg_resources.resource_listdir('simplejson', '') In [99]: pkg_resources.resource_listdir('simplejson', '/') Google Code Info: |
Nose 0.10.3 fails to find tests even in unzipped eggs for me (testing PyMC). I notice this issue has not been Google Code Info: |
This issue seems to have been around for at least a year and is still unresolved as far as I can tell... When you install an egg, setuptools explicitly changes the permissions of all *.py files to a+x (755), making This behaviour can be overridden with a command-line option to nosetests (--exe), which solves the problem For more history on the issue, see http://mail.python.org/pipermail/distutils-sig/2008-April/009396.html Regards, Google Code Info: |
Support for loading tests from eggs should be added, so that eg.:
nosetests some-distribution.egg
will work. This should done via a plugin.
Google Code Info:
Issue #: 78
Author: [email protected]
Created On: 2007-08-11T14:54:59.000Z
Closed On:
The text was updated successfully, but these errors were encountered: