I checked but now but no, every tests are running with each test running method.
But I think I understand. Python 2.7.2 (default, Oct 20 2011, 18:06:34) [GCC 4.5.2] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from pyramid import paster >>> import pyramid >>> pyramid.paster <zope.deprecation.deprecation.DeprecationProxy object at 0x1fa5c10> >>> So maybe the test discovery mechanism of setuptools does an import like this which enable the `pyramid.paster.get_app` not to crash in my functionnal test. And maybe nosetests does not....sounds likely ? Any way if someone could point me to a good explanation of the python import mechanism, because I don't understand why doing this: >>> from pyramid import paster before this >>> import pyramid lets you access to the `paster` module through the pyramid package: >>> pyramid.paster <zope.deprecation.deprecation.DeprecationProxy object at 0x1fa5c10> As far I understand this: >>> from pyramid import paster loads the paster module put it in your local namespace. I don't understand why invoking this command does not crash: >>> pyramid.paster Thanks. Le mercredi 27 juin 2012 14:31:33 UTC+2, Michael Merickel a écrit : > > On Wed, Jun 27, 2012 at 3:51 AM, Emmanuel Cazenave <[email protected]> > wrote: > > I understand that the paster module is not imported in the pyramid's > > __init__, so it's not visible. > > But why the hell does this work using `python setup.py test`: > > Most likely this works with `setup.py test` because you do not have > the `test_suite` option properly configured and thus the unittest > discovery mechanism is not finding your tests but nosetests does find > them with its more aggressive scanning, thus your tests aren't > actually running via `setup.py test`. > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To view this discussion on the web visit https://groups.google.com/d/msg/pylons-discuss/-/7EpEw7zJ0FsJ. 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/pylons-discuss?hl=en.
